Hitachi Command Suite. Command Director. User Guide MK-90HCMD001-13

Transcription

1 Hitachi Command Suite Command Director User Guide MK-90HCMD001-13

2 2014 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users. Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries. Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems. AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/os, z9, z10, zseries, z/vm, and z/vse are registered trademarks or trademarks of International Business Machines Corporation. ipad is a trademark of Apple Inc., registered in the U.S. and other countries. All other trademarks, service marks, and company names in this document or web site are properties of their respective owners. Microsoft product screen shots are reprinted with permission from Microsoft Corporation. Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products. 2

3 Contents Preface Intended audience Product version...12 Release notes Document revision level...12 Referenced documents Document conventions Conventions for storage capacity values...14 Accessing product documentation Getting help...15 Comments Overview...17 About Hitachi Command Director...18 Features...18 What's new in Hitachi Command Director...20 Setup workflow...20 Logging in Registering a license...24 Specifying an address when you first log in Modifying your user profile...27 Hitachi Command Director graphical user interface Navigating the Help system...28 Logging out Using dashboards to quickly access vital system reports About the Hitachi Command Director dashboards Dashboard access and controls Overview of dashboard access and controls...33 Specifying dashboard reports from the Settings dialog...34 Setting a default dashboard...35 Resizing the dashboard layout

4 Exporting and downloading a dashboard to PDF Global and DataCenter dashboards default reports Total number of applications with SLO misses Response Time SLO Status report IOPS SLO Status report...38 DTR SLO Status report Application SLO Details report...40 Applications with Most SLO Misses in the Last 24 hours report Storage System Capacity Overview report...43 VMware Datastore Overview report...43 Hyper-V Filesystem Overview report...44 Pool Capacity Overview report Top 5 Busiest HNAS Nodes report HNAS Capacity Overview report HNAS Cluster Overview report Storage System Health Status report...49 Storage System Health Detail report...50 Storage System Performance Overview report...52 Planning dashboard default reports Pools dashboard default reports Top 20 Pool Utilization by Capacity report Storage Pool Health Status report Storage Pool Health Detail report Hosts dashboard default reports...57 Host Capacity Utilization Status report...57 Host Capacity Utilization Detail report Managing resources About business views Using business views...63 Displaying business views...64 Custom business view...65 Logical Group view Hosts view File Servers view...69 Storage Systems view All Applications view Applications by pool view Applications by capacity view...75 Creating a new business view Business view modification restrictions...79 Managing business views...79 Deleting business views Monitoring applications SLO overview...82 Application SLO types Understanding SLO profile recommendations...84 Managing application SLO profiles About application SLO profiles

5 Viewing application SLO profiles...86 Creating application SLO profiles...88 Editing application SLO Profiles...90 Deleting application SLO profiles...91 Accepting SLO profile recommendations Updating SLO profiles for volumes...93 Updating SLO profiles for application volumes Updating SLO profiles for pool volumes...99 Global SLO settings SLO Investigation Unit About SLO Investigation Unit Accessing the SLO Investigation Unit from the Dashboard Accessing the SLO Investigation Unit from the Resources tab Monitoring infrastructure Monitoring storage systems Storage system health thresholds Managing storage system monitoring profiles Viewing storage system monitoring profiles Creating a storage system monitoring profile Modifying a storage system monitoring profile Deleting a storage system monitoring profile Data metrics in storage system monitoring profiles Assigning monitoring profiles to storage systems Storage system monitoring settings Monitoring hosts Managing host monitoring profiles Assigning monitoring profiles to hosts Host monitoring settings Working with applications About applications Application elements Configuring applications Application creation process flow Application notes Creating applications manually Managing untagged applications Modifying applications Modifying a single application Modifying multiple applications Deleting applications Reporting on applications Application reports Accessing application reports for a selected application Accessing application reports at the folder level in a business view Application Summary report SLO Status report

6 Storage System Performance report Storage Allocation report Filesystem Utilization report SLO Profile Details report Storage Allocation Trend Storage allocation forecast trend report Specifying criteria for the storage allocation forecast trend report Application Response Time Trend report IO Utilization Trend report Storage allocation information Storage Allocation Details report Pool Utilization report Storage Path report Tier Definition report Replication Details report Total number of applications in a folder Response Time SLO Status report IOPS SLO Status report Application List report Application Capacity Comparison Trend report Specifying criteria for Application Capacity Comparison Trend report DTR SLO Status report Pool Tier Utilization Trend report Pool Tier Utilization Forecast Trend report Specifying criteria for the pool tier utilization forecast trend report Reporting on hosts Host reports Available summary host reports Summary host reports Accessing summary host reports Storage Utilization report Volume Manager Group report Available HNAS host reports HNAS host reports Accessing HNAS host reports Filesystem IO Trend report Filesystem Load Trend report HNAS Filesystem report HNAS Pool Summary report HNAS Pool Details report HNAS Shares report Protocol Op/s Trend report Total Throughput Trend report Filesystem Utilization Trend report Filesystem Utilization Forecast Trend report Hyper-V Server report Accessing the Hyper-V server report Hyper-V server report VMware host reports Accessing VMware host reports

7 VMware Datastores report ESX Server VMDKs report Volumes Mapped to ESX Server VMs report Reporting on storage systems Storage system reports Accessing storage system reports for all storage systems Accessing storage system reports for a given type of system Accessing storage system reports for a specific system Storage System Performance Overview report Storage System Capacity Overview report Pool Capacity Overview report Applications with Most SLO Misses (last 24 hours) report Performance Overview by Storage System report Storage System Capacity Trend report Specifying criteria for Storage System Capacity Trend report Storage system capacity forecast trend report Specifying criteria for the storage system capacity forecast trend report Pool Capacity Trend report Specifying criteria for Pool Capacity Trend report Pool Capacity Forecast Trend report Specifying criteria for the Pool Capacity Forecast Trend report Pool Utilization report Application Capacity Utilization report Application Capacity by Storage Class report Specifying criteria for Application Capacity by Storage Class report Application Capacity Consumption by Storage System report Application Capacity Consumption Trend by Storage System for Application report Using reports Features available in the report viewer About report viewer pagination controls Refreshing the report view Sorting a report Scheduling a report Exporting and downloading graphical reports in PDF Exporting and downloading a tabular report in Excel or XML Customizing tabular reports Saving a report Pinning reports to a selected dashboard Report gallery About the report gallery Utilization report gallery Physical Capacity by Storage System report Pool Detailed Capacity Trend report Pool Capacity by Storage System report Pool detailed capacity trend for storage system pool Pool detailed capacity forecast trend

8 Pool Usage by Application report Performance report gallery Storage Port Workload report Pool Storage Performance report Parity group utilization for pool Top 20 Busiest Storage System Ports report Specifying criteria for Top 20 Busiest Storage System Ports report Top 20 Busiest Parity Groups report Top 20 Most or Least Busy Volumes report Specifying criteria for Top 20 Most or Least Busy Volumes report Underutilized Volumes report Specifying criteria for Underutilized Volumes report Application SLO Conformance report Application SLO Conformance Details report Specifying criteria for Application SLO Conformance Details report Application volume SLO conformance details (CSV only) Storage economics report gallery Top 10 Tiers by Capacity report Underutilized Host Filesystems report Replication Capacity Distribution by Tier report Asset and Inventory report gallery Storage System Inventory report Filesystem Inventory report Physical Server Inventory report Storage Port Details report Capacity by Storage Class report Chargeback report gallery Application Storage Allocation by Tier report Application Storage Allocation by Pool report Storage Allocation by VMware VMs report Accessing reports Accessing reports from the report gallery Accessing reports from the Resources tab Administering Hitachi Command Director Administration tasks overview Managing licenses Hitachi Command Director licenses License types Updating license information Configuring Storage System Collectors About storage system data collection Viewing information about Storage System Collectors Prerequisites for configuring Storage System Collectors Configuring Storage System Collectors Modifying Storage System Collectors Deleting Storage System Collectors Viewing storage system data collection history Viewing details about a specific Storage System Collector Modifying how often data is refreshed Manually refreshing data

9 Enabling and disabling Storage System Collectors Enabling and disabling storage systems Configuring Host Collectors Host discovery and agentless data gathering mechanism Host access requirements Viewing Host Collector information Enabling host discovery and data collection Prerequisites for host discovery on other subnets Configuring a new Host Collector Configuring a new vcenter Collector Launching Host Collector to discover hosts Discovering hosts on the current subnet Discovering hosts by specifying a range of host IP addresses Discovering hosts by specifying a list of host IP addresses Modifying Host Collector Refreshing Host Collector data Deleting Host Collectors Viewing information about discovered hosts Viewing information about discovered ESX hosts Viewing information about discovered HNAS hosts Validating host connectivity Specifying host login settings Modifying host login settings for specific hosts Specifying data collection refresh frequency Deleting hosts Organizing resources by tagging Managing custom tags and tag categories Managing scheduled reports Stopping scheduled reports Configuring servers Configuring LUN Owner settings About LUN Owner configuration LUN Owner creation scenarios Impact of LUN Owner configuration changes on applications Excluding volumes from LUN Owner Including volumes in LUN Owner List of applications affected by LUN Owner volumes Specifying how applications are automatically created Creating applications automatically Impact of switching to a different auto-create option Managing Hitachi Command Director users About user management Viewing user information Deleting users A Using Host Collector in a secure environment Host Collector in a secure environment Data gathered with and without root access Ports and services used Ping (Initial discovery)

10 SNMP Telnet Connection Protocols Protocols for UNIX systems Protocols for Microsoft Windows systems Common services that must be enabled Services on Windows hosts Service on UNIX hosts Network impact Performance impact B Setting up configuration gathering operation using sudo Configuration gathering operation using sudo Binary used for configuration gathering operation Commands used by Gather binary Requirements for account used for configuration gathering operation Sample content of sudoers file Glossary Index

11 Preface This manual provides information about Hitachi Command Director (HCmD). Intended audience Product version Release notes Document revision level Referenced documents Document conventions Conventions for storage capacity values Accessing product documentation Getting help Comments Preface 11

12 Intended audience This document is intended for users of the Hitachi Command Director. You should have a working knowledge of the following: Hitachi Device Manager, Hitachi Tuning Manager, and Tiered Storage Manager Storage system and performance concepts Service Level Objectives (SLOs) and Service Level Agreements (SLAs) The use of Hitachi Command Director and all Hitachi Data Systems products is governed by the terms of your agreements with Hitachi Data Systems. Product version This document revision applies to Hitachi Command Director v8.0.1 or later. Release notes Read the release notes before installing and using this product. They may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document. Release notes can be found on the documentation CD or on the Hitachi Data Systems Support Portal: Document revision level Revision Date Description MK-90HCMD November 2010 Initial release MK-90HCMD December 2010 Revision 1, supersedes and replaces MK-90HCMD MK-90HCMD May 2011 Revision 2, supersedes and replaces MK-90HCMD MK-90HCMD August 2011 Revision 3, supersedes and replaces MK-90HCMD MK-90HCMD November 2011 Revision 4, supersedes and replaces MK-90HCMD MK-90HCMD March 2012 Revision 5, supersedes and replaces MK-90HCMD MK-90HCMD July 2012 Revision 6, supersedes and replaces MK-90HCMD Preface

13 Revision Date Description MK-90HCMD August 2012 Revision 7, supersedes and replaces MK-90HCMD MK-90HCMD November 2012 Revision 8, supersedes and replaces MK-90HCMD MK-90HCMD February 2013 Revision 9, supersedes and replaces MK-90HCMD MK-90HCMD May 2013 Revision 10, supersedes and replaces MK-90HCMD MK-90HCMD October 2013 Revision 11, supersedes and replaces MK-90HCMD MK-90HCMD April 2014 Revision 12, supersedes and replaces MK-90HCMD MK-90HCMD August 2014 Revision 12, supersedes and replaces MK-90HCMD Referenced documents The following Hitachi referenced documents are available for download from the Hitachi Data Systems Support Portal: Hitachi Command Director Installation and Configuration guide, MK-90HCMD002 Hitachi Command Director Release Notes, RN-90HCMD003 Hitachi Command Director CLI Reference Guide, MK-90HCMD004 Hitachi Command Director API Reference Guide, MK-90HCMD005 Hitachi Command Suite System Requirements, MK-92HC209 Hitachi Command Suite documentation Hitachi Command Suite Tuning Manager documentation Hitachi Command Suite Tiered Storage Manager documentation Document conventions This document uses the following typographic conventions: Convention Bold Italic Monospace Description Indicates text on a window, other than the window title, including menus, menu options, buttons, fields, and labels. Example: Click OK. Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: copy source-file target-file Note: Angled brackets (< >) are also used to indicate variables. Indicates text that is displayed on screen or entered by the user. Example: pairdisplay -g oradb Preface 13

14 Convention Description < > angled brackets Indicates a variable, which is a placeholder for actual text provided by the user or system. Example: pairdisplay -g <group> Note: Italic font is also used to indicate variables. [ ] square brackets Indicates optional values. Example: [ a b ] indicates that you can choose a, b, or nothing. { } braces Indicates required or expected values. Example: { a b } indicates that you must choose either a or b. vertical bar Indicates that you have a choice between two or more options or arguments. Examples: [ a b ] indicates that you can choose a, b, or nothing. { a b } indicates that you must choose either a or b. This document uses the following icons to draw attention to information: Icon Label Description Note Calls attention to important or additional information. Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Caution Warns the user of adverse conditions or consequences (for example, disruptive operations). WARNING Warns the user of severe conditions or consequences (for example, destructive operations). Conventions for storage capacity values Physical storage capacity values (for example, disk drive capacity) are calculated based on the following values: Physical capacity unit Value 1 kilobyte (KB) 1,000 (10 3 ) bytes 1 megabyte (MB) 1,000 KB or 1,000 2 bytes 1 gigabyte (GB) 1,000 MB or 1,000 3 bytes 1 terabyte (TB) 1,000 GB or 1,000 4 bytes 1 petabyte (PB) 1,000 TB or 1,000 5 bytes 1 exabyte (EB) 1,000 PB or 1,000 6 bytes Logical storage capacity values (for example, logical device capacity) are calculated based on the following values: 14 Preface

15 Logical capacity unit Value 1 block 512 bytes 1 KB 1,024 (2 10 ) bytes 1 MB 1,024 KB or 1,024 2 bytes 1 GB 1,024 MB or 1,024 3 bytes 1 TB 1,024 GB or 1,024 4 bytes 1 PB 1,024 TB or 1,024 5 bytes 1 EB 1,024 PB or 1,024 6 bytes Accessing product documentation Product user documentation is available on the Hitachi Data Systems Portal: Check this site for the most current documentation, including important updates that may have been made after the release of the product. Getting help Hitachi Data Systems Support Portal is the destination for technical support of your current or previously-sold storage systems, midrange and enterprise servers, and combined solution offerings. The Hitachi Data Systems customer support staff is available 24 hours a day, seven days a week. If you need technical support, log on to the Hitachi Data Systems Support Portal for contact information: Hitachi Data Systems Community is a new global online community for HDS customers, partners, independent software vendors, employees, and prospects. It is an open discussion among these groups about the HDS portfolio of products and services. It is the destination to get answers, discover insights, and make connections. The HDS Community complements our existing Support Portal and support services by providing an area where you can get answers to non-critical issues and questions. Join the conversation today! Go to community.hds.com, register, and complete your profile. Comments Please send us your comments on this document to [email protected]. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation. Preface 15

16 Thank you! 16 Preface

17 1 Overview This module describes how to start using Hitachi Command Director. About Hitachi Command Director Features What's new in Hitachi Command Director Setup workflow Logging in Registering a license Specifying an address when you first log in Modifying your user profile Hitachi Command Director graphical user interface Navigating the Help system Logging out Overview 17

18 About Hitachi Command Director Hitachi Command Director (HCmD) centralizes storage management reporting across the Hitachi Command Suite by providing business application views of Hitachi storage infrastructures. Hitachi Command Director also provides a way to easily align Hitachi storage assets with the applications and business functions that rely on them. By monitoring key performance indicators from various Hitachi Storage Suite products, Hitachi Command Director enables consolidated storage reporting by applications, business units, and storage tiers. Application specified storage service level objectives based on storage capacity and performance requirements can be established and proactively monitored to ensure that service levels are being met. Hitachi Command Director correlates storage system configuration data from Hitachi Device Manager (HDvM), performance data from the Agent for RAID instances, storage tier data from Tiered Storage Manager (HTSM), and storage utilization data from the hosts (that is, your application hosts). Host Collector discovers hosts on your network and gathers their file system and storage utilization information, providing end-to-end mapping of the path from the host to the storage system volumes. Thus, Hitachi Command Director provides a single point of access for the following tasks: Monitoring application storage. Define corporate-wide standard Service Level Objectives (SLOs) for all your applications and issue proactive alerts when application SLOs are at risk. Monitoring Hitachi enterprise storage health. You can detect potential storage system performance problems. You can also outsource the function of keeping your storage systems running optimally and finding root causes of problems if they arise. Generating Key Performance Indicator reports that align your storage allocation, performance, and trend data with your business organization. Related concepts Features on page 18 Setup workflow on page 20 Features Hitachi Command Director includes these key features: A global dashboard that provides you access to real-time enterprise storage information that enables you to monitor the overall health of your storage resources. 18 Overview

19 When you first logon to Hitachi Command Director, you see the dashboard. The dashboard provides a quick overview of the health of your storage environment. It enables you to quickly identify potential problem areas that need further investigation. The application SLO Investigation Unit that lets storage administrators quickly identify potential cause of application SLO miss and SLO violation. When you view an SLO miss for a specific application on the global dashboard, you can use the SLO Investigation Unit to drill-down into the specific application details, understand the various factors that resulted in SLO miss, and apply your best practices for managing the miss and take pre-emptive actions before an SLO violation occurs. A report gallery that provides fast and simple access to performance and capacity utilization reports of your storage systems and servers. It provides the ability to create your own fully-customized reports by simply choosing columns and sort criteria and save these reports for future reference or reuse. The gallery includes these predefined reports: Asset and Inventory reports that provide quick inventory of your data center assets such as storage systems and servers. Storage economics reports that analyze your capacity and application data utilization with respective to Hitachi storage tiers. Storage utilization reports for waste and reclaim identification or chargeback support. Chargeback reports that provide insight into your capacity consumption and allocation at an application or host per tier or per pool level. This is useful when calculating charge back storage consumption with respect to application or host owners. Storage performance reports that quickly identify busiest storage resources across the data center. Application tagging that provides the flexibility to map storage and application to your business structure. An option to create applications automatically from the LUN Owner information, logical groups, or hosts discovered in your environment. Once set, this option enables automatic creation of applications when HCmD Host Collector performs agentless data gather from remote hosts and storage systems at specific intervals or on demand. Related concepts About Hitachi Command Director on page 18 What's new in Hitachi Command Director on page 20 Setup workflow on page 20 Overview 19

20 What's new in Hitachi Command Director Hitachi Command Director includes the following new or enhanced functionality: Support for installation of HCmD server and HCmD Host Collector on Red Hat Enterprise Linux v6.4 and v6.5. Separate user roles for Admin and View users enable you allow to users limited access, including viewing reports and business views, and customizing dashboards. Users with the View role are not able to perform administrative tasks. Support for HNAS v11.3. Support for VMware ESXi 5.5. Enhanced reporting of the mapping of ESX (VMDK) to VM to LUNs with the Volumes Mapped to ESX Server VMs report. Reporting support for global-active device (GAD). Support for HNAS internal SMU setup. Setup workflow After installing Hitachi Command Director software, you must perform some initial setup tasks to configure the system. The following table summarizes the initial setup workflow. Users with the View role cannot perform setup, except that they must specify an address when they first log in. Setup task Description Section reference Log on to HCmD Web UI Set up server and notification Add Storage System Collectors Add Host Collectors Initial logon to HCmD Web UI. This procedure also includes: Registering the license key Specifying your address Set up the SMTP server to send notifications automatically for Service Level Objective (SLO) alerts and scheduled reports. Set up to receive notifications. Configure storage system data collection to enable HCmD to collect configuration data from Hitachi Device Manager and storage system performance data from Agent for RAID, and collect configuration data from supported third party storage systems. Add/configure Host Collectors to discover hosts in your network and gather their file system and storage utilization information. Logging in on page 23 Registering a license on page 24 Specifying an address when you first log in on page 26 Configuring servers on page 355 Specifying an address when you first log in on page 26 Configuring Storage System Collectors on page 319 Host discovery and agentless data 20 Overview

21 Setup task Description Section reference gathering mechanism on page 330 Set the option to create applications automatically or create new applications manually. Perform manual refresh to gather storage system or host data (optional) Create custom categories/tags (optional) Create new SLO profiles or modify the default SLO profile (optional) Manage unassigned applications Create custom business views if the preconfigured business views does not suit your requirements. Or, use preconfigured business views that HCmD provides. Applications for the Device Manager Logical Groups are created automatically by default after installation. You can change the default configuration and set to create applications automatically from LUN Owners or hosts configured in your environment. You can also choose to create new applications manually in a custom business view. Manual refresh gathers data before the next scheduled collection and updates reports with the latest information. Hitachi Command Director (HCmD) comes with predefined set of tags and tag categories you can use to create a custom business view that matches your organization structure. If these predefined tags or tag categories do not apply to your business structure, you can create custom categories and tags to organize your resources according to your business structure. HCmD provides a default SLO profile that includes the Average Storage Response Time SLO type. You can create new SLO profiles using the supported SLO types and assign them to applications, or modify the default SLO profile. Unassigned applications are created automatically during the discovery of storage systems or hosts by HCmD. Unassigned applications are also those when you fail to assign them to custom tags. To monitor these applications, you must assign these applications to a relevant tag in your business view. Create a custom business view that represents the organization of resources in your environment. You can also use preconfigured business views provided by HCmD to organize your resources. Creating applications automatically on page 367 or Creating applications manually on page 135 Manually refreshing data on page 327 Managing custom tags and tag categories on page 352 Creating application SLO profiles on page 88 or Modifying application SLO profiles on page 100 Creating applications manually on page 135 Creating a new business view on page 77 or Custom business view on page 65 Setup task Description Section reference Log on to HCmD Web UI Initial logon to HCmD Web UI. This procedure also includes: Logging in on page 23 Overview 21

22 Setup task Description Section reference Set up server and notification Add Storage System Collectors Add Host Collectors Set the option to create applications automatically or create new applications manually. Perform manual refresh to gather storage system or host data (optional) Create custom categories/tags (optional) Create new SLO profiles or modify the default SLO profile (optional) Manage unassigned applications Registering the license key Specifying your address Set up the SMTP server to send notifications automatically for Service Level Objective (SLO) alerts and scheduled reports. Set up to receive notifications. Configure storage system data collection to enable HCmD to collect configuration data from Hitachi Device Manager and storage system performance data from Agent for RAID, and collect configuration data from supported third party storage systems. Add/configure Host Collectors to discover hosts in your network and gather their file system and storage utilization information. Applications for the Device Manager Logical Groups are created automatically by default after installation. You can change the default configuration and set to create applications automatically from LUN Owners or hosts configured in your environment. You can also choose to create new applications manually in a custom business view. Manual refresh gathers data before the next scheduled collection and updates reports with the latest information. Hitachi Command Director (HCmD) comes with predefined set of tags and tag categories you can use to create a custom business view that matches your organization structure. If these predefined tags or tag categories do not apply to your business structure, you can create custom categories and tags to organize your resources according to your business structure. HCmD provides a default SLO profile that includes the Average Storage Response Time SLO type. You can create new SLO profiles using the supported SLO types and assign them to applications, or modify the default SLO profile. Unassigned applications are created automatically during the discovery of storage systems or hosts by HCmD. Unassigned applications are also those when you fail to assign them to custom tags. To monitor these applications, you must assign these Specifying an address when you first log in on page 26 Configuring servers on page 355 Specifying an address when you first log in on page 26 Configuring Storage System Collectors on page 319 Host discovery and agentless data gathering mechanism on page 330 Creating applications automatically on page 367 or Creating applications manually on page 135 Manually refreshing data on page 327 Managing custom tags and tag categories on page 352 Creating application SLO profiles on page 88 or Modifying application SLO profiles on page 100 Creating applications manually on page Overview

23 Setup task Description Section reference applications to a relevant tag in your business view. Create custom business views if the preconfigured business views does not suit your requirements. Or, use preconfigured business views that HCmD provides. Create a custom business view that represents the organization of resources in your environment. You can also use preconfigured business views provided by HCmD to organize your resources. Creating a new business view on page 77 or Custom business view on page 65 Related tasks Registering a license on page 24 Specifying an address when you first log in on page 26 Logging in on page 23 Logging in To log on to Hitachi Command Director (HCmD), you require the following information: Hitachi Command Director web URL User ID Password License key, if not already registered. You can obtain this information from your administrator, who is responsible for setting up your user account in Device Manager. To log on to Hitachi Command Director: Procedure 1. In a web browser, enter the Hitachi Command Director URL: HCmD-server-address: IP address or host name of the Hitachi Command Director server. port-number: Port number of the Hitachi Command Director server, default is To access Hitachi Command Director in secure mode, enter the following URL: HCmD-server-address: IP address or host name of the Hitachi Command Director server. Overview 23

24 port-number: The SSL port number of Hitachi Command Director server is Note: If your administrator has set up a shortcut, you can launch Hitachi Command Director from the appropriate Start menu folder. 2. Enter a user ID and password to log in. 3. Click Login. Result The first time you log in, you are required to: Specify a valid license key. Enter your address to receive Service Level Objective (SLO) alerts and scheduled reports. When you log in to Hitachi Command Director, the dashboard appears. Note: When using Internet Explorer on Windows Server 2003, 2008, and 2012, the browser security setting for enhanced security is enabled by default. This might cause the following conditions: The animation that indicates the status of the loading process does not move. Files cannot be downloaded from servers on which HTTPS is enabled. To resolve either of these conditions, disable the advanced security configuration in the Internet Explorer security settings. When using Internet Explorer 9 or 10, the following events may occur: An error message prompting you to install Adobe Flash Player appears, even though the correct version of Adobe Flash is already installed. The help content is not displayed properly. If either of these events occur, disable Active X Filtering, register the IP address or host name of the management server in the Internet Explorer Compatibility View Settings, and press F5 to refresh the browser window. Related concepts About the Hitachi Command Director dashboards on page 32 Related tasks Specifying an address when you first log in on page 26 Registering a license on page 24 Registering a license Users with the View role cannot register licenses. 24 Overview

25 Register a license in any of the following cases: You are accessing Hitachi Command Director (HCmD) for the first time after installation. You cannot access the web UI without a license. A license is not registered. A license is expired. When adding licenses for additional capacity. Procedure 1. Enter the Hitachi Command Director URL. Note: If your administrator has set up a shortcut, you can launch Hitachi Command Director from the appropriate Start menu folder. If you are accessing Hitachi Command Director for the first time after installation, the License Configuration window appears. In this case, register the license key, and then log in. 2. In the login window, click License. Figure 1-1 Initial license configuration 3. In the Device Manager pane of License Configuration window, specify the following license settings for Device Manager. IP Address: enter the IP address for Device Manager. Port: enter the Device Manager HTTP or HTTPS port (the default port is for HTTP and for HTTPS). SSL: select the check box to enable secure sockets layer (SSL) communication between the Hitachi Command Director server and Device Manager server (when selected, the port automatically changes to 22016). Overview 25

26 Note: Before you select the SSL checkbox, make sure that SSL is enabled on the Device Manager server. For more information about enabling SSL on the Device Manager server, see the Hitachi Command Suite Configuration Reference Guide. User ID: this is the Device Manager instance user account used by the system, and the user ID is always system (you cannot change it). Password: enter the password of the system user account for Device Manager. 4. In the Enter License pane for Key, enter the Hitachi Command Director license key and click OK. Result If you are registering the license key for the first time, you are prompted for your address. After you register a license, the value in the Licensed Capacity column of the License Details pane shows the storage capacity from the registered license. However, if you have registered an unlimited storage capacity license of any storage system, the licensed capacity displays Unlimited after you configure the Storage System Collectors in Hitachi Command Director, and refresh the gathered storage system configuration data. Note: The model information for all storage systems is populated only after you perform a data refresh. Related concepts Hitachi Command Director licenses on page 309 Related tasks Configuring Storage System Collectors on page 319 Manually refreshing data on page 327 Specifying an address when you first log in on page 26 Managing licenses on page 309 Specifying an address when you first log in Your is associated with your user account and is used to send Service Level Objective (SLO) alerts and scheduled reports. Note: Your administrator must configure the server before you can specify your address. 26 Overview

27 Procedure 1. In the User dialog box, enter your address in the field. 2. Click Save. Related tasks Modifying your user profile on page 27 Modifying your user profile In your user profile, you can only change your address. address is used to send you alerts and reports. Note: You can only manage your own user account. You cannot manage other users, even if you are an administrator. Procedure 1. In the control bar, click System to open the Edit User Profile dialog. 2. Modify the address. Note that you cannot change your user ID, role, name, or description. 3. When you have finished, click OK. Hitachi Command Director graphical user interface The Hitachi Command Director (HCmD) graphical user interface (GUI) is organized into the following areas: Dashboard When you log in to Hitachi Command Director, the initial screen is the Global dashboard. You can launch reports that provide you with quick access to near real-time status of your applications and storage health of your enterprise. There are also pre-configured dashboards labeled DataCenter, Planning, Pools, and Hosts. You can customize all except the Global dashboard to show only the reports you want. Navigation pane Use the navigation pane to the left in the Resources and Administration tabs to access business views and administration settings. You can also access reports for hosts, applications and storage systems from the Reports tab. Overview 27

28 Content pane The content pane also includes the Additional Reports list, where you can select additional available reports for the selected folder, host, or application. Control bar Use the control bar to view and access the following information: User ID: When you are logged in, your user ID appears in the User button. License violation: The License button turns red when the license expires or the data exceeds the licensed capacity. Online Help: To view the Hitachi Command Director online help, click Help. Global tabs area Access the main features of Hitachi Command Director in the Dashboard, Resources, Reports, and Administration tabs. About button The About button provides a brief description of Hitachi Command Director and includes the current version and node ID. Related concepts Setup workflow on page 20 Related tasks Navigating the Help system on page 28 Using reports on page 247 Navigating the Help system The Hitachi Command Director Help system is an information resource you can use to locate concept and task information applicable to your work objectives. Access the online Help by clicking Help on the control bar. This Help system is also context-sensitive; when you click? (question mark icon) from within a specific window in the web client, you are presented with information that pertains to the task you are performing. From any topic, click Show All Contents to launch the navigation pane, access to the contents, index, search functions, and glossary. In this Help, books are used to group topics that are related to the subject of the book. By default, when you launch the Help navigation pane, all books are closed. When you open a book, topic content is displayed in the right viewing pane. The topic content is displayed in the viewing pane until you open another book or topic. 28 Overview

29 Navigating among topics As you open books and browse to topics of interest, you may want to revisit topics that you have recently viewed. You can navigate among previously viewed topics by right-clicking in the current topic and selecting the applicable Back or Forward options from the menu. Use the links under Related topics to find information related to a specific topic. Use the breadcrumbs at the top of each topic to move to more conceptual information about a specific task or procedure. Using the navigation buttons Contents Open book icons in the navigation pane to reveal topic entries and sub sections. As you move through the Help, the contents tracks the different topics that you access by highlighting them. Index Provides an alphabetical list of subjects contained in the Help. You can scroll though the entries, or type a word to navigate to related topics. Click an entry to view the topic information. Search Allows you to search for occurrences of a word or phrase. Type in the word you want to search for and then click the search icon. In the resulting list, click a topic name to view the topic. Glossary Provides brief explanations for the terms used in Hitachi Command Director. Related concepts Setup workflow on page 20 Related tasks Logging in on page 23 Logging out For security reasons, log out when you have finished using Hitachi Command Director. To log out of Hitachi Command Director, click Logout on the control bar. Related tasks Logging in on page 23 Overview 29

30 30 Overview

31 2 Using dashboards to quickly access vital system reports This module introduces the Hitachi Command Director dashboards, which include reports that show the status or health of your applications, enterprise storage components, datastores, and storage devices in your enterprise. About the Hitachi Command Director dashboards Dashboard access and controls Global and DataCenter dashboards default reports Planning dashboard default reports Pools dashboard default reports Hosts dashboard default reports Using dashboards to quickly access vital system reports 31

32 About the Hitachi Command Director dashboards The Hitachi Command Director (HCmD) dashboards provide a quick and convenient means of accessing the status of your applications and storage health through a collection of relevant reports in the following categories: Global DataCenter Planning Pools Hosts The dashboards are preconfigured with reports that provide a starting point. All but the Global dashboard can be customized with reports of your choice or deleted. You can also create up to 5 additional dashboards and add your choice of reports to each one. All together, the Dashboard tab can display a total of 10 dashboards. The dashboards reveal your application health, based on real-time service level objective (SLO) information, and provide a resource summary report that displays the capacity and performance data of your storage resources, and health of the datastores in your enterprise. Application storage health The Hitachi Command Director dashboards display a summary of status information for all applications that are currently monitored based on defined storage SLOs, which can match operation guidelines set for the implementation of service negotiated under a service level agreement (SLA). An SLO profile groups storage SLOs and associates the SLOs with an application. When an application is assigned an SLO profile, the performance of its storage is monitored to ensure compliance with every SLO threshold (specified in the table below). To enable storage-oriented service solutions (SOSS), you can: Monitor application storage SLOs to ensure that your storage infrastructure provides adequate service to your applications. Take timely action when SLO violations occur. SLO status OK (green) Borderline (yellow) Miss (red) SLO violation None. The application storage is below its threshold (not in jeopardy) and working normally. Warning. The application storage has exceeded its threshold and is at a greater risk of failing. Error. The application storage has exceeded its threshold. Immediate attention is required. 32 Using dashboards to quickly access vital system reports

33 SLO status Unmonitored (gray) SLO violation Not applicable. This application has not been assigned any SLO, and is therefore not monitored. Hitachi enterprise storage health The Hitachi Command Director dashboards provide a snapshot of your enterprise-wide storage system health. Application specified storage SLOs based on storage capacity and performance requirements can be established and proactively monitored to ensure that service levels are being met. The dashboards also provide a quick overview of the physical capacity across all storage systems within your company. They help you gain insight into your storage capacity, identify unused capacity, and track storage utilization. Hitachi Command Director complements Hitachi Command Suite by enabling Hitachi enterprise storage customers to streamline their business level storage reporting and provide further insights into how their Hitachi storage environments can be better utilized and optimized. It also reports on the storage consumption to help you assign storage effectively and plan new purchases of storage, if necessary. Datastore health The Hitachi Command Director dashboards provide information you need to monitor the health of datastores in discovered VMware servers in your environment. The dashboards provide you with an insight into storage allocation, usage, and consumption details of each of these datastores. They also provide you with the current snapshot of your enterprise-wide Hitachi Dynamic Provisioning (HDP) pool capacity and its usage. Storage trends You can use the dashboards to view trends for allocation and capacity. You can also access associated forecasts. This information enables you to plan and anticipate your storage requirements. Related tasks Dashboard access and controls on page 33 Dashboard access and controls Overview of dashboard access and controls Using dashboards to quickly access vital system reports 33

34 When you log on to Hitachi Command Director, the Dashboard tab is automatically selected and a set of available dashboards are shown that provide quick access to a predefined set of relevant reports. If the list of dashboards is hidden, you can click the arrow under the tab to display the list. The following dashboards are provided, each with preconfigured sets of reports: Global DataCenter Planning Pools Hosts Click a dashboard name to access the available reports. With the exception of the Global dashboard, you can customize the reports that are shown for a given dashboard through the Settings dialog or by opening a report and pinning it to a dashboard. You can also add new dashboards and populate them with the reports that you want to access. To add a new dashboard, click the + under the Dashboard tab to open the Add/Edit dialog. Enter a name and an optional description and click OK. You can rearrange reports on a dashboard by dragging, or you can hide them by closing them. To show them again, you can use the Settings dialog. Related tasks Specifying dashboard reports from the Settings dialog on page 34 Setting a default dashboard on page 35 Resizing the dashboard layout on page 35 Exporting and downloading a dashboard to PDF on page 36 Pinning reports to a selected dashboard on page 259 Specifying dashboard reports from the Settings dialog You can specify which reports are displayed for a given dashboard. You can access the same functionality from any report that is open in the report viewer by pinning it to a dashboard. Procedure 1. In the Dashboard tab, select a dashboard where you want to pin a report. 2. Click Settings in the control bar to open the Settings dialog box. Reports currently displayed on the Dashboard are shown under the 34 Using dashboards to quickly access vital system reports

35 Show/Hide tab, from which you can choose which reports to display or hide. Note: You cannot add or remove reports in the Global dashboard and the Add/Remove tab is unavailable. 3. Click the Add/Remove tab to view a listing of available and currently selected reports. You can limit the scope of reports in the listing by selecting one of the available categories: All: All default dashboard reports. Global: All reports on the Global dashboard. Gallery: Reports that can be added from Standard Reports in the Reports Gallery. Saved: Reports that you have saved in the Reports Gallery. 4. Click and highlight any report that you want to add to the dashboard, then click on the right facing arrows (>>) to add the report to the Pinned Reports list. You can highlight reports and remove them from the list by clicking on the left facing arrows (<<). 5. Click OK when you are through. The reports you have selected for display are now shown for the dashboard. Related tasks Pinning reports to a selected dashboard on page 259 Setting a default dashboard You can select a default dashboard so it will display automatically when you log in. Procedure 1. Click the dashboard you want to select from the list under the Dashboard tab. 2. Click Make Default in the control bar above the dashboard. The selected dashboard moves to the top of the list and its reports display by default whenever you log in. Resizing the dashboard layout Change the dashboard layout to control the size of reports in the content pane and enable you to get an oversized view of reports or, alternatively, view more reports at a glance. Procedure 1. Click the Layout button in the control bar above the content pane to open the Dashboard Layout slider. Using dashboards to quickly access vital system reports 35

36 2. Drag the slider button or click the desired point on the Zoom line to minimize or maximize the size of reports in the content pane. Your chosen layout is preserved when you log out and log back in. Exporting and downloading a dashboard to PDF You can export a PDF of an entire dashboard and save or share it. Procedure 1. Open the dashboard you are interested in and click the PDF button in the dashboard control bar. 2. When the File Download dialog opens, click Open to open the PDF or Save to save it to a location you select. Global and DataCenter dashboards default reports The Global and DataCenter dashboards display nearly the same default reports. You cannot add or remove reports from the Global dashboard, but you can choose to show or hide reports. Additional reports are available in the Settings menu. The Global dashboard enables you to maintain a stable collection of important system reports. You can use the DataCenter dashboard to add or remove reports to the list included in the Global dashboard. Total number of applications with SLO misses on page 37 Response Time SLO status on page 38 IOPS SLO status on page 38 DTR SLO status on page 39 Applications with most SLO misses in the past 24 hours on page 42 Storage system capacity overview on page 43 VMware datastore overview on page 43 Hyper-V filesystem overview on page 44 Pool capacity overview on page 45 Top 5 busiest HNAS nodes on page 47 HNAS capacity overview on page 48 Storage system health status on page 49 Related tasks Specifying dashboard reports from the Settings dialog on page Using dashboards to quickly access vital system reports

37 Total number of applications with SLO misses The Applications Missing SLO report on the Hitachi Command Director dashboard displays the total number of applications that missed either of the following Service Level Objectives (SLOs): Average Response Time Total IOPS Data Transfer Rate The displayed number indicates how many applications require your attention. Figure 2-1 Total number of applications with SLO misses This report displays the total number of monitored applications that missed either of the SLOs. For example, if Application A missed the Average Response Time SLO, Application B missed the Total IOPS SLO, and Application C missed both SLOs, the total number of applications with SLO misses is 3. The report provides a rolling snapshot that updates every five minutes. For example, there could be 50 applications missing SLO at 1:00 p.m. If the status of 10 of those applications improves to Borderline before 1:05 pm, the report shows only 40 applications missing SLO at 1:05 p.m. (The example assumes that no other applications downgrade to missing SLO status in between 1:00 and 1:05.) For details about the applications with SLO misses, view the Response Time SLO Status and IOPS SLO Status reports displayed on the dashboard. Related references Response Time SLO Status report on page 38 IOPS SLO Status report on page 38 Using dashboards to quickly access vital system reports 37

38 Response Time SLO Status report The Response Time SLO Status report on the Hitachi Command Director dashboard displays the response time SLO status for all applications in your environment. It provides a breakdown of the overall application SLO status indicating the number of applications that missed, were on the borderline of, and conformed with the Response Time SLO. It also displays the number of applications that are not currently monitored for this SLO. The report provides a rolling snapshot that updates every five minutes. For example, there may be 20 applications in Missed status at 1:00 p.m. If the status of 5 applications improves to OK before 1:05 pm, the report will show 15 applications in Missed status at 1:05 p.m. The example assumes that no other applications downgrade to Missed status in between 1:00 and 1:05. Figure 2-2 Response Time SLO Status You can use this report to address potential storage performance problems that may arise if these violations are left unaddressed. For details about the applications that missed or were on the borderline of the Response Time SLO, click the relevant value to display the Application SLO Details report. Related references Application SLO Details report on page 40 IOPS SLO Status report The IOPS SLO Status report on the Hitachi Command Director Global and DataCenter dashboards displays the total I/O operations per second (IOPS) SLO status for all applications in your enterprise. It provides a breakdown of 38 Using dashboards to quickly access vital system reports

39 overall application SLO status indicating the number of applications that missed, were on the borderline of, and conformed with the Total IOPS SLO. It also displays the number of applications that are not currently monitored for this SLO. The report provides a rolling snapshot that updates every five minutes. For example, there may be 20 applications in Missed status at 1:00 p.m. If the status of 5 applications improves to Borderline before 1:05 pm, the report will show 15 applications in Missed status at 1:05 p.m. The example assumes that no other applications downgrade to Missed status in between 1:00 and 1:05. Figure 2-3 IOPS SLO Status You can use this report to track applications that frequently violate the defined IOPS SLO threshold, and to observe and track the storage usage. For details about the applications that missed or were on the borderline of the IOPS SLO, click the relevant value to display the Application SLO details report. Related references Application SLO Details report on page 40 DTR SLO Status report The DTR SLO Status report on the Hitachi Command Director Global and DataCenter dashboards displays the DTR (data transfer rate) SLO status for all applications in your enterprise. It provides a breakdown of overall application SLO status indicating the number of applications that missed, were on the borderline of, and conformed with the DTR SLO. It also displays the number of applications that are not currently monitored for this SLO. Using dashboards to quickly access vital system reports 39

40 The report provides a rolling snapshot that updates every five minutes. For example, there may be 20 applications in Missed status at 1:00 p.m. If the status of 5 applications improves to Borderline before 1:05 pm, the report will show 15 applications in Missed status at 1:05 p.m. The example assumes that no other applications downgrade to Missed status in between 1:00 and 1:05. You can use this report to track applications that frequently violate the defined DTR SLO threshold, and to observe and track the storage usage. Figure 2-4 DTR SLO Status report For details about the applications that missed or were on the borderline of the DTR SLO, click the relevant value to display the Application SLO details report. Related references Application SLO Details report on page 40 Application SLO Details report The Application SLO Details report displays the SLO profile status for an application over a period of time and indicates which metrics are in violation of the SLO profile. This report is displayed when you select any of following: Missed or Borderline value in the Response Time SLO Status dashboard report. Missed or Borderline value in the IOPS SLO Status dashboard report. Missed or Borderline value in the DTR SLO Status dashboard report. 40 Using dashboards to quickly access vital system reports

41 Figure 2-5 Application SLO details report This report provides the following information: Application: Click the application name to open the SLO Investigation Unit. Response Time SLO status: SLO status of the response time for the application. IOPS SLO status: SLO status of the I/O operations per second for the application. DTR SLO Status: SLO status of the data transfer rate for the application. Response Time: The weighted average response time of the application. IOPS: Total I/O operations per second for the application. DTR: The current data transfer rate for the application. SLO Conformance (past 24 hrs): The percentage of time when the application was in conformance with a monitored SLO in the past 24 hours. Related concepts About SLO Investigation Unit on page 103 Related references Response Time SLO Status report on page 38 IOPS SLO Status report on page 38 DTR SLO Status report on page 39 Using dashboards to quickly access vital system reports 41

42 Applications with Most SLO Misses in the Last 24 hours report The Application with Most SLO Misses report on the Hitachi Command Director dashboard lists the top 5 applications in your environment with the most SLO misses recorded in the past 24 hours. You can use this list to identify the troubled applications that may need your immediate attention. The report provides a rolling time window that includes the last 24 hours of data from the current data time. This means that if the time current data time is 1:00 p.m. the SLO status and conformance will be calculated from the previous day at 1:05 p.m. Because the data updates every five minutes, there is a total of 288 data points. The SLO Status shows the oldest data starting from left and latest to the right. Figure 2-6 Applications with Most SLO Misses (Last 24 Hrs) The report provides the following information for each application: Application: The name of the application. SLO Status (Last 24 Hrs): Provides a historical trend of SLO violations over the past hour. Visual indicators indicate the following: A green bar indicates a period during which no violation of miss or borderline threshold occurred for any monitored SLO profiles. Note: A green bar can also indicate a data hole when no data was available from Agent for RAID and the application was monitored during that time. A red bar indicates a period during which a miss threshold was exceeded for one or more monitored SLO profiles. A yellow bar indicates a period during which a borderline threshold was exceeded for one or more monitored SLO profiles. A gray bar indicates the period when there was no SLO profile associated with the application (also known as unmonitored application). SLO Conformance: Indicates the percentage of time when the application was in conformance with all associated SLOs in the past 24 hours. 42 Using dashboards to quickly access vital system reports

43 Storage System Capacity Overview report The Storage System Capacity Overview report on the Hitachi Command Director dashboard differentiates the used and raw storage capacity across all storage systems within your enterprise. The report provides a rolling snapshot that updates every five minutes. For example, if the allocated volume changes between noon and 12:05 p.m., the Volume graphic will update and reflect the change. Figure 2-7 Storage System Capacity Overview In the report, the Parity Group bar indicates the total usable capacity of disk drives within the storage system. The Volume bar indicates the total capacity of all the volumes carved out from the Parity Group usable capacity. It further shows the breakdown of allocated, unallocated, and reserved capacity. This information helps you determine how much of the Parity Group capacity has been allocated and unallocated to hosts. Note: If the capacity values range from a higher value to a lower value, the lower value is not displayed in the bar chart. For example, if the capacity values range from terabytes (TB) to kilobytes (KB), the bar chart does not display information for capacity values in kilobytes. Click the graphic to open the Physical Capacity by Storage System report. Related references Physical Capacity by Storage System report on page 263 VMware Datastore Overview report The VMware Datastore Overview report on the Hitachi Command Director dashboard provides a quick insight into the total capacity of all your VMware datastores and its usage in your enterprise. Using dashboards to quickly access vital system reports 43

44 This report provides a visual indication of the total available (free) physical storage capacity of the datastores and the capacity used by the applications. The report is a rolling snapshot that updates every five minutes. For example, if the usage changes between 1:00 and 1:05, the graphic will update to reflect the change at 1:05 p.m. Figure 2-8 VMware Datastore Overview You can use this report to analyze the datastores in your enterprise to check if you have enough storage to add a new application and where you can locate it. Click the numeric value displayed to open the VMware Datastores report. Related references VMware Datastores report on page 212 Hyper-V Filesystem Overview report The Hyper-V Filesystem Overview report on the Hitachi Command Director dashboard provides a quick insight into total capacity of all your Hyper-V file systems and its usage in your enterprise. This report provides a visual indication of the total available (free) physical storage capacity of the Hyper-V file systems and the capacity used by the applications. The report is a rolling snapshot that updates every five minutes. For example, if the usage changes between 1:00 and 1:05, the graphic will update at 1:05 to reflect the change. 44 Using dashboards to quickly access vital system reports

45 Figure 2-9 Hyper-V Filesystem Overview report You can use this report to analyze the file systems in your enterprise to check if you have enough storage to add a new application and where you can locate it. Click the numeric value displayed to open the Hyper-V server report. Related references Hyper-V server report on page 210 Pool Capacity Overview report The Pool Capacity Overview report on the Hitachi Command Director is included by default on the Global, DataCenter, and Pools dashboards. It displays the current snapshot of your enterprise-wide pool capacity and its usage. This report differentiates the used pool and the subscribed usage across all storage systems within your enterprise. The report displays a rolling snapshot that updates every five minutes. For example, if the percentage of Used Pages changes between noon and 12:05 p.m, the change will be reflected in the graphic at 12:05. Using dashboards to quickly access vital system reports 45

46 Figure 2-10 Pool Capacity Overview In the report, the Pool bar indicates the volumes in your storage system used for pool creation. The Thin Vols bar indicates the carved out V-VOLs out of the DP Pool with the dark blue portion of the bar indicating the pool capacity associated with a host while the rest in light blue is the unallocated pool capacity. The Used Pages bar indicates the actual usage of the pool capacity. Note: If the capacity values range from a higher value to a lower value, the lower value is not displayed in the bar chart. For example, if the capacity values range from terabytes (TB) to kilobytes (KB), the bar chart does not display information for capacity values in kilobytes. You can use the following information displayed alongside the chart to compare Demand capacity versus Free capacity to identify a potential risk of running out of storage capacity: Used %: Indicates the percentage of total pool consumption derived by calculating the Used Pages by the Pool volume. Demand: Indicates the total capacity in demand, which could potentially be used. This value is the difference in capacity between total DP Volumes allocated capacity and Used Pages allocated capacity. Free: Indicates the actual available pool capacity. This value is the difference in capacity between Pool Physical Capacity and total Used Pages capacity. Click the graphic in the report to open the Pool Capacity by Storage System report. Related references Pool Capacity by Storage System report on page Using dashboards to quickly access vital system reports

47 Top 5 Busiest HNAS Nodes report The Top 5 Busiest HNAS Nodes report on the Hitachi Command Director dashboard lists the top five busy Hitachi NAS Platform server nodes in your enterprise and the node details. The report provides a rolling snapshot that updates every five minutes. For example, if the Busy % changes for a displayed node between noon and 12:05 p.m., the report will update to reflect the change. Figure 2-11 Top 5 Busiest HNAS Nodes This report displays the following details for each HNAS node sorted by average file system load (Busy %) in the descending order: Node: The name of the HNAS node. Cluster: The HNAS cluster this node belongs to. Busy %: The average file system load percentage on the HNAS CPU. IOPS: The total number of IO operations per second for the file system. DTR: The total Data Transfer Rate (DTR) for the file system. Note: For an HNAS node with no file systems, the above report does not display any IOPS or DTR information. You can use the information displayed in the report to identify busy HNAS nodes and check if you can offload some tasks to less busy HNAS nodes, or perform effective load balancing of these nodes. You can view detailed reports about HNAS nodes by selecting these nodes in the File Servers business view and displaying the available HNAS reports in the Resources tab. Related concepts HNAS host reports on page 198 Using dashboards to quickly access vital system reports 47

48 HNAS Capacity Overview report The HNAS Capacity Overview report on the Hitachi Command Director dashboard provides an overview of your Hitachi NAS Platform capacity and usage to help you assign storage effectively and plan any new purchases of storage, if necessary. The report displays a snapshot of the latest data. It updates after every data refresh. Figure 2-12 HNAS Capacity Overview This report displays the storage consumption (in KB) of each of the following physical and logical components of the HNAS server nodes: File System: Total file system capacity of all HNAS systems. Pool: Total Pool capacity of all HNAS Pools. Disk: Total disk capacity that has been allocated to HNAS systems. Clusters: Total number of HNAS clusters. Nodes: Total number of HNAS nodes. Note: If the capacity values range from a higher value to a lower value, the lower value is not displayed in the bar chart. For example, if the capacity values range from terabytes (TB) to kilobytes (KB), the bar chart does not display information for capacity values in kilobytes. You can use the information displayed in the report to analyze the amount of HNAS resources in your environment. Click the graphic to open the HNAS Cluster Overview report, which includes information for each cluster. Related concepts HNAS host reports on page 198 Related references HNAS Cluster Overview report on page Using dashboards to quickly access vital system reports

49 HNAS Cluster Overview report The HNAS Cluster Overview report provides a tabular display of nodes, filesystems, HNAS pools, and disks corresponding to a specific cluster. Access the report by clicking the graphic in the HNAS Capacity Overview report. Figure 2-13 HNAS Cluster Overview The report includes the following fields: Field Cluster Node #Filesystems FS Capacity #Pools Pool Capacity #Disks Disk Capacity Description Name of the HNAS cluster. Nodes belonging to the cluster. Number of file systems in the cluster. Capacity of the file systems in the cluster. Number of pools in the cluster. Capacity of pools in the cluster. Number of disks in the cluster. Capacity of disks in the cluster. Storage System Health Status report The Storage System Health Status report displays the current health status of the following storage system resource types: cache, parity groups, and processors. Access this tabular report from the DataCenter dashboard. The report lists the storage system resource type status based on the most recent data collection. It includes the status for the corresponding number of cache, parity groups, or processor resources that are currently in a Critical, Warning, Normal, or Unmonitored state. Using dashboards to quickly access vital system reports 49

50 The Storage System Health Status report displays by default on the DataCenter dashboard and is hidden on the Global dashboard. You can access specific status details about a storage system resource type when you click the hyperlink that corresponds to the resource state in which you are interested. The report is a rolling snapshot that updates every five minutes. For example, if the status of a resource is Warning at 1:00 and changes to Critical before 1:05, the new status will be reflected at 1:05. Figure 2-14 Storage System Health Status report Note: The following two cases describe when there is no performance and latest configuration data yet available, and as a result, no status for the resource can be displayed in the report: When a new storage array is added, the data collection refresh is in progress, but there is not yet any performance data available for Command Director (typically, this is a five-minute period). In this case, the report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). When resources that had been in an unmonitored state were just assigned a monitoring profile. In this case, until there is performance data collected, the report displays the resource state as Normal, thresholds display as a hyphen (-), and the Data Time field displays a hyphen (-). Storage System Health Detail report The Storage System Health Detail report is accessible from the Storage System Health Status report, when you click on the status hyperlink of one of the supported resource types. This tabular report displays metric details about each storage system array resource state type in which you are interested. The supported resource types listed show cache logical partition resource (CLPR), parity group, and processor values. Each report displays resource information for a Critical, Warning, or Normal state based on the corresponding storage system monitoring profile applied to it, and these categories are described in the following table. 50 Using dashboards to quickly access vital system reports

51 Figure 2-15 Storage System Health Detail report Resource Information Description Resource Type Cache Parity group Processor Storage System Model Resource Metric Name Warning Threshold Critical Threshold Metric Value Conformance % Data Time Status Name and IP address of storage system Storage system model Name of resource Metric names vary by resource type: CLPR (Write Pending %) Parity group (Busy %) Processor (Busy %) Warning threshold setting (in percentage) Critical threshold setting (in percentage) Value of measured metric (in percentage) Calculation (in percentage) for conformance based on total number of data collection points minus the number of critical violations detected during a 24-hour period. Date and time in which data was collected Current status and warning state of resource Note: The following two cases describe when there is no performance and latest configuration data yet available, and as a result, no status for the resource can be displayed in the report: When a new storage array is added, the data collection refresh is in progress, but there is not yet any performance data available for Command Director (typically, this is a five-minute period). In this case, the Using dashboards to quickly access vital system reports 51

52 report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). When resources that had been in an unmonitored state were just assigned a monitoring profile. In this case, until there is performance data collected, the report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). Related references Storage Pool Health Status report on page 55 Storage System Performance Overview report The Storage System Performance Overview report is hidden on the Global and DataCenter dashboards. It provides an overview of the performance of your enterprise storage. You can use the information to analyze the overall health of your storage systems. The report provides a rolling snapshot that updates every 5 minutes. For example, if the Avg. Read Hit changes between noon and 12:05 p.m., the report will update at 12:05 to reflect the change. Figure 2-16 Storage System Performance Overview report This report provides near, real-time data for the following monitored metrics: Avg. Response Time(in ms): Weighted average response time of all storage systems based on their total IO count. A high response time indicates potential latency problem on some storage systems. Total IOPS: The total number of IO operations per second across all storage systems in your environment. Total DTR: Total data transfer rate (MB/s) for all storage systems in your environment. 52 Using dashboards to quickly access vital system reports

53 Avg. Read Hit (in percentage): Average read hit percentage for all storage systems based on their read IO counts. A high read hit percentage is optimal; A low value indicates storage performance issues. Avg. Write Pending (in percentage): Weighted average write pending percentage for all storage systems based on cache size. A high write pending percentage indicates storage performance issues. Related references Performance Overview by Storage System report on page 226 Planning dashboard default reports The Planning dashboard is pre-configured with the following reports: Storage System Capacity Trend Storage Allocation Trend reports for HNAS, Windows, and Hyper-V. Related references Storage System Capacity Trend report on page 227 Storage Allocation Trend on page 164 Pools dashboard default reports The Pools dashboard is pre-configured with the following reports: The Pool Capacity Overview report displays the overall enterprise pool capacity and its usage. The Top 20 Pool Utilization by Capacity report displays the top 20 pools by used capacity, including HDP and HDT. The Storage Pool Health Status report displays storage array pool metrics, and shows the corresponding number of resources currently in Critical, Warning, Normal and Unmonitored state. You can also access details for any storage pool that is being monitored. Related references Pool Capacity Overview report on page 45 Top 20 Pool Utilization by Capacity report Access the Top 20 Pool Utilization by Capacity report on the Pools dashboard to display information for each pool. Using dashboards to quickly access vital system reports 53

54 Figure 2-17 Top 20 Pool Utilization by Capacity report The following fields are available: Field Pool Pool Name Storage System Model Pool Capacity Used Free Used % Multi-Tier Tier1 Used Tier1 DiskType Tier2 Used Tier2 DiskType Tier3 Used Tier3 DiskType Description The pool ID. The pool name specified in Device Manager. Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). For third-party storage system registered using the SMI-S Provider, it is the storage system model and serial number. The storage system model type. Total capacity for the pool. Amount of capacity used. Unused capacity. Capacity used as a percentage of the total. Enabled or Disabled for Hitachi arrays. For third-party models, this field is not applicable and displays a hyphen. Tier 1 used capacity. For third-party models, Tier fields are not applicable and the fields display hyphens. Type of Tier 1 disk. Tier 2 used capacity. Type of Tier 2 disk. Tier 3 used capacity. Type of Tier 3 disk. # Applications Number of applications using this pool. Click the hyperlink to open the Pool Usage by Application report for the selected pool. For more information, see Pool usage by application on page Using dashboards to quickly access vital system reports

55 Related references Pool Usage by Application report on page 271 Pool Capacity Overview report on page 45 Storage Pool Health Status report on page 55 Storage Pool Health Status report The Storage Pool Health Status report displays the current health status of the following storage array pool metric types: capacity utilization %, over provisioning ratio, and risk ratio. Access this tabular report from the Pools dashboard, which lists storage array pool status based on the most recent data collection. This report displays the status for the corresponding number of storage array pool resources for capacity utilization %, over provisioning ratio, and risk ratio that are currently in a Critical, Warning, Normal, or Unmonitored state. The Storage Pool Health Status report displays by default on the Pools dashboard and is hidden on the Global and DataCenter dashboards. You can access specific status details about a storage array pool type when you click the hyperlink that corresponds to the resource state in which you are interested. Figure 2-18 Storage Pool Health Status report Note: The following two cases describe when there is no performance and latest configuration data yet available, and as a result, no status for the resource can be displayed in the report: When a new storage array is added, the data collection refresh is in progress, but there is not yet any performance data available for Command Director (typically, this is a five-minute period). In this case, the report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). When resources that had been in an unmonitored state were just assigned a monitoring profile. In this case, until there is performance data collected, the report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). Related references Storage System Health Detail report on page 50 Using dashboards to quickly access vital system reports 55

56 Pools dashboard default reports on page 53 Pool Capacity Overview report on page 45 Storage Pool Health Detail report The Storage Pool Health Detail report is accessible from the Storage Pool Health Status report, when you click on the status hyperlink of one of the supported resource types. This tabular report displays metric details about each storage array pool resource state type in which you are interested. The supported resource types listed show capacity utilization %, over provisioning ratio, and risk ratio values. Each report displays storage array pool resource information for a Critical, Warning, or Normal state based on the corresponding storage system monitoring profile applied to it, and these categories are described in the following table. Figure 2-19 Storage Pool Health Detail report Resource Information Storage System Model Pool Pool Name Multi-Tier Metric Name Warning Threshold Critical Threshold Description Name and IP address of storage system Storage system model Number of pools Pool name Pool tiering policy Metric name (depends on the selected resource type) Warning threshold setting (in percentage) Critical threshold setting (in percentage) 56 Using dashboards to quickly access vital system reports

57 Resource Information Metric Value Data Time Status Description Value of measured metric (in percentage) Date and time in which data was collected Current status and warning state of resource Note: The following two cases describe when there is no performance and latest configuration data yet available, and as a result, no status for the resource can be displayed in the report: When a new storage array is added, the data collection refresh is in progress, but there is not yet any performance data available for Command Director (typically, this is a five-minute period). In this case, the report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). When resources that had been in an unmonitored state were just assigned a monitoring profile. In this case, until there is performance data collected, the report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). Hosts dashboard default reports The Hosts dashboard is preconfigured with the following reports: Host Capacity Utilization Status Host Capacity Utilization Detail Storage Allocation Trend Storage Allocation Details Volumes Mapped to ESX Server VMs Related references Storage Allocation Trend on page 164 Storage Allocation Details report on page 170 Volumes Mapped to ESX Server VMs report on page 213 Host Capacity Utilization Status report The Host Capacity Utilization Status report displays the current health status of the following resource types: Hitachi NAS Platform (HNAS) pools, VMware datastores, and file systems on hosts/hnas/vm instances. Access this tabular report from the Hosts dashboard, which lists the hostresource capacity status based on the most recent data collection. The report displays the corresponding number of pool, datastore, and file system resources that are currently in a Critical, Warning, Normal, or Unmonitored state. Using dashboards to quickly access vital system reports 57

58 The Host Capacity Utilization Status report displays by default on the Hosts dashboard and is hidden on the Global dashboard. You can access specific status details about host-related resources when you click the hyperlink that corresponds to the resource state in which you are interested. Figure 2-20 Host Capacity Utilization Status report Note: The following two cases describe when there is no performance and latest configuration data yet available, and as a result, no status for the resource can be displayed in the report: When a new storage array is added, the data collection refresh is in progress, but there is not yet any performance data available for Command Director (typically, this is a five-minute period). In this case, the report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). When resources that had been in an unmonitored state, were just assigned a monitoring profile. In this case, until there is performance data collected, the report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). Related references Host Capacity Utilization Detail report on page 58 Host Capacity Utilization Detail report The Host Capacity Utilization Detail report is accessible from the Host Capacity Utilization Status report, when you click the status hyperlink of one of the supported host resources. This tabular report displays metric details about each resource state type in which you are interested: Hitachi NAS Platform (HNAS) pools, VMware datastores, and host/hnas/vm instance file systems. Each report displays resource information for a Critical, Warning, or Normal state based on the corresponding host monitoring profile applied to it, and these categories are described in the table below. 58 Using dashboards to quickly access vital system reports

59 Figure 2-21 Host Capacity Utilization Detail report Resource Information Description Resource Type VMware datastore HNAS file system HNAS pool Host file system VM instance file system Identifier Type/Container Resource Name Warning Threshold Critical Threshold Capacity Host name or IP address of resource with listed violation or state Type/Container information can vary by resource type, for example: Datastore does not display this column HNAS file systems and pools can list by cluster or node name Host file systems can list by OS and file system type (for example: Windows NTFS) VM instance file systems can list by OS type and version (for example: Windows 2008 R2) Resource name can vary by resource type, for example: Datastore and HNAS file systems can list by file system, node, or repository name HNAS pools can list by disk or pool name Host and VM instance file systems can list by drive location Warning threshold setting (in percentage) Critical threshold setting (in percentage) Total capacity of resource (in GB) Using dashboards to quickly access vital system reports 59

60 Resource Information Consumed Capacity Capacity Utilization % Description Capacity being consumed by resource (in GB) Capacity being utilized by resource (in percentage) Note: This value may be incorrect if a VMware datastore is shared across two ESX servers and one of the ESX servers does not have the updated consumed capacity for this VMware datastore. This issue originates in vcenter. Data Time Status Date and time of data collection Current status and warning state of resource Note: The following two cases describe when there is no performance and latest configuration data yet available, and as a result, no status for the resource can be displayed in the report: When a new storage array is added, the data collection refresh is in progress, but there is not yet any performance data available for Command Director (typically, this is a five-minute period). In this case, the report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). When resources that had been in an unmonitored state were just assigned a monitoring profile. In this case, until there is performance data collected, the report displays the resource state as Normal, thresholds display as 0%, and the Data Time field displays a hyphen (-). Related references Host Capacity Utilization Status report on page Using dashboards to quickly access vital system reports

61 3 Managing resources This module describes how to manage your resources efficiently and configure applications for Hitachi Command Director usage. About business views Using business views Creating a new business view Business view modification restrictions Managing business views Deleting business views Managing resources 61

62 About business views Use business views to organize hosts, applications, and other folders so that you can receive storage reports according to your business structure and criteria. For example, you can group your applications by department (Human Resources, Product Marketing, Sales), geography (North America, South America, EMEA, APAC), or data center. The Admin user role is required in order to create, manage, or delete business views. The Business Views drop-down list at the top of the Navigation Pane in the Resources tab allows you to select any business view. The folders in business views aggregate information about their children (hosts, applications, and folders) and typically represent a business or other organizational unit. For example, when viewing the Storage Allocation report, a folder can represent the total storage capacity allocated to all its applications. When viewing the SLO Status report, a folder can represent all the Service Level Objective (SLO) threshold violations for all its applications. Custom business view Custom business views are generated using one or more tag categories you have defined in Hitachi Command Director. A new business view structure is created hierarchically by arranging one or more categories. When categories are arranged, the business view shows all tags under each category in a treelike hierarchy. Hitachi Command Director provides predefined tag categories that enable you to get started creating business views right away. You can also assign predefined tags to applications to associate them with a business view. The association of application with a business view provides a context for the application about who owns the application or where the application is located. For example, tag USA will indicate that the application is located in USA while tag Finance will indicate that the application is used by the "Finance" group in your organization. Built-In business views Built-In business views are the Hosts view, File Servers View, Storage Systems view, All Applications view, Applications by Pool view, and Applications by Capacity view that are available from the Business View list. These are read-only views that cannot be created, deleted, or modified. Hosts view Displays the hosts organized by the operating system. File Servers view 62 Managing resources

63 Displays pertinent information about the discovered Hitachi NAS Platform (HNAS) servers. Storage Systems view Displays the storage systems successfully registered in Hitachi Command Director or third-party storage systems (such as EMC systems) registered through the SMI-S Provider. Separate views are provided for all storage systems, storage systems from a particular category (Hitachi or EMC), and for a specific storage system. All Applications view Lists every application that is auto-generated, custom, or imported into Hitachi Command Director. You can use this view to find any application without navigating a business view hierarchy. Applications by Capacity Shows applications grouped by capacity range and ordered by capacity of individual applications. Applications by Pool Shows applications belonging to each pool of a storage system. Device Manager Logical Group view The Device Manager Logical Group View allows you to view the Device Manager logical groups without having to recreate them. Each logical group contains mapping information to the volumes on the storage system. The Logical View is created automatically and displayed only when the autocreate application option is set to Logical Group. After changing the setting to Logical group for the first time, perform a refresh to update the business view. Related concepts About applications on page 132 Related tasks Managing custom tags and tag categories on page 352 Creating applications automatically on page 367 Displaying business views on page 64 Using business views This module describes how you can use business views to organize the various storage resources in your organization in a way that reflects your organization structure. Managing resources 63

64 Displaying business views A business view depicts your organization structure. It determines organization of your applications and enables you to manage them in the way your organization works. Hitachi Command Director displays the following business views: Predefined, custom business views: Geography Function Geography-Function Function-Geography Hosts view File Servers view Storage Systems view All Applications view Logical Group view Applications by Pool view Applications by Capacity view Procedure 1. Select the Resources tab. 2. Select a business view from the drop-down list. A list of available business views is displayed. Related concepts About business views on page 62 Related tasks Figure 3-1 Business views Creating a new business view on page 77 Managing business views on page Managing resources

65 Deleting business views on page 80 Custom business view A custom business view is an ordered set of tag categories. The tags in each tag category represent the nodes that show up at the node level. Only those tags that are assigned to applications will appear in the business view. Using the custom business view you can navigate to individual application or groups of applications (application folders). By selecting the application or application folder, you can view their details in individual reports for each selected application or summarized reports for the application folder. You can access the custom business view from the Business Views drop-down list in the Resources tab. You can choose to display your business view based on the categories you have set: A simple business view based on one tag category. A compound business view based on multiple categories and specific conditions. For example, if you have categorized your business view based on geography and business function, you can set to display your business view in a simple way based on geography or in a compound way by displaying first by geography and then by the business function within the geography. The following figure shows examples of a simple single category view and a compound view that displays multiple categories. Untagged applications Figure 3-2 Custom business view For an application to appear in a business view it must be tagged with at least one tag category defined in the business view definition. The categories for which the application is not tagged will show up under the All Applications view. Managing resources 65

66 Application search You can search for applications in the custom business view by typing the complete application name or part of it in the Search field and clicking the Search icon. A list of applications that match the search criteria (without the business view hierarchy) is displayed, and the first result displayed is highlighted and the corresponding reports are displayed in the content pane. To clear the displayed results, enter new search criteria, or to display the initial business view hierarchy, click the Clear icon. Related concepts All Applications view on page 73 About business views on page 62 Related tasks Logical Group view Creating a new business view on page 77 The Logical Group view allows you to view logical groups from the Device Manager without having to create them in Hitachi Command Director. Each logical group contains mapping information to the volumes on the storage system. Hitachi Command Director treats logical groups that have paths assigned like an application and all reports for applications are also directly available for these Logical Groups. You can use this view as an easy way to assign SLOs directly to the logical groups without having to create the application in Hitachi Command Director and assign storage to it. You can access the Logical Group view from the Business Views drop-down list in the Resources tab. This view is created automatically and available only when you configure Storage System Collectors and select the Logical Group auto create application option available in Administration tab > Application Settings. The following is an example of folders in a Logical Group view: 66 Managing resources

67 Figure 3-3 Logical Group view Note the following: Imported folders represent Device Manager logical groups and you cannot modify them in Hitachi Command Director. Imported folders are synchronized with Device Manager logical groups at every data refresh of the storage system configuration data and after initial import of the logical group data when you choose to automatically create applications based on Device Manager logical groups. Logical groups without storage association are not imported and therefore do not appear in the Logical Group Business View in Hitachi Command Director. Application search You can search for applications in the Logical Group view by typing the complete application name or part of it in the Search field and clicking the Search icon. A list of applications that match the search criteria (without the business view hierarchy) is displayed, and the first result displayed is highlighted and the corresponding reports are displayed in the content pane. To clear the displayed results, enter new search criteria, or to display the initial business view hierarchy, click the Clear icon. Managing resources 67

68 Hosts view Related concepts About business views on page 62 Specifying how applications are automatically created on page 366 Related tasks Displaying business views on page 64 The Hosts view allows you to view the hosts successfully discovered by the Host Collectors. Note that the host group information is not included in the Hosts view information. You can access the Hosts view from the Business Views drop-down list in the Resources tab. The following is an example of folders in a Hosts view: Figure 3-4 Hosts view Hitachi Command Director organizes the hosts by OS, with the hosts organized in the following folders: AIX HP-UX 68 Managing resources

69 Hyper-V Linux Solaris VMware ESX DataStore Windows All VMware host instances are listed under their respective OS folder. ESX servers and Data Store servers are listed under the VMware folder. When a new host is discovered, the Hosts view displays the new host. After every data refresh of the host collector data, volumes added to or removed from a host are automatically updated in the host-to-its-volume mapping. Note: If the host has devices that are not connected to volumes from a storage system (for example, when the volumes are unprovisioned for the host), Hitachi Command Director will not display such devices. Host search You can search for a host in the Hosts view by typing the complete host name or part of it in the Search field and clicking the Search icon. A list of hosts that match the search criteria (without the business view hierarchy) is displayed, and the first result is highlighted and corresponding reports are displayed in the content pane. To clear the displayed results, enter new search criteria, or to display the initial business view hierarchy, click the Clear icon. Related concepts About business views on page 62 Related tasks File Servers view Displaying business views on page 64 The File Servers view allows you to view pertinent information about the discovered Hitachi NAS Platform (HNAS) servers, file systems, and storage pools. You can access the File Servers view from the Business Views drop-down list in the Resources tab. The following is an example of the HNAS tree in the File Servers view: Managing resources 69

70 Figure 3-5 File Servers view The File Servers view displays the HNAS tree with the HNAS cluster at the top folder. Each cluster includes the cluster name and its SMU IP address. For a multi-node cluster, the following folders are displayed: Nodes Filesystems Pools For a single HNAS node, the following folders are displayed: Filesystems Pools Expand each of those nodes for information and access to each of those HNAS elements. Single node clusters do not have any nodes folder. File server search You can search for a file system or pool in the File Servers view by typing the complete or partial file system or pool name in the Search field and clicking the Search icon. A list of file systems or pools that match the search criteria (without the business view hierarchy) is displayed, and the first result is highlighted and corresponding reports are displayed in the content pane. 70 Managing resources

71 To clear the displayed results, enter new search criteria, or to display the initial business view hierarchy, click the Clear icon. About HNAS in Hitachi Command Director The physical and logical components of HNAS server nodes are as follows: Clusters: An HNAS cluster is composed of two to eight nodes. The nodes share the same storage devices; the network requests can be distributed across cluster nodes. HNAS Nodes: If a cluster node fails, its file services and administration functions are transferred to other nodes. EVS (Virtual Servers): Each EVS (Virtual Server) is assigned unique network settings and storage resources that allows Administrators to logically partition access to shared storage resources. In clusters, EVSs are migrated between servers when faults occur to ensure maximum availability. File Systems: Before it can be shared or exported, a file system must be associated with a Virtual Server (EVS), thereby making it available to network clients. The association between a file system and an EVS is established when the file system is created, but over time the file system could be relocated to a different EVS. Storage Pools: Storage Pools are logical containers for a collection of one or more system drives. Storage pools that can be expanded as additional system drives are created in the storage system. By default, one file system is allowed on a storage pool. With appropriate licenses, more than one file system could be created on a storage pool. System Drives: Basic logical storage element used by the HNAS server. Physical Disk Drives: These are the volumes on the storage system. Related concepts About business views on page 62 Related tasks Displaying business views on page 64 Storage Systems view The Storage Systems view allows you to view information about storage systems obtained successfully by the Storage System Collectors configured for Hitachi Device Manager, Agent for RAID, and Tiered Storage Manager instances in your environment. For EMC systems, storage system configuration information is provided by the SMI-S provider. Access the Storage Systems view from the Business Views drop-down list in the Resources tab. This view will display storage systems only when these conditions are met: Managing resources 71

72 Storage systems are registered with both Device Manager and Agent for RAID. Storage system (VMAX-SE) is registered with SMI-S provider for EMC systems. Storage System Collectors have been configured through Administration tab > Storage System Collectors. A data refresh is performed by the configured Storage System Collectors. Following is an example that shows a list of storage systems in the Storage Systems view. It displays the name of the storage systems configured by Device Manager. If the name is not specified in Device Manager, Command Director creates a name that includes the storage system model and serial number (for example, VSP 25210). Figure 3-6 Storage Systems view The Storage Systems view can display the following supported storage systems: Virtual Storage Platform Virtual Storage Platform G1000 Universal Storage Platform V Universal Storage Platform Universal Storage Platform V/VM 72 Managing resources

73 Adaptable Modular Storage Workgroup Modular Storage Simple Modular Storage Hitachi Unified Storage Hitachi Unified Storage VM (HUS VM) EMC SYMMETRIX VMAX-SE Upon refresh of Storage System Collectors, the storage systems list in the Storage Systems view is updated. However, note that the list of storage systems displayed in the updated Storage Systems view will include: New storage systems that were recently registered in Hitachi Device Manager and Agent for RAID. Existing storage systems that were recently unregistered from Hitachi Device Manager and Agent for RAID. This information is retained for historical reporting purposes. For EMC systems, the VMAX-SE Storage systems registered with SMI-S Collector are shown. Storage system search You can search for a storage system in the Storage Systems view by typing the complete storage system name or part of it in the Search field and clicking the Search icon. A list of storage systems that match the search criteria is displayed and the first result is highlighted and corresponding reports are displayed in the content pane. To clear the search results or to enter new search criteria, click Clear. Related concepts About business views on page 62 Related tasks All Applications view Displaying business views on page 64 The All Applications view is a list of every application that is defined or imported in Hitachi Command Director. You can use this view to find any application without navigating a business view hierarchy. You can also use this view to manage applications. Access the All Applications view from the Business Views drop-down list in the Resources tab. The following is an example of a list of applications in the All Applications view: Managing resources 73

74 Figure 3-7 All Applications view Note: LUN-Owner applications which include EMC volumes do not support SLO profile monitoring as indicated by "Unmonitored" for the SLO Profile. Application search You can search for an application in the All Applications business view by typing the complete application name or part of it in the Search field and clicking the Search icon. A list of applications that match the search criteria is displayed, and the first result displayed is highlighted and corresponding reports are displayed in the content pane. To clear the displayed results or to enter new search criteria, click the Clear icon. Related concepts About business views on page 62 Related tasks Displaying business views on page 64 Applications by pool view View applications by pool details as a business view. 74 Managing resources

75 The Applications by Pool view shows applications belonging to each pool of a storage system. Figure 3-8 Applications by Pool view The top level in this view consists of storage systems. You can expand the level to expose pools, and below pools are applications using storage from those pools. Note: The contents of the view depend on the setting in the Auto Create Application dialog in Application Settings as follows: Logical Group: Only Hitachi pools display. Host: Only Hitachi pools display. LUN Owner: Hitachi and third party pools display. None: No data will display. For more information, see Creating applications automatically on page 367. Related concepts About business views on page 62 Related tasks Displaying business views on page 64 Creating applications automatically on page 367 Applications by capacity view View applications by capacity details. Managing resources 75

76 The Applications By Capacity view shows applications grouped by capacity range and ordered by capacity of individual applications. You can access the Applications By Capacity view from the Business Views drop-down list in the Resources tab. Figure 3-9 Applications by Capacity view Application capacity is calculated by adding up allocated capacity of all the member LDEVs for the application. Ranges for capacity can be specified in the custom properties file. The default thresholds are 5 TB and 1 TB. For more information about the custom properties file, see the Hitachi Command Director Installation and Configuration Guide. Note: The contents of the view depend on the setting in the Auto Create Application dialog in Application Settings as follows: Logical Group: Only Hitachi capacity displays. Host: Only Hitachi capacity displays. Lun Owner: Hitachi and third party capacities display. None: No data will display. For more information, see Creating applications automatically on page 367. Related concepts About business views on page 62 Related tasks Displaying business views on page Managing resources

77 Creating a new business view You can use the tag categories defined in Command Director to create your own business view that will be displayed in the Business Views drop-down list. You can create a new business view based on any of the following: Custom tag categories You can create custom tags and tag categories and then use them to create a new custom business view. To create custom tags and tag categories, see Managing custom tags and tag categories on page 352. Predefined tag categories Hitachi Command Director provides the following predefined custom business views derived from predefined tag categories: Geography Function Geography - Function Function - Geography Categories provided in the New Business View dialog: Function Geography Application Capacity Pool Storage System Procedure 1. Select the Resources tab. Managing resources 77

78 2. Next to the Business Views drop-down list, from the Action drop-down menu, select New Business View. The New Business View dialog opens. Figure 3-10 New Business View dialog with example business view 3. In the Business View Name field, enter the name for your business view. It can include the characters _ (underscore),. (at symbol) and - (dash). 4. To select a category for your business view, move it in to the Hierarchy of Categories list. To remove a category, move it back to the Categories list. To move a category between scroll lists, select the category and click the relevant arrow. 5. If you have selected multiple categories for your business view, specify the hierarchical order for the categories to appear in the business view. To apply a display order, move the category either up or down in the Hierarchy of Categories list. Click the appropriate arrow on the right side of this list to set the display order. The Preview shows an partial example of the resulting structure. 6. To view only applications that are tagged with all chosen categories, select Show only applications that are tagged with all selected categories. 7. Click OK to save your business view. 78 Managing resources

79 8. Review the new business view by selecting the new custom business view from the Business Views drop-down list. Related concepts Custom business view on page 65 Related tasks Managing business views on page 79 Deleting business views on page 80 Displaying business views on page 64 Business view modification restrictions For the logical views you imported from Device Manager: You cannot rename imported business views. You cannot modify imported folders. You cannot add, modify, or assign storage to the imported applications. Device Manager storage groups contain unique fully qualified names, and shorter display names. These display names are used for Hitachi Command Director application names. You cannot modify built-in business views such as the Hosts, File Servers, Storage Systems, All Applications, Applications by Pool, and Applications by Capacity. Related tasks Managing business views on page 79 Deleting business views on page 80 Managing business views You can modify only custom business views. You can rename a custom business view or modify its definition by changing the tag categories or their order. Review the modification restrictions for other business views in Business view modification restrictions on page 79. Procedure 1. From the Resources tab, select the business view you are modifying. 2. From the Action drop-down menu, select Manage Business View. 3. Perform the appropriate modification task in the Manage Business View window. Managing resources 79

80 You can select the Show only applications that are tagged with all selected categories checkbox to display applications only at the leaf level. a. To modify categories, move the required category between the Categories and Hierarchical Categories lists by selecting the category and clicking an arrow. As you add and remove categories and change their hierarchy, you can view an example of the effect in the Preview pane. The examples include representative sample applications for purposes of illustrating the hierarchy. b. To rename, enter the new name of the business view in the Business View Name field. c. Click OK to save your modifications. 4. Review the business view modifications you made on the Business Views drop-down list. Related concepts About business views on page 62 Related tasks Deleting business views on page 80 Related references Business view modification restrictions on page 79 Deleting business views You can delete any business view that is custom, preconfigured, or logical group. Procedure 1. From the Resources tab, select the business view you are deleting. 2. From the Action drop-down menu, select Delete Business View. 3. In the Confirmation dialog box, verify that the business view you are deleting is correct, then click Yes. Related concepts About business views on page 62 Related tasks Displaying business views on page Managing resources

81 4 Monitoring applications Use storage Service Level Objectives (SLOs) to monitor selected application and volume parameters based on user-defined parameters The Admin user role is required in order to access Global SLO settings, SLO profiles, and SLO profile recommendations. SLO overview Managing application SLO profiles Accepting SLO profile recommendations Updating SLO profiles for volumes Updating SLO profiles for application volumes Updating SLO profiles for pool volumes Global SLO settings SLO Investigation Unit Monitoring applications 81

82 SLO overview Use storage Service Level Objectives (SLOs) to monitor selected application and volume parameters based on user-defined parameters. A Service Level Objective (SLO) is a performance or configuration metric of a storage volume. Two distinct threshold values are defined for each SLO - one to identify the missed condition and the other to identify the borderline condition. Hitachi Command Director (HCmD) offers Application SLO that is measured on volumes that are assigned to the application. Three metrics are supported - Data Transfer Rate, Response Time, and IOPS. You can create multiple SLOs for a given SLO type by assigning different threshold values. To ensure that the storage assigned to an application meets the application s SLOs, the application must be assigned an SLO profile during a monitoring window (time period). An application that exceeds its borderline SLO threshold has a Borderline violation status. An application that exceeds its missed SLO threshold has a Miss violation status. An application that is below its borderline SLO threshold does not have a violation and has an OK status. SLO profile A Service Level Objective (SLO) profile is a group of SLOs (threshold values) that define a service tier and is used to track the service level of an application or a storage resource. When you assign an SLO profile to an application, you are configuring Hitachi Command Director to monitor that application for all the SLOs contained in the SLO profile. alerts You can send alerts when borderline or miss SLO violations occur during their monitoring window. SLO violation alerts can be sent to anyone and are not limited to Hitachi Command Director user accounts. Monitoring window Monitoring window specifies the time periods when the application SLOs are monitored. A monitoring window can contain multiple time periods and reflects your organization s activity schedule. For example, if a business application runs from 9 am to 5 pm and requires certain performance SLO, you can create a monitoring window for this timeframe. For rest of the time 82 Monitoring applications

83 this application is not running and therefore does not require a monitoring window. Related concepts Storage system health thresholds on page 114 About application SLO profiles on page 85 Related tasks Global SLO settings on page 100 Modifying a single application on page 143 Application SLO types You can have only one SLO of a given type in an SLO profile. However, you can create multiple SLO profiles. Hitachi Command Director provides the following Application SLO types that you can include in an SLO. The list explains how SLOs are calculated for applications. By default, Hitachi Command Director monitors volumes. When volumes are monitored, each SLO violation is propagated against the volume's application. Average Storage Response Time: monitors the weighted average of the I/O response times for all the volumes used by the application. The response time of each volume is measured at the storage system port and is compared to the specified SLO thresholds. When calculating the application s average volume response time, each volume response time is weighted according to the volume s I/O count. As a result, the response time for a volume with a small I/O load does not misrepresent the calculated average volume response time for the application. For example, if application A uses two volumes (X and Y), the average response time is: (X response time * X I/O count) +(Y response time * Y I/O count) / (X I/O count + Y I/O count) Total IOPS: Monitors an application s total I/O operations per second when reading from a volume or writing to a volume. Data Transfer Rate: Monitors the sum of data transfer rates of application volumes. Related concepts Understanding SLO profile recommendations on page 84 Related tasks Global SLO settings on page 100 Monitoring applications 83

84 Understanding SLO profile recommendations SLO profile recommendations are calculated using IO performance data over time for each volume. The time period in number of days and other values that are used in calculating the recommendations can be edited in the custom.properties file. The following list describes how recommendations are calculated and generated. Each data point is identified as random, sequential, or mixed, based on thresholds that can be edited in the custom.properties file. The data points are grouped by random, sequential, and mixed. For each volume, the mean and standard deviation for each group of data points is determined. The sum of the mean plus one (or more) standard deviations is used as the representative value for the volume. The number of standard deviations used can be defined in the custom.properties file. The default is one standard deviation. The representative values for volumes are grouped in buckets that can be defined in the Settings tab of SLO Monitoring. The buckets are ranges of values for response time group size and data transfer rate group size. The bucket upper limit is the miss threshold. For example, if the bucket size for the SLO response time is 5 ms, the system generates SLO profile recommendations with miss thresholds of 5 ms, 10 ms, 15 ms, and so on. The borderline threshold is the product of the miss threshold times a ratio set in the custom.properties file. When the calculation are performed the buckets display as SLO profile recommendations on the Recommendations tab of the SLO Monitoring window. You can schedule the recommendation calculations on the Settings tab of the SLO Monitoring window, where you can also generate calculations manually. For more information about the custom.properties file, refer to the Hitachi Command Director Installation and Configuration Guide Related tasks Accepting SLO profile recommendations on page 91 Related references Application SLO types on page 83 Managing application SLO profiles This module describes SLO profiles and SLO profile management tasks. Related tasks Accepting SLO profile recommendations on page Monitoring applications

85 Global SLO settings on page 100 About application SLO profiles A Service Level Objective (SLO) profile is a group of storage SLOs (threshold values) or service tier and is used to assign SLOs to applications to ensure that the application storage meets its objectives. When an application is assigned a SLO profile, the performance of its storage is monitored to ensure compliance with every SLO thresholds (borderline and miss) contained in its profile. When you assign a SLO profile to an application, you are configuring Hitachi Command Director to monitor that application for all the SLOs contained in its SLO profile. Note that SLO profiles must be created before they can be assigned to applications. Note: Due to the lack of performance details currently accessible for EMC systems, you cannot assign SLO profiles for EMC volumes. Default application SLO profile HCmD provides a default application SLO profile that includes the Average Storage Response Time SLO metric. You can assign this profile to any application to start monitoring the application. You can modify the default application SLO profile information but you cannot delete it. Preconfigured SLO profiles HCmD includes the following 15 preconfigured SLO profiles, which can be edited or deleted. They each use the Average Storage Response Time SLO metric Name Borderline/Miss Citrix_CMD_device RT: 12.0/15.0 Citrix_Mgmt_DB RT: 8.0/10.0 Citrix_OS_VM RT: 12.0/15.0 Citrix_Rep_DB RT: 8.0/10.0 Exchange_DB RT: 8.0/10.0 Exchange_Log RT: 4.0/5.0 Exchange_OS_VM RT: 12.0/15.0 Orace_ASM-data RT: 8.0/10.0 Orace_ASM_arch RT: 20.0/25.0 Orace_ASM_orah RT: 8.0/10.0 Monitoring applications 85

86 Name Borderline/Miss Orace_ASM_redo RT: 4.0/5.0 SQL_DB RT: 8.0/10.0 SQL_Log RT: 4.0/5.0 SQL_OS_VM RT: 12.0/15.0 SQL_Temp_DB RT: 8.0/10.0 Application SLO profile management notes When managing application SLO profiles, note the following: SLO profiles must have unique names. SLOs can only be assigned to applications by assigning SLO profiles. SLOs are subject to global monitoring settings, which can be fine-tuned for individual applications. Related tasks Viewing application SLO profiles on page 86 Creating application SLO profiles on page 88 Deleting application SLO profiles on page 91 Editing application SLO Profiles on page 90 Accepting SLO profile recommendations on page 91 Global SLO settings on page 100 Modifying a single application on page 143 Viewing application SLO profiles You can view every application SLO profile and its metrics. You can also see where each SLO profile is assigned. The SLO Profiles tab includes profiles created by users in addition to the Default SLO Profile, the Unmonitored profile and the preconfigured profiles included in Command Director. You can also view profiles that were generated by the system as SLO profile recommendations and then accepted (assigned). If a profile has been generated but not accepted, it will display on the Recommendations tab. If an SLO profile recommendation has been assigned and later unassigned, it will still display on the SLO Profiles tab. To view application SLO summary information: Procedure 1. Select the Administration tab. 86 Monitoring applications

87 2. Under Monitoring, click SLO Monitoring. Click the SLO Profiles tab if it is not already selected. Figure 4-1 SLO Profiles tab The SLO Profiles tab displays the following: Click New to add a new SLO profile in the New SLO Profile dialog. For more information, see Creating application SLO profiles on page 88. Click Delete Unused to delete any or all unused profiles in the Unused SLO Profiles dialog. For more information, see Deleting application SLO profiles on page 91. Profile Name: The name of the application SLO Profile. Click Edit to open the Edit SLO Profile dialog and change the name and metrics for the selected SLO profile. You cannot edit the profiles generated by the SLO Recommendation Settings on the Settings tab. For more information, see Global SLO settings on page 100 Beneath each profile name you can see the type of SLO(s) and the borderline and miss thresholds. Monitoring applications 87

88 For more information, see Editing SLO profiles on page 90. Click the Delete SLO Profile icon to delete the selected profile after confirming your choice. You cannot delete a profile that is assigned, the Default SLO Profile, or the Unmonitored profile. # Volumes: You can click a value in this column to open a volumes view of the SLO Profiles & Recommendations window, which includes all volumes associated with the selected SLO profile. You can use the view to accept SLO profile recommendations for individual or multiple volumes. For more information, see Updating SLO profiles for volumes on page 93. # Applications: Applications with volumes that are using the selected profile. You can click a value in this column to open the SLO profile >> Applications view of the SLO Profiles & Recommendations window. You can use this page to accept SLO profile recommendations for application volumes, or to access recommendations for volumes. For more information, see Updating SLO profiles for application volumes on page 96. # Pools: Pools with volumes that are using the selected profile. You can click a value in this column to open the SLO profile >> Pools view of the SLO Profiles & Recommendations window. You can use this page to accept SLO profile recommendations for pool volumes, or to access recommendations for volumes. For more information, see Updating SLO profiles for pool volumes on page 99. Click the New icon to add a new SLO profile in the New SLO Profile dialog. Related tasks Creating application SLO profiles on page 88 Editing application SLO Profiles on page 90 Deleting application SLO profiles on page 91 Accepting SLO profile recommendations on page 91 Global SLO settings on page 100 Creating application SLO profiles Application SLO profile definitions include the metrics you want to apply to the application, along with threshold values for each metric. After creating Service Level Objective (SLO) profiles, you can assign them to applications. To create a new application SLO profile: Procedure 1. Select the Administration tab. 88 Monitoring applications

89 2. Under Monitoring, click SLO Monitoring. Click the tab if it is not already selected. Available SLO profiles appear. After initial installation, a default SLO profile is created with default SLO settings and monitoring window, and this profile is assigned automatically to an application when it is created. 3. Click New. Figure 4-2 New SLO Profile dialog 4. Enter a unique name in the SLO Profile Name field. 5. Select SLO Metrics. Metrics that are not checked as Active SLOs on the Settings tab are unavailable. At least one threshold metric must be used in order to save your changes. The miss value must be greater than the borderline value for any selected metric. By default, Response Time and Data Transfer Rate are available and IOPS is unavailable. The default settings can be changed in the global SLO settings in the Settings tab. For more information, see Global SLO settings on page 100 Response Time: Enter Borderline and Miss values in milliseconds. Data Transfer Rate: Enter Borderline and Miss values in megabits per second. IOPS: Enter Borderline and Miss values. Note: For the Default SLO Profile, you can modify all information except the profile name. 6. Click Save to save the new profile. Result The information about the new SLO profile you created is added to the existing SLO profiles list in the SLO Profiles window. Monitoring applications 89

90 Related tasks Viewing application SLO profiles on page 86 Editing application SLO Profiles on page 90 Deleting application SLO profiles on page 91 Modifying a single application on page 143 Accepting SLO profile recommendations on page 91 Editing application SLO Profiles When your best-practice Service Level Objective (SLO) monitoring thresholds change, you can update your application SLO profiles. To modify the application SLO profile, you edit the SLO metrics to suit your SLO requirements. Procedure 1. Click the Administration tab and expand the Monitoring menu. Select SLO Monitoring. 2. Click the Edit SLO Profile icon next to the profile you want to edit to open the Edit SLO Profile dialog. 3. Edit the name if desired. At least one metric must be checked in order to save your changes. The miss value must be greater than the borderline value for any selected metric. By default, Response Time and Data Transfer Rate are available and IOPS is unavailable. The default settings can be changed in the global SLO settings in the Settings tab. Response Time: Enter Borderline and Miss values in milliseconds. Data Transfer Rate: Enter Borderline and Miss values in megabits per second. IOPS: This field is not available by default. Enter Borderline and Miss values. Note: For the Default SLO Profile, you can modify all information except the profile name. 90 Monitoring applications

91 4. Click Save to save your changes. Related concepts About application SLO profiles on page 85 Related tasks Viewing application SLO profiles on page 86 Creating application SLO profiles on page 88 Deleting application SLO profiles on page 91 Accepting SLO profile recommendations on page 91 Global SLO settings on page 100 Deleting application SLO profiles You can permanently delete Service Level Objective (SLO) profiles that are unassigned. If a profile is assigned, you can unassign it and the delete it. You cannot delete the Default SLO Profile or the Unmonitored profile. To delete SLO profiles: Procedure 1. Select the Administration tab. 2. Under Monitoring, click SLO Monitoring. Every SLO profile appears. 3. Select an SLO profile that displays zero in the # Volumes field, and click Delete SLO Profile. 4. In the confirmation dialog box, click Yes. Related concepts About application SLO profiles on page 85 Related tasks Viewing application SLO profiles on page 86 Creating application SLO profiles on page 88 Editing application SLO Profiles on page 90 Accepting SLO profile recommendations on page 91 Global SLO settings on page 100 Accepting SLO profile recommendations You can use the Recommendations tab to view all SLO profile recommendations. You can also access views of current SLO profile assignments. Monitoring applications 91

92 If desired, you can filter volumes by application or by pool. This enables you to easily select the volumes for which you want to view or change SLO profiles. SLO profile recommendations are system-generated, and based on historical performance data. Procedure 1. Click the Administration tab and select SLO Monitoring. In the SLO Monitoring window, select Recommendations. The table lists all SLO profiles by name. From this tab, you can access volumes filtered by recommended SLO profiles, and volumes sorted by applications or by pools. Figure 4-3 Recommendations tab 2. Choose one of the options below: Click a value in the # Volumes column to open a view of volumes for which the selected SLO profile is recommended. You can use the view to update SLO profiles at the volume level. For more information, see Updating SLO profiles for volumes on page 93 Click a value in the # Applications column to open a view of volumes by application for which the selected SLO profile is recommended. You can use the view to update SLO profiles for volumes in listed applications. 92 Monitoring applications

93 For more information, see Updating SLO profiles for application volumes on page 96. Click a value in the # Pools column to open a view of volumes by pool for which the selected SLO profile is recommended. You can use the view to update SLO profiles for volumes in listed pools. For more information, see Updating SLO profiles for pool volumes on page 99. Related concepts Understanding SLO profile recommendations on page 84 Managing application SLO profiles on page 84 Updating SLO profiles for volumes View and update SLO profiles for individual volumes. Command Director enables you to view and accept SLO profile recommendations for individual volumes, or select other SLO profiles. Access the volume details by SLO profile to view and choose recommendations. Procedure 1. Navigate to the Recommendations tab by selecting Administration, then SLO Monitoring under Monitoring. Monitoring applications 93

94 2. Choose one of the following options to display SLO profile recommendations for volumes. You can view volumes by SLO profile. You can also filter volumes by application or by pool, and then access details of the filtered volumes. Select an SLO profile recommendation in the Recommendation Name column and click the value in the # Volumes column to display details for volumes with the selected recommendation. Figure 4-4 Volumes filtered by SLO profile recommendation Fields available in the volumes view of the SLO Profiles & Recommendations window are described below. To access application volumes, start from the Recommendations tab and click a value in the # Applications column to open the SLO Profile >> Applications view of the window. For more information, see Updating SLO profiles for application volumes on page Monitoring applications

95 Figure 4-5 Volume details and SLO profile recommendations for a single application To access pool volumes, start from the Recommendations tab and click a value in the # Pools column to open the SLO Profile >> Pools view of the window. For more information, see Updating SLO profiles for pool volumes on page Choose whether to accept SLO profile recommendations. By default, all volumes that have a recommendation are selected in the check box column and the Other SLO Profiles column displays Accept Recommendation. You can click Save to apply all recommendations, or you can uncheck any volume to keep the existing profile. If you want to choose among other profiles, you can select an option in the drop-down list in the Other SLO Profiles column. If you are viewing volumes for a single application, you can check the Apply SLO profile To Existing and New Volumes check box to apply the recommended profile to all application volumes currently existing and created later. Note: Volumes in EMC storage systems are included in the volume details. Due to unavailability of performance data, SLO profiles cannot be assigned. The Existing Profile is listed as Unmonitored and the Other SLO Profiles field is disabled for these volumes. 4. You can use the #Total Volumes link to view all volumes for a selected application or pool and update the SLO profiles. If no SLO profile is recommended, you can choose among available Matching SLO Profiles or Other SLO Profiles in the Other SLO Profiles column. There are options available under Matching SLO Profiles only if there is a recommendation. Monitoring applications 95

96 Table 4-1 Fields available for volume details Column Check box Volume Volume Label Storage System Application Pool Pool Name Existing Profile Recommended Profile Other SLO Profiles Description You can select all volumes or none by using the check box in the header row. Click any check box to select the volume in that row. Volume ID Volume label specified in Device Manager. The field is blank if no label has been specified. Name of the storage system configured by Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number. The application to which the volume belongs. The pool ID. If the volume is not part of a dynamic provisioning pool, this field displays a hyphen. Pool name specified in Device Manager. If it is not specified in Device Manager, this field displays a hyphen. The SLO profile currently assigned to the volume. For every new application, a default SLO profile is assigned. For volumes in EMC storage systems, no SLO profile can be assigned due to unavailability of performance data. For such volumes, a hyphen is displayed. If you have accessed the window through a # Total Volumes link, the currently selected SLO profile (displayed in the window breadcrumbs) may not be recommended for all volumes. This field may display a different SLO profile. If there are other Matching SLO Profiles, you can select one from the list. You can also select from the list of Other SLO Profiles. Related concepts Understanding SLO profile recommendations on page 84 Related tasks Accepting SLO profile recommendations on page 91 Updating SLO profiles for application volumes View and apply SLO profile recommendations for volumes sorted by application. You can access recommendations for application volumes through either the SLO Profiles tab or the Recommendations tab. 96 Monitoring applications

97 Updating SLO profiles for application volumes through the SLO Profiles tab From the SLO Profiles tab, you can view all applications with volumes assigned a given SLO profile, and then accept recommendations, if desired. Navigate to Administration > Monitoring > SLO Monitoring. Select an SLO profile and click the # Applications column to open the <SLO profile> >> Applications view of the SLO Profiles & Recommendations window. This view includes the list of Applications assigned to the selected SLO profile. It also shows the # Volumes using the select SLO profile and the Total Volumes in Application. By default, all applications are selected. You can deselect all applications and then select one or more applications by using the checkbox column. Click Save to automatically accept all SLO profiles recommendations for all volumes in the selected application(s). You can click a value in the # Volumes using <SLO profile> column or the #Total Volumes in Application column to access and accept SLO profile recommendations for the volumes in each application. For more information, see Updating SLO profiles for volumes on page 93. Updating SLO profiles for application volumes through the Recommendations tab You can use the Recommendations tab to sort volumes with a selected SLO recommendation by applications and apply recommendations to all volumes in an application at once. To access application volumes through the Recommendations tab, navigate to Administration > Monitoring > SLO Monitoring. Click the Recommendations tab and select the SLO profile recommendation you want to view in the Recommendation Name column. Click the link for the selected SLO profile in the # Applications column. Monitoring applications 97

98 Figure 4-6 Volumes with a specific SLO profile recommendation, sorted by applications The SLO Profiles and Recommendations window displays the list of applications with volumes for which the selected SLO profile is recommended. By default, all applications are selected. You can click Save to apply the SLO to all volumes in the #Recommended Volumes column. You can also deselect any or all rows to avoid applying the recommended SLO profile. Click Save to save any changes. If you want to view and update profiles for the volumes at a more granular level, you can click any value in the #Recommended Volumes column or in the #Total Volumes to view volume details and SLO profile recommendations for a single application. For more information, see Updating SLO profiles for volumes on page 93. Related concepts Understanding SLO profile recommendations on page 84 Related tasks Accepting SLO profile recommendations on page 91 Related references Updating SLO profiles for pool volumes on page Monitoring applications

99 Updating SLO profiles for pool volumes View and apply an SLO profile recommendation for volumes sorted by pool. You can access SLO profile recommendations for pool volumes through either the SLO Profiles tab or the Recommendations tab. Updating SLO profiles for pool volumes through the SLO Profiles tab From the SLO Profiles tab, you can view all pools with volumes assigned a given SLO profile, and then accept recommendations, if desired. Navigate to Administration > Monitoring > SLO Monitoring. Select an SLO profile and click the # Pools column to open the <SLO profile> >> Pools view of the SLO Profiles & Recommendations window. This view includes the list of Pools assigned to the selected SLO profile and the Pool Name of each pool, along with the Storage System to which the pool belongs. It also shows the # Volumes using the select SLO profile and the Total Volumes in Pool. By default, all pools are selected. You can deselect all pools and then select one or more pools by using the checkbox column. Then click Save to automatically accept all SLO profiles recommendations for all volumes in the selected pool(s). You can click a value in the # Volumes using <SLO profile> column or the #Total Volumes in Pool column to access and accept SLO profile recommendations for the volumes in each pool. For more information, see Updating SLO profiles for volumes on page 93. Updating SLO profiles for pool volumes through the Recommendations tab You can use Command Director to sort volumes with a selected SLO recommendation by pools. Navigate to Administration > Monitoring > SLO Monitoring. Click the Recommendations tab and select the SLO profile recommendation you want to view in the Recommendation Name column. Click the link for the selected SLO profile in the # Pools column. Monitoring applications 99

100 Figure 4-7 Volumes with a specified SLO profile recommendation, sorted by pools The SLO Profiles & Recommendations window displays the list of pools with volumes for which the selected SLO profile is recommended. By default, all pools are selected. You can click Save to apply the SLO profile to all volumes in the #Recommended Volumes column. You can also deselect any or all rows to avoid applying the recommended SLO profile. Click Save to save any changes. If you want to view the volumes and update their SLO profiles at a more granular level, you can click any value in the #Recommended Volumes column or in the #Total Volumes to view volume details and SLO profile recommendations for a single pool. For more information, see Updating SLO profiles for volumes on page 93. Related concepts Understanding SLO profile recommendations on page 84 Related tasks Accepting SLO profile recommendations on page 91 Related references Updating SLO profiles for application volumes on page 96 Global SLO settings You can use global SLO settings to set the frequency of SLO profile recommendation generation and data ranges for each recommendation 100 Monitoring applications

101 generated. You can also select SLO types and windows, and set SLO violation notifications. The metrics for the SLOs are set when each SLO profile is created or edited. You can fine-tune settings for individual applications in the Resources tab. To access global SLO settings, click the Administration tab and select SLO Monitoring in the Monitoring menu. Click the Settings tab. Figure 4-8 Global SLO settings in the Settings tab SLO Recommendation Settings SLO recommendation settings create buckets for SLO recommendations, and set a floor for the minimum IOPS that is monitored. Use the SLO Recommendation Settings panel to update the following global settings: Provide Recommendations: Open the list to choose frequency of recommendation generation. The default setting is Every 4 Weeks. Select On Demand Only if you want recommendations to only be generated manually. You can click Recommend Now to generate recommendations immediately by running the algorithm used to create recommendations. Note: Changes made on the Settings tab must be saved before they become part of recommendations. Monitoring applications 101

102 Minimum IOPS: Enter the lowest IOPS value (between 0 and 9999) that will be used as to generate a recommendation. The default setting is 5. Data points with an IOPS lower than this value are identified as less busy data points, and are ignored when recommended SLO profiles are generated. Response Time Group Size: Enter a value between 0 and 9999 for the bucket size for the response time group size. The default setting is 5. The default will generate a bucket every 5 milliseconds. If you choose to monitor applications rather than volumes in SLO Monitoring Settings, the weighted average of response times for application volumes are used to determine thresholds for the resulting recommendations. Data Transfer Rate Group Size: Enter a value between 0 and 9999 for the bucket size for the data transfer rate group size. The default setting is 10. If you choose to monitor applications rather than volumes in SLO Monitoring Settings, the DTRs for application volumes are added together to determine thresholds for the resulting recommendations. SLO Monitoring Settings Use the SLO Monitoring Settings to select active SLOs, and choose whether to apply them to volumes or applications. Note: When SLOs are applied to volumes, the DTR SLO is only processed for sequential IO loads and the Response Time SLO is only processed for random or mixed IO loads. Active SLOs: Choose any combination of Response Time, Data Transfer Rate and IOPS. By default, IOPS is deselected. Any deselected options are unavailable when you create or edit SLO profiles. Evaluate SLOs on: Select Volume or Application. Select Volume to evaluate each volume separately. Each violation is propagated against the application. Volume is selected by default, because this option provides greater control and flexibility. If Application is selected, all volumes for a given application will have the same recommendation. Monitoring Window: Select the daily period, in half hour increments, to monitor SLOs. The default setting monitors 24 hours per day. Recurrence Type: Choose whether to monitor Daily, Weekly, or Monthly. The default setting is Daily. Recurrence Options: Choose days of the week or month to monitor. If Recurrence Type is Daily, no options are available. If Recurrence Type is Weekly, you select individual days of the week. If Recurrence Type is Monthly, you can choose to monitor on a selected day of each month, or to monitor on one ordinal day of one week every month. 102 Monitoring applications

103 SLO Violation Notification Settings Choose the trigger for violation notifications via and add address(es) to be notified. The default setting provides an alert for every SLO miss. You can also choose the number of misses per minute(s). If desired, enter one or more comma-separated addresses to be notified. Postrequisites Click Save to save any changes on the Settings tab. Related concepts SLO Investigation Unit on page 103 Modifying applications on page 143 Related tasks Accepting SLO profile recommendations on page 91 Managing application SLO profiles on page 84 SLO Investigation Unit This module describes the Service Level Objective Investigation Unit (SLO IU), accessing the SLO IU, and interpreting the data from the SLO IU. HCmD also provides you with an Application Volume SLO Conformance Details report as a CSV file that includes SLO conformance details of the provisioned volumes over a period of time. This information helps you to analyze the application SLO conformance data by reviewing the SLO conformance details of its provisioned volumes over a period of time. Related references Application volume SLO conformance details (CSV only) on page 289 About SLO Investigation Unit The SLO Investigation Unit enables you to understand at a glance any problems with your application or volumes allocated to the application. It also provides you with the ability to quickly isolate applications with SLO violations and analyze the violation in depth to address them quickly and early. Note: SLO profile monitoring is not supported for EMC volumes, as indicated by "Unmonitored". Monitoring applications 103

104 SLO IU Report display notes If the application has been recently created, you may not have enough data to investigate. The storage system performance reports will not display new data when storage systems are disabled. Even after they are enabled and data collection resumed, the performance data will not be displayed for a few data points. For more information about enabling or disabling storage systems, see Enabling and disabling storage systems on page 328. The SLO Investigation Unit includes an SLO profile selector, time slider, a summary pane, and four tabular reports that provide in depth information about a specific application: SLO profile selector The SLO profile selector lists SLO profiles of all volumes allocated to an application, and enables you to select SLO profile one at a time to view application details and analyze SLO performance. Data Time time slider The time slider shows the current data point and lets you select any previous data point to analyze the application at that point in time. Summary pane Displays a summary about the SLO miss for the application, and for the selected SLO profile and time period. 104 Monitoring applications

105 Name: The name of the application. Created: The date/time when the application was created. Total Storage: The total storage capacity. # Volumes: The number of volumes allocated to the application. SLO Status: Displays if the SLO status has been met for the investigation time. Avg Response Time: The response time for all volumes assigned to the selected SLO profile. Total IOPS: Total IOPS of all the volumes assigned to the selected SLO profile. Total DTR: Total Data Transfer Rate of all the volumes assigned to the selected SLO profile. IOPS Distribution: Application vs. Storage System report The IOPS Distribution report enables you to quickly compare the IO operations per second (IOPS) of the application, application ports (ports where the application is sharing with other applications), and storage system to view the impact the application has on the storage system and ports. If the application is taking up a lot of bandwidth in the shared application ports or entire storage system, you may want to consider providing additional bandwidth for the application elsewhere. Monitoring applications 105

106 This report includes the following information: Storage System: Name of the storage system configured by Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). For EMC systems, this is the name of storage system configured by SMI-S Provider (for example, SYMMETRIX ). Model: The storage system model type. All Ports IOPS: Total IOPS for all the ports in the storage system. For example, if the storage system has 5 ports with 200 IOPS each, then the total IOPS for all ports is 1,000. App Ports IOPS: Total IOPS for the storage system ports the application is using. For example, if application A uses port 1 (200 IOPS) and port 2 (200 IOPS), then the value of this field is 400. App IOPS: Total IOPS for all the volumes allocated to the application. For example, if from the set IOPS of 200 each for port 1 and port 2, application A uses 150 IOPS on port 1 and 100 IOPS on port 2, the IOPS for this application is the sum of IOPS on both ports which is 250. App vs. All Ports: The ratio of total IOPS for all volumes allocated to the application to the Total IOPS for all ports in the storage system. For example, if the App IOPS for application A is 250 and the All Ports IOPS is 1000, the App vs. All Ports is 250/1000 which is 25%. App vs. App Ports: The ratio of total IOPS for all volumes allocated to the application to the Total IOPS for the storage system ports the application is using. For example, if the App IOPS for application A is 250 and the App Ports IOPS is 400, the App vs. App Ports is 250/400 which is 62.5%. DTR Distribution: Application vs. Storage System report The DTR Distribution report enables you to quickly compare the data transfer rate (DTR) and its throughput performance generated by the application, 106 Monitoring applications

107 application ports (ports where the application is sharing with other applications), and storage system to view the impact the application has on the storage system and ports. If the application is taking up a lot of bandwidth in the shared application ports or entire storage system, you may want to consider providing additional bandwidth for the application elsewhere. This report includes the following information: Storage System: Name of the storage system configured by Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). For EMC systems, this is the name of storage system configured by SMI-S Provider (for example, SYMMETRIX ). Model: The storage system model type. All Ports DTR: Total DTR for all the ports in the storage system. App Ports DTR: Total DTR for the storage system ports the application is using. App DTR: Total DTR for all the volumes allocated to the application. App vs. All Ports: The ratio of total DTR for all volumes allocated to the application to the Total DTR for all ports in the storage system. App vs. App Ports: The ratio of total DTR for all volumes allocated to the application to the Total DTR for the storage system ports the application is using. Connected Ports The Connected Ports report lists a set of ports connected to the application. Looking at the performance of these connected ports may indicate a potential cause of the application SLO miss. You can utilize this report to quickly determine if a particular connected port is oversaturated that may have caused the SLO miss or violation. If there are Monitoring applications 107

108 multiple ports you can also determine if there is any workload imbalance among ports, for example, one port is much busier than others. This report includes the following information: Storage System: Name of the storage system configured by Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). For EMC systems, this is the name of storage system configured by SMI-S Provider (SYMMETRIX ). Model: The storage system model type. Port: The storage system port name. For EMC systems, this is the Front End port. IOPS: IOPS for the port. DTR: DTR for the port. Processor: The back-end processor serving the port. Busy%: The percentage of time the processor is busy serving IO requests. Note: Performance data is not available for third-party storage and this field will contain a hyphen (-). Volume List The Volume List report lists all the application volumes assigned to the selected SLO profile. You can use this report to view the SLO status of each Application SLO profile associated with the volumes and also check their conformance to the SLO profile in the past 24 hours. From this report, you can also identify the tier information of each volume. If the volume is in violation of the monitored SLO, you may want to check the tier that includes this volume and consider promoting it to a higher tier. However, the tier data will not be available if you have not configured Tiered Storage Manager. 108 Monitoring applications

109 This report includes the following information: Volume: Volume ID. Click this link to display the performance report for this volume in Hitachi Tuning Manager. This report displays historical information for the past two hours only. For more information about this report and how to set the report display conditions, access the online help available in the report window or see the Hitachi Command Suite Tuning Manager User Guide. To understand the prerequisites to successfully launch the volume report in Tuning Manager and use it, see the related topic on Tuning Manager report display notes in the. Volume Label: Volume label specified in Device Manager. If it is not specified, this field displays a hyphen. Status: SLO status of the volume for the monitored metric. Storage System: Name of the storage system configured by Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). For EMC systems, this is the name of storage system configured by SMI-S Provider (for example, SYMMETRIX ). Model: Storage system model type. Parity Group: The name of the parity group that includes the volume. For EMC systems, this is the Disk-Group. Pool: The pool ID. If the volume is not part of a dynamic provisioning pool, this field displays a hyphen. Note: For EMC systems, the pool ID is not provided. Pool Name: Pool name specified in Device Manager. If it is not specified in Device Manager, this field displays a hyphen. Capacity: Capacity of the volume. Tier: Storage tier of the volume. This column will display a hyphen if Tiered Storage Manager is not configured. Tuning Manager report display notes You can display the Tuning Manager report only when Device Manager and Tuning Manager that connect to the same storage systems are configured Monitoring applications 109

110 in the same HBase (Hitachi Base). If they are not, an error will be displayed when you launch the performance report. To successfully launch the performance report in Tuning Manager, make sure the Storage System Collectors for Device Manager and Agent for RAID in Command Director are enabled. To verify this, see Viewing information about Storage System Collectors on page 315. If at any time the Storage System Collectors are disabled or deleted, then the performance report launched for the selected volume will display an error message. However, for an already open performance report for any volume, you will be able to refresh or update the report. Enable the Storage System Collectors, or add them again if they are deleted. The Tuning Manager performance report window session remains active for 1,000 seconds, and then times out. To relaunch the report, close the active browser window of the Tuning Manager performance report, and then select the volume ID link in the Volumes List report. Changes to user profiles in Device Manager can affect the accessibility of the Tuning Manager report. If your user password has changed or the permission to launch Tuning Manager report is revoked, the Tuning Manager report is accessible to you for 15 minutes, and then the session is terminated. After you synchronize user accounts in Command Director, you must wait up to 15 minutes before accessing the Tuning Manager report again. If your account is locked, you will obtain an error message in the report window indicating an invalid session. After the lock has been removed, you must wait up to 15 minutes before accessing the Tuning Manager report again. Related concepts About application SLO profiles on page 85 Related tasks Accessing the SLO Investigation Unit from the Dashboard on page 110 Accessing the SLO Investigation Unit from the Resources tab on page 111 Accessing the SLO Investigation Unit from the Dashboard By accessing the SLO Investigation Unit from the Dashboard, you can quickly identify the potential cause of Application SLO violation by looking at key storage components performance used by the application. Procedure 1. Select the Dashboard tab. 2. Click any of the SLO missed or borderline links one of these reports to display the Application SLO Details report: 110 Monitoring applications

111 Response Time SLO Status IOPS SLO Status DTR SLO Status 3. Click the Application hyperlink of interest to display the SLO Investigation Unit. Related concepts About SLO Investigation Unit on page 103 About application SLO profiles on page 85 Accessing the SLO Investigation Unit from the Resources tab By accessing the SLO Investigation Unit from the Resources tab, you can quickly identify the potential cause of Application SLO violation by looking at key storage components performance used by the application. Procedure 1. Select the Resources tab. 2. Select the business view that contains the application you are monitoring. 3. From the appropriate folder in your business view, select the application. A list of standard reports for the selected application appears in the Content pane. 4. View the SLO Profile Details report and click the SLO Profile (link) of interest to display the SLO Investigation Unit. Related concepts About SLO Investigation Unit on page 103 About application SLO profiles on page 85 Monitoring applications 111

112 112 Monitoring applications

113 5 Monitoring infrastructure The Admin user role is required in order to monitor storage systems and hosts. Monitoring storage systems Monitoring hosts Monitoring infrastructure 113

114 Monitoring storage systems This module describes storage system health thresholds and related management tasks. Storage system health thresholds Storage system health monitoring leverages Hitachi best practice performance thresholds to ensure that your storage system performs optimally. Storage system health can be monitored and evaluated by measuring the four corresponding resource types (cache, parity group, pool, and processor). Each resource type has the following specific data metrics that are monitored: Cache: Write Pending % Parity group: Busy % Pool: Capacity utilization %, over provisioning ratio, and risk ratio Processor: Busy % The storage system is considered healthy if the utilization remains below best practice thresholds. While storage system health evaluates overall system health, you can also view the health of storage system resources used by any application, host, or folder. This allows you to quickly determine which applications, hosts, and folders may have performance problems. Information Technology (IT) departments are experiencing dwindling resources and escalating workloads. Typically, when a storage system utilization or performance problem occurs, there are not enough resources to quickly troubleshoot and fix the problem. However, Hitachi Command Director storage system health monitoring can proactively alert you to these problems. Related tasks Storage system monitoring settings on page 121 Assigning monitoring profiles to storage systems on page 119 Managing storage system monitoring profiles on page 114 Related references Data metrics in storage system monitoring profiles on page 118 Managing storage system monitoring profiles This module provides information about how to create a new storage system monitoring profile, or modify or delete an existing storage system monitoring profile that you created. 114 Monitoring infrastructure

115 Related concepts Storage system health thresholds on page 114 Related tasks Assigning monitoring profiles to storage systems on page 119 Storage system monitoring settings on page 121 Viewing storage system monitoring profiles You can view the current set of storage system monitoring profiles in the Storage System window, which is also the starting point for creating new storage system monitoring profiles, and modifying or deleting existing profiles that you created. Procedure 1. Click the Administration tab. 2. Under Monitoring in the Administration pane, select Storage System to open the Storage System window. Figure 5-1 Storage System Monitoring Profiles The Profiles tab in the Storage System window lists the current set of storage system profiles by name, the resource type associated with each profile (cache, parity group, pool, or processor), the number of resources associated with each profile, and is where you can launch the Assigning Monitoring Profile window. The Default Settings tab lists the storage systems by type, the currently associated profile for each resource type, and is where you can update the profiles for the storage system resource types. Related tasks Creating a storage system monitoring profile on page 116 Modifying a storage system monitoring profile on page 117 Deleting a storage system monitoring profile on page 117 Related references Data metrics in storage system monitoring profiles on page 118 Monitoring infrastructure 115

116 Creating a storage system monitoring profile You can create a new storage system monitoring profile by entering a profile name, selecting a resource type, and setting monitoring metrics that are different from the system-created default profiles. Procedure 1. Click the Administration tab. 2. Under Monitoring in the Administration pane, select Storage System to open the Storage System window. 3. Click the Profiles tab, and click New. 4. In the New Monitoring Profile window, enter a name for the new profile in Profile Name. 5. In Resource Type, select the appropriate resource type (cache, parity group, pool, or processor). The corresponding metrics differ based on the resource type you selected: Cache (Write Pending % - warning and critical thresholds) Parity Group (Busy % - warning and critical thresholds) Pool (Pool Capacity Utilization %, Over Provisioning Ratio, and Risk Ratio - warning and critical thresholds) Processor (Busy % - warning and critical thresholds) 6. In Monitoring Metric, enter the values for the Warning and Critical thresholds (accepted range is from 1%-99%). 7. Click Save to save the settings for the new storage system profile (or click Cancel to reset any unsaved settings). 8. Click OK in the Information confirmation dialog box. Related tasks Figure 5-2 Creating a Storage System Monitoring Profile Deleting a storage system monitoring profile on page 117 Modifying a storage system monitoring profile on page 117 Viewing storage system monitoring profiles on page Monitoring infrastructure

117 Related references Data metrics in storage system monitoring profiles on page 118 Modifying a storage system monitoring profile You can only modify the profile name and monitoring metrics for a storage system monitoring profile that you created. Note: You cannot modify the Profile Name for any of the five default storage system profiles included in Command Director. You cannot change the Resource Type for any existing storage system monitoring profile. Procedure 1. Click the Administration tab. 2. Under Monitoring in the Administration pane, select Storage System to open the Storage System window. 3. Click the Profiles tab. 4. In the Storage System Profiles window, select the storage system profile that you want to modify. 5. Click the Edit the Monitoring Profile icon. 6. Rename the profile in Profile Name or revise the Warning or Critical threshold values. 7. Click Save to save the settings for this modified storage system profile (or click Cancel to reset any unsaved settings). 8. Click OK in the Information confirmation dialog box. Related tasks Figure 5-3 Modifying a Storage System Monitoring Profile Creating a storage system monitoring profile on page 116 Deleting a storage system monitoring profile on page 117 Viewing storage system monitoring profiles on page 115 Deleting a storage system monitoring profile Monitoring infrastructure 117

118 Note: You cannot delete any of the five default storage system profiles that are created by Command Director. Procedure 1. Click the Administration tab. 2. Under Monitoring in the Administration pane, select Storage System to open the Storage System window. 3. Click the Profiles tab. 4. In the Storage System Profiles window, select the storage system profile that you want to delete. 5. Click the Delete the Monitoring Profile icon if it is enabled. Note: If the storage system profile is in use, the Delete the Monitoring Profile icon is disabled and the profile cannot be deleted until its associated resources are assigned to another profile. You can only delete a storage system monitoring profile that you created. 6. If the profile you want to delete is the default profile for the selected resource type, click Yes in the Profiles dialog box to delete the selected profile (or click No to cancel deletion and return to the Storage System Profiles window). Note: Deleting the default profile will reset the resource type to use the appropriate system-created profile. 7. Click OK in the Profiles confirmation dialog box. Related tasks Creating a storage system monitoring profile on page 116 Modifying a storage system monitoring profile on page 117 Viewing storage system monitoring profiles on page 115 Related references Data metrics in storage system monitoring profiles on page 118 Data metrics in storage system monitoring profiles Storage system monitoring profiles include warning and critical threshold levels for all resource types, and generate alerts when the thresholds are exceeded. The values that you set in the profiles you create depend on the type of resource type being monitored in the storage system. The following table lists resource types and monitored data metric settings in storage system profiles. 118 Monitoring infrastructure

119 Resource Type Monitored Data Metric Cache Parity Group Write Pending %, which is the percentage of CLPR (Cache Logical Partition) data that is currently being written to the storage system disk. Busy %, which is the percentage that is currently engaged in parity group read and write operations for the storage system. Pool Capacity Utilization %, which is the current pool capacity usage percentage rate (in relation to the total actual pool capacity). Over Provisioning Ratio, which is the current total managed pool capacity (in relation to total actual pool capacity). Risk Ratio, which is the current total managed used capacity (in relation to total actual used capacity). Processor Busy %, which is the percentage of the processor that is currently engaged in port microprocessor operations for the storage system. The Profiles tab displays the current profile names, resource type, and number of resources used by the profile. Command Director generates five default storage system profiles with these settings: Default Cache Profile, configured with write pending threshold levels (warning at 55% and critical at 70%). Default Parity Group Profile, configured with busy threshold levels (warning at 50% and critical at 70%). Default Pool Profile, configured with three sets of threshold levels (capacity utilization warning at 70% and critical at 80%, over provisioning ratio warning at 1 and critical at 3, and risk ratio warning at 1 and critical at 3). Default Processor Profile, configured with busy threshold levels (warning at 40% and critical at 70%). Unmonitored host profile, with no configured threshold levels. Related tasks Viewing storage system monitoring profiles on page 115 Creating a storage system monitoring profile on page 116 Modifying a storage system monitoring profile on page 117 Assigning monitoring profiles to storage systems Assign a specific storage system monitoring profile to a specific storage system. Command Director allows you to selectively assign a default monitoring profile for subsequent use in storage system cache, parity groups, pools, or Monitoring infrastructure 119

120 processors settings. In addition, you can selectively update any existing storage system cache, parity group, pool, or processor resource to use a different default monitoring profile. You can assign the profiles created by Command Director or assign profiles that you created. Note: Any profile you assign to a resource type becomes the default. For example, if you create a custom cache profile and assign it to a VSP G1000 system, all other VSP G1000 systems will use this as the default cache profile until you assign one or more systems to use a different profile. Procedure 1. Select the Administration tab, and under Monitoring, select Storage System to open the Storage System window. 2. Click the Profiles tab, and click the entry in the # Resource column to view all associations with the selected monitoring profile. The Assign Monitoring Profile window opens for the selected monitoring profile, and lists storage systems with matching profiles. Figure 5-4 Assigning Storage System Monitoring Profiles 3. In the Assign Monitoring Profile window, there are three options that you can use to filter a storage system profile (type, profile, and view). These options affect the storage system profile you can select (the current Storage System Profiles values list by default). Option Description Type Select a resource type (cache, parity group, pool, or processor) from the available choices. Profile Select a profile type (system-generated or ones you created) from the available choices. The Profile list is populated based on the resource type that was selected (for example: if you created a new cache profile, only cache-related profile choices are listed under Assign). View Select a storage system type from the available choices. The View list is populated based on the resource type that was 120 Monitoring infrastructure

121 Option Description selected (for example: if you created a new pool profile, only pool-related profile choices would be listed under Assign). 4. Click Apply after you select your type, profile, and view choices in the lists above the table to display the entries that match these selections. The table columns list details about each storage system entry in the list, such as Name and IP address, Model, # Parity Groups (or CLPRs), and the Monitoring Profile in use. The content of these columns will vary depending on the type, profile, and view selections that you make. Note: Only the Storage System and Model column headers in this table allow you to sort the values in ascending or descending order. 5. (Optional) To refine the number of entries for which monitoring needs to be enabled or thresholds changed, enter alphanumeric text in the Search text box, and click Search (or click Clear to clear the text box). 6. Select one or more row entries in the Assign Monitoring Profile table (using Shift+select or Ctrl+select) to which you want to assign a storage system monitoring profile. 7. In the Assign list, select the storage system monitoring profile, and click Apply to apply it to the entries you selected (or click Apply All to apply the profile to all entries on the page). Note: Assigning a profile to the selected storage system resource will assign it to all matching storage system resources. You can reassign individual storage system resources to use other profiles or update all storage system resources to use one profile by your use of Apply or Apply All. 8. Click Save to configure the selected storage system monitoring profile for the selected entries (or click Reset to clear all settings and return it the previous values). Related concepts Storage system health thresholds on page 114 Related tasks Storage system monitoring settings on page 121 Managing storage system monitoring profiles on page 114 Storage system monitoring settings Use a specific default storage system monitoring profile to configure and monitor all new storage systems that are added. You can also update the storage system monitoring profile being used in any of the existing storage systems. Monitoring infrastructure 121

122 The Default Settings tab displays the storage systems, the current profiles in use, and is where you associate a storage system monitoring profile to use for the respective cache, parity group, pool, or processor resource types in all new storage systems. For example, the following table lists some supported storage systems and the corresponding monitoring profiles that they use. Storage Systems VSP G1000, VSP, and HUS VM USP V/VM, USP, HUS, and Hitachi Adaptable Modular Storage (AMS) 2000 family of storage systems Symmetrix VMAX Monitoring Profiles Used Cache, Parity Group, and Pool Cache, Parity Group, Pool, and Processor Pool The selected profiles and the storage system type define the settings for all new cache, parity group, pool, and processor resource types in storage systems. In addition, you can also update any existing storage system and its corresponding resource types to use the supported profiles that you select. Note: Any profile you assign to a resource type becomes the default. For example, if you create a custom cache profile and assign it to a VSP G1000 system, all other VSP G1000 systems will use this as the default cache profile until you assign one or more systems to use a different profile. Procedure 1. Select the Administration tab. Under Monitoring, select Storage System to open the Storage System window. 2. Click the Default Settings tab to view and assign profiles for the cache, parity group, pool, and processor resource types for all new storage systems, and update any existing storage system with the monitoring profile that you select. Note: All storage systems use cache, parity group, and pool profiles, and selected storage systems also require a processor profile. To configure a new cache, parity group, pool, or processor profile to use in a storage system, in the Default Settings window, select the profile in the Profile list that you want to use for each corresponding storage system resource type. To update an existing storage system to use a specific cache, parity group, pool, or processor profile: 1. In the Default Settings window, select the profile in the Profile list that you want to use to update each corresponding resource type in an existing storage system. 122 Monitoring infrastructure

123 2. Select the Update Existing check box that corresponds to each profile that you want to update. 3. Click Save to use the selected monitoring profiles for all new storage systems or to update the existing storage systems with the new selected profiles (or click Reset to reset the unsaved settings). Figure 5-5 Storage System Profile Default Settings Monitoring hosts This module describes how to monitor hosts by using profiles. Managing host monitoring profiles on page 123 Assigning monitoring profiles to hosts on page 125 Host monitoring settings on page 127 Managing host monitoring profiles Create a new host monitoring profile, modify an existing host monitoring profile, or delete an existing host monitoring profile that you created. Host monitoring profiles track the capacity percentage being used in hosts, which are based on the warning and critical threshold levels set in the profile that alert when these capacity levels are exceeded. The Profiles tab displays current profile names, the number of host filesystems, the number of VM instance filesystems, the number of Hitachi NAS Platform (HNAS) filesystems, the number of VMware datastores, and the Monitoring infrastructure 123

124 number of HNAS pools. By default, Command Director provides two systemgenerated profiles: Note: You cannot delete the system-generated profiles (Default and Unmonitored). Default Host Profile, configured with two capacity utilization threshold levels: warning at 55% and critical at 80%. Unmonitored host profile, with no configured capacity utilization threshold levels. Procedure 1. Select the Administration tab. Under Monitoring, select Host to open the Host window. In the Host window, you can: Create a new host monitoring profile Modify an existing host monitoring profile Delete an existing host monitoring profile 2. To create a new host monitoring profile: a. Click the Profiles tab. b. Click New. c. In the New Monitoring Profile window, enter a name for the new profile in Host Profile Name. d. In Capacity Utilization %, enter a percentage threshold in Warning (for example, 50) and in Critical (for example, 85). e. Click Save to save the settings for the new host profile (or click Reset to reset any unsaved settings). f. Click OK in the Settings confirmation dialog box. 3. To modify an existing host monitoring profile: a. Click the Profiles tab. b. In the Host Profiles window, select the existing host monitoring profile that you want to modify. c. Click Edit the Monitoring Profile. d. Rename the profile in Host Profile Name or revise the Warning or Critical thresholds with new values. e. Click Save to save the settings for the modified host profile (or click Reset to reset any unsaved settings). f. Click OK in the Settings confirmation dialog box. 4. To delete an existing host monitoring profile: a. Click the Profiles tab. b. In the Host Profiles window, select the existing host monitoring profile that you want to delete. c. Click Delete the Monitoring Profile if enabled. 124 Monitoring infrastructure

125 Note: If the host profile is in use, Delete the Monitoring Profile is disabled and the profile cannot be deleted until its associated host resources are assigned to another profile. A status message displays prompting whether you want to delete the profile if the selected profile is set as the default for the selected resource type. Deletion will reset the default profile to be the default profile for that resource type. d. Click Yes to delete the selected profile. e. Click OK in the Profiles confirmation dialog box. Related tasks Assigning monitoring profiles to hosts on page 125 Host monitoring settings on page 127 Assigning monitoring profiles to hosts Assign a specific host monitoring profile to a specific host resource. Command Director provides flexibility in selecting and assigning a host monitoring profile only to AIX, HP-UX, Windows, Solaris, or Linux file systems. Note: Any profile you assign to a host resource becomes the default. For example, if you create a custom capacity utilization % profile and assign it to a host resource, all other host resources will use this as the default capacity utilization % profile until you assign one or more host resources to use a different profile. Procedure 1. Select the Administration tab. Under Monitoring, select Host to open the Host window. Monitoring infrastructure 125

126 2. In the Host Profiles table, click on the hyperlink in the # FS Host, # FS VM instance, # FS HNAS, # Datastore, or # HNAS Pool columns that corresponds to the host resource to which you want to assign a monitoring profile. Note: When you click a column hyperlink, the Assign Monitoring Profile dialog displays, and the Profile, Type, and View options that are available to use when assigning a profile depend on the hyperlink type that you selected. The current values in the Host Profiles table display by default (with 0 being the default when no host is added using Host collector). Figure 5-6 Assign Monitoring Profile 3. In the Profile list, select a profile type from the available choices (for example: Default Host Profile, and Unmonitored, or any host profiles that you created). 4. In the Type list, select a host resource type from the available choices (for example: AIX, HP-UX, Windows, Solaris, or Linux). 5. In the View list, select either Host or Filesystem. Your selection lets you view entries at different resource levels: Host displays a host-level list associated with the profile, while Filesystem displays a detailed file system-level list associated with the profile. 6. Click Apply to display the selected entries that match the selections you made in the Assign Monitoring Profile table. The Assign Monitoring Profile table lists details about the selected resources in columns (for example: host name, host type, IP address, number of file systems, number of file systems using the selected profile, and the profile in use), and these columns will vary depending on the host type and view that you selected. 126 Monitoring infrastructure

127 Note: Click the Host Name and Host Type column headers to sort the values in ascending or descending order in the Assign Monitoring Profile table. 7. (Optional) To refine the number of entries for which monitoring needs to be enabled or thresholds changed, enter alphanumeric text in the Search text box, and click Search (or click Clear to clear the text box). 8. Select one or more row entries in the Assign Monitoring Profile table (using Shift+select or Ctrl+select) to which you want to assign a host monitoring profile. 9. In the Assign list, select the host monitoring profile, and click Apply to apply it to the selected entries (or click Apply All to apply the profile to all entries on the page). Note: Assigning a profile to the selected host resource type will assign it to all matching resources. You can reassign individual resources to use other profiles or update all resources to use one profile by your use of Apply or Apply All. 10. Click Save to configure the selected host monitoring profile for the selected entries (or click Reset to clear all settings and return it the previous values). An Information dialog box indicates that the assigned monitoring profile was successfully updated. 11. Click OK. The assigned entries associated with the selected profile no longer appear in the Assigned Monitoring Profile dialog box. To view these same assigned entries in the Assigned Monitoring Profile dialog box, adjust the Profile, Type, and View selections accordingly. Related tasks Managing host monitoring profiles on page 123 Host monitoring settings on page 127 Host monitoring settings Use a specific default host monitoring profile to configure all new VMware datastores, file systems, and file servers that are added. You can also update the host monitoring profile being used in any of the existing host resource types. The Default Settings tab displays the file system, datastore, and file server types, the current profile in use, and is where you can associate a host monitoring profile for each host resource type. The selected profile defines the settings for all new VMware datastores, file systems, and file servers. In addition, you can also update any existing host resource type to use the profile that you select. Monitoring infrastructure 127

128 Procedure 1. Select the Administration tab. Under Monitoring, select Host to open the Host window. 2. Click the Default Settings tab to view and assign default host profiles for all new file system, datastore, and file server types, and update any existing file system, datastore, and file server with any host profile that you select. To configure a new file system, VMware datastore, or file server to use a specific host profile: In the Default Settings window, select the default host profile to use for each of the corresponding host resource types (file system, VMware, and file server) in the Profile list. To update an existing file system, VMware datastore, or file server to use a specific host profile: In the Default Settings window, select the host profile to use to update each of the existing host resource types (file system, VMware, and file server) in the Profile list. Select the Update Existing check box that corresponds to each profile being updated. 3. Click Save to use the selected monitoring profile for all new host resources or to update the existing host resources with the new selected profile (or click Reset to reset the unsaved settings). 128 Monitoring infrastructure

129 4. Click OK in the Settings confirmation dialog box. Related tasks Figure 5-7 Host Monitoring Settings Managing host monitoring profiles on page 123 Assigning monitoring profiles to hosts on page 125 Monitoring infrastructure 129

130 130 Monitoring infrastructure

131 6 Working with applications This module describes how to create and configure applications for Hitachi Command Director usage. About applications Application elements Configuring applications Working with applications 131

132 About applications An application in Hitachi Command Director (HCmD) is a representation of an actual application running on a host. It represents groups of storage volumes used by an actual application, which can be an application in your business environment such as a payroll application in your division or a marketing website. An application can be defined by volumes that belong to a host group or by storage consumed by a physical host discovered by the Hitachi Command Director agentless host collector. By default, every application in Hitachi Command Director has a default SLO profile and default Monitoring window assigned to it. You can define different SLO profiles for different volumes of the application. For example, Oracle database volumes require better response time SLO than the log volumes that require more serial read/write, and therefore requires less response time SLO for the same Oracle application. The Admin user role is required in order to create, manage, modify, or delete applications. Related concepts Application elements on page 132 Configuring applications on page 133 Application elements An application can include the following elements: Tag association: Application has to be tagged to indicate its usage. Once tagged, the application shows up in relevant business views that use the related tag categories. Application storage: Application must be assigned a storage through host (discovered through HDC) or LUN Owner. After the storage is assigned, you can view various storage-related reports on the application or monitor the storage performance for the application using a service level objective (SLO). For more information about LUN Owner, see the glossary at the end of this guide. SLO assignments and monitoring windows: Service Level Objective (SLO) profiles are assigned to an application or application volumes so that you can monitor the application s performance based on desired thresholds. For every new application, a default SLO profile is assigned. You can modify this default profile. You can also create new SLOs and assign them to volumes allocated to the application. SLOs can only be assigned to applications through SLO profiles. When assigning SLO profiles, you are 132 Working with applications

133 also specifying monitoring windows that identify when the application is monitored for the SLO. SLO notifications: Hitachi Command Director sends alerts when missed and borderline Service Level Objective (SLO) violations occur during the monitoring window. SLO violation alerts can be sent to anyone who is configured to receive the notification for a given application and are not limited to Command Director user accounts. Configuring applications This module describes how to configure applications for Hitachi Command Director usage. Application configuration is available to users with the Admin role. Related concepts About applications on page 132 Application creation process flow The following graphic illustrates the flow for creating applications in Hitachi Command Director. Working with applications 133

134 Related concepts Figure 6-1 Application creation process flow Modifying applications on page 143 Related tasks Creating applications manually on page 135 Managing untagged applications on page Working with applications

135 Application notes Deleting applications on page 152 Related references Application notes on page 135 Note the following: Every application must have a unique name. Application storage is automatically updated when additional volumes are pathed through the host or LUN Owner in Hitachi Device Manager. Storage allocation and trends are based on the volumes provisioned to the application through assigned hosts or host groups. Same application can reside in multiple business views. You cannot assign the following types of storage to applications: Command Device DP-POOL VOL: Volumes created from Dynamic Pool S-VOL: Secondary Volume V-VOL: Virtual Volume LUSE volume: Logical Unit Size Expansion LUSE volume, which is not a HEAD Volume JNL-VOL: Journal Volume iscsi volume: Volume exported using the iscsi protocol Related concepts Application creation process flow on page 133 Modifying applications on page 143 Related tasks Creating applications manually on page 135 Managing untagged applications on page 142 Deleting applications on page 152 Creating applications manually You can create applications manually in a custom business view. When you create an application in Hitachi Command Director (HCmD), you are creating a representation of an actual application running on a host. Manual application creation is available only to users with the Admin role. Creating an application includes assigning tags to the application, specifying users who are notified when SLO violations occur, associating storage to the application, and assigning an SLO profile to monitor the application. Before you create a new application: Choose to enable or disable automatic creation of applications. Working with applications 135

136 Applications are created automatically when you set the auto-create application option ( Administration tab > System Settings & Operations > Application Settings) to Logical Group, LUN Owner, or Host. When any of these options, except the Logical Group is set, you can create applications manually. To create applications manually, disable the automatic creation of applications by selecting None in the Application Settings window. Decide what storage you want to assign to the application. You can assign storage to the application from the discovered hosts or LUN Owner information. To assign storage on hosts, configure Host Collectors and Storage System Collectors. To assign storage using the LUN Owner information, configure only the Storage System Collectors. For information about configuring Host Collectors, see the following topics: Enabling host discovery and data collection on page 334 Configuring Storage System Collectors on page 319 Review Application notes on page 135. Procedure 1. On the Resources tab, select the business view where you are creating the application. 136 Working with applications

137 2. On the Action menu, select Create Application. Figure 6-2 Manage Application window: Assign Storage tab 3. In the Manage Application (Application Name) box, enter the application name not exceeding 256 characters and click Save. 4. Assign storage to the application. To do so, select the Storage tab, and then the Assign Storage tab. a. Click the LUN Owner or Host option. b. In the Search box, enter the storage name to search LUN Owner or enter host name to search hosts. You can enter the complete storage name or part of it to display only storage systems that match the search criteria. Click the Search icon. Click the Clear icon to clear the displayed results, and to enter a new search criteria. c. When selecting Host, review the host details in the search results and select a host to assign its storage to the application. You can assign storage on any available hosts of different OS types to the application. Working with applications 137

138 For LUN Owner, select the LUN Owner from the search results and review the host groups that are available for the storage system you want to assign to the application. You can assign multiple LUN Owners to the application. d. From the displayed storage entries, select one or more storage systems (using Shift+select or Ctrl+select on rows) that are listed as unassigned in the Status column. Then, click Assign to assign the selected storage to the application and view it in the Assigned Storage pane. The Status column updates the status of the selected storage as To be assigned. The storage is assigned and the status changes to Assigned after you click Save. e. To reset the changes you made to the storage assignments, click Reset, or click Save to save the changes. 138 Working with applications

139 5. Assign an application SLO profile to volumes that are allocated to the application. To do so, select the Storage tab, and then the Assign SLO tab. A default SLO profile is assigned. Figure 6-3 Manage application window: Assign SLO tab To assign a different SLO profile, select the SLO profile from the SLO Profile list, select one or more volumes (using Shift+select or Ctrl +select on rows) you want to assign it to, and then click Apply. You can choose from the Filter options to show All Volumes or Hitachi Volumes. Note: Due to the lack of performance details currently accessible for EMC systems, you cannot assign SLO profiles for EMC volumes. If there is an SLO profile displayed in the Recommendation column, you can accept it, by selecting Accept Recommendation in the SLO Profile list. Then select the volumes to be assigned. Click the Apply button. You can also search for volumes to apply the SLO profile. To do so, enter the complete name of the volume or part of it in the Search Volume field, and click the Search icon. The search results are displayed. If these are not intended results, click the Clear icon to clear the displayed results, and to enter a new search criteria, or from the displayed list of volumes that match your search criteria, select one or more volumes to assign the SLO profile. To reset the changes you made to the SLO profile assignments, click Reset, or click Save to save the changes. Working with applications 139

140 6. Click the Settings tab to specify application settings. Figure 6-4 Manage application window: Settings tab a. In the SLO Profile panel, use the Default SLO Profile list to select an SLO profile or accept the default assignment. If you want to apply the selected application SLO profile to the application volumes, select the Apply to Existing & New Volumes check box. This will override any SLO profile assignments you made to the application volumes in the Assign SLO tab, under the Storage tab. If you do not want to monitor the application, select Unmonitored. To change monitoring, use the options in the SLO Profile pane. You can use these settings to override global settings for SLO monitoring that are managed in the Administration tab. Notify On: Use the default value Every Miss to be notified every time the application misses an SLO. You can use the lists to select anywhere from 2 to 12 misses in 10, 15, 30 minute or 1 hour windows. 140 Working with applications

141 Monitoring Window: Choose the hours during which the application will be monitored. Recurrence Type: Choose to monitor on a Daily, Weekly, or Monthly basis. The default value is Daily. Recurrence Options: If you choose to monitor weekly, choose at least one day of the week. If you choose to monthly monitoring, the options enable you to choose the same day each month or one ordinal day of the week per month. The default values are Day 1 of every Month or the first Sunday of every month. Under Tags, assign new tags to the application or modify existing tags. Select the check box of each tag you want to assign to your application, or unassign from the application. Under Notification, select the check box to send notifications to the address shown. The address can be edited in the user profile. To reset the changes you made to the settings, click Reset, or click Save to save the settings. Command Director assigns a default SLO Profile to any new application you create. To apply the selected application SLO profile to the application volumes, select Apply To Existing & New Volumes. This setting overrides any SLO profile assignments you made to the application volumes on the Assign SLO tab. If you do not want to monitor the application, select Unmonitored from the Default SLO Profile list. Note: Different SLO profiles are assigned to the application's volume and also set as the default profile. The application is monitored for the SLO profile assigned to the volume, irrespective of the SLO profile that is set as the default profile. b. In the Tags pane, select each tag you want to assign to the application. A list of tags you have created and predefined tags are grouped under relevant category names. c. In Notification, select the check box of the address of each user you want to notify when SLO violations occur for the application. d. Click Save to save the changes or Reset to return the settings to their previous state. Working with applications 141

142 7. Click Close to close the Manage Application window. If you close the window without saving your changes, you are prompted to save changes or discard them. 8. (Optional) To check the application you created, view the application in the business view. Related concepts Application creation process flow on page 133 Modifying applications on page 143 Related tasks Managing untagged applications on page 142 Deleting applications on page 152 Creating applications automatically on page 367 Related references Application notes on page 135 Managing untagged applications The All Applications view lists all applications in Hitachi Command Director irrespective of whether the applications are tagged or not. The applications are untagged in these conditions: when applications are created automatically from the Device Manager Logical Groups or during discovery of storage and hosts by Hitachi Command Director. when you fail to assign manually created applications to predefined or custom tags. To monitor these applications, you must assign them to a relevant tag category in your business view. Procedure 1. From the Business Views drop-down list, select the All Applications view. 2. From the list of applications, select the application, and click Manage. 3. In the Manage Application window, assign tags to the application. a. Select the Settings tab. b. Under Tags, a list of tags you have created and system-defined tags are listed. The category name for each tag is listed alongside the tag name. Select the check box of each tag you want to assign to your application. c. When you are done selecting the tags, click Save. 4. Click Close to close the Manage Application window. 142 Working with applications

143 Result After the tags are assigned, the application will appear in various business views of categories that includes these tags, and continue to be in the All Applications view. Related concepts Application creation process flow on page 133 Modifying applications on page 143 Related tasks Creating applications manually on page 135 Deleting applications on page 152 Related references Application notes on page 135 Modifying applications You can modify applications created automatically or manually in Hitachi Command Director. However, for the logical group applications created automatically by Hitachi Command Director, you can perform all modifications except renaming the application and modifying storage assignments. Modifying applications include: Modifying a single application to rename the application, modify tag, storage, and SLO profile assignments, or user notification list for SLO violations. Modifying multiple applications at a time to modify SLO profile assignments, tag associations, or user notification list for SLO violations. However, for multiple applications you cannot modify existing storage assignments or make new assignments. Related concepts Application creation process flow on page 133 Related tasks Creating applications manually on page 135 Managing untagged applications on page 142 Deleting applications on page 152 Related references Application notes on page 135 Modifying a single application Working with applications 143

144 Procedure 1. On the Resources tab, select the view that includes the application you want to modify. Select the Logical Group business view or the All Applications view for logical group applications. Select the All Applications view for all untagged applications that were automatically created based on the auto-create application option you chose. Select a custom business view for applications that are tagged for a specific category. 2. Select an application to modify, and click Manage. Figure 6-5 Manage application window for single application 3. In the Application Name field, modify the application name. Enter a new name not exceeding 256 characters, and click Save. 4. Select the Settings tab to modify the application settings. 144 Working with applications

145 In the SLO Profile pane, open the Default SLO Profile list to select an application SLO profile if the default SLO Profile does not suit your SLO requirements. If you want to apply the selected application SLO profile to the application volumes, select the Apply to Existing & New Volumes check box. This will override any SLO profile assignments you made to the application volumes in the Assign SLO tab, under the Storage tab. If you do not want to monitor the application, select Unmonitored. To change monitoring, use the options in the SLO Profile pane. You can use these settings to override global settings for SLO monitoring that are managed in the Administration tab. Notify On: Use the default value Every Miss to be notified every time the application misses an SLO. You can use the lists to select anywhere from 2 to 12 misses in 10, 15, 30 minute or 1 hour windows. Monitoring Window: Choose the hours during which the application will be monitored. Recurrence Type: Choose to monitor on a Daily, Weekly, or Monthly basis. The default value is Daily. Recurrence Options: If you choose to monitor weekly, choose at least one day of the week. If you choose to monthly monitoring, the options enable you to choose the same cardinal day each month or one ordinal day of the week per month. The default values are Day 1 of every Month or the first Sunday of every month. Under Tags, assign new tags to the application or modify existing tags. Select the check box of each tag you want to assign to your application, or unassign from the application. Under Notification, select the check box to send notifications to the address shown. addresses for all active users are included. To reset the changes you made to the settings, click Reset, or click Save to save the settings. Working with applications 145

146 5. Modify the existing storage assignment or make new assignments. To do so, select the Storage tab, and then the Assign Storage tab. Figure 6-6 Manage application window: Assign storage tab For applications created automatically from LUN Owners or discovered hosts, the Assigned Storage pane displays the storage information associated with the application. Note: Skip this step for logical group applications. The logical group applications imported from Device Manager come with storage assignments that you cannot modify. 146 Working with applications

147 Review the storage assignments you made to the current application. To unassign storage from an application, select the storage in the Assign Storage pane, and click Unassign. The Status column modifies the status of the selected storage to To be unassigned. The storage is unassigned and the status changes to Unassigned only after you click Save. To modify the existing storage assignment from LUN Owner or Host, unassign the storage using the Unassign button, click Save, and then click the LUN Owner or Host radio button. To assign additional storage to the application, in the Search field, enter the storage name to search LUN Owner or enter host name to search hosts. You can enter all or part of the storage name to display only storages that match the search criteria. Click the Search icon. The search results are displayed. If these are not intended results, click the Clear icon to clear the displayed results, and to enter a new search criteria. From the displayed storage entries, select one or more storages (using Shift+select or Ctrl+select on rows) you want to assign to the application. Then, click Assign to assign the selected storage and view it in the Assigned Storage pane. To reset the changes you made to the storage assignments, click Reset, or click Save to save the changes. 6. Modify the existing application SLO profile assignment of the volumes allocated to the application or assign a new profile. To do so, select the Storage tab, and then the Assign SLO tab. Figure 6-7 Manage application window: Assign SLO tab Modify the existing SLO profile assignment. To assign a different SLO Profile, choose from the options in the SLO Profile list, and select one or more volumes (using Shift+select or Ctrl+select on rows) for SLO profile assignment. Then click Apply. Working with applications 147

148 If there is one or more SLO profile displayed in the Recommendation column, you can assign select volumes and select Accept Recommendation in the SLO Profile list. You cannot select volumes that do not have a recommendation. Click the Apply button. To unassign an SLO profile from volumes, select the volumes again to unselect it. Assign SLO profile to new volumes. To do so, search for volumes to apply the SLO profile to by specifying all or part of the volume name in the Search Volume field, and clicking the Search icon. The search results are displayed. If these are not intended results, click the Clear icon to clear the displayed results, and to enter a new search criteria. From the displayed list of volumes that match your search criteria, select one or more volumes to assign the SLO profile. To reset the changes you made to the SLO profile assignments, click Reset, or click Save to save the changes. 7. Click Close to close the Manage Application window. If you close the window without saving your changes, you are prompted to save changes or discard them. Related concepts Modifying applications on page 143 Related tasks Modifying multiple applications on page 148 Modifying multiple applications Procedure 1. From the Resources tab, select the view that includes applications you want to modify. You can select Logical Group, All Applications, or any custom business view. Select the Logical Group business view or the All Applications view for logical group applications. Select the All Applications view for all untagged applications that were automatically created based on the auto-create application option you chose. Select a custom business view for applications tagged to a specific category. 148 Working with applications

149 2. Select multiple applications using Shift+select to select a range of applications, or Ctrl+select to select multiple applications. The Total Apps counter displays the total number of applications in the business view; the Selected counter displays the total number of applications you have selected. The following figure shows an example of these counters: Working with applications 149

150 3. Click Manage to open the Manage Application window with a list of your selected applications shown in the left pane. Figure 6-8 Manage application window for multiple applications To remove any application from the selected applications list displayed in the left pane, select the application, and then click Remove. 4. You can search for applications you want to modify and add them to the list of Selected applications. In the Search pane, enter all or part of the application name, and click the Search icon. The search results are displayed. If these are not intended results, click the Clear icon to clear the displayed results and start a new search. 150 Working with applications

151 5. From the displayed applications, select the applications you want to modify. Then, click Add to add them to the Selected pane. The count of total number of applications in the Selected pane increases when you add more applications to modify and if these applications do not already exist in this pane. This count helps you determine the total number of applications you have selected to modify. The following figure shows the Search pane and the Selected pane with the count of total number of selected applications displayed. 6. Modify the application settings in the Settings tab. Use the Default SLO Profile list to select an application SLO profile if the default SLO Profile does not suit your SLO requirements. If you want to apply the selected application SLO profile to the application volumes, select the To Existing & New Volumes check box. This will override any SLO profile assignments you made to the application volumes in the Assign SLO tab. If you do not want to monitor the application, select Unmonitored. Under Tags, assign new tags to the application or modify existing ones. Select the check box of each tag you want to assign to your application. If the selected applications have been assigned the same tags, then the check boxes for these tags are selected. If they are assigned to Working with applications 151

152 different tags, then the relevant check boxes are shown in gray. Unselected check boxes represent unassigned tags. Under Notification, select the check box to send notifications to the address shown. addresses for all active users are included. To reset the changes you made to the settings, click Reset, or click Save to save the settings. 7. Click Close to close the Manage Application window. If you close the window without saving your changes, you are prompted to save changes or discard them. Related concepts Modifying applications on page 143 Related tasks Modifying a single application on page 143 Deleting applications In Hitachi Command Director, you can delete applications: manually from custom business or All Applications view. automatically when you switch to a different auto-create option (in Administration tab > System Settings & Operations > Application Settings) When you switch to the Logical Group option, all applications that were created manually or automatically are deleted. When you switch to the LUN Owner, Host, or None option, only the auto-created applications are deleted. You can also choose to delete one or more applications at a time. When you delete an application from a business view, you delete it from Hitachi Command Director. However, the historical data of this application will be preserved for audit purposes. Procedure 1. From the Resources tab, select the business view where you are deleting applications. 2. To delete a single application, select the application you want to delete, and click Delete. To delete multiple applications at a time, use Shift+select to select a range of applications, or Ctrl+select to select multiple applications. Then, click Delete. 3. In the Confirmation dialog box, verify that you are deleting the correct application, and then click Yes. 152 Working with applications

153 Result The application is successfully deleted from this business view and all other business views that includes it. Related concepts Application creation process flow on page 133 Modifying applications on page 143 About business views on page 62 Related tasks Creating applications manually on page 135 Managing untagged applications on page 142 Displaying business views on page 64 Related references Application notes on page 135 Working with applications 153

154 154 Working with applications

155 7 Reporting on applications This module provides information about application reports available in Hitachi Command Director. Application reports Accessing application reports for a selected application Accessing application reports at the folder level in a business view Application Summary report SLO Status report Storage System Performance report Storage Allocation report Filesystem Utilization report SLO Profile Details report Storage Allocation Trend Application Response Time Trend report IO Utilization Trend report Storage allocation information Total number of applications in a folder Response Time SLO Status report Reporting on applications 155

156 IOPS SLO Status report Application List report Application Capacity Comparison Trend report DTR SLO Status report Pool Tier Utilization Trend report Pool Tier Utilization Forecast Trend report 156 Reporting on applications

157 Application reports Application reports are available for a selected application or for all applications within a folder (folder level) in the business view. Hitachi Command Director provides you with a set of predefined standard reports for applications or application folder. You can modify report definitions of these reports and save them as new reports. The following table lists the standard application reports that are available when you select an application or application folder in the business view: Summary Report name Description Provides a quick overview of the application SLO status and associated tags, if any. See Application summary report on page 159. Available for application, application folder, or both Application SLO Status Displays the application SLO status for the past 24 hours. See SLO status report on page 160. SLO Profile Details Lists every storage Service Level Objective (SLO) monitored over a period of time for the selected application. See SLO profile details report on page 163. IO Utilization Trend Displays the total application or host I/O operations per second (IOPS) over a period of time. See IO utilization trend report on page 169. Pool Tier Utilization Trend The trend of pool tier capacity used by the HDT volumes of a single application. Pool Tier Utilization Forecast Trend Total applications IOPS SLO Status Response Time SLO status Application List Pool tier utilization trend report on page 185 Displays a forecast of pool tier capacity used by HDT volumes of a single application. Indicates the total number of applications in a selected folder. See Application list on page 180. Displays the total IO operations per second SLO status for all applications in the selected folder. See IOPS SLO status report on page 180. Displays the response time SLO status for all applications in the selected folder. See Response Time SLO status on page 179. A list of top 20 applications in a selected folder that violated the set SLO threshold in the past 24 hours. Application folder Reporting on applications 157

158 Report name Application Capacity Comparison Trend DTR SLO Status Storage System Performance Storage Allocation Filesystem Utilization Storage Allocation Details Storage Allocation Trend Application Response Time Trend Description See Application list on page 180. Provides comparison scenarios of capacity allocation utilization by applications over a period of time. See Application capacity comparison trend report on page 182. Displays the total data transfer rate in megabits per second SLO status for all applications in the selected folder. DTR SLO Status (folder) on page 184 Displays the current storage performance metrics. See Storage system performance report on page 161. Provides the current snapshot of your storage allocation. See Storage allocation report on page 161. Reports on file system utilization by a host-based application. See Filesystem utilization report on page 162. Displays the configuration information of the storage disks allocated to the host or application or allocated to all the hosts or applications in the All Applications view. See Storage allocation details on page 170. Displays the storage allocation trend, for the selected application or all applications within a selected folder, for the past 7 years. See Storage allocation trend report on page 164. Provides response time breakdown over the past 24 hours. See Application response time trend report on page 168. Available for application, application folder, or both Both Accessing application reports for a selected application Procedure 1. From the Resources tab, select the business view that contains the application you are monitoring. 2. From the appropriate folder in your business view, select the application. A list of standard reports for the selected application appears in the Content pane and also available from the Select a report drop-down list. The drop-down list also includes your saved reports. 158 Reporting on applications

159 Related concepts Application reports on page 157 Accessing application reports at the folder level in a business view Procedure 1. From the Resources tab, select the business view that contains the folder you are monitoring. 2. Select the appropriate folder in your business view. A list of standard reports for the selected application folder appears in the Content pane and also available from the Select a report drop-down list. The drop-down list also includes your saved reports. Related concepts Application reports on page 157 Application Summary report The Application Summary report provides a quick overview of the application SLO status and application details. Figure 7-1 Application summary report This report displays the following information: Name: The application name. Reporting on applications 159

160 Status: Indicates the SLO status whether the application conformed with the monitored SLO (OK), missed the SLO (Miss), on the borderline (Borderline), or unmonitored. Tags: Tags assigned to the application. No tags are displayed for applications that are not assigned any tags. Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 SLO Status report The SLO Status report provides a quick overview of the application SLO status for the past 24 hours. Figure 7-2 SLO status report This report displays an SLO band that provides a historical trend of SLO status over the past 24 hours. Visual indicators such as the red, yellow, and green bars indicate the time period when the application was monitored and its SLO status. The gray bar indicates the time when the application was unmonitored. This report also indicates the percentage of time when the application conformed with the monitored SLO in the past 24 hours. Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page Reporting on applications

161 Storage System Performance report The Storage System Performance report provides an overview of the application storage for a selected application or all applications within a selected folder in the business view. Figure 7-3 Storage system performance report This report displays the following information: Response Time: Displays the weighted average response time. IOPS: Total I/O operations per second when reading from a volume or writing to a volume. DTR: Total data transfer rate (in MBps) when reading from a volume or writing to a volume. Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 Storage Allocation report The Storage Allocation report provides a quick insight into total assigned physical and thin storage capacity of a selected application or application folder in a business view. At the folder level, the report displays the cumulative capacity of physical and thin storage assigned to all applications in the folder. This report does not display any storage information, if no storage is assigned to the selected application. Reporting on applications 161

162 Figure 7-4 Storage Allocation report This report displays the following information: Physical: Total physical storage capacity allocated to the selected application. Thin Used: Total pool storage consumed by the application. Thin Free: Total pool storage that is unused by the application. Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 Filesystem Utilization report The Filesystem Utilization report indicates the percentage of the used capacity in the file system for a selected host-based application or all hostbased applications within a selected folder in the business view. 162 Reporting on applications

163 Figure 7-5 Filesystem Utilization report Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 SLO Profile Details report The SLO Profile Details report lists every storage Service Level Objective (SLO) monitored over a period of time for an application. Figure 7-6 SLO Profile Details report This report provides the following information: SLO Profile: The SLO profile associated with the application. For EMC systems, this fields displays "Unmonitored". Status: SLO status of the application. Response Time: The current response time for the application. Response Time Miss %: The percentage value of the average application response time to response time threshold. A value greater than 100 indicates the percentage by which the application has violated the SLO profile and a value lesser than 100 indicates the proximity to violation. IOPS: Total I/O operation per second for the application. Reporting on applications 163

164 IOPS Miss %: The percentage value of the Total Application IOPS to IOPS threshold. A value greater than 100 indicates the percentage by which the application has violated the SLO profile and a value lesser than 100 indicates the proximity to violation. DTR: The current data transfer rate for the application. DTR Miss %: The percentage value of the average application data transfer rate to data transfer rate threshold. A value greater than 100 indicates the percentage by which the application has violated the SLO profile and a value lesser than 100 indicates the proximity to violation. # Volumes: Number of volumes associated with the application. SLO Conformance (Last 24 hrs): Indicates the percentage of time when the application was in conformance with the monitored SLO in the past 24 hours. Related tasks Accessing application reports for a selected application on page 158 Related references Application Response Time Trend report on page 168 Storage Allocation Trend The Storage Allocation Trend report displays storage allocation trend for the following resources, for the past 7 years: A selected application or all applications within a selected folder in a custom business view. A selected application in the All Applications business view. A selected host or all hosts within a selected folder in the Hosts business view. A selected HNAS node - cluster, file system, or pool or all HNAS nodes within a selected cluster in the File Servers business view. You can view this report in the content pane of the various business views or from the Select a Report drop-down list in the content pane. Versions of the report can also be viewed on the Planning dashboard: The Storage Allocation Trend - Windows report displays the cumulative trend report of total physical and thin storage capacity assigned to Windows hosts. The Storage Allocation Trend - Hyper-V report displays the cumulative trend report of total physical and thin storage capacity assigned to Hyper- V hosts. The Storage Allocation Trend - HNAS report displays the cumulative trend report of total physical and thin storage capacity assigned to HNAS nodes. 164 Reporting on applications

165 At the folder level, this report displays the cumulative trend report of total physical storage capacity assigned to applications, hosts, or HNAS nodes within the selected folder and the total thin storage capacity consumed and unused by applications, hosts, or HNAS elements within the selected folder. For applications or hosts with no assigned storage, this report does not display any storage allocation trend information. Note: At the folder level, the capacity trend for applications is based on the number of applications that are currently available within the folder, and not on applications that existed in the past. Similarly, the capacity trend for hosts is based on the number of hosts available within the folder. Figure 7-7 Storage Allocation Trend report Click the Forecast button to open the Storage Allocation Forecast Trend report to view a forecast of the storage allocation trend capacity. This report provides the following information: Physical: Total physical storage capacity allocated to the selected application, host, folder, or HNAS node. Thin Used: Total pool storage consumed by the application, host, folder, or HNAS node. Reporting on applications 165

166 Thin Free: Total pool storage that is unused by the application, host, folder, or HNAS node. Related tasks Accessing application reports for a selected application on page 158 Related references Planning dashboard default reports on page 53 Hosts dashboard default reports on page 57 Storage allocation forecast trend report The Storage Allocation Forecast Trend report displays a forecast of storage allocation over time for the metrics in the Storage Allocation Trend report. You can launch the report from the Storage Allocation Trend report or from the Select a Report list wherever the Storage Allocation Trend report is available. For more information, see Storage allocation trend report on page 164 Figure 7-8 Storage Allocation Forecast Trend report Click the Filter button to select attributes, operators, and values for the forecast, including the date range, confidence level, and metrics. For more information, see Specifying Criteria for the Storage Allocation Forecast Trend report on page 167 The report displays the dates and confidence level selected as attributes to compute the forecast, including: Historical Data Start Date: The data for the oldest data available for forecasting. 166 Reporting on applications

167 Forecast Start Date: The earliest date included in the forecast. This is the date after the forecast is launched. Forecast End Date: The last date included in the forecast. This can be 1 month, 3 months, 6 months, 9 months, or 1 year. Confidence Level: The reliability of the forecast, anywhere from 90 % to 99%. The graph displays a forecast of storage allocation capacity over time for each metric selected as an attribute. There is a legend displaying the name and color assigned to each metric. You can hover over the forecast to display confidence intervals for each point in the forecast. You can also drag the date line across the graph to display confidence intervals for the date shown at the top of the forecast. Date range controls The forecast includes tools to control the view of the range of dates. You cannot display dates outside the Forecast Start Date and Forecast End Date. Use the sliders below the forecast to expand or contract the date range. The range is reflected in the From and To fields. Enter a date in the From or To field and click Enter to change the dates displayed in the forecast. Click a Zoom option to display one of the available ranges, within the length of time selected for the forecast. Related tasks Specifying criteria for the storage allocation forecast trend report on page 167 Related references Storage Allocation Trend on page 164 Specifying criteria for the storage allocation forecast trend report Specify report criteria for the Storage Allocation Forecast Trend report to view a forecast of storage allocation capacity over time. For more information, see Storage Allocation Forecast Trend report on page 166. Procedure 1. Click the Filter button in the report to edit the Attributes, Operators, and Values for the forecast. Reporting on applications 167

168 Attribute Operator Values Projection Input Data Projection Output Range Confidence Level (%) Metric EQ (equals) EQ (equals) EQ (equals) IN (includes) 1 month, 3 Months, 6 Months, 9 Months, or 1 Year through 7 Years. 1 month, 3 Months, 6 Months, 9 Months, or 1 Year 90 through 99 Select any or all: Physical, Thin Used, Thin Free. Note: The following fields are not available: Additional Filters Applied, All/Any, Top X, and Date Range. 2. Click Apply to save any changes and Close the window. Related references Storage allocation forecast trend report on page 166 Application Response Time Trend report The Application Response Time Trend report provides information about the response time breakdown over the past 24 hours for a selected application or all applications within a selected folder in the business view. Figure 7-9 Application response time trend report This report displays the total response time for each read/write operation request. Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page Reporting on applications

169 IO Utilization Trend report The IO Utilization Trend report is a graph that displays the total application or host I/O operations per second (IOPS) for the past 24 hours. You can access this report from the Select a Report drop-down list in the Content pane. For example, when you view the application IO utilization trend, you can determine whether preventive action is required to maintain optimal storage performance (such as allocating additional storage, migrating it to faster storage, or adding more paths). When used with the Storage Utilization report, you can also plan your storage resource purchases such as ports and cache, and generate Key Performance Indicator (KPI) and chargeback reports. To review the Storage Utilization report, see Storage utilization report on page 195. Figure 7-10 IO utilization trend report This report provides the following information: Total IOPS: The total number of IO operations per second. Reporting on applications 169

170 Data Transfer Rate: Total Megabytes per second (MBps) the application is performing when reading and writing. Read Hit %: The percentage of total read operations that are cache hits (for example, read operations that are accessed from the cache rather than from the disk). Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 Storage allocation information This module describes the Storage Allocation Details report available in Hitachi Command Director. Storage allocation details on page 170 Pool utilization report on page 173 Storage path report on page 176 Tier definition report on page 177 Replication details report on page 178 Storage Allocation Details report The Storage Allocation Details report includes information on the storage volumes to which the host file systems are mapped. You can view this report in the content pane for the host folder in the business view or access a detailed report from the Select a Report list. Note: Some fields, including Virtual Model, Virtual Serial No., and Virtual LDEV, are available only when you access the report from the Select a Report list. The Storage Allocation Details report provides details on the amount and type of primary storage capacity used by a given host or application. This report also displays the configuration information of the storage disks allocated to the host or application or allocated to all the hosts or applications in the business view folder. It includes the volume-to-host mapping and storage capacity information. You can use the report editing capability to aggregate the results by a particular attribute, such as the Storage System or Volume Type, and specify the type of information that is to be displayed. This report provides the following information: 170 Reporting on applications

171 LDEV: The volume ID assigned by the storage system on which this volume is allocated. Label: The label assigned to the volume from Device Manager. Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. # of Paths: Displays the total number of paths for this volume. The number displayed is a navigable link to the Storage Path report. Vol Type: Displays the type of volume; for example, standard, CVS, or LUSE. If the volume is reserved for future global-active device, the Vol Type column displays GAD Reserved, along with any other attributes. If volume type is P-VOL, the Vol Type column displays GAD along with other types. Vol Role: The attributes of the volume. If the volume has multiple attributes, they are separated with a comma. CVS: Indicates that the volume has been created with the Custom Volume Size (CVS) function. LUSE: Indicates that the volume is a Logical Unit Size Expansion (LUSE) volume. # Thin Vols: Indicates that the volume is a Dynamic Provisioning volume. V-VOL: Indicates that the volume is a V-volume used in QuickShadow/Copy-on-Write Snapshot. P-VOL: Indicates the primary (physical) copy source volume in a volume pair. GUARD: Indicates that data retention has been set up. External: Indicates that the volume is an external volume. IO Suppression: Indicates that the volume is an internal volume to which an external volume is mapped. This attribute indicates that the host Input/Output (I/O) suppression mode is enabled. Cache Enable: Indicates that the volume is an internal volume to which an external volume is mapped. This attribute indicates that the I/O cache mode is enabled. None Displayed: Indicates that the volume is ordinary. P-VOL: Indicates a primary volume. Pool: The pool ID. When the volume is not part of a dynamic provisioning pool, this field displays a hyphen. The pool ID is a navigable link to the Pool Utilization report. Note: Because no Pool value is provided for EMC systems, a navigable link to the Pool Utilization report is provided through Pool Name. Pool Name: Pool name specified in Device Manager. If the name is not specified in Device Manager, this field displays a hyphen. It will also display a hyphen when the volume is not part of a dynamic provisioning pool. Reporting on applications 171

172 Note: For EMC systems, the Pool Name provides a navigable link to the Pool Utilization report. CLPR: Displays the CLPR (Cache Logical Partition) number with which this volume is associated. Array Group: The name of the array group that holds the storage disk (volume). For DP- Volumes, this is the Hitachi Dynamic Provisioning VDEV; for snapshot volumes, this is the Copy-on-Write Snapshot VDEV; for external volumes, this is the External Array Group. Parity Group: The name of the parity group to which this volume belongs. RAID Level: The volume RAID level; for example Raid 5 format 3D+1P. Emulation: Displays the emulation type; for example, Open-V. Disk Type: Provides disk space size and data link type; for example, GB 10K SAS. Tier: Displays the name of HTSM tiers associated with this volume. The volume can be part of more than one tier. Each tier name is a navigable link to the Tier Definition report. Storage Class: Displays the storage classification based on the available storage resources; for example, SAS GB 10K RAID6(2D+2P) 4 drives. Capacity: The total storage capacity of the volume (in MB, GB, or TB). Consumed Capacity: Displays the current consumed capacity of the volume. For DP volumes, this is the capacity that is consumed from the Dynamic Provisioning pool (DP-Pool). Replication Capacity: Provides details on secondary level capacities that are accessible through a drill-down report. Click an entry in this column to access the Replication Details report. Ext. LDEV: Number of the external volume (in hexadecimal format). Ext. Storage System: Model and serial number of the external storage system. Virtual Model: The virtual model name of the migration source. Virtual Serial No.: The virtual serial number of the migration source. Virtual LDEV: The virtual LDEV ID of the migration source. Note: For EMC systems, # Path, Pool ID, CLPR, Array Group, Tier, Replication Capacity, Ext. LDEV and Ext. Storage are not provided, as indicated by a dash (-). Refreshing Information In some cases, a refresh is required to get the latest storage allocation details. If the host has devices that are not connected to volumes from a storage system (for example, when the volumes are unallocated for the host), Hitachi Command Director will not display such devices. 172 Reporting on applications

173 If you have allocated volumes from an HUS V/VM or VSP system to an ESX 3.5 host, the report does not display the volume information. When new volumes are provisioned or existing volumes are removed from an HNAS storage pool, these changes are not refreshed immediately and displayed in the report. Related references Hosts dashboard default reports on page 57 Pool Utilization report on page 173 Storage Path report on page 176 Tier Definition report on page 177 Replication Details report on page 178 Pool Utilization report The Pool Utilization report provides detailed information about how a pool is being utilized by a selected application or host. To access this report, click the Pool link in the Pool column, in the Storage Allocation Details report. Reporting on applications 173

174 Figure 7-11 Pool Utilization report The Pool Utilization report is organized into three parts: Pool Properties table Pool Vols tab Thin Vols tab Pool Properties The Pool Properties table lists the following pool properties and their values: Pool: The pool ID. Note: Pool ID is not available for EMC systems, and this field displays a hyphen (-). Pool Name: Pool name specified in Device Manager or defined in EMC. If the name is not specified in Device Manager, this row displays a hyphen. 174 Reporting on applications

175 Storage System: Storage system name specified in Device Manager. If the name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: Type of storage system model. Tier: Name of the tier to which this pool belongs in Tiered Storage Manager (HTSM). Note: For EMC systems, Tier information is not applicable, and this field displays a hyphen (-). # Thin Vols: Number of thin volumes in this pool. # Pool Vols: Total number of volumes contributing storage for this pool. Pool Capacity: Total physical capacity of this pool. Sum of Thin Vol Capacities: Total capacity of all thin volume pools. Pool Free: Unconsumed pool capacity. Pool Used %: Consumed capacity as a percentage of the pool s physical capacity. Over Provisioning Ratio: This is the over-provisioned ratio for each pool in the system, which is calculated as: (Total pool provisioned capacity) / (Total physical capacity of pool) Risk Ratio: This is the pool risk ratio for each pool in the system, which is calculated as: (Total pool provisioned capacity) - (Total consumed capacity) / (Total free capacity of the pool) Status: Displays pool status for the three supported types of pool status: Normal, Blocked, and Over Threshold. Pool Vols When you click this tab, the Pool Vols table lists the following information about each of the DP Pool-VOLs in the pool: LDEV: Name of the volume (in hexadecimal format). Label: The Device Manager label name for the volume. Tier: The name of the tier to which the pool volume belongs in Tiered Storage Manager. Array Group: Array group name for this volume. Volume Type: Indicates type of volume (for example, Standard, External, CVS, LUSE, DP Pool VOL). Capacity: Allocated capacity of this volume. Disk Type: Disk type expressed in capacity and type (for example, 1.79 TB 7.2K SATA). The disk type displayed depends on the disk types that are supported by each storage system. RAID Level: RAID level type and configuration (for example, RAID6(6D +2P). Reporting on applications 175

176 Emulation: Type of emulation; for example, in Hitachi-based systems it Open-V (open volume); for EMC systems, it is Fixed-Block Architecture (FBA). Note: For EMC systems, Tier, and Array Group information is not applicable, and this field displays a hyphen (-). Thin Vols When you click this tab, the Thin Vols table lists the following information about each of the Thin Volumes in the pool: LDEV: Name of the volume (in hexadecimal format). Label: The Device Manager label name for the volume. Tier: The name of the tier to which the pool volume belongs in Tiered Storage Manager. Array Group: Array group name for this volume. Volume Role: Indicates the volume role as either S-VOL (secondary volume) or P-VOL (primary volume). Capacity: Allocated capacity of this volume. Consumed Capacity: Capacity consumed from the total pool capacity. Virtual Model: The virtual model name of the migration source. Virtual Serial No.: The virtual serial number of the migration source. Virtual LDEV: The virtual LDEV ID of the migration source. Note: For EMC storage systems, Tier and Array Group information is not applicable, and this field displays a hyphen (-). Related references Storage Path report Storage Allocation Details report on page 170 The Storage Path report provides path information for a specific volume. If the volume has more than one path, each path is listed separately. Access this report from the # of Paths column in the Storage Allocation Details report. 176 Reporting on applications

177 Figure 7-12 Storage path report The Storage Path report provides the following information: LDEV: The volume number. Port: The storage port name through which this volume is allocated. HSD: The host group name. Host Group: The type of host group. HBA WWN: The world wide name (WWN) of the host bus adapter (HBA) that is using this volume. If the volume is allocated to multiple HBA WWNs in the same host group, this report will display this information. Host Name: The gathered name of the host. Virtual Model: The virtual model name of the migration source. Virtual Serial No.: The virtual serial number of the migration source. Virtual Port: The virtual port name of the migration source. Virtual HSD: The virtual host group name of the migration source. Virtual LDEV: The virtual LDEV ID of the migration source. Related references Storage Allocation Details report on page 170 Tier Definition report This report displays one tier definition at a time. You can access this report from the Tier column in the Storage Allocation Details report. This report provides the following information: Tier Name: The name of the tier. Tier Definition: A string containing the search conditions that define a tier in HTSM. Reporting on applications 177

178 Related references Storage Allocation Details report on page 170 Replication Details report The Replication Details report provides details on replication pairs. You can access this report from the Replication Capacity column in the Storage Allocation Details report. This report provides the following information: Application: Application name. Volume: Volume name. Volume Label: Label assigned to the volume from Device Manager. CoW: Total S-VOL capacity of CoW (Copy on Write) volumes. HUR: Total capacity of Universal Replicator volumes. True Copy: Total capacity of True Copy volumes. Shadow Image: Total S-VOL (secondary volume) capacity of Shadow Image volumes. Thin Image: Total V-VOL capacity of CAW (Copy After Write) volumes. GAD: S-VOL capacity for global-active device. Total Replicated: Total capacity of all replicated volume pairs. Note: The P-VOL (Primary Volume) capacity is not included for the CoW, HUR, True Copy, Shadow Image, and Thin Image statistics. Related references Storage Allocation Details report on page 170 Total number of applications in a folder The Total Applications report displays the total number of applications within a selected application folder. This total includes all applications that are part of the selected folder, regardless of whether they are in a sub-folder of the selected folder. 178 Reporting on applications

179 Figure 7-13 Total applications Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 Response Time SLO Status report The Response Time SLO Status report displays the response time SLO status for all applications within a selected folder. Figure 7-14 Response time SLO status This report provides a breakdown of overall application SLO status indicating the number of applications that missed, were on borderline of, and conformed with the response time SLO. It also displays the number of applications that are not currently monitored for this SLO. This total includes all applications that are part of the selected folder, regardless of whether they are in a sub-folder of the selected folder. Reporting on applications 179

180 Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 IOPS SLO Status report The IOPS SLO Status report displays the total I/O operations per second SLO status for all applications within a selected folder. This total includes all applications that are part of the selected folder, regardless of whether they are in a sub-folder of the selected folder. Figure 7-15 IOPS SLO Status report This report provides a breakdown of overall application SLO status indicating the number of applications that missed, were on borderline of, and conformed with the Total IOPS SLO. It also displays the number of applications that are not currently monitored for this SLO. Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 Application List report The Application List report provides details about all applications within a selected folder. 180 Reporting on applications

181 Figure 7-16 Application List report This report provides the following information: Application: Name of the application. Status: Displays the current SLO status. Last Miss: Timestamp when the application was last in an SLO Miss state. The Miss State for an application is calculated as an aggregate of statuses of all SLO profiles associated with the application. Physical: Indicates the sum of the physical volumes associated with the application. Virtual: Indicates the sum of the virtual volumes (DP-VOLs) associated with the application. Virtual Consumed: The total consumed capacity of all virtual volumes associated with the application. File System: The total file system capacity of a host-based application. Used: Indicates the used capacity of the file system of a host-based application. # SLO Miss: The total number of SLO misses in the past 24 hours. Response: The response time of the application for the last available data. IOPS: Total application I/O operations per second (IOPS) for the last available data. DTR: Total Data Transfer Rate (in MB/s) of the application for the last available data. Reporting on applications 181

182 Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 Application Capacity Comparison Trend report The Application Capacity Comparison Trend report enables you to compare up to five applications based on the following capacity information available for the past 7 years: Provisioned (default): Total capacity from physical parity groups and thin capacity from pool allocated to the application. Physical: Total physical storage capacity allocated to the application. Thin Used: Total pool storage consumed by the application. Thin Free: Total pool storage that is unused by the application. The different comparison scenarios provide an insight into allocation of capacity and its utilization by applications over a period of time and helps you to identify applications that may require your attention. Access this report for the application folder from the Select a Report dropdown list in the content pane. It is also available for pool folders. This report displays, by default, the capacity utilization trend for the top five applications based on their provisioned capacity. Note: For applications in the selected folder that are not assigned any storage, or created new with assigned storage but with data aggregation still pending, the legend that displays the application name and storage capacity alongside will not display storage capacity. After the storage is assigned and data aggregation is completed, the report will display storage capacity. 182 Reporting on applications

183 Figure 7-17 Application Capacity Comparison Trend report You can choose to view comparison scenarios for a different set of applications using any of the capacity breakdown metrics by specifying the report criteria as described in Specifying criteria for Application Capacity Comparison Trend report on page 183. Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 Specifying criteria for Application Capacity Comparison Trend report Specify report criteria for the Application Capacity Comparison Trend report to compare storage capacity for selected applications based on the allocated physical (from parity groups) and thin (from HDP) capacity. Procedure 1. Select the report to use in the report viewer. 2. Click Filter and use the attribute criteria shown in the following table to filter trend data in the report. Reporting on applications 183

184 Table 7-1 Criteria for Application Capacity Comparison Trend report Attribute (Criteria) Operator Allowable value Value/Range Multiple values allowed? Capacity Type EQ (Equal to) String Physical, Provisioned, Thin Used, Thin Free Application IN (Includes) String Application Name. You can select a maximum of five applications. No Yes 3. Click Apply to apply the criteria, and then click Close to close the report criteria pane to view the report customized to your criteria. Example of tracking application consumption To compare the thin capacity consumed by your top five critical applications, and identify those that are about to reach their maximum allocated capacity limit, specify the following criteria: Select Capacity Type from the Attribute drop-down list, EQ from the Operator drop-down list, and Thin Used from the Values dropdown list. Select Application from the Attribute drop-down list, IN from the Operator drop-down list, and select five applications one at a time from the Values drop-down list. Click Apply to apply the criteria and filter the report accordingly. Related references Application Capacity Comparison Trend report on page 182 DTR SLO Status report The DTR SLO Status report displays the total data transfer rate in megabits per second SLO status for all applications within a selected folder. This total includes all applications that are part of the selected folder, regardless of whether they are in a sub-folder of the selected folder. 184 Reporting on applications

185 Figure 7-18 DTR SLO Status report This report provides a breakdown of overall application SLO status indicating the number of applications that missed, were on borderline of, and conformed with the Total DTR SLO. It also displays the number of applications that are not currently monitored for this SLO. Related concepts Application reports on page 157 Related tasks Accessing application reports for a selected application on page 158 Pool Tier Utilization Trend report The Pool Tier Utilization Trend report is a view of the trend of pool tier capacity used by the HDT volumes of a single application. Access the Pool Tier Utilization Trend report in the Resources tab. Select the All Applications business view and click an application. Then open the report from the Select a Report list. Reporting on applications 185

186 Figure 7-19 Pool Tier Utilization Trend report The trend chart shows the capacity used in each tier for up to 7 years. The default view is up to 3 months of the most recent data. Note: The report is empty for applications without HDT volumes and for third-party storage. The trend values for each tier are the sum of all tier capacity used by all HDT volumes in the selected application. Click the Filter button to choose Tiers 1 Used, Tiers 2 Used, or Tiers 3 Used. Click the Forecast button to launch a forecast of pool tier capacity used by virtual volumes. For more information, see Pool tier utilization forecast trend report on page 187. Date range controls The report includes tools to control the view of the range of dates. Use the sliders below the forecast to expand or contract the date range. The range is reflected in the From and To fields. Enter a date in the From or To field and click Enter to change the dates displayed in the forecast. Click a Zoom option to display one of the available ranges, within the length of time selected for the forecast. 186 Reporting on applications

187 Related concepts Application reports on page 157 Related references Pool Tier Utilization Forecast Trend report on page 187 Pool Tier Utilization Forecast Trend report The Pool Tier Utilization Forecast Trend report enables you to view a forecast of pool tier capacity used by HDT volumes of a single application. Access the report in one of these ways: Click the Forecast button in the Pool Tier Utilization Trend report. For more information, see Pool tier utilization trend report on page 185 Select an application in the All Applications business view and open the report from the Select a Report list. Figure 7-20 Pool Tier Utilization Forecast Trend report Note: The report is empty for applications without HDT volumes and for third-party storage. A warning message displays above the chart area. Click the Filter button to select attributes, operators, and values for the forecast, including the date range, confidence level, and metrics. For more information, see Specifying criteria for the pool tier utilization forecast trend report on page 188. The report displays the dates and confidence level selected as attributes to compute the forecast, including: Reporting on applications 187

188 Historical Data Start Date: The date for the oldest data available for forecasting. Forecast Start Date: The earliest date included in the forecast. This is the date after the forecast is launched. Forecast End Date: The last date included in the forecast. This can be 1 month, 3 months, 6 months, 9 months, or 1 year. Confidence Level: The reliability of the forecast, from 90% to 99%. The graph displays a forecast of pool tier capacity consumption by virtual volumes over time for each metric selected as an attribute. There is a legend displaying the name and color assigned to each metric. Date range controls The forecast includes tools to control the view of the range of dates. You cannot display dates outside the Forecast Start Date and Forecast End Date. Use the sliders below the forecast to expand or contract the date range. The range is reflected in the From and To fields. Enter a date in the From or To field and click Enter to change the dates displayed in the forecast. Click a Zoom option to display one of the available ranges, within the length of time selected for the forecast. Related concepts Application reports on page 157 Related references Pool Tier Utilization Trend report on page 185 Specifying criteria for the pool tier utilization forecast trend report Specify report criteria for the Pool Tier Utilization Forecast Trend report to view forecast of pool tier capacity used by virtual volumes for a single application over time. For more information, see Pool tier utilization forecast trend report on page 187. Procedure 1. Click the Filter button in the report to edit the Attributes, Operators, and Values for the forecast. Attribute Operator Values Projection Input Data EQ (equals) 1 month, 3 Months, 6 Months, 9 Months, or 1 Year through 7 Years. 188 Reporting on applications

189 Attribute Operator Values Projection Output Range Confidence Level (%) Metric EQ (equals) EQ (equals) IN (includes) 1 month, 3 Months, 6 Months, 9 Months, or 1 Year 90 through 99 Select any or all: Tier 1 Used, Tier 2 Used, Tier 3 Used. Note: The following fields are not available: Additional Filters Applied, All/Any, Top X, and Date Range. 2. Click Apply to save any changes and Close the window. Related references Pool Tier Utilization Forecast Trend report on page 187 Reporting on applications 189

190 190 Reporting on applications

191 8 Reporting on hosts This module describes the reports on the hosts discovered by Hitachi Command Director. The storage reports are used in the context of the host/ application that is using that storage. Host reports Available summary host reports Available HNAS host reports Hyper-V Server report VMware host reports Reporting on hosts 191

192 Host reports You can view reports for the hosts successfully discovered by Hitachi Command Director Host Collectors, as well as the mapping information from the host file system to the volumes on the storage system. These hosts include Hitachi NAS Platform (HNAS) servers, VMware ESX servers, and Hyper-V servers and the hosts on Windows, Solaris, and HP platforms. The HNAS host reports are available when you select any discovered HNAS server node of interest from the File Servers view in the Resources tab. The VMware host and Hyper-V host reports are available in the Hosts view in the Resources tab. The following table lists the various host reports that are available when you select a host or the host folder in the business view: Report name Description Available for host, host folder, or both Storage Allocation Details Storage Allocation Trend Storage Utilization Lists the storage volumes to which host file systems are mapped. See Storage allocation details on page 170. Displays the storage allocation trend for the past 7 years for a selected host or all hosts in a selected folder. See Storage allocation trend report on page 164. Lists filesystems and the volumes to which they are mapped. See Storage utilization report on page 195. Both Host Volume Manager (Accessible from the Vol Mgr column in the Storage Utilization report) Provides a summary of volume groups and details about provisioned and storage volumes. See Volume manager group report on page 197. Application Response Time Trend IO Utilization Trend Provides the response time breakdown over the past 24 hours. See Application response time trend report on page 168. Displays the total host I/O operations (IOPS) per second over a period of time. Hyper-V Server See IO utilization trend report on page 169. Hyper-V server report lists each virtual machine (VM) instance on a separate row. See Hyper-V server report on page 210. Hyper-V host only 192 Reporting on hosts

193 Report name Description Available for host, host folder, or both VMware Datastores VMware datastores report provides basic information about the datastores for each VMware server. See VMware datastores report on page 212. ESX Server VMDKs ESX server VMDKs report provides mapping information between the Virtual Machine Disk, the datastore, and the VM instance. See ESX server VMDKs report on page 212. Filesystem IO Trend Trends the Read and Write throughput and IO Utilization for a period of time for each file system in an HNAS server. See Filesystem IO trend report on page 200. Filesystem Load Trend Filesystem Load Trend report trends the total percentage of the file system load on the HNAS CPU for a period of time. See Filesystem load trend report on page 201. HNAS Filesystem Lists all file systems under each HNAS server and its associated pool information. See HNAS filesystem report on page 201. HNAS Pool Summary Provides an overview of each of the storage pools controlled by the System Management Unit (SMU). See HNAS pool summary report on page 202. HNAS Pool Details Provides HNAS pool for HNAS server nodes. See HNAS pool details report on page 203. HNAS Shares Displays key information for all shares by each filesystem in the HNAS server. See HNAS shares report on page 204. Protocol Op/s Trend Trends total operations resulting from reads, writes, or metadata for all supported protocol traffic on the HNAS node for the past 24 hrs. See Protocol Op s trend report on page 204. Total Throughput Trend Trends the total Ethernet and FC (Fibre Channel) data transfer rate for all ports belonging to an HNAS node for the past 24 hours. See Total throughput trend report on page 205. Filesystem Utilization Trend Trends the HNAS file system utilization trend for the past seven years for a selected file system folder or file system node. See Filesystem utilization trend report on page 206. Reporting on hosts 193

194 Related tasks Accessing summary host reports on page 195 Accessing HNAS host reports on page 200 Accessing the Hyper-V server report on page 210 Accessing VMware host reports on page 211 Available summary host reports This module describes each of the summary host report available in Hitachi Command Director. Storage allocation details on page 170 Storage allocation trend report on page 164 Application response time trend report on page 168 IO utilization trend report on page 169 Storage utilization report on page 195 Volume manager group report on page 197 Summary host reports The following summary host reports are available in Hitachi Command Director: Storage Allocation Details report Reports on the storage volumes to which the host file systems are mapped. Storage Allocation Trend report Displays the storage allocation trend for the past 7 years for selected host(s) Application Response Time Trend report Provides the response time breakdown over the past 24 hours. IO Utilization report Displays the total host I/O operations per second over a period of time. Storage Utilization report Reports on storage utilization of file systems. Volume Manager Group report Provides volume group summary and information about each of the provisioned volumes and storage volume. Related tasks Accessing summary host reports on page 195 Related references Storage Utilization report on page 195 Volume Manager Group report on page Reporting on hosts

195 Accessing summary host reports Procedure 1. Select the Resources tab. 2. From the Business Views drop-down list, select Hosts. 3. Expand the host folder and select the host of interest. 4. View the report in the Content pane, or from the Select a Report dropdown list in the content pane, select a summary host report you want to view. Related references Storage Utilization report on page 195 Volume Manager Group report on page 197 Storage Utilization report The Storage Utilization report reports on file systems rather than the volumes to which those file systems are mapped. Access the report in the Hosts business view in by selecting a host. The report will be available in the content pane. To view a version with additional fields, open the report from the Select a Report list. This report provides the following information: FS: The name of the file system (for example, C:\). This may be blank if the application uses a raw device. FS Type: Type of file system (for example, FAT, NTFS, NFS). If the application uses a raw device, this field may be blank. Device File: The name of the physical device. The device filename can be the NFS share name. Mount Point: The mount point of the file system. If a file system is not mounted, this field displays a hyphen. FS Capacity: Total storage capacity of the file system. FS Free %: Percentage of the file system s free capacity. Vol Mgr: The name of the volume manager. The value displayed is a navigable link to the Volume Manager Group report. If the file system is not from Volume Manager, this field is blank. To review the Volume Manager Group report, see Volume manager group report on page 197. Vol Mgr Type: Type of volume manager (for example, Veritas volume manager, LVM, SVM). Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. Reporting on hosts 195

196 Port: The storage port through which the volumes are allocated. If the volumes come from multiple ports (or multipathed), this field displays a comma separated list of all ports. If the file system is from Volume manager, this field displays a hyphen. Vol ID: If this file system is carved from a volume, this field displays the volume number. If this file system is carved out of a volume from the Volume Manager, this field displays the volume name. Vol Label: If this file system is from a volume, the volume label will be the Device Manager volume label. If this file system is from Volume Manager, this field is blank. Tier: Displays the name of the tiers that this volume belongs to in Hitachi Tier Storage Manager (HTSM) tiers. The volume can be part of more than one tier. Each tier name is a navigable link to the Tier Definition report. Each tier is line-separated within the single cell. To review the Tier Definition report, see Tier definition report on page 177. Vol Capacity: Total capacity of the volume. Vol Free %: The percentage of the volume s total unpartitioned capacity. Vol Role: Displays the volume role. Vol Type: Displays the type of volume (for example, standard, CVS, LUSE, DP-VOL, CoW-VOL, External). Pool: The pool ID. The pool ID is a navigable link to the Pool Utilization report. If the volume is not part of a dynamic provisioning pool, a hyphen is displayed in this field. Note: The Pool ID is not provided for EMC systems. For more information, see Pool utilization report on page 173. Pool Name: Pool name specified in Device Manager. If it is not specified in Device Manager, this field displays a hyphen. Array Group: Displays the array group name. Parity Group: Displays the Parity Group name. RAID level: RAID level the volume belongs to. This field displays the RAID level when a parity group is present, and a hyphen when the parity group is not present. If the file system has multiple volumes from different RAID types, this field also displays a hyphen. Virtual Model: The virtual model name of the migration source. Virtual Serial No.: The virtual serial number of the migration source. Virtual Port: The virtual port name of the migration source. Virtual LDEV: The virtual LDEV ID of the migration source. Related concepts Summary host reports on page Reporting on hosts

197 Volume Manager Group report You can access the Volume Manager Group report from the Vol Mgr column in the Storage Utilization report. For more information, see Storage utilization report on page 195. Volume group summary The Volume Group Summary section has the following columns: DiskGroup/Datastore Name: If it is an ESX server, this column displays the name of the disk group or datastore. # Provisioned Volumes: Total number of volumes provisioned from this volume group. Host Name: Name of the host. # Storage Volumes: Total number of storage volumes. Capacity: If it is an ESX server, this column displays the total capacity of the disk group or datastore. Free Capacity: If it is an ESX server, this column displays the free capacity in this disk group or datastore. % Used: The percentage of the storage capacity currently being used. Provisioned volumes The Provisioned Volumes section of the report provides the following information about each of the provisioned volumes. Volume: Volume ID. Volume Name: Name of the volume. Provisioned Host: Name of the host to which this volume is provisioned. For an ESX server, the provisioned host name will be the name of the VMware instance that is using this volume. For Volume Manager, it will be the name of the host itself. Capacity: Total capacity of the volume. Storage volumes The Storage Volumes section of the report includes the following information about each storage volume: LDEV: Volume ID (in hexadecimal). Label: Volume label specified in the Device Manager. Storage System: Storage system name. Volume Type: Displays the type of volume (for example, standard, CVS, LUSE, DP-VOL, CoW-VOL, External). Volume Role: Displays the volume role (for example, P-VOL). RAID Level: RAID level expressed in RAID 5 (3D+1P) format. Reporting on hosts 197

198 Port: The storage port through which the volumes are allocated. If the volumes come from multiple ports (or multipathed), this field displays a comma separated list of all ports. Emulation: Type of emulation used (for example, Open-V). Disk Type: The size and type of disk expressed in 130 GB 10 K FC format. Capacity: Total storage capacity of the volume. Virtual Model: The virtual model name of the migration source. Virtual Serial No.: The virtual serial number of the migration source. Virtual Port: The virtual port name of the migration source. Virtual LDEV: The virtual LDEV ID of the migration source. Related concepts Summary host reports on page 194 Related references Storage Utilization report on page 195 Available HNAS host reports HNAS host reports This module describes each of the Hitachi NAS Platform (HNAS) reports available in Hitachi Command Director. HNAS host reports on page 198 Accessing HNAS host reports on page 200 Filesystem IO trend report on page 200 Filesystem load trend report on page 201 HNAS filesystem report on page 201 HNAS pool summary report on page 202 HNAS pool details report on page 203 HNAS shares report on page 204 Protocol Op s trend report on page 204 Total throughput trend report on page 205 Storage allocation trend report on page 164 Filesystem utilization trend report on page 206 You can view these HNAS host reports available in Hitachi Command Director: Filesystem IO Trend report Trends the Read and Write throughput and IO utilization over a period of time for each file system in an HNAS server. See Filesystem IO trend report on page 200. Filesystem Load Trend report 198 Reporting on hosts

199 Trends the total percentage of the file system load on the HNAS CPU over a period of time. See Filesystem load trend report on page 201. HNAS Filesystem report Lists all the file systems under each HNAS server and its associated pool information. See HNAS filesystem report on page 201. HNAS Pool Summary report Provides an overview of each of the storage pools controlled by the selected System Management Unit (SMU). See HNAS pool summary report on page 202. HNAS Pool Details report Provides HNAS pool details for HNAS server nodes. See HNAS pool details report on page 203. HNAS Shares report Displays key information for all the shares by each file system in the HNAS server. See HNAS shares report on page 204. Protocol Op/s Trend report Trends the total operations resulting from reads, writes, or metadata for all supported protocol traffic for the past 24 hours on the HNAS node. See Protocol Op s trend report on page 204. Total Throughput Trend report Trends the total Ethernet and FC (Fibre Channel) data transfer rate in the past 24 hours for all ports belonging to an HNAS node. See Total throughput trend report on page 205. Filesystem Utilization Trend report Trends the HNAS file system utilization trend for the past seven years for a selected file system folder or file system node. See Filesystem utilization trend report on page 206. Related tasks Accessing HNAS host reports on page 200 Related references Filesystem IO Trend report on page 200 Filesystem Load Trend report on page 201 HNAS Filesystem report on page 201 HNAS Pool Summary report on page 202 HNAS Pool Details report on page 203 HNAS Shares report on page 204 Protocol Op/s Trend report on page 204 Total Throughput Trend report on page 205 Reporting on hosts 199

200 Accessing HNAS host reports Procedure 1. Select the Resources tab. 2. From the Business Views drop-down list, select File Servers. 3. Select the pertinent SMU folder. To view the HNAS Pool-related reports, expand the Pools folder under the SMU folder, and then select the storage pool of interest. To view the HNAS Shares report, expand the Filesystems folder under the SMU folder, and then select the file system of interest. To view the HNAS Nodes report, expand the Nodes folder under the SMU folder, and then select the HNAS node of interest. 4. View the report in the Content pane, or from the Select a Report dropdown list in the content pane, select an HNAS host report you want to view. Related references Filesystem IO Trend report on page 200 Filesystem Load Trend report on page 201 HNAS Filesystem report on page 201 HNAS Pool Summary report on page 202 HNAS Pool Details report on page 203 HNAS Shares report on page 204 Protocol Op/s Trend report on page 204 Total Throughput Trend report on page 205 Filesystem Utilization Trend report on page 206 Filesystem IO Trend report The Filesystem IO Trend report trends the Read and Write throughput and IO utilization over a period of time for each file system in an HNAS server. This report contains the following information about the selected file system: Read Transfer Rate (MB/s): Read transfer throughput for the file system. Write Transfer Rate (MB/s): Write transfer throughput for the file system. Total IOPS: Total read and write IO per second for the file system. Related concepts HNAS host reports on page Reporting on hosts

201 Filesystem Load Trend report The Filesystem Load Trend report trends the total percentage of the file system load on the HNAS CPU over a period of time. This report is available for HNAS server nodes in the File Servers business view. The Filesystem Load Trend report contains the following information about the selected file system: FSA Load %: File system load percentage on board A of the HNAS CPU (Hitachi High-performance NAS 3100 or 3200 model only if board A is available). FSB Load %: File system load percentage on board B of the HNAS CPU (Hitachi High-performance NAS 3100 or 3200 model only if board B is available). FS Load %: File system load percentage on the HNAS CPU (available only for the Hitachi High-performance NAS 3080 or 3090 model). Related concepts HNAS host reports on page 198 HNAS Filesystem report The HNAS Filesystem report is available for HNAS server nodes in the File Servers business view. This report lists all the file systems under each HNAS server and its associated pool information. Figure 8-1 HNAS Filesystem report The HNAS Filesystem report contains the following information about each HNAS file system: FS: The name of the HNAS file system. The file system name is a navigable link to the HNAS Shares report, which lists all the shares in the selected file system. To review the HNAS Shares report, see HNAS shares report on page 204. Capacity: Total capacity of the file system. Used: The amount of storage currently being used by the file system. Free: The free capacity of the file system. Free %: The percentage of free storage capacity in the file system. Pool: The name of the HNAS Storage Pool. The Pool name is a navigable link to the HNAS Pool Details report. To review the HNAS Pool Details report, see HNAS pool details report on page 203. Reporting on hosts 201

202 EVS: The name of the Exchange Virtual Server (EVS) from which this file system is hosted. EVS IP: The IP address of the EVS server. Node: The name of the node the EVS is currently on. Status: Indicates whether the file system is mounted or not. The supported statuses are: Mount - The file system has been mounted. MntRO - The file system has been mounted read-only. UnMnt - The file system is unmounted. RepTg - The file system is mounted as replication target. SysLk - The file system is mounted but syslocked; it is read-only to protocols, but read-write to NDMP. Related concepts HNAS host reports on page 198 HNAS Pool Summary report The HNAS Pool Summary report provides an overview of each of the storage pools controlled by the selected SMU. You can access this report from the Pool column in the HNAS Filesystem report. Figure 8-2 HNAS Pool Summary report This report provides the following information about each file system: Pool: Name of the storage pool. The pool name is a navigable link to the HNAS pool details report. To review the HNAS pool details report, see HNAS pool details report on page 203. # of LDEVs: The number of volumes that have been allocated to the storage pool. Capacity: The total storage capacity of each pool. Used: The amount of storage currently being used by the pool. Free: The free capacity of the storage pool. Free %: The percentage of allotted storage capacity that is currently free. Healthy: Whether the pool s condition is currently healthy or not. Related references HNAS Filesystem report on page Reporting on hosts

203 HNAS Pool Details report The HNAS Pool Details report is available for HNAS server nodes under the File Servers business view. You can access this report from the Pool column in the HNAS Filesystem report or HNAS Pool Summary report. Figure 8-3 HNAS Pool Details report The top section of the report provides the HNAS storage pool name and the total storage capacity of the selected pool. The HNAS Pool Details report has two tabs: File Systems and Volumes. File Systems tab The File Systems tab lists all the file systems that have been created out of the selected storage pool. This report provides the following information about each file system: FS: Name of the file system. Capacity: Total storage capacity of the file system. Used: Capacity of the file system that is being used. Free: Free storage capacity of the file system. Free %: The percentage of the file system s free storage capacity. EVS: The name of the EVS server. EVS IP: The IP address of the EVS server. Volumes tab The Volumes tab lists all the volumes that are part of the selected pool. Note: The volume information in this report is limited because Hitachi Command Director does not gather information on AMS or WMS storage and the volume information in this report is gathered from the HNAS server itself. Reporting on hosts 203

204 The HNAS Pool Details report provides the following information about each volume in the pool: LDEV: Volume ID in hexadecimal value. Capacity: Total capacity of the volume (in GB). Storage System: Name and model of the storage system. Related references HNAS Shares report HNAS Filesystem report on page 201 HNAS Pool Summary report on page 202 The HNAS Shares report displays key information for all the shares by each file system in the HNAS server. Figure 8-4 HNAS Shares report This report provides the following information for each share: Share: Name of the Share. Path: Path of the Share. Type: Indicates whether the share is an NFS (Network File System) or CIFS (Common Internet File System) share. Related concepts HNAS host reports on page 198 Protocol Op/s Trend report The Protocol Op/s (operations per second) Trend report trends the total operations resulting from reads and writes for all NFS, SMB, iscsi, and FTP traffic for the past 24 hours on the HNAS node. 204 Reporting on hosts

205 This report is available for HNAS nodes in the File Servers business view, and can be accessed from the Select a Report drop-down list in the content pane. Related concepts HNAS host reports on page 198 Total Throughput Trend report Figure 8-5 Protocol Op/s Trend report The Total Throughput Trend report trends the total Ethernet and FC (Fibre Channel) data transfer rate in the past 24 hours for all ports belonging to an HNAS node. This report is available for HNAS nodes in the File Servers business view, and can be accessed from the Select a Report drop-down list in the content pane. The following diagram illustrates the data transfer through Ethernet and FC for an HNAS node. Reporting on hosts 205

206 This report displays a line chart showing data transfer received and sent through Ethernet and FC for the past 24 hours. Related concepts Figure 8-6 Total Throughput Trend report HNAS host reports on page 198 Filesystem Utilization Trend report The Filesystem Utilization Trend report displays HNAS file system utilization trend details for selected file system folders or selected file system nodes. You can view this report in the content pane of the File Servers business view (from the Filesystems folder or node level) or from the Select a Report dropdown list in the content pane. 206 Reporting on hosts

207 Figure 8-7 Filesystem utilization trend report This report provides the following information: Filesystem Used: The sum of used capacity for all file systems in a Filesystem folder or the specific utilization for an individual Filesystem node. Filesystem Free: The sum of free capacity for all files systems in a Filesystem folder or the specific free capacity for an individual Filesystem node. Related concepts HNAS host reports on page 198 Filesystem Utilization Forecast Trend report The Filesystem Utilization Forecast Trend report displays a forecast of file system utilization over time for the metrics in the File System Utilization report. You can access the report in two ways: Open the File Servers business view in Resources. Select an HNAS filesystem folder or an HNAS filesystem, and then open the report from the Select a Report list. Click the Forecast button in the Filesystem Utilization Trend report. Reporting on hosts 207

208 For more information, see Filesystem utilization trend report on page 206. Figure 8-8 Filesystem Utilization Forecast Trend report Click the Filter button to select attributes, operators, and values for the forecast, including the date range, confidence level, and metrics. For more information, see Specifying criteria for the Filesystem Utilization Forecast Trend report on page 209. The report displays the dates and confidence level selected as attributes to compute the forecast, including: Historical Data Start Date: The data for the oldest data available for forecasting. Forecast Start Date: The earliest date included in the forecast. This is the date after the forecast is launched. Forecast End Date: The last date included in the forecast. This can be 1 month, 3 months, 6 months, 9 months, or 1 year. Confidence Level: The reliability of the forecast, anywhere from 90 % to 99%. The graph displays a forecast of filesystem utilization capacity over time for each metric selected as an attribute. There is a legend displaying the name and color assigned to each metric. You can hover over the forecast to display confidence intervals for each point in the forecast. You can also drag the date line across the graph to display confidence intervals for the date shown at the top of the forecast. 208 Reporting on hosts

209 Date range controls The forecast includes tools to control the view of the range of dates. You cannot display dates outside the Forecast Start Date and Forecast End Date. Use the sliders below the forecast to expand or contract the date range. The range is reflected in the From and To fields. Enter a date in the From or To field and click Enter to change the dates displayed in the forecast. Click a Zoom option to display one of the available ranges, within the length of time selected for the forecast. Specifying criteria for the Filesystem Utilization Forecast Trend report Specify report criteria for the Filesystem Utilization Forecast Trend report to view a forecast of file utilization capacity over time. For more information, see Filesystem Utilization Forecast Trend report on page 207. Procedure 1. Click the Filter button in the report to edit the Attributes, Operators, and Values for the forecast. Attribute Operator Values Projection Input Data Projection Output Range Confidence Level (%) Metric EQ (equals) EQ (equals) EQ (equals) IN (includes) 1 month, 3 Months, 6 Months, 9 Months, or 1 Year through 7 Years. 1 month, 3 Months, 6 Months, 9 Months, or 1 Year 90 through 99 Select either or both: Filesystem Used, Filesystem Free. Note: The following fields are not available: Additional Filters Applied, All/Any, Top X, and Date Range. 2. Click Apply to save any changes and Close the window. Hyper-V Server report This module describes the Hyper-V server report available in Hitachi Command Director. Reporting on hosts 209

210 Accessing the Hyper-V server report on page 210 Hyper-V server report on page 210 Accessing the Hyper-V server report The Hyper-V Server report lists each VM (virtual machine) instance in a separate row. This report is available on the Hyper-V folder node and on the Hyper-V Server application node. Access the report for the Hyper-V folder node by clicking the graphic in the Hyper-V Filesystem Overview report on the dashboard, or in the Resources tab, as described below. For more information, see Hyper-V filesystem overview on page 44. Access the report for a node in the Resources tab as follows: Procedure 1. Select the Resources tab. 2. From the Business Views drop-down list, select Hosts. 3. Expand the Hyper-V folder node or Hyper-V Server application node, and select the Hyper-V host of interest. 4. View the report in the Content pane, or from the Select a Report dropdown list in the content pane, select Hyper-V Server Report. Related references Hyper-V server report on page 210 Hyper-V server report The Hyper-V Server report allows you to see: Which VMs (for example, virtual machine guest operating systems) are running on that Hyper-V Server. Which VM instances are running on that Hyper-V Server. Figure 8-9 Hyper-V server report This report displays the following information: Hyper-V Server: Name of the Hyper-V server. Available only when run from the Hyper-V folder node. Hyper-V Server OS: Windows edition and version. VM Instance: Name of the VM (virtual machine) instance. 210 Reporting on hosts

211 VM MAC Address: The MAC address of the VM instance. If there are multiple MAC addresses, all the MAC addresses are listed and separated by commas. VM Instance IP Address: The IP address of the VM instance. If there are multiple IP addresses, all the IP addresses are listed and separated by commas. The VM instance IP address will be available only when the Host Data collection is complete on this VM instance; otherwise this value is displayed as a hyphen. VM OS: The OS name of the VM instance. Allocated Capacity: The total allocated capacity of the VM instance from the selected Hyper-V server. Related tasks Accessing the Hyper-V server report on page 210 VMware host reports This module describes each VMware host report available in Hitachi Command Director. Accessing VMware host reports on page 211 VMware datastores report on page 212 ESX server VMDKs report on page 212 Volumes Mapped to ESX Server VMs report on page 213 Accessing VMware host reports You can view these summary host reports available in Hitachi Command Director: ESX Server Data Stores Report Provides basic information about the datastores for each ESX server. ESX Server VMDKS Report Reports the mapping information between the Virtual Machine Disk (VMDK), the datastore, and the Virtual Machine (VM) instance. Procedure 1. Select the Resources tab. 2. From the Business Views drop-down list, select Hosts. 3. Expand the VMware folder and select VMware, ESX, or Data Stores server of interest. 4. View the report in the Content pane, or from the Select a Report dropdown list in the content pane, select a VMware host report you want to view. Related references VMware Datastores report on page 212 Reporting on hosts 211

212 ESX Server VMDKs report on page 212 Volumes Mapped to ESX Server VMs report on page 213 VMware Datastores report The VMware Datastores report provides basic information about the datastores for each VMware server. Access the report in the Resources tab, or click the graphic in the VMware Datastores Overview report in the dashboard to open the report for the DataStore folder in the Hosts business view. For more information, see Accessing VMware host reports on page 211 and VMware datastore overview on page 43. Figure 8-10 VMware datastores report This report contains the following information about each ESX datastore: Datastore: Name of the datastore. Free %: The percentage of the datastore s free capacity. Capacity: Total capacity (in GB) of the datastore. #of VMs: Total number of virtual machines (VMs) on this datastore. # Active VMDKs: Total number of Virtual Machine Disks (VMDKs) active on this datastore. In a virtual machine, the VMDK file is an encapsulation of an entire server or desktop environment in a single file. The VMDK file can be considered as the hard drive for a virtual machine. Related tasks Accessing VMware host reports on page 211 ESX Server VMDKs report This report provides the mapping information between the Virtual Machine Disk (VMDK), the datastore, and the Virtual Machine (VM) instance. Figure 8-11 ESX Server VMDKs report The ESX Server VMDKs report provides the following information: 212 Reporting on hosts

213 VMDK: The name of the VMDK. Click one of the links to open the Volumes Mapped to ESX Server VMs report. VMDK Capacity: The total storage capacity (in GB) of the VMDK. Datastore: The name of the datastore where this VMDK was created. ESX Server: The name of the ESX server. VM Instance: The name of the VM instance. VM MAC Address: MAC address of the VM. If there are multiple MAC addresses, they are separated by commas. VM Instance IP: IP address of the VM. If there are multiple IP addresses, they are separated by commas. VM OS: The OS type of the VM instance. Related tasks Accessing VMware host reports on page 211 Related references Volumes Mapped to ESX Server VMs report on page 213 Volumes Mapped to ESX Server VMs report The Volumes Mapped to ESX Server VMs report exposes mapping from virtual disk to VM instance to LUN for ESX servers. The Volumes Mapped to ESX Server VMs report enables you to identify any LUN needing investigation when IO is low on a virtual disk (VMDK) of a VM instance. The report can also help identify which VM instance depends on a specific LUN. You can also identify the set of LUNs on which a VM instance depends. You can access the report as follows: On the Global Dashboard, under Settings. On the Hosts Dashboard. In the Hosts view of the Resources tab, at the VMWare level as well as for Datastores and ESX servers. From the VMDK column of the ESX Server VMDKs report. Figure 8-12 Volumes Mapped to ESX Server VMs report Reporting on hosts 213

214 The report includes the following information: Field Description VM Instance VMDK Volume Storage System Model Pool Pool Name Datastore ESX Server Virtual Model Virtual Serial No Virtual LDEV VM instance name VMDK path LDEV name Storage array name Storage model name Pool ID Pool name Datastore name ESX server name The virtual model name of the migration source. The virtual serial number of the migration source. The virtual LDEV of the migration source. Related references ESX Server VMDKs report on page Reporting on hosts

215 9 Reporting on storage systems This module provides information about storage system reports available in Hitachi Command Director. Storage system reports Accessing storage system reports for all storage systems Accessing storage system reports for a given type of system Accessing storage system reports for a specific system Storage System Performance Overview report Storage System Capacity Overview report Pool Capacity Overview report Applications with Most SLO Misses (last 24 hours) report Performance Overview by Storage System report Storage System Capacity Trend report Pool Capacity Trend report Pool Capacity Forecast Trend report Pool Utilization report Application Capacity Utilization report Application Capacity by Storage Class report Reporting on storage systems 215

216 Application Capacity Consumption by Storage System report Application Capacity Consumption Trend by Storage System for Application report 216 Reporting on storage systems

217 Storage system reports Storage system reports are available for a selected storage system or for all storage systems within the All Storage Systems folder (folder level) in the Storage Systems view. The following set of predefined standard reports are available for the storage systems registered with Hitachi Command Director. Report name Storage System Performance Overview Description Provides a performance overview of your enterprise storage. See Storage system performance overview report on page 222. Storage System Capacity Overview Differentiates the used and raw storage capacity of your enterprise storage. See Storage system capacity overview report on page 223. Pool Capacity Overview Displays the current snapshot of the pool capacity and usage of your enterprise storage. See Pool capacity overview report on page 224. Applications with Most SLO Misses (Last 24 Hrs) Lists the top 5 applications with the most SLO misses recorded in the past 24 hours for your enterprise storage. See Applications with most SLO misses (last 24 hours) report on page 225. Performance Overview by Storage System Provides an overview of the overall storage performance by each storage system. This report is only available at the All Storage Systems folder level. See Performance overview by storage system report on page 226. Storage System Capacity Trend Displays the capacity allocation and utilization trend for a selected Hitachi storage system in the business view for the past 7 years. See Storage system capacity trend report on page 227. Storage System Capacity Forecast Trend Displays a forecast of storage system capacity over time for the metrics available in the Storage System Capacity Trend report. See Storage System Capacity Forecast Trend report on page 229. Pool Capacity Trend Displays the pool usage trend for a selected Hitachi storage system. This report is not available at the storage systems folder level. See Pool capacity trend report on page 231. Pool Capacity Forecast Trend report Displays a forecast of capacity over time for the metrics available in the Pool Capacity Trend report. See Pool capacity forecast trend report on page 233. Pool Utilization Displays a heat map of the pool utilization for a selected Hitachi storage system at a given point in time. See Pool utilization report on page 236. Application Capacity Utilization Displays the available capacity and the amount of storage that is being utilized by the applications for a given storage system. Reporting on storage systems 217

218 Report name Description See Application capacity utilization report on page 238. Application Capacity by Storage Class Provides details on the allocated capacity and usage by applications on a given storage system tier which is useful for calculating and planning capital expenditures. See Application capacity by storage class report on page 239. Capacity by Storage Class Provides capacity details for a given Storage Class including the number of volumes and pools that are capable of contributing storage and the amount of available storage that is being utilized. See Capacity by storage class on page 299. Application Capacity Consumption by Storage System Displays the applications with the highest capacity consumption in the selected storage system. See Application capacity consumption by storage system report on page 243. Application Capacity Consumption Trend by Storage System for Application Displays the trend of consumption by the selected application for up to 7 years. See Application capacity consumption trend by storage system for application report on page 245. Accessing storage system reports for all storage systems You can access storage system reports for all storage systems from the All Storage Systems folder level. Procedure 1. On the Resources tab, select the Storage Systems view. 2. Select the All Storage Systems folder to view reports for all of the registered storage systems. Result The following reports are available from the dashboard from the All Storage Systems view: Storage System Capacity Trend Application Capacity Utilization Storage System Capacity Overview Pool Capacity Overview The following reports are available from the Select a Report list from the All Storage Systems view: Application Capacity by Storage Class Capacity by Storage Class Storage Port Details Storage System Capacity Forecast Trend 218 Reporting on storage systems

219 Storage System Capacity Trend Related concepts Storage system reports on page 217 Related references Storage System Capacity Overview report on page 223 Storage System Capacity Trend report on page 227 Application Capacity Utilization report on page 238 Pool Capacity Overview report on page 45 Application Capacity by Storage Class report on page 239 Capacity by Storage Class report on page 299 Storage Port Details report on page 298 Accessing storage system reports for a given type of system You can access storage system reports for a specific category of storage systems from the system level folder view. Procedure 1. From the Resources tab, select the Storage Systems view. 2. Select the system level folder associated with a particular type of system to view the available reports. Result The following reports are available from the dashboard for Hitachi storage systems: Storage System Capacity Trend Application Capacity Utilization Storage System Performance Overview Storage System Capacity Overview Pool Capacity Overview Applications with Most SLO Misses The following reports are available from the Select a Report drop down list for Hitachi storage systems: Application Capacity By Storage Class Capacity By Storage Class Performance Overview by Storage System Storage Port Details Storage System Capacity Trend Storage System Capacity Forecast Trend Reporting on storage systems 219

220 The following reports are available from the dashboard for EMC storage systems: Storage System Capacity Trend Application Capacity Utilization Storage System Capacity Overview Pool Capacity Overview The following reports are available from the Select a Report drop down list for EMC storage systems: Application Capacity By Storage Class Capacity By Storage Class Storage Port Details Storage System Capacity Trend Storage System Capacity Forecast Trend Related concepts Storage system reports on page 217 Related references Storage System Performance Overview report on page 222 Storage System Capacity Overview report on page 223 Applications with Most SLO Misses (last 24 hours) report on page 225 Storage System Capacity Trend report on page 227 Application Capacity Utilization report on page 238 Pool Capacity Overview report on page 45 Application Capacity by Storage Class report on page 239 Capacity by Storage Class report on page 299 Storage Port Details report on page 298 Accessing storage system reports for a specific system You can access storage system reports for a specific storage system. Procedure 1. From the Resources tab, select the Storage Systems view. 2. Select a specific storage system from the displayed list. Result The following reports are available from the dashboard when selecting a specific Hitachi storage system: Storage System Capacity Trend Application Capacity Utilization Pool Utilization 220 Reporting on storage systems

221 Storage System Performance Overview Storage System Capacity Overview Pool Capacity Overview Applications with Most SLO Misses The following reports are available from the Select a Report drop down list when selecting a specific Hitachi storage system: Application Capacity Consumption by Storage System Application Capacity By Storage Class Capacity By Storage Class Pool Capacity Trend Pool Capacity Forecast Trend Storage Port Details Storage System Capacity Trend Storage System Capacity Forecast Trend The following reports are available from the dashboard when selecting a specific EMC storage system: Storage System Capacity Trend Application Capacity Utilization Pool Utilization Storage System Capacity Overview Pool Capacity Overview The following reports are available from the Select a Report drop down list when selecting a specific EMC storage system: Application Capacity Consumption by Storage System Application Capacity By Storage Class Capacity By Storage Class Pool Capacity Trend Pool Capacity Forecast Trend Storage Port Details Storage System Capacity Trend Storage System Capacity Forecast Trend Related concepts Storage system reports on page 217 Related references Storage System Performance Overview report on page 222 Storage System Capacity Overview report on page 223 Applications with Most SLO Misses (last 24 hours) report on page 225 Storage System Capacity Trend report on page 227 Pool Capacity Trend report on page 231 Pool Capacity Trend report on page 231 Reporting on storage systems 221

222 Application Capacity Utilization report on page 238 Pool Capacity Overview report on page 45 Application Capacity by Storage Class report on page 239 Capacity by Storage Class report on page 299 Storage Port Details report on page 298 Storage System Performance Overview report The Storage System Performance Overview report provides a performance overview of your enterprise storage. You can use the information to analyze the overall health of all storage systems or a specific storage system on the business view. Figure 9-1 Storage system performance overview This report provides near, real-time data for the following monitored metrics: Avg. Response Time (in ms): Weighted Average Response Time of a selected storage system or all storage systems in the folder based on Total IO count. A high response time indicates potential latency problem on some storage systems. Total IOPS: The total number of IO operations per second across all storage systems or a selected storage system in your environment. Total DTR: Total data transfer rate (MB/s) for a selected storage system or all storage systems in your environment. Avg. Read Hit (in percentage): Average Read Hit % for a selected storage system or all storage systems based on their read IO counts. A high read hit % is optimal; Read hit % under a certain value can indicate storage performance issues. Avg. Write Pending (in percentage): Weighted Average Write Pending % for a selected storage system or all storage systems based on cache size. A high write pending % indicates storage performance issues. 222 Reporting on storage systems

223 Related concepts Storage system reports on page 217 Storage System Capacity Overview report The Storage System Capacity Overview report differentiates the used and raw storage capacity for All Storage Systems, for all storage systems in a given category, or for a specific storage system in a given category. You can access the appropriate report in the Storage Systems view of the Resources tab. Note: Capacity details for the All Storage Systems folder includes all storage systems (for example, Hitachi and EMC). Figure 9-2 Storage system capacity overview In this report, the Parity Group bar indicates the total usable capacity of disk drives within the storage system and the Volume bar indicates the total capacity of all the volumes carved out from the Parity Group usable capacity. It further shows the breakdown of allocated, unallocated, and reserved capacity. This information helps you determine how much of the Parity Group capacity has been allocated and unallocated to hosts. Note: If the capacity values range from a higher value to a lower value, the lower value is not displayed in the bar chart. For example, if the capacity values range from terabytes (TB) to kilobytes (KB), the bar chart does not display information for capacity values in kilobytes. Related concepts Storage system reports on page 217 Reporting on storage systems 223

224 Pool Capacity Overview report The Pool Capacity Overview report displays the current snapshot of the pool capacity and usage for All Storage Systems, for a given category of storage system, or for a specific storage system from the Storage Systems view. This report differentiates the used pool and the subscribed usage across all storage systems or a selected storage system. Figure 9-3 Pool capacity overview In this report, the Pool bar indicates the volumes in your storage system used for pool creation. The Thin Vols bar indicates the carved out V-VOLs out of the DP Pool with the dark blue portion of the bar indicating the pool capacity associated with a host while the rest in light blue is the unallocated pool capacity. The Used Pages bar indicates the actual usage of the pool capacity. Note: If the capacity values range from a higher value to a lower value, the lower value is not displayed in the bar chart. For example, if the capacity values range from terabytes (TB) to kilobytes (KB), the bar chart does not display information for capacity values in kilobytes. You can use the following information displayed alongside the chart to compare Demand capacity versus Free capacity to identify a potential risk of running out of storage capacity: Used %: Indicates the percentage of total pool consumption derived by calculating the Used Pages by the Pool volume. Demand: Indicates the total capacity in demand, which could potentially be used. This value is the difference in capacity between total DP Volumes allocated capacity and Used Pages allocated capacity. Free: Indicates the actual available pool capacity. This value is the difference in capacity between Pool Physical Capacity and total Used Pages capacity. 224 Reporting on storage systems

225 Related concepts Storage system reports on page 217 Related references Pools dashboard default reports on page 53 Applications with Most SLO Misses (last 24 hours) report The Applications with Most SLO Misses report lists the top 5 applications with the most SLO misses recorded in the past 24 hours for a selected storage system or all storage systems in the Storage Systems view. You can use this list to identify the troubled applications that may need your immediate attention. Figure 9-4 Applications with most SLO misses (last 24 hours) It reports the following information for each application: Application: The name of the application. SLO Status (Last 24 Hrs): Provides a historical trend of SLO violations over the past 24 hours. Visual indicators indicate the following: A green bar indicates a period during which no violation of miss or borderline threshold occurred for any monitored SLO profiles. Note: A green bar can also indicate a data hole when no data was available from Agent for RAID and the application was monitored during that time. A red bar indicates a period during which a miss threshold was exceeded for one or more monitored SLO profiles. A yellow bar indicates a period during which a borderline threshold was exceeded for one or more monitored SLO profiles. A gray bar indicates the period when there was no SLO profile associated with the application (also known as unmonitored application). Reporting on storage systems 225

226 SLO Conformance: Indicates the percentage of time when the application conformed with all associated SLOs in the past 24 hours. Related concepts Storage system reports on page 217 Performance Overview by Storage System report The Performance Overview by Storage System report displays the various storage performance metrics and its values for your enterprise storage. It provides a breakdown of performance information by storage system to display which storage system is overloaded and which is under loaded. You can use this information to balance the load across your enterprise storage by moving volumes out from the overloaded storage system to that with less load. You can access this report from the Storage Systems view (Report drop-down list) for a particular category of storage system (e.g., Hitachi), the Storage System Performance Overview report on the dashboard (Dashboard tab), and Performance category of the Report gallery (Reports tab). Figure 9-5 Performance overview by storage system report This report displays the following information: Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. Avg. Response Time: The weighted average of the I/O response times for all the storage volumes used by the application per storage system. Total IOPS: An application s total IOPS for all parity groups, when reading from or writing to a volume on a storage system. Total DTR: The total amount of data an application is reading and writing for all parity groups. 226 Reporting on storage systems

227 Avg. Read Hit: The percentage of total read operations that are cache hits (for example, read operations accessed from cache) for all parity groups. Avg. Write Pending: The percentage of data in the cache/clpr (Cache Logical Partition) that is to be written to the storage system disk. Related concepts Storage system reports on page 217 Storage System Capacity Trend report The Storage System Capacity Trend report displays the capacity allocation and utilization trend for a selected Hitachi storage system or all storage systems (folder level) in the business view for the past 7 years. This report provides a breakdown of the storage capacity from physical parity groups and external storage virtualized through the storage system. This report appears by default on the Planning dashboard. It is also available in the content pane on the storage system business view and from the Select a Report drop-down list in the content pane. From the All Storage Systems level, this report displays an aggregated trend for all storage systems. You can choose to view the storage system capacity trend for all storage systems in a given category (for example, Hitachi) or for a selected storage system by specifying the appropriate criteria. See Specifying criteria for Storage System Capacity Trend report on page 228 Figure 9-6 Storage system capacity trend report This report displays the trend information for the following metrics: Internal Used: The allocated, reserved by pool, and reserved by system capacity from physical parity groups in the storage system. Reporting on storage systems 227

228 Internal Free: The unallocated and free capacity from physical parity groups in the storage system. External Used: The capacity allocated from external storage that is virtualized through the storage system. External Free: The unallocated external storage capacity. Note: For EMC systems, External Used and External Free are always set to zero. Related concepts Storage system reports on page 217 Related references Planning dashboard default reports on page 53 Storage system capacity forecast trend report on page 229 Specifying criteria for Storage System Capacity Trend report Specify report criteria in the Storage System Capacity Trend report to display the trend for a selected storage system. Prerequisites In order to specify criteria for the report, first open it from the Additional Reports list in Resources. Procedure 1. Select the report for use in the report viewer. 2. Click Filter and select any of the following criteria to filter trend data in the report. Attribute (Criteria): Storage System Operator: IN (Includes) Values: Choose from the available storage system names Value/ Range: Storage system names Multiple values allowed: Yes 3. Click Apply to apply the criteria, and then click Close to close the report criteria pane to view the report customized to your criteria. Example of checking capacity trends To view the Storage system capacity trend for USP_V and AMS2300 systems, specify the following criteria: Select Storage System from the Attribute drop-down list and IN from the Operator drop-down list. Select USP_V and AMS2300 from the list of values for the storage systems. 228 Reporting on storage systems

229 Click Apply to apply the criteria and filter the report accordingly. Storage system capacity forecast trend report The Storage System Capacity Forecast Trend report displays a forecast of storage system capacity over time for the metrics available in the Storage System Capacity Trend report. Launch the report in one of these ways: Open the Storage Systems business view in Resources. Select either All Storage Systems, a type of storage system (such as Hitachi or EMC) or an individual storage system. Open the report from the Select a Report list. Click the Forecast button in the Storage System Capacity Trend report. For more information, see Storage system capacity trend report on page 227. You can click the Filter button to select attributes, operators, and values for the forecast, including the date range, confidence level, and metrics. For more information, see Specifying criteria for the storage system capacity forecast trend report on page 230 The report displays the dates and confidence level selected as attributes to compute the forecast, including: Historical Data Start Date: The data for the oldest data available for forecasting. Forecast Start Date: The earliest date included in the forecast. This is the date after the forecast is launched. Forecast End Date: The last date included in the forecast. This can be 1 month, 3 months, 6 months, 9 months, or 1 year. Confidence Level: The reliability of the forecast, from 90 % to 99%. Reporting on storage systems 229

230 The graph displays a forecast of storage system capacity over time for each metric selected as an attribute. There is a legend displaying the name and color assigned to each metric. You can hover over the forecast to display confidence intervals for each point in the forecast. You can also drag the date line across the graph to display confidence intervals for the date shown at the top of the forecast. Date range controls The forecast includes tools to control the view of the range of dates. You cannot display dates outside the Forecast Start Date and Forecast End Date. Use the sliders below the forecast to expand or contract the date range. The range is reflected in the From and To fields. Enter a date in the From or To field and click Enter to change the dates displayed in the forecast. Click a Zoom option to display one of the available ranges, within the length of time selected for the forecast. Specifying criteria for the storage system capacity forecast trend report Specify report criteria for the Storage System Capacity Forecast Trend report to view a forecast of storage system capacity over time. Procedure 1. Click the Filter button in the report to edit the Attributes, Operators, and Values for the forecast. Attribute Operator Values Projection Input Data Projection Output Range Confidence Level (%) Metric EQ (equals) EQ (equals) EQ (equals) IN (includes) 1 month, 3 Months, 6 Months, 9 Months, or 1 Year through 7 Years. 1 month, 3 Months, 6 Months, 9 Months, or 1 Year 90 through 99 Select any or all: Internal Used, Internal Free, External Used, External Free. Note: The following fields are not available: Additional Filters Applied, All/Any, Top X, and Date Range. 2. Click Apply to save any changes and Close the window. 230 Reporting on storage systems

231 Pool Capacity Trend report The Pool Capacity Trend report displays the pool capacity usage trend for a selected storage system for the past 7 years. This report provides a breakdown of the total physical capacity, the subscribed and consumed capacity of a pool, and the risk ratio as a measure of capacity required to fulfill the subscription commitment when compared with the actual capacity available in the pool. You can access this report from the Select a Report drop-down list for a specific storage system in the content pane of the Storage Systems business view. By default, an aggregated trend chart for all pools for the selected storage system is displayed. To view both the pool capacity usage trend and the risk ratio for a specific pool, you can specify appropriate report criteria as described in Specifying criteria for Pool Capacity Trend report on page 233. You can interpret the risk ratio of a pool in the following ways: A value of 1 or less indicates that the pool has adequate physical capacity to meet the thin provisioning requirement. The ratio of 1 or less also suggests that the pool will not run out of disk space, irrespective of the consumption. A value greater than 1 suggests that the pool requires additional physical capacity to meet the subscription commitment. In addition, if the consumption increases suddenly, the pool is at greater risk of running out of disk space. In such cases, you can add more storage capacity to keep the risk ratio low. Figure 9-7 Pool capacity trend report This report displays capacity trend for the following metrics: Reporting on storage systems 231

232 Physical: Total physical capacity of the pool. Subscribed: Total capacity of all volumes created from the pool including both allocated and unallocated volumes. Thin Used: Total consumed capacity from the pool. Risk Ratio: Ratio of (Subscribed capacity - Thin used capacity) to (Physical capacity - Thin used capacity). Note: This report will not display the pool capacity usage trend for storage systems with no pools. In addition, t is unavailable for storage systems without HDP capability. An example of risk ratio calculation The risk ratio displayed on the pool capacity trend report is a measure of the capacity required to fulfill the subscription commitment compared with the total available free capacity of a storage pool. The following table illustrates the impact of capacity allocation and consumption on the risk ratio: Table 9-1 An example of risk ratio calculation No (A) Physical Subscribed (B) Thin used (C) Required capacity to meet subscription (D) Available capacity to meet subscription (E) Risk ratio (F) D/E B-C A- C GB 300 GB 50 GB 250 GB 50 GB GB 300 GB 60 GB 240 GB 40 GB GB 300 GB 70 GB 230 GB 30 GB GB 300 GB 80 GB 220 GB 20 GB GB 300 GB 80GB 220 GB 70 GB 3.14 For the pools listed in rows 1-4, observe that the risk ratio (F) changes with changes in the thin used capacity. In order to lower the risk ratio for a pool, you must add more physical capacity to meet the thin used capacity requirement. In this example, if you increase the physical capacity to 150 GB (row 5 in the table), observe that the risk ratio reduces to This ratio signifies that with a lower over provisioning ratio (Subscribed/Physical), the pool can meet the current subscription commitment without running out of capacity. The risk ratio trend is a powerful analytical tool to validate the effectiveness of your storage provisioning strategy over a period of time. A risk ratio consistently greater than 1 indicates that your actual capacity is inadequate to meet your subscription commitment at the current provisioned levels. Similarly, a ratio consistently less than 1 suggests that the pool will not 232 Reporting on storage systems

233 completely utilize the provisioned capacity beyond the current levels and you may safely move the unutilized capacity to another pool. Related concepts Storage system reports on page 217 Related references Pool Capacity Forecast Trend report on page 233 Specifying criteria for Pool Capacity Trend report Specify report criteria in the Pool Capacity Trend report to display pool capacity usage trend information for a specific pool in the selected storage system. Procedure 1. Select the report for use in the report viewer. 2. Click Filter and use any of the following criteria to filter trend data in the report: Attribute (Criteria): Pool Operator: EQ (Equal to) Values: Pool ID (Only one numeric value is allowed) Note: For EMC storage systems, the pool name is used instead of the pool ID. 3. Click Apply to apply the criteria, and then click Close to close the report criteria pane to view the report customized to your criteria. Example of checking pool capacity trends for a storage system To view the pool capacity trend for Pool 1 of a selected storage system, specify the following criteria: Select Pool from the Attribute drop-down list and EQ from the Operator drop-down list. Select 1 from the list of values for the pool IDs. Click Apply to apply the criteria and filter the report accordingly. Related references Pool Capacity Trend report on page 231 Pool Capacity Forecast Trend report The Pool Capacity Forecast Trend report displays a forecast of capacity over time for the metrics available in the Pool Capacity Trend report. Reporting on storage systems 233

234 Launch the Pool Capacity Forecast Trend report in one of these ways: Click the Forecast button in the Pool Capacity Trend report. For more information, see Pool capacity trend report on page 231. Open the Applications by Pool business view in the Resources tab. Select the report from the Additional Reports list. Figure 9-8 Pool Capacity Forecast Trend report You can click the Filter button to select attributes, operators, and values for the forecast, including the date range, confidence level, and metrics. For more information, see Specifying criteria for the Pool Capacity Forecast Trend report on page 235. The report displays the dates and confidence level selected as attributes to compute the forecast, including: Historical Data Start Date: The data for the oldest data available for forecasting. Forecast Start Date: The earliest date included in the forecast. This is the date after the forecast is launched. Forecast End Date: The last date included in the forecast. This can be 1 month, 3 months, 6 months, 9 months, or 1 year. Confidence Level: The reliability of the forecast, anywhere from 90 % to 99%. The graph displays a forecast of pool capacity over time for each metric selected as an attribute. There is a legend displaying the name and color assigned to each metric. You can hover over the forecast to display confidence intervals for each point in the forecast. You can also drag the date line across the graph to display confidence intervals for the date shown at the top of the forecast. 234 Reporting on storage systems

235 Date range controls The forecast includes tools to control the view of the range of dates. You cannot display dates outside the Forecast Start Date and Forecast End Date. Use the sliders below the forecast to expand or contract the date range. The range is reflected in the From and To fields. Enter a date in the From or To field and click Enter to change the dates displayed in the forecast. Click a Zoom option to display one of the available ranges, within the length of time selected for the forecast. Related references Pool Capacity Trend report on page 231 Specifying criteria for the Pool Capacity Forecast Trend report Specify report criteria for the Pool Capacity Forecast Trend report to view a forecast of pool tier capacity used by virtual volumes of a single application. For more information, see Pool tier utilization forecast trend report on page 187. Procedure 1. Click Filter to edit the Attributes, Operators, and Values for the forecast. Attribute Operator Values Projection Input Data Projection Output Range Confidence Level (%) Metric Pool EQ (equals) EQ (equals) EQ (equals) IN (includes) EQ(equals ) 1 month, 3 Months, 6 Months, 9 Months, or 1 Year through 7 Years. 1 month, 3 Months, 6 Months, 9 Months, or 1 Year 90 through 99 Select any or all: Physical, Subscribed, Thin Used, Risk Ratio. For HDT pools you can also select Tier 1 Used, Tier 1 Free, Tier 2 Used, Tier 2 Free, Tier 3 Free, Tier 3 Used. Select an available pool. You may need to add a row to the Attributes in order to display the Pool attribute. Note: The following fields are not available: Additional Filters Applied, All/Any, Top X, and Date Range. 2. Click Apply to save any changes and Close the window. Reporting on storage systems 235

236 Pool Utilization report The Pool Utilization report displays a heat map of the current pool utilization of a selected Hitachi storage system. The heat map categorizes pools in a storage system based on their capacity utilization percentage and provides a breakdown of the utilization information. You can view this report in the content pane of the Storage Systems business view when you select a specific storage system. The heat map provides a visual indication of the pool usage status of a selected storage system to help you identify pools that are underutilized and those that can run out of capacity. You can use this information to distribute load across the underutilized pools, and add more capacity to pools that are at risk of running out of capacity. The heat map displays cells representing the pools in a selected storage system, and the following colors represent the utilization percentages in the order of least used to heaviest used pools: Ivory: Indicates pool utilization percentage between Yellow: Indicates pool utilization percentage between Orange: Indicates pool utilization percentage between Red: Indicates pool utilization percentage between Note: Blank cells on the heat map indicate that there are no pools to display. Also, this report is unavailable for storage systems without pools and for storage systems with no pool capability. 236 Reporting on storage systems

237 Figure 9-9 Pool utilization report A tooltip appears when you hover over a cell on the heat map to display the following information: Pool (Pool name): The pool ID, and the pool name specified in Device Manager. If the pool name is not specified, this field is empty. Note: The Pool ID is not provided for EMC systems. Physical: Total pool capacity of the storage system. Thin Used: Total consumed capacity of the pool. Utilization: The percentage of thin used capacity to physical capacity. Related concepts Storage system reports on page 217 Reporting on storage systems 237

238 Application Capacity Utilization report The Application Capacity Utilization report displays the allocated capacity and the amount of storage that is being utilized by the applications for a given storage system. The applications are grouped according to the available capacity and the percentage of capacity that is currently being used where each grouping is represented by a bubble on the chart. Note: For EMC systems, applications that specify Logical Group (rather than the LUN Owner) in the Application Settings are not represented in this report. You can view this report in the content pane of the Storage Systems business view for all storage systems in a given category (for example, Hitachi) or for a selected storage system. Figure 9-10 Application capacity utilization report When accessing this report from the All Storage Systems folder, an aggregate of applications from all storage systems is presented or you can access a specific Storage System node to see just the applications for that particular storage system. 238 Reporting on storage systems

239 By hovering over a bubble, you can see the number of applications in a given grouping and the names of the top five applications based on the amount of capacity that is allocated, the percentage that each is utilizing and the alphabetic ordering of the application name. By clicking on a bubble or selecting the report from the Select a Report drop-down list, you can access the Application Capacity By Storage Class report that shows a filtered listing of all the applications associated with the grouping and their storage utilization that can be further analyzed based on your input criteria. Related concepts Storage system reports on page 217 Related references Application Capacity by Storage Class report on page 239 Application Capacity by Storage Class report The Application Capacity by Storage Class report provides details on the allocated capacity and usage by applications associated with a given tier or storage class. The statistics are provided for all storage systems from a given category (for example, Hitachi) that are contributing to a tier or storage class when selected from the folder level or for a specific storage system when selected from the node level. This information is useful for calculating and planning capital expenditures and can be saved for inclusion in a spreadsheet or in some other useful format. Note: No application data is provided for EMC systems when the Application Settings specify the Logical Group or Host setting. Access the report in one of these ways: Click one of the bubbles from the Application Capacity Utilization report or from the Select a Report drop-down list for a given category of storage system (for example, Hitachi) or for a specific storage system. The report is automatically populated with applicable values for applications in the grouping you have selected. For information about the Application Capacity Utilization report, see Application capacity utilization report on page 238. In the Reports tabs, click the Storage Economics category. For a more detailed analysis, you can edit the input criteria to generate customized reports as described in Specifying criteria for Application Capacity by Storage Class report on page 242. This report provides the following information: Application Name: Name of the application. Total Volumes: Total number of volumes allocated to the application from all contributing storage systems. Reporting on storage systems 239

240 Total Allocated: Total capacity allocated to the application from all contributing storage systems. Total Used: Total capacity used by the application from all contributing storage systems. Total Consumed %: Percentage of available capacity consumed by the application from all contributing storage systems. Storage System: Names of storage systems contributing capacity to the application. Volumes (Storage System): Sum of volumes allocated to the application from the current storage system. Allocated (Storage System): Available capacity allocated to the application from the current storage system. Used (Storage System): Available capacity used by the application from the current storage system. Consumed % (Storage System): Percentage of available capacity consumed by the application from the current storage system. Tier: HTSM Tier name (if applicable). Entries are presented in a comma separated list if multiple tiers are included. Note: For EMC systems, Tier data is not supported, as indicated by a dash (-). RAID Type: Shows the RAID type for a given storage system. Storage Class: Storage classification based on the storage resources available for a given application. The storage class details are generated based on the characteristics of storage system resources that are available for an application and are presented in a comma delimited list in the following order: 1. Disk type 2. Capacity 3. Speed 4. RAID level 5. Number of drives Volumes (Storage Class): Number of storage system volumes allocated to the application from the current storage class. Allocated (Storage Class): Sum of available storage system capacity allocated to the application from the current storage class. Used (Storage Class): Sum of available storage system capacity used by the application from the current storage class. Consumed % (Storage Class): Percentage of storage system capacity used by the application from the current storage class. The following table lists storage system types and the corresponding supported disk types. 240 Reporting on storage systems

241 Storage System Supported Disk Types VSP G1000 and VSP SATA SAS SSD FMD USP V/VM FC SATA SAS SSD USP FC SATA SAS HUS VM SATA SAS FMD HUS SAS SSD FMD Hitachi Adaptable Modular Storage (AMS) 2000 storage system family SATA SAS SSD EMC Symmetrix VMAX FC SATA The storage class details are generated based on the characteristics of storage system resources that are available for an application and are presented in a comma delimited list in the following order: Note: Data Pool volumes are grouped together as one record per application per type. For an HDP pool, the tier name begins with HDP and for an HDT pool the tier name begins with HDT and each case is represented in the associated storage class characteristics. Speed statistics are not provided in the class definition for SSD drives. Virtualized storage systems (such as AMS behind VSP), are grouped together as a single tier and are listed as an external storage class type. Application storage Related concepts Storage system reports on page 217 Related references Application Capacity Utilization report on page 238 Reporting on storage systems 241

242 Specifying criteria for Application Capacity by Storage Class report Specify report criteria for the Application Capacity by Storage Class report to view statistics on available storage system resources and to determine how they are currently being utilized by a given application. Procedure 1. Select the report for use in the report viewer. 2. Click Filter and use any of the criteria from the following table to filter data on the report. Table 9-2 Criteria for Application Capacity by Storage Class report Attribute (Criteria) Operator Allowable Value Value Multiple Values allowed? Storage System IN (Including) String Storage system name. Yes Consumption Range (in %) Allocation Range (in GB) Application Name BETWEEN x-y (default), GTEQ, LTEQ, LTGT BETWEEN x-y (default), GTEQ, LTEQ, LTGT LIKE (default), IN (Including) String String String Storage consumed by applications in a specified range. Only positive numbers are allowed with a maximum of 4 decimal places. Storage allocated for applications in a specified range. Only positive numbers are allowed with a maximum of 4 decimal places. Names of applications to be included in the statistics. Tier IN (Including) String Storage system tiers to be included in the statistics. Storage Class LIKE (default) IN (Including) String Storage Class entries to be included in the statistics. No No No (for LIKE) Yes (for IN) Yes Yes 3. Click Apply, and then click Close to close the report criteria pane to view the report customized to your criteria. Note: The Consumption Range input criteria does not currently have a corresponding data column in the report that is generated. As a work around, you can manually approximate and correlate the values between the criteria and the data columns shown in the report. 242 Reporting on storage systems

243 The Tier criteria applies only to the default tier names specified using the HTSM classification. Input criteria for storage class definitions is not currently supported. Example of checking application consumption To view details for all applications that have been allocated storage in a given range that are currently consuming in the upper range of their allocated limit, specify the following criteria: Select Storage System from the Attribute drop-down list, IN from the Operator drop-down list, and enter a valid name in the Values field. Select Allocation Range from the Attribute drop-down list, BETWEEN from the Operator drop-down list, and a range (for example, ) in the Values field. Select Consumption Range from the Attribute drop-down list, BETWEEN from the Operator drop-down list, and enter a range (for example, ) in the Values field. Click Apply to apply the criteria and filter the report accordingly. Related references Application Capacity Utilization report on page 238 Application Capacity Consumption by Storage System report The Application Capacity Consumption by Storage System report is a tabular report that displays the applications with the highest capacity consumption in the selected storage system. Access the report in the Storage System business view by selecting a storage system. Open the report from the Select a Report list. Reporting on storage systems 243

244 Figure 9-11 Application Capacity Consumption by Storage System report Click the Filter button to open options for: Top X: Choose the number of applications to display, up to 100. Date Range: You can select dates and hours for data to be displayed. The range is limited to the data available. If there is no data, the current date will display. Note: Holes in data at either end of the range will be filled with data 2 days after the start date or 2 days before the end date. The logic used for calculation will be affected but not the date range displayed. The default Start Date is the date of the earliest available data, up to 3 months prior to the End Date. The default End Date is the most recent date with data. The report includes the following fields: Field Application Description The application name. Click the hyperlink to open the Application Capacity Comparison Trend by Storage System for Application <application name> report. For more information, see Application capacity consumption trend by storage system for application report on page 245. Tags Physical Capacity User-defined tags applied to the application. Physical storage capacity allocated to the application. 244 Reporting on storage systems

245 Field Thin Capacity Total Capacity Thin Consumed Total Consumed Consumption from Storage System Net Growth Description Thin storage capacity allocated to the application. Total storage capacity allocated to the application. Thin storage capacity used by the application. Total storage capacity used by the application. Percentage of the storage system consumed by the application. The difference between current total consumed and the past total consumed. Application Capacity Consumption Trend by Storage System for Application report Access the Application Capacity Consumption Trend by Storage System for Application report from the Application Capacity Consumption by Storage System report to view the trend of consumption by the selected application for up to 7 years. Figure 9-12 Application Capacity Consumption Trend by Storage System for Application report The chart displays Storage System Capacity and the Consumed by Application capacity. Reporting on storage systems 245

246 Hover over the chart to view Physical, Thin, and Thin Consumed capacity and total Storage System Capacity for the storage system at any point in time. Drag the sliders below the chart to change the date range displayed. You can also control the date range with the From: / To: fields and the Zoom: control. 246 Reporting on storage systems

247 10 Using reports Command Director reports offer features that enable you to maximum their usefulness and flexibility. Features available in the report viewer About report viewer pagination controls Refreshing the report view Sorting a report Scheduling a report Exporting and downloading graphical reports in PDF Exporting and downloading a tabular report in Excel or XML Customizing tabular reports Saving a report Pinning reports to a selected dashboard Using reports 247

248 Features available in the report viewer The report viewer enables you to view, customize, and manage all drill-down and detailed reports in Command Director. In the report viewer, you can open multiple reports at one time, without disabling the initial report that was first opened. If you have multiple reports open, you can drag and reposition overlaying reports to make a specific report the active report window. Use the report viewer to sort, add or move columns, drag rows, or filter column information on any active report when multiple reports are open at the same time. The report viewer features are available in the Reports tab, Resources tab, and the Dashboard tab. However, the set of report viewer features available to you depends on from which tab you access the report. Reports in the report viewer have the features as listed in the following table: Table 10-1 Report viewer features Feature Data refreshing Report data sorting Displaying report data Reordering column positions Adding report columns Reordering row positions Searching reports for text matches Selecting columns to display Selecting column summary values to display Scheduling and distributing reports Description Refresh data at any time to retrieve and view the most current data. Sort report data in ascending or descending order by clicking the column header, and the sort order changes each time the column head is clicked. Review and display any page of report data by using the report pagination controls at the foot of the report viewer. Rearrange column positions in tabular reports by moving (click and drag) a column header horizontally to the desired location in the report. Create new report columns to dynamically customize the report with information extracted from the existing report data. Rearrange row positions in tabular reports by moving (click and drag) one or more column rows vertically to the desired location in the report. Search for alphanumeric text matches using the Find field in any tabular report (the Find field is located in the left lower corner of tabular reports). The first instance of matching alphanumeric text is highlighted in bold, and use the < (Next) and > (Previous) buttons to move to the next or previous instance of matching text. Select which columns you want to show or hide in a tabular report. Select the summary values (Maximum, Minimum, Sum, and Average) to display in tabular report columns that support this feature. Schedule when to automatically generate and send reports by in Microsoft Excel (XLS) or Extensible Markup Language (XML) format. 248 Using reports

249 Feature Exporting and downloading reports Saving reports Filtering report data Filtering report column data Pinning reports to a dashboard Description Export and download report data in either Excel or XML format and send it by , or upload it to a supported external program such as a spreadsheet to further process the data. Save a copy of any existing report or any report you customize (for example, one modified by sorting or filtering specific data) for later use. Customize reports to include only the report information that meets your specific search criteria by filtering the amount and types of data presented in a report. Customize report columns to include only the specific column information that meets your specific search criteria by filtering the amount and types of report data presented in individual columns of a report. Select reports in the report viewer and pin them to a dashboard you select. Note: Not all of the report viewer features are available for all reports. Related concepts About report viewer pagination controls on page 249 Related tasks Refreshing the report view on page 250 Sorting a report on page 250 Customizing tabular reports on page 253 Scheduling a report on page 251 Exporting and downloading a tabular report in Excel or XML on page 252 Saving a report on page 257 Refreshing the report view on page 250 About report viewer pagination controls You can review and display the pages of tabular report data in your reports by using the report pagination controls in the report viewer. All tabular reports with one or more pages provide the following report pagination controls at the foot of the report viewer: Row indicator that displays the number of rows in first page of report and the total number of rows in the report (for example: Rows 1 to 50 of 61). First Page icon (for example: to jump to the first page of the report, click this icon). Previous page icon (for example: to display the previous page of the report, click this icon). Using reports 249

250 Page list (for example: to display a desired page of the report, select that page number from this drop-down list). Next page icon (for example: to display the next page of the report, click this icon). Last Page icon (for example: to jump to the last page of the report, click this icon). Page Size list (for example: to display a desired number of rows per page, select that value from this drop-down list; 25, 50, 100, or 200). Refreshing the report view To obtain the most current data for a displayed report in the report viewer, click Refresh. This action fetches the latest data from the database that corresponds to your report. Any previous operations you completed on the report remain unchanged after the refresh, for example: Filtering by columns Sorting by columns Columns displayed or hidden Column order Report criteria Related tasks Sorting a report on page 250 Customizing tabular reports on page 253 Scheduling a report on page 251 Exporting and downloading a tabular report in Excel or XML on page 252 Saving a report on page 257 Sorting a report You can sort the report columns in all tabular reports in Command Director. Click the column headers to sort the values in ascending or descending order. Procedure 1. Open a drill-down report. 2. Click on a column header. The values are displayed in ascending order, and a down arrow appears next to the column header. Click the header again to display values in descending order, and an up arrow appears next to the column header. 250 Using reports

251 3. Click Save As if you want to save the report in the set sort order. You can choose to save the reports in a new folder or in an existing folder in Command Director. For more information about saving reports, see Saving a report on page 257. Related concepts Features available in the report viewer on page 248 Related tasks Saving a report on page 257 Customizing tabular reports on page 253 Scheduling a report You can schedule reports to be generated and sent via as Microsoft Excel (XLS) or Extensible Markup Language (XML) attachment. For example, you can generate and reports when an application violates its SLO thresholds and its response time is degrading. Procedure 1. Click on the report viewer to access the Schedule options. 2. In the Report Name field, enter a report name. 3. In the Recipient(s) list, select the users to whom you are sending the report. To add additional recipients, enter the recipient's address in Recipient (s), and click Add. 4. Under Format, select Excel or XML. 5. Under When, select one of the following choices: To send the report immediately, select Now. To send the report on a recurring basis, select Schedule and then specify when you want the report ed. From the Time drop-down list, select the time of day when you want the report ed. Under Recurrence Type, select how often the report is ed (daily, weekly, monthly, or yearly). If you select the weekly, monthly, or yearly intervals, select the corresponding information for the weekly, monthly, or yearly interval period in which to send the report. 6. When you have finished, click Send. 7. Click Close to return to the report. Related tasks Refreshing the report view on page 250 Sorting a report on page 250 Customizing tabular reports on page 253 Using reports 251

252 Exporting and downloading a tabular report in Excel or XML on page 252 Exporting and downloading graphical reports in PDF You can create a snapshot of a dashboard or a graphical report and save it as a PDF file. Each PDF contains the following additional information when generated: The area where the PDF was generated; for example, Global Dashboard, Global Dashboard Portlet, Resource Dashboard, Resource Dashboard Portlet, or report viewer. Breadcrumbs that display the navigational path to the report that has been captured. The default name of the PDF includes the name of the dashboard or report, as well as the time and date when generated. Reports can be exported and downloaded in PDF format in the following ways: To open or save a PDF snapshot of the entire Dashboard or Resources tab, click the PDF icon in the command bar in either tab. To open or save a PDF of an individual dashboard or graphical report, click the Download icon at the top of a report in the Dashboard or Resources tab. To open or save a PDF of an individual graphical report in the Reports tab, click Download in the report viewer, select PDF, and then click Download. Exporting and downloading a tabular report in Excel or XML You can export and download any tabular report using either Microsoft Excel (XLS) or Extensible Markup Language (XML) format. When using either XLS or XML to export and download a report, and you have completed any filter operations on the data, these changes will be listed in the downloaded file. Note: Only dashboard and graphical reports can be exported and downloaded using the Portable Document Format (PDF) format. Procedure 1. Click Download in the report viewer. 2. Click Excel or XML format. 3. Click Download to export and download the file. 4. Choose one of the following options: Click Open to open and view the report in either XLS or XML format. Click Save and navigate to a location to save the report in either XLS or XML format. 5. Click Close to return to the report viewer. 252 Using reports

253 Related tasks Refreshing the report view on page 250 Sorting a report on page 250 Customizing tabular reports on page 253 Scheduling a report on page 251 Saving a report on page 257 Customizing tabular reports You can customize your tabular reports in the following ways: Reorder column positions: Click and drag column headers horizontally to change their position in the report. Reorder row positions: Click and drag one or more column rows vertically to change their position in the report. Show and hide columns: Select which columns appear by selecting or clearing column names. Add new columns: Create new report columns to dynamically customize the report with information extracted from the existing report data. Show and hide summary column values (Maximum, Minimum, Sum, and Average) by selecting or clearing the corresponding check boxes (this is available only in those reports and columns that support this type of summary information). Filter data: Specify report criteria to display only the information that meets your specific criteria, and further refine information by specifying data in individual columns of a report to meet your specific search criteria. Find: Use this field in any tabular report to search for matching alphanumeric text (the Find field is located in the left lower corner of tabular reports). The first instance of matching alphanumeric text is highlighted in bold, and all matches within that page of the report are displayed. Use the < (Next) and > (Previous) buttons to move to the next or previous instance of matching alphanumeric text. Customizing reports in the report viewer Use the report viewer to open one or more reports at the same time, and click on any report in the background to make that the active report window. If you have multiple reports open, you can drag and reposition overlaying reports to make a specific report the active report window. You can sort data, move or add columns, drag rows, or filter column information on any active report when multiple reports are open at the same time. Note that not all option types are available for every report in the report viewer. Reordering column positions in a report To reorder column positions in a report, complete the following: 1. Select the report that you want to edit in the report viewer. Using reports 253

254 2. Click the column head that you want to reposition, and drag it to the desired column position in the report (you can only reorder one column at a time) 3. Click Close to close the modified report. Reordering row positions in a report To reorder row positions in a report, complete the following: 1. Select the report that you want to edit in the report viewer. 2. Click the row that you want to reposition, and drag it to the desired row position in the report. To reposition more than one row, click Ctrl, select the rows, and drag them to the desired row position. Note: You can reorder row positions in tabular reports even when not in report viewer. 3. Click Close to close modified report. Hiding specific information columns in a report To hide specific information columns (by selecting not to display them), complete the following: 1. Select the report that you want to edit in the report viewer. 2. Click Settings, clear the check boxes for the columns names that you do not want to display, and then click Apply. 3. Click Close to close the modified report. Displaying specific information columns in a report To display specific information columns, complete the following: 1. Select the report that you want to edit in the report viewer. 2. Click Settings, select the check boxes for those columns that you want to display, and then click Apply. 3. Click Close to close the modified report. Creating new columns in a report To create a new column in the report, complete the following: 1. Select the report that you want to edit in the report viewer. 2. Click the Add Column icon (adjacent to the last column). 3. In Column Name enter a name for the new column (for example, Total Free Memory). 4. In the Data Type list, select the appropriate type (for example, Memory). 5. In Expression, enter a Java script expression based on the existing column names (for example, Total Internal + Total External), and click Add Column. 6. Click Close to close the modified report. 254 Using reports

255 Hiding calculated summary information in all report columns To hide calculated summary information (Sum) in all report columns, complete the following: 1. Select the report that you want to edit in the report viewer. 2. Click Sigma, and clear the Show calculated summaries check box. 3. Click Apply and calculated summaries no longer appear at the bottom of each column. 4. Click Close to close the modified report. Displaying calculated summary information in all report columns To display calculated summary information (Sum) in all report columns, complete the following: 1. Select the report that you want to edit in the report viewer. 2. Click Sigma, and select the Show calculated summaries check box. 3. Click Apply and the calculated summaries are displayed at the bottom of each column. 4. Click Close to close the modified report. Hiding calculated summary information in selected report columns To hide calculated summary information in selected report columns, complete the following: 1. Select the report that you want to edit in the report viewer. 2. Click Sigma, and clear the check boxes (Max, Min, Sum, Average) for those columns of information that you do not want to display. 3. Click Apply and the calculated summaries are only displayed at the bottom of the columns you selected to display. 4. Click Close to close the modified report. Displaying calculated summary information in selected columns To display calculated summary information in selected report columns, complete the following: 1. Select the report that you want to edit in the report viewer. 2. Click Sigma, and select the check boxes (Max, Min, Sum, Average) for those columns of information that you want to display. 3. Click Apply and the calculated summaries are only displayed at the bottom of those columns that you selected to display. 4. Click Close to close the modified report. Specifying criteria for filtering data in a report To specify report-level criteria to use in filtering report data, complete the following: 1. Open the report that you want to edit in the report viewer, and click Filter. Using reports 255

256 Note: Only a subset of the standard reports allow report-level criteria for filtering report data. 2. Specify the criteria you want to use for filtering report data by selecting an option in the Attribute list, selecting an option in the Operator list, and entering a corresponding entry in the Values field. Click + to add additional entries for Attribute, Operator, and Values. Note: The Additional Filters Applied table lists all column-level filters that have already been applied to the data in this report. 3. (Optional if enabled) Choose the All or Any buttons to include all or any input criteria to customize a report view. 4. (Optional if enabled) Choose a numeric value in Top X field to refine the number of entries (1-100) that you want to display that match the data you specify. 5. (Optional if enabled) Click the Calendar icon to set a Date Range that includes Start and End Dates based on hourly or daily settings. 6. Click Apply to apply your input criteria to a report. Note: For tabular reports only, your input criteria filter is applied and displays as the first breadcrumb element above the columns, and this cannot be deleted. Hover the cursor over the breadcrumb element to show the detail of the input criteria applied to it. 7. Click Close to close the report filter dialog, and view the filtered report results. Specifying criteria for filtering data in selected report columns To specify report criteria for filtering data in individual columns in a report, complete the following: 1. Select the report that you want to edit in the report viewer. 2. Click the Filter icon (when displayed in a column), and choose one of the following filter types to configure (depending on the data type within the column): To configure a list filter, select check box choices from the list that correspond to your criteria (for example: Storage System, Model, Role, or Processor type). By default, all check boxes are selected. Scroll through the list and select or clear check boxes to define your filter criteria, and click Apply to display the selected values in the column. To configure a text filter, select an operator choice from the list that correspond to your criteria (for example: Starts with, Ends with, or Contains, enter text in the text box that corresponds to the operator choice, and click Apply to display the selected values in the column. 256 Using reports

257 To configure a slider-range filter, select a numeric value using the left and right slider controls that correspond to your filter criteria (for example: for report capacity in megabytes that range beginning at 2.4 to 22.9 MB, the left and right slider range would run between 0 and 23 MB), and the values you set will display in the To and From text boxes. After you define a filter range using the sliders, click Apply to display only those values that fall within the specified range. 3. Click Close to close the modified report. Related tasks Refreshing the report view on page 250 Sorting a report on page 250 Scheduling a report on page 251 Exporting and downloading a tabular report in Excel or XML on page 252 Saving a report on page 257 Saving a report Default reports are available in the report gallery and are for applications, hosts, storage systems, and file servers in business views. You can edit and customize them by hiding, reordering, adding and aggregating columns, as well as filtering and sorting column data. You can save a copy of the customized report to the My Reports tab in the report gallery, or in a list you can access using the Resources tab. Saved reports on the Resources tab When you select a report to save from the Resources tab and click Save As in the report viewer, the system saves a copy under Saved Reports in the Select a Report list. Using reports 257

258 Saved reports on the Reports tab Customized reports from the report gallery can be saved to a folder that you previously created or to a new folder that you are creating. These reports appear in the My Reports pane. 258 Using reports

259 Procedure 1. Select the report you want to save, and perform the following actions on the appropriate tab to save it: (On Resources tab) Click Save As, use the default name of the report in the Name field (or modify it as needed), click Save As, and click OK. This saves the report in the Saved Reports section in the Select a Report list. (On Reports tab) Click Save As, use the default name of the report in the Name field (or modify it as needed), click Save In, select New Folder and define a name in the Folder field or select an existing folder in the User Folder list, click Save As, and click OK. This saves the report in the new folder or the existing folder that you designated. 2. Click Close to return to the main Resources tab view or the main Reports tab view. Note: When you click Save As, this action creates a new report. When you open an existing report, you have two options: Save As or Save. Clicking Save As saves the existing report in its current state, and clicking Save overwrites the existing report with a new version. Related tasks Refreshing the report view on page 250 Sorting a report on page 250 Customizing tabular reports on page 253 Scheduling a report on page 251 Exporting and downloading a tabular report in Excel or XML on page 252 Pinning reports to a selected dashboard You can select reports that are displayed in the report viewer, use the existing report name or rename it, and pin the report to a selected dashboard by using the Pin feature. Using reports 259

260 Procedure 1. Click the Pin icon (in the report reviewer control bar). The Dashboard Selector dialog box displays. 2. (Optional) Use the existing report name, or enter a new name for the report in Report Name. Note: A report name is required and must be between 1 and 255 characters in length. 3. Click and highlight the name of the dashboard where you want the report to be displayed. 4. Click OK to pin the report to the specified dashboard. A status dialog box displays and confirms that the selected report is now pinned to the dashboard you have selected. You can pin a report to multiple dashboards by repeating this process. 5. Click OK to return to the report viewer. Postrequisites To hide a pinned report in a selected dashboard, click the Settings (gear) icon in the Dashboard tab, and clear the check box that corresponds to the report that you wish to hide. To remove a pinned report in a selected dashboard, click the Dashboard > Settings > Add/Remove tabs, select the report to delete in the Pinned Reports list, and click OK. For more details, see Specifying dashboard reports from the Settings dialog on page Using reports

261 11 Report gallery This module describes how to access and use information obtained from the report gallery. About the report gallery Utilization report gallery Performance report gallery Storage economics report gallery Asset and Inventory report gallery Chargeback report gallery Accessing reports Report gallery 261

262 About the report gallery Hitachi Command Director (HCmD) provides a comprehensive collection of predefined reports designed to provide an analysis of the overall health of your enterprise. You can easily customize each of these reports by changing any of its parameters and saving the customized reports separately. The following report categories are provided by default: Utilization: Includes reports that help you understand storage utilization and enable you to optimize the use of storage resources or provide utilization data to chargeback systems. Physical capacity by storage system on page 263 Pool capacity by storage system on page 265 Pool usage by application on page 271 Pool detailed capacity trend on page 264 Performance: Includes reports that provide insight into your enterprisewide storage performance to help you gain an overall understanding of potential storage problems that may arise over time. Storage port workload on page 273 Pool storage performance on page 274 Top 20 busiest storage system ports on page 275 Top 20 busiest parity groups on page 278 Top 20 most or least busy volumes on page 278 Underutilized volumes on page 281 Application SLO conformance on page 283 Performance overview by storage system on page 226 Application SLO conformance details on page 284 Storage Economics: Includes reports that help you optimize storage utilization by utilizing Hitachi s Tiered Storage technology. Top 10 tiers by capacity on page 293 Underutilized host filesystems on page 294 Replication capacity distribution by tier on page 294 Application capacity by storage class on page 239 Asset and Inventory: Includes reports that provide inventory details on physical assets in your enterprise for audit, planning, and other purposes. Storage system inventory on page 295 Filesystem inventory on page 296 Physical server inventory on page 297 Storage port details on page 298 Capacity by storage class on page 299 Chargeback: Includes reports that provide insight into your capacity consumption and allocation at an application/host per tier or per pool level so that your storage resources can be metered and you can charge back your application/host owners. 262 Report gallery

263 Note: Although the chargeback reports provide enough data for you to charge back the application/host owners, it requires further processing to generate a complete, final chargeback report. Application storage allocation by tier on page 300 Application storage allocation by pool on page 301 Storage allocation by VMware VMs on page 302 Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Utilization report gallery on page 263 Performance report gallery on page 273 Storage economics report gallery on page 293 Asset and Inventory report gallery on page 295 Chargeback report gallery on page 300 Utilization report gallery This module describes each of the utilization reports available in the Utilization report gallery. Physical capacity by storage system on page 263 Pool capacity by storage system on page 265 Pool usage by application on page 271 Pool detailed capacity trend on page 264 Physical Capacity by Storage System report The Physical Capacity by Storage System report provides a breakdown of your overall storage capacity indicating capacity from physical parity groups and external storage virtualized through the storage system. The detailed information gives you a view of different tiers of capacity and reports on usage of external storage. If the storage arrays are not balanced, you could potentially balance the uneven usage by off-loading data to low-tier external storage, and thereby making effective usage of external capacity. Access this report in one of the following ways: Click the graphic in the Storage System Capacity Overview report on the dashboard. For more information, see Storage system capacity overview on page 43. Click the Utilization category of the report gallery. This report displays the following information: Report gallery 263

264 Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). For third-party storage system registered using the SMI-S Provider, it is the storage system model and serial number. Model: The storage system model type. Internal Used: The allocated, reserved by pool, and reserved by system capacity from physical parity groups in the storage system. Internal Free: The unallocated and free capacity from physical parity groups in the storage system. Total Internal: Total capacity of all physical parity groups in the storage system. External Used: Capacity allocated from external storage that is virtualized through this storage system. If the storage system does not have external storage, this field displays a hyphen. The field also displays a hyphen for third-party storage. External Free: Unallocated external storage capacity. If the storage system does not have external storage, this field displays a hyphen. The field also displays a hyphen for third-party storage. Total External: Total capacity of external storage. If the storage system does not have external storage, this field displays a hyphen. The field also displays a hyphen for third-party storage. Total Allocated: Total allocated internal and external storage capacity of the storage system. If the storage system does not have external storage, this field displays the total allocated internal storage capacity. Total Unallocated: Total unallocated internal and external storage capacity. If the storage system does not have external storage, this field displays the total unallocated internal storage capacity. Reserved: Total capacity that is reserved and total pool capacity of the storage system. Total Parity Group Free: Total free space that includes internal and external free capacities. For third-party storage systems registered in Command Director, this field displays the free capacity of the Disk Group. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Utilization report gallery on page 263 Related references Global and DataCenter dashboards default reports on page 36 Storage System Capacity Overview report on page 43 Pool Detailed Capacity Trend report 264 Report gallery

265 Access the Pool Detailed Capacity Trend report in the Utilization tab of the report gallery. Click the Filter button to choose a storage system, pool, and metrics. Click the Forecast button to open the Pool Detailed Capacity Forecast Trend report. For more information, see Pool detailed capacity forecast trend on page 269. The chart displays the following: Date: The date for any given point in the chart. Tier1 Used: Capacity of Tier 1 in use. Tier1 Free: Unused capacity of Tier 1. Tier2 Used: Capacity of Tier 2 in use. Tier2 Free: Unused capacity of Tier 2. Tier3 Used: Capacity of Tier 3 in use. Tier3 Free: Unused capacity of Tier 3. Subscribed: Total volume capacity of the pool. Note: This report does not currently display capacity by disk type for Hitachi Unified Storage (HUS130, HUS150) Pools with Tier. Allocated: Total volume capacity of the pool that has at least one path. Pool Used: Total used capacity. Pool Free: Total unused capacity. Warning: Pool threshold 1, which is the user-defined threshold of the consumed capacity. Critical: Pool threshold 2, which is the system-defined threshold of the consumed capacity. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Utilization report gallery on page 263 Related references Pool detailed capacity forecast trend on page 269 Pool Capacity by Storage System report The Pool Capacity by Storage System report provides drill downs from storage system to storage pool to individual pool volumes. The utilization and subscription ratio informs you about your consumption of virtual capacity or if you are at risk of over-subscribing pools. Access this report in one of the following ways: Report gallery 265

266 From the Utilization category of the report gallery. Click the graphic in the Pool Capacity Overview report in the dashboard. For more information, see Pool capacity overview on page 45. This report displays the following information: Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). For third-party storage system registered using the SMI-S Provider, it is the storage system model and serial number. Click a storage system name to open the Storage capacity by pool for storage system report. Model: The storage system model type. Pool Capacity: Total pool capacity for the storage system. Used: The sum of all volumes consumed capacity for the storage system. Free: Total pool free capacity for the storage system. Used%: Percentage of used capacity by pool capacity. Subscribed: Total capacity of the volumes subscribing to the pool. Includes both allocated and unallocated volumes. Subscribed%: Percentage of subscribed volumes by pool capacity. # Pools: Total number of pools. # HDT Pools: Total number of pools that are HDT-enabled. HDT Pool statistics are not provided for EMC storage systems, as indicated by a dash (-). Note: When calculating Pool Volume statistics for EMC systems where some pool volumes have been disabled, the sum of used and free capacities is the EMC "Enabled Capacity" that excludes disabled volumes and, therefore, does not reflect the total pool capacity. Storage capacity by pool for storage system < storage system name > report Click the Storage System link in the Pool Capacity by Storage Systems report to view the storage capacity by pool details for a specific storage system. The following information is displayed: Pool: The pool ID. Click a pool ID to open the Pool Detailed Capacity Trend for Storage System <storage system>, Pool <pool> report. For more information, see Pool detailed capacity trend storage system pool on page 268. Pool Name: Pool name specified in Device Manager. If it is not specified in Device Manager, this column displays a hyphen. It will also display a hyphen when the volume is not part of a dynamic provisioning pool. 266 Report gallery

267 Click a pool name to open the Pool Detailed Capacity Trend for Storage System <storage system>, Pool <pool> report. For more information, see Pool detailed capacity trend storage system pool on page 268. Multi-Tier: Enabled or Disabled for Hitachi Virtual Storage Platform (VSP) pools. For other models, this field is not applicable and displays a hyphen. # Pool Volumes: Number of pool volumes. Pool Capacity: Total capacity of the pool. Used: Total pool used capacity. Free: Total pool free capacity. Demand: Pool Capacity less Used. Used%: Percentage of the used capacity by total pool capacity. Threshold1%: The user-defined threshold of the consumed capacity. Threshold2%: The system-defined threshold of the consumed capacity. # Thin Volumes: Total number of thin volumes. Subscribed: Total capacity of the DP volumes subscribing to the pool. Subscribed%: Percentage of the total DP volumes by pool capacity. Allocated: The capacity of thin volumes that have at least one path. The capacity of HDP volumes allocated to a Host or host group. Allocated Used: The consumed capacity of volumes that have at least one path. Unallocated: The capacity of volumes that have no path. Unallocated Used: The consumed capacity of volumes that have no path. # Applications: Total number of applications that have allocated volumes from this pool. # Pool Tiers: Total number of tiers on this pool. Applicable only for VSP pools. For other models, this field is not applicable and displays a hyphen. Note: The # Pool Tiers column does not currently show the number of tiers for Hitachi Unified Storage (HUS130, HUS150) storage systems. Tier Management: Auto or Manual for VSP or VSP G1000 pools. For other models, this field is not applicable and displays a hyphen. Note: For EMC systems, the pool ID, Multi-Tier, Threshold2%, # Pool Tiers and Tier Management values are not available as indicated by a dash (-). Thin Vols capacity for Pool for storage system < storage system name >, Pool < pool ID > (<pool name>) Click the Thin Vols link in the Storage Capacity by Pool for Storage System report to gain an in depth knowledge of all thin volumes for a specific pool. It also helps you to determine the thin volumes allocated to an application. The following information is displayed: Volume: The volume name. Report gallery 267

268 Volume Capacity: Volume capacity. Consumed Capacity: Volume consumed capacity. Application: Applications that have the thin volume allocated to it. If this volume is unallocated, a hyphen is displayed. Virtual Model: The virtual model name of the migration source. Virtual Serial No.: The virtual serial number of the migration source. Virtual LDEV: The virtual LDEV ID of the migration source. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Related references Pool Capacity Overview report on page 45 Pool detailed capacity trend for storage system pool Click the Pool link in the Storage Capacity by Pool for Storage System report to view a chart that displays the pool capacity trend for seven years for the selected storage system and pool. For more information, see Pool capacity by storage system on page 265. Click the Forecast button to open the Pool Detailed Capacity Forecast Trend report. For more information, see Pool detailed capacity forecast trend on page 269. The chart displays the following: Date: The date for any given point in the chart. Tier1 Used: Capacity of Tier 1 in use. Tier1 Free: Unused capacity of Tier 1. Tier2 Used: Capacity of Tier 2 in use. Tier2 Free: Unused capacity of Tier 2. Tier3 Used: Capacity of Tier 3 in use. Tier3 Free: Unused capacity of Tier 3. Subscribed: Total volume capacity of the pool. Note: This report does not currently display capacity by disk type for Hitachi Unified Storage (HUS130, HUS150) Pools with Tier. Allocated: Total volume capacity of the pool that has at least one path. Pool Used: Total used capacity. Pool Free: Total unused capacity. Warning: Pool threshold 1, which is the user-defined threshold of the consumed capacity. Critical: Pool threshold 2, which is the system-defined threshold of the consumed capacity. 268 Report gallery

269 Pool detailed capacity forecast trend You can use the Pool Detailed Capacity Forecast Trend report to predict pool capacity over time for metrics that are available in the Pool Detailed Capacity Trend report. You can access the report in the following ways: In the Resources tab, select the Applications by Pool business view and select a pool. Open the report from the Select a Report list. Click the Forecast button in the Pool Detailed Capacity Trend report. For more information, see Pool capacity by storage system on page 265. Figure 11-1 Pool Detailed Capacity Forecast Trend report Click the Filter button to select attributes, operators, and values for the forecast, including the date range, confidence level, and metrics. For more information, see Specifying criteria for the Pool Detailed Capacity Forecast Trend report on page 270 The report displays the dates and confidence level selected as attributes to compute the forecast, including: Historical Data Start Date: The data for the oldest data available for forecasting. Forecast Start Date: The earliest date included in the forecast. This is the date after the forecast is launched. Forecast End Date: The last date included in the forecast. This can be 1 month, 3 months, 6 months, 9 months, or 1 year. Report gallery 269

270 Confidence Level: The reliability of the forecast, anywhere from 90 % to 99%. The graph displays a forecast of capacity over time for each metric selected as an attribute. There is a legend displaying the name and color assigned to each metric. You can hover over the forecast to display confidence intervals for each point in the forecast. You can also drag the date line across the graph to display confidence intervals for the date shown at the top of the forecast. Date range controls The forecast includes tools to control the view of the range of dates. You cannot display dates outside the displayed Forecast Start Date and Forecast End Date. Use the sliders below the forecast to expand or contract the date range. The range is reflected in the From and To fields. Enter a date in the From or To field and click Enter to change the dates displayed in the forecast. Click a Zoom option to display one of the available ranges, within the length of time selected for the forecast. Related references Pool Detailed Capacity Trend report on page 264 Specifying criteria for the pool detailed capacity forecast trend report Specify report criteria for the Pool Detailed Capacity Forecast Trend report to view a forecast of capacity over time. For more information, see Pool detailed capacity forecast trend report on page 269. Procedure 1. Click the Filter button in the report to edit the Attributes, Operators, and Values for the forecast. Attribute Operator Values Projection Input Data Projection Output Range EQ (equals) EQ (equals) 1 month, 3 Months, 6 Months, 9 Months, or 1 Year through 7 Years. 1 month, 3 Months, 6 Months, 9 Months, or 1 Year 270 Report gallery

271 Attribute Operator Values Confidence Level (%) Metric EQ (equals) IN (includes) 90 through 99 Select any or all: Subscribed, Allocated,Pool Used, Pool Free, Warning, Critical. Note: The following fields are not available: Additional Filters Applied, All/Any, Top X, and Date Range. 2. Click Apply to save any changes and Close the window. Pool Usage by Application report The Pool Usage by Application report provides information about pool capacity usage by applications. The utilization and subscription ratio informs you about your consumption of virtual capacity or if you are at risk of oversubscribing pools. Access the report in one of these ways: On the Pools dashboard. In the Utilization category of the report gallery. From the #Applications field in the Top 20 Pool Utilization by Capacity report to view the report for the applications in the selected pool. For more information, see Top 20 pool utilization by capacity report on page 53. This report includes the following information: Application: The application name. LG Path: The logical group hierarchical path as defined in Device Manager. This field will display information when the application was created automatically based on logical groups in Device Manager. For more information about setting the auto create application option, see Creating applications automatically on page 367. Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. Pool: The pool ID whose volumes are allocated to the application. Pool Name: Pool name specified in Device Manager. If it is not specified, this field displays a hyphen. It will also display a hyphen when the volume is not part of a dynamic provisioning pool. Multi-Tier: Enabled or Disabled for Hitachi pools. For third-party models, this field is not applicable and displays a hyphen. Thin Vols: Number of thin volumes from this pool that are associated with the application. Report gallery 271

272 Allocated: Total capacity of all thin volumes that have at least one path and associated with the application. Used: The consumed capacity of all thin volumes that are associated with the application. Tier1 Used: The consumed capacity of the pool s thin volumes associated with the application, and mapped to Tier 1. The value will be a hyphen if it is not a multi-tier enabled pool. Tier1 DiskType: Type of disk. Tier2 Used: The consumed capacity of the pool s thin volumes associated with the application, and mapped to Tier 2. The value will be a hyphen if it is not a multi-tier enabled pool. Tier2 DiskType: Type of disk. Tier3 Used: The consumed capacity of the pool s thin volumes associated with the application, and mapped to Tier 3. The value will be a hyphen if it is not a multi-tier enabled pool. Tier3 DiskType: Type of disk. Tags: Tags assigned to the application. Tag type names are separated by a semi-colon and each tag name associated to the tag type is separated by a comma. Note: This report does not currently display Tier1 Used, Tier2 Used or Tier3 Used Capacity for Hitachi Unified Storage (HUS130, HUS150) Pools with Tier. Note: The LG Path, Pool ID, Multi-Tier, Tier<number> Used, and Tier<number> DiskType statistics are not provided for EMC systems, as indicated by a dash (-). Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Related tasks Creating applications automatically on page 367 Utilization report gallery on page 263 Related references Pools dashboard default reports on page 53 Top 20 Pool Utilization by Capacity report on page 53 Storage Pool Health Status report on page Report gallery

273 Performance report gallery This module describes each of the performance reports available in the Performance report gallery. Storage port workload on page 273 Pool storage performance on page 274 Top 20 busiest storage system ports on page 275 Top 20 busiest parity groups on page 278 Top 20 most or least busy volumes on page 278 Underutilized volumes on page 281 Application SLO conformance on page 283 Performance overview by storage system on page 226 Application SLO conformance details on page 284 Storage Port Workload report The Storage Port Workload report shows the current workload on existing storage ports thus enabling the storage administrator to assign appropriate ports for new application storage or for storage off load. You can also verify hot and cold ports by looking at both fan-in/fan-out ratio as well as performance statistics. You can access this report from the Performance category of the report gallery. This report displays the following information: Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. Port: The storage port name. Role: The role of the port such as target and RCU target ports. Fan In: Number of volumes with path. Fan Out: Total number of unique WWNs on HSD for each storage. IOPS: Sum of port I/O data, which includes Read IOPS and Write IOPS. DTR: Sum of port DTR (Data Transfer Rate), which includes Read DTR and Write DTR. Processor: The port processor associated with the storage port. This field is not applicable (displays a hyphen) for VSP and HUS VM ports that are dynamically allocated to the microprocessor based on its workload. Busy%: The port processor s utilization or performance rate. This field is not applicable (displays a hyphen) for VSP and HUS VM ports that are dynamically allocated to a microprocessor based on its workload. Report gallery 273

274 Max Busy%: The maximum port processor s utilization or performance rate. This field is not applicable (displays a hyphen) for VSP ports that are dynamically allocated to microprocessor based on its workload. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Performance report gallery on page 273 Pool Storage Performance report The Pool Storage Performance report provides drill-down reports for key performance metrics that will enable you to determine if a storage pool is over utilized from a performance perspective. You can access this report from the Performance category of the report gallery. This report displays the following information: Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. Pool: The pool ID. If available, the pool ID is a navigable link to the Parity Group Utilization for Pool <pool ID > (<pool name > )report. To review this report, see Parity group utilization for Pool on page 275. Note: The pool ID is not provided for EMC systems, as indicated by a dash (-). Pool Name: Pool name specified in Device Manager. If it is not specified in Device Manager, this column displays a hyphen. It will also display a hyphen when the volume is not part of a dynamic provisioning pool. Note: Although the Pool Name information is provided for EMC systems, and a link is provided to the Parity Group Utilization for Pool report, no utilization information is provided for this report. Pool Capacity: Total capacity of the pool. Free: Total free capacity of the pool. Total IOPS: Total IOPS (sum of Read IOPS and Write IOPS) for all volumes in the pool. Response Time: The weighted average response time for all thin volumes in the pool. Read IOPS: The average read IOPS for all thin volumes in the pool. Read Response Time: The read response time for all volumes in the pool. 274 Report gallery

275 Read Hit %: The weighted read hit % for all thin volumes in the pool. Write IOPS: The write IOPS for all volumes in the pool. Write Response Time: The write response time for all volumes in the pool. Total DTR: Total throughput (DTR) for all volumes in the pool. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Performance report gallery on page 273 Parity group utilization for pool The Parity group utilization for Pool report provides parity group utilization details for a given storage pool. Click the Pool link in the Pool Storage Performance report to view the Parity Group utilization report for a specific storage pool. The following information is displayed: Parity Group: The parity group name. RAID Type: RAID level, for example, Raid 5 (3D+1P). Drive Capacity: Total capacity of each drive in a parity group. Drive Speed: The parity group drive speed. Busy %: The parity group busy %. Total IOPS: Total IOPS for the parity group. Random IOPS: Random IOPS for the parity group. Sequential IOPS: Sequential IOPS for the parity group. Total DTR: Total DTR of the parity group. Top 20 Busiest Storage System Ports report The Top 20 Busiest Storage System Ports report provides information about the 20 busiest storage ports that potentially impact your applications. For each port, you can drill-down into the potentially impacted applications. You can access this report from the Performance category of the report gallery. This report displays the following information: Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. Port: The storage port name. Role: The role of the port such as the target and RCU target ports. Report gallery 275

276 Processor: The port processor associated with the storage port. This field is not applicable (displays a hyphen) for VSP ports that are dynamically allocated to microprocessor based on its workload. IOPS: Total IOPS (Read IOPS and Write IOPS) for the storage port. Max IOPS: Maximum IOPS for the storage port. DTR: Total DTR (Data Transfer Rate) for the storage port. Max DTR: Maximum DTR for the storage port. Busy%: The port processor busy percentage. This field is not applicable (displays a hyphen) for VSP ports that are dynamically allocated to microprocessor based on its workload. Max Busy%: The maximum port processor busy percentage. This field is not applicable (displays a hyphen) for VSP ports that are dynamically allocated to microprocessor based on its workload. Specifying report criteria You can specify report criteria to filter and customize the report to display focused results that suit your reporting requirements. To specify criteria for this report, see Specifying criteria for Top 20 Busiest Storage System Ports report on page 276. Applications using a specific busy storage system port Click the Port link in the Top 20 Busiest Storage System Ports report to view the applications that use a specific storage system port. The following information is displayed: Application: The application name using the storage system port. IOPS: Total IOPS (Read IOPS and Write IOPS) for the storage system port. DTR: Total DTR for the storage system port. Avg Response Time: The weighted average response time across all volumes in the application. Other Ports: List of other ports used by the application. Related concepts Features available in the report viewer on page 248 Accessing reports on page 303 Performance report gallery on page 273 Specifying criteria for Top 20 Busiest Storage System Ports report Specify report criteria for the Top 20 Busiest Storage System Ports report to filter ports on storage systems that are based on the port busy percentage to determine ports that are busy, and which in turn can impact application performance. You can also set criteria to view less busy volumes on specific storage systems. 276 Report gallery

277 Procedure 1. Select the report for use in the report viewer. 2. Click Filter and use any of the criteria from the following table to filter data on the report. Table 11-1 Criteria for Top 20 Busiest Storage Systems Ports report Attribute (Criteria) Operator Allowable value Range Multiple values allowed? Model IN (Including) String Model name Yes NOT IN (Not Including) String Model name Yes EQ (Equal to) String Model name No Busy % EQ (Equal to) Numeric No NE (Not equal to) Numeric No LT (Less than) Numeric No GT (Greater than) Numeric No LTEQ (Less than or equal to) Numeric No GTEQ (Greater than or equal to) Numeric No 3. Click Any or All to apply any or all of the selected criteria. 4. In the Top X field, set the number to display the top storage system ports that match your criteria. 5. Click Apply to apply the criteria, and then click Close to close the report criteria pane to view the report customized to your criteria. Example for identifying the busiest ports on selected storage systems To view the Top 20 Busy Storage System Ports report for all storage systems other than AMS2300, specify the following criteria: Select Model from the Attribute drop-down list. Select NOT IN from the Operator drop-down list. Select AMS2300 from the Values drop-down list. Click Apply to apply the criteria and filter the report accordingly. Related concepts Features available in the report viewer on page 248 Related tasks Saving a report on page 257 Related references Top 20 Busiest Storage System Ports report on page 275 Report gallery 277

278 Top 20 Busiest Parity Groups report The Top 20 Busiest Parity Groups report provides information about the 20 busiest parity groups that could potentially impact back-end storage performance, applications, or the storage pools that serve your applications. You can access this report from the Performance category of the report gallery. This report displays the following information: Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. Parity Group: The parity group name. RAID Type: RAID level, for example, Raid 5 (3D+1P). Drive Type: The parity group drive type. Drive Capacity: Total capacity of each drive in a parity group. Drive Speed: The parity group drive speed. Busy %: The parity group busy %. Total IOPS: Total IOPS (Read IOPS and Write IOPS) for the parity group. Random IOPS: Random IOPS for the parity group. Sequential IOPS: Sequential IOPS for the parity group. Total DTR: Total DTR (Data Transfer Rate) of the parity group. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Performance report gallery on page 273 Top 20 Most or Least Busy Volumes report The Top 20 Most or Least Busy Volumes report displays, by default, the top 20 most busy volumes of the configured storage systems in your environment. This report helps you identify the volumes that might impact back-end performance so you can promote them to a higher storage tier based on their usage by the applications. You can choose to view the top 20 least busy volumes of your configured storage systems and move these volumes to a lower storage tier; thereby, releasing them for high performance applications. To obtain such a report, apply the least busy criterion in the report viewer. For more information on how to specify report criteria, see Specifying criteria for Top 20 Most or Least Busy Volumes report on page Report gallery

279 You can access this report from the Performance category of the report gallery. This report displays the following information: Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. Volume: The volume ID. Click this link to display the performance report for this volume in Hitachi Tuning Manager. This report displays historical information for the past two hours only. Label: The volume label specified in Device Manager. If it is not specified, a hyphen is displayed. Parity Group: Parity group that includes the volume. Pool: The pool ID. When the volume is not part of a dynamic provisioning pool, this field displays a hyphen. Pool Name: Pool name specified in Device Manager. If it is not specified in Device Manager, this field displays a hyphen. It will also display a hyphen when the volume is not part of a dynamic provisioning pool. Tier: Storage tier that the volume belongs to. Capacity: Capacity of the volume. Total IOPS: Total IOPS for the volume. Total DTR: Total DTR (Data transfer rate) for the volume. IO Density: Total IOPS by volume capacity for the volume. Response Time: Average response time of the volume. Application: Application using the volume. Tuning Manager report display notes You can display the Tuning Manager report only when Device Manager and Tuning Manager that connect to the same storage systems are configured in the same HBase (Hitachi Base). If they are not, an error will be displayed when you launch the performance report. To successfully launch the performance report in Tuning Manager, make sure the Storage System Collectors for Device Manager and Agent for RAID in Command Director are enabled. To verify this, see Viewing information about Storage System Collectors on page 315. If at any time the Storage System Collectors are disabled or deleted, then the performance report launched for the selected volume will display an error message. However, for an already open performance report for any volume, you will be able to refresh or update the report. Enable the Storage System Collectors, or add them again if they are deleted. The Tuning Manager performance report window session remains active for 1,000 seconds, and then times out. To relaunch the report, close the active Report gallery 279

280 browser window of the Tuning Manager performance report, and then select the volume ID link in the Volumes List report. Changes to user profiles in Device Manager can affect the accessibility of the Tuning Manager report. If your user password has changed or the permission to launch Tuning Manager report is revoked, the Tuning Manager report is accessible to you for 15 minutes, and then the session is terminated. After you synchronize user accounts in Command Director, you must wait up to 15 minutes before accessing the Tuning Manager report again. If your account is locked, you will obtain an error message in the report window indicating an invalid session. After the lock has been removed, you must wait up to 15 minutes before accessing the Tuning Manager report again. Specifying report criteria You can specify report criteria to filter and customize this report to display results that suit your reporting requirements. To specify criteria for this report, see Specifying criteria for Top 20 Most or Least Busy Volumes report on page 280. Related concepts Features available in the report viewer on page 248 Accessing reports on page 303 Performance report gallery on page 273 Specifying criteria for Top 20 Most or Least Busy Volumes report Specify report criteria for the Top 20 Most or Least Busy Volumes report to view the top 20 least busy volumes in your configured storage systems, and use this information to move these volumes to a lower storage tier and release them for high performance applications. Procedure 1. Select the report to use in the report viewer. 2. Click Filter and any of use the criteria from the following table to filter data on the report. Table 11-2 Criteria for Top 20 Most or Least Busy Volumes report Attribute (Criteria) Operator Allowable Value Value Multiple Values allowed? Busy Metric EQ (Equal to) String IOPS or Response Time No Busy Type EQ (Equal to) String Most or Least Busy No 280 Report gallery

281 Attribute (Criteria) Operator Allowable Value Value Multiple Values allowed? Storage System EQ (Equal to) String Storage system name No Pool or Parity Group IN (Including) Numeric Based on Storage system configuration Yes 3. In the Top X field, set the number to display the top most or least busy volumes that match your criteria. 4. Click Apply to apply the criteria, and then click Close to close the report criteria pane to view the report customized to your criteria. Example of identifying the least busiest volumes To view the top 20 least busy volumes for the AMS2300 systems, specify the following criteria: Select Busy Metric from the Attribute drop-down list, EQ from the Operator drop-down list, and IOPS or Response Time from the Values drop-down list. Select Busy Type from the Attribute drop-down list, EQ from the Operator drop-down list, and Least Busy from the Values dropdown list. Select Storage System from the Attribute drop-down list, EQ from the Operator drop-down list, and AMS2300 from the Values dropdown list. To view the top 20 least busy volumes drilled down to the Pool level, select Pool from the Attribute drop-down list, IN from the Operator drop-down list, and 0 from the Values drop-down list. Click Apply to apply the criteria and filter the report accordingly. Related concepts Features available in the report viewer on page 248 Related tasks Saving a report on page 257 Related references Top 20 Busiest Storage System Ports report on page 275 Underutilized Volumes report The Underutilized Volumes report provides information about the volumes with lowest usage levels for the current quarter. This report helps you identify these underutilized volumes, so that you can move them to different tiers of the storage system to improve storage performance. In this report, volumes are considered underutilized using two metrics, IOPS and response time. If the volume's IOPS and response time values meet the Report gallery 281

282 default criteria, which is IOPS less than 100 and response time less than 5 milliseconds in the current quarter, then it is considered as underutilized. You can access this report from the Performance category of the report gallery. This report displays the following information: Storage System: The name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: Storage system model type. Volume: Volume ID. Parity Group: The parity group name. Pool: The pool ID. When the volume is not a part of a dynamic provisioning pool, this field displays a hyphen. Pool Name: Pool name specified in Device Manager. If it is not specified in Device Manager, this field displays a hyphen. It will also display a hyphen when the volume is not part of a dynamic provisioning pool. Max Response Time: The maximum response time for the volume. Time of Max Response Time: Data time of Max Response Time. Max IOPS: The maximum IOPS for the volume. Time of Max IOPS: Data time of Max IOPS. Applications: List of applications using the volume. Note: If volumes are moved between parity groups, the existing historical data of volume utilization is overwritten with new information. Specifying report criteria You can specify report criteria to filter and customize the report to display results that suit your reporting requirements. To specify criteria for this report, see Specifying criteria for Underutilized Volumes report on page 282. Related concepts Features available in the report viewer on page 248 Accessing reports on page 303 Performance report gallery on page 273 Specifying criteria for Underutilized Volumes report Specify report criteria for the Underutilized Volumes report to filter volumes based on its utilization using the maximum response time and maximum IOPS metrics, for a specific quarter or all quarters. 282 Report gallery

283 Procedure 1. Select the report for use in the report viewer. 2. Click Filter and use any of the criteria from the following table to filter data on the report. Table 11-3 Criteria for Underutilized Volumes report Attribute (Criteria) Operator Allowable value Range Multiple values allowed? Max Response Time Less than (LT) Numeric No Max IOPS Less than (LT) Numeric No Last Quarter Including (IN) String Name of Quarter Yes Equal to (EQ) String Name of Quarter No 3. Click Apply to apply the criteria, and then click Close to close the report criteria pane to view the report customized to your criteria. Example of viewing underutilized volumes To view the Underutilized volumes with a Max response time of 10 milliseconds and Max IOPS of 100 for the quarter Q1, specify the following criteria: Select Max Response Time from the Attribute drop-down list, LT from the Operator drop-down list, and enter 10 in the Values field. Select MAX IOPS from the Attribute drop-down list, LT from the Operator drop-down list, and enter 100 in the Values field. Select Last Quarter from the Attribute drop-down list, EQ from the Operator drop-down list, and select Q1 from the list of values available in the Values drop-down list. Click Apply to apply the criteria and filter the report accordingly. Related concepts Features available in the report viewer on page 248 Related tasks Saving a report on page 257 Related references Underutilized Volumes report on page 281 Application SLO Conformance report The Application SLO Conformance report lists all applications and its SLO conformance information for the past 30 days. For each of the monitored application in the Command Director environment, this report displays the percentage of time when an application conformed with a monitored SLO. Report gallery 283

284 You can use this list to identify the troubled applications and promote them to a higher storage tier to ensure SLO conformance. You can further process this report by exporting it to a spreadsheet to filter data by category and tag for more focused reporting on a particular business unit or customer as identified by your category and tag definitions. You can access this report from the Performance category of the report gallery. This report is sorted by the Application Name and displays the following information: Category: The tag category assigned to the application. If the application is not assigned to any category, then a hyphen is displayed. Tag: Tag assigned to the application. If the application is not assigned to any tag, then a hyphen is displayed. Application Name: The name of the application. LG Path: The logical group hierarchical path as defined in Device Manager. This field will display information when the application was created automatically based on logical groups in Device Manager. For more information about setting the auto create application option, see Creating applications automatically on page 367. SLO Conformance: Indicates the percentage of time when the application conformed with a monitored SLO in the past 30 days. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Related tasks Creating applications automatically on page 367 Performance report gallery on page 273 Application SLO Conformance Details report The Application SLO Conformance Details report, by default, provides an hourly update of SLO conformance details of applications that are in SLO violation - miss or borderline- for a selected time range. You can use this information to identify applications that consistently violate SLO, narrow down the time when the violations occur, and act based on this information to promote applications to a higher storage tier to ensure they meet the application s SLO. You can access this report from the Performance category of the report gallery. This report is sorted by SLO Conformance and displays the following information for the available data range: 284 Report gallery

285 Application: Name of the application. SLO Conformance: Indicates the percentage of time when the application conformed with a monitored SLO for the selected time range. Tags: Tags assigned to the application. If the application is not assigned to any tag, then a hyphen is displayed. LG Path: The logical group hierarchical path as defined in Device Manager. This field will display information when the application was created automatically based on logical groups in Device Manager. For more information about setting the auto create application option, see Creating applications automatically on page 367. Date-Time: Selected date and time range that displays the SLO status of the application for each day and time within the available data range. It can display any of the following statuses: Ok icon: Indicates that the application has no SLO violations. Warning icon: Indicates that the application has exceeded the borderline threshold of any of the monitored SLO types - Avg Storage Response Time or Total IOPS. Error icon: Indicates that the application has exceeded the miss threshold of any of the monitored SLO type - Avg Storage Response Time or Total IOPS. hyphen: Indicates no application exists for the specified duration. Specifying report criteria You can switch the report view mode from hourly to daily to gain a broader view of your application SLO conformance data. To obtain such a report, specify report criteria to filter and customize this report to display results that suit your reporting requirements. To specify criteria for this report, see Specifying criteria for Application SLO Conformance Details report on page 286. Application volume conformance details If you want to further analyze the application SLO conformance data by reviewing the SLO conformance of its provisioned volumes over a period of time, you can use the information provided in the Application Volume Conformance Details report available as a CSV file. For more information about how to generate this report, see Application volume SLO conformance details (CSV only) on page 289. Related concepts Features available in the report viewer on page 248 Accessing reports on page 303 Related tasks Creating applications automatically on page 367 Report gallery 285

286 Performance report gallery on page 273 Specifying criteria for Application SLO Conformance Details report Specify report criteria for the Application SLO Conformance Details report to obtain a daily view of your application SLO conformance data and in turn get a broader view of applications that are in SLO violation. Procedure 1. Select the report for use in the report viewer. 2. Click Filter and use any of the criteria from the following table to filter data on the report. Table 11-4 Criteria for Application SLO Conformance Details report Attribute (Criteria) Operator Allowable value Value/Range Multiple Values allowed? Application Name LIKE (contains) String Complete or partial application name No Tag Name IN (includes) String Category [Tag] name Yes Date Range Hourly Day, Hour Day range: Within the available data range with maximum up to 1 day. N/A Hour range: Within the allowable data range with a maximum up to 24 hours. Daily Day Day range: Within the allowable range when data exists, with a maximum of 30 days. N/A 286 Report gallery

287 3. Click Apply to apply the criteria, and then click Close to close the report criteria pane to view the report customized to your criteria. Examples of checking SLO conformance details Example 1: To view SLO conformance details for all applications tagged to the Sales function for two consecutive days, specify the following criteria: Select Tag Name from the Attribute list, IN from the Operator list, and Function [Sales] from the Values list. Select the date range. To confirm data is available for the selected date range, point your mouse to the tip icon in the Date Range box to view how much data is available. Click the double-up arrow icon, and then click Daily. Review the availability of data, set the start date and end date that spans two days accordingly, and then click Apply. With this selection, the report displays data for two days based on the period when the data is available. For example, if you entered the date range as 04/19 to 04/20 as shown in the figure above, the report will display data for the complete day (24 hours). Since there is no data present before 7:28 hours on 4/19, the report will display data only Report gallery 287

288 from this time onward until the end of the 24-hour period ending on 4/20. Example 2: To view SLO conformance details for all applications tagged to the Sales function, by hour of the day for 24 hours, specify the following criteria: Select Tag Name from the Attribute list, IN from the Operator list, and select Function [Sales] from the Values list. Select the date range. To confirm data is available for the selected day, point your mouse to the tip icon in the Date Range box to view how much data is available. Click the double-up arrow icon, and then click Hourly. Review the availability of data, and set the start and end dates accordingly. In the following figure, the highlighted days on the calendar confirm the availability of data. For this example, select the start date as 05/01 and the end date as 05/02. Set the time to span 24 hours. For example, set the report to show data from 9 am on 05/01 until 9 am on 05/ Report gallery

289 Click Apply. The displayed report will include SLO conformance details for applications that match the Sales tag for 24 hours spread across a two-day period. Related concepts Features available in the report viewer on page 248 Related tasks Saving a report on page 257 Related references Application SLO Conformance Details report on page 284 Application volume SLO conformance details (CSV only) The Application Volume SLO Conformance Details report available as a CSV file includes SLO conformance details of provisioned volumes over a period of time. This information helps you to analyze the application SLO conformance data by reviewing the SLO conformance details of its provisioned volumes over a period of time. You can further process this data by exporting the CSV file to a spreadsheet to filter data by storage systems, applications, or volumes for more focused reporting on violated volumes specific to storage systems. The CSV file is available in the following folder: _HCmD_Installation_Folder > \data\reports\dailydump The CSV file is created daily, and includes more detailed information about the application in violation, the volumes assigned to the application in violation, SLO metric that is violated, and allows you to specify more granular time intervals for the report dump. The CSV file is not created in the following cases: An application or its allocated volumes did not violate any SLO for an entire day. Performance data was not available from the configured Agent for RAID Extension, for example, when Agent for RAID Extension was disabled or its service was stopped. Report gallery 289

290 Information included in the CSV file SLO conformance information is included in the CSV file only if an application or any of its allocated volumes has violated a set SLO threshold on a particular day. The following table describes the conditions when the SLO conformance information is included in the CSV file: Condition Application SLO status Volume status SLO conformance information included in the CSV file? 1 OK (No SLO violation) 2 Miss/Borderline (In SLO violation) Ok - No SLO violation reported on any volume allocated to this application. Some volumes have reported SLO violation while the rest of the volumes have no violation. All volumes are in violation. OK - No SLO violation reported on any volume allocated to this application. Some volumes have reported SLO violation while the rest of the volumes have no violation. All volumes are in violation. No Yes - Only for volumes in SLO violation. Yes - For all volumes. Yes - For all volumes. The CSV file includes the following information: Date: Date and time of SLO violation in the format mm/dd/yyyy hh:mm. Volume: Volume ID or volume number. Storage System: The name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. Pool ID: The pool ID. If the volume is not part of a dynamic provisioning pool, a hyphen is displayed in this field. Note: For EMC systems, the pool ID is not provided. Pool Name: Pool name specified in Device Manager. If it is not specified in Device Manager, a hyphen is displayed in this field. Application: The application name. Tags: Tags assigned to the application. Tag category names are separated by a comma and each tag name associated to the tag category is separated by a comma. For example, category1[tag1, tag2], category2[tag3]. 290 Report gallery

291 LG Path: The logical group hierarchical path as defined in Device Manager. This field will display information when the application was created automatically based on logical groups in Device Manager. Application Status: SLO status of the application that can any of these: Borderline: Indicates that the application has exceeded the Borderline threshold of any of the monitored SLO type - Avg Storage Response Time or Total IOPS. Miss: Indicates that the application has exceeded the Miss threshold of any of the monitored SLO type - Avg Storage Response Time or Total IOPS. OK: Indicates that the application has no SLO violations. SLO Profile: The SLO profile associated with the application. SLO Profile Status: SLO profile status for an application whether OK, Miss, or Borderline. # Volumes in SLO Profile: Number of application volumes that use this profile. # Volumes in Application: Total number of volumes allocated to this application. Volume RT Status: SLO status of the response time for the volume. Volume IOPS Status: SLO status of the I/O operations per second for the volume. SLO Profile RT: Value (in ms) of the Average Response Time SLO profile at the time of violation. Volume RT: Value (in ms) of the volume response time at the time of violation. RT Miss Threshold: The miss threshold value (in ms) of the volume response time SLO profile. If this metric was not set in the SLO profile, then it will display a hyphen. RT Borderline Threshold: The borderline threshold value (in ms) of the volume response time SLO profile. If this metric was not set in the SLO profile, then it will display a hyphen. SLO Profile IOPS: Value of the I/O operations per second SLO profile at the time of violation. Volume IOPS: Value of the volume IOPS at the time of violation. IOPS Miss Threshold: The miss threshold value of the volume IOPS SLO profile. If this metric was not set in the SLO profile, then it will display a hyphen. IOPS Borderline Threshold: The borderline threshold value of the volume IOPS SLO profile. If this metric was not set in the SLO profile, then it will display a hyphen. SLO Profile DTR: Value in (MB/s) of the volume data transfer rate SLO profile at the time of violation. Volume DTR: Value in (MB/s) of the volume data transfer rate at the time of violation. Report gallery 291

292 CSV file creation The creation of CSV files is disabled by default. To enable creation, set the slo.conformance.dump.enable property to true in the custom.properties file available in the <HCmD_Installation_Folder>\conf directory. After you enable creation, a CSV file is created daily for the retention period you set as part of the report dump properties explained next after this section. _HCmD_Installation_Folder > \data\reports\dailydump\ onvolumesloconformance<@varname_mm-dd-yyyy >.csv For example, if you specify the retention period as 5 days starting from April 5, 2012, you will obtain five CSV files that includes all SLO status data in one file for each day: ApplicationVolumeSLOConformance csv ApplicationVolumeSLOConformance csv ApplicationVolumeSLOConformance csv ApplicationVolumeSLOConformance csv ApplicationVolumeSLOConformance csv Report dump properties To disable the creation of CSV files, modify the frequency of file creation, or specify the retention of these files, configure the following properties in the custom.properties file: Enable or disable creation of CSV files Property: slo.conformance.dump.enable Valid values: true to enable, false (default) to disable When you disable the creation of the CSV file and enable it again, CSV files that were created earlier than the current retention period will be deleted. If you want to retain old files, move them to a different directory before re-enabling the file creation. Specify the time in hours when you want to obtain a dump of the report data. Note: For optimal processing time, we recommend that you specify a value based on the number of storage systems configured in your environment. We recommend a low value for a large number of storage systems, and a high value for fewer storage systems. Property: slo.conformance.dump.interval.in.hours Valid values: 1 to 24. Default is Report gallery

293 Specify the period in days for how long you want to retain the report dump in the CSV files. Property: slo.conformance.dump.retention.in.days Valid values: 1 or higher. Default is 30. If you modify any of the above properties, save the custom.properties file. Examples of setting report dump properties To obtain the report dump (CSV file) at every hour, set the value of the slo.conformance.dump.interval.in.hours property to 1. To retain data in the dump files (CSV file) for a week, set the value of the slo.status.dump.retention.in.days property to 7. To disable the creation of the dump file, set the value of the slo.conformance.dump.enable property to false. Related references Application SLO Conformance Details report on page 284 Storage economics report gallery This module describes each of the storage economics reports available in the Storage Economics report gallery. Top 10 tiers by capacity on page 293 Underutilized host filesystems on page 294 Replication capacity distribution by tier on page 294 Application capacity by storage class on page 239 Top 10 Tiers by Capacity report The Top 10 Tiers by Capacity report shows the total capacity of the top ten storage tiers so you are informed about the tier composition in your data center. Having this information may aid you in planning updates to your storage tiers to better address your business needs. You can access this report from the Storage Economics category of the report gallery. Displays a bar chart that reports the top ten tiers with each bar in the graph representing a tier and the total capacity for this tier. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Storage economics report gallery on page 293 Report gallery 293

294 Underutilized Host Filesystems report The Underutilized Host Filesystems report aids in identification of underutilized hosts so you can reclaim storage from the hosts or deploy data to them, if warranted. You can access this report from the Storage Economics category of the report gallery. This report displays the following information: Host: The host name. OS Details: The host operating system details. Filesystem / Datastore: The name of the file system or datastore if the host is ESX. Capacity: Total capacity of all the volumes allocated to this host. Used: Used capacity of all the volumes allocated to this host. Free: Free capacity of all the volumes allocated to this host. Free %: Percentage of free capacity by total capacity. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Storage economics report gallery on page 293 Replication Capacity Distribution by Tier report The Replication Capacity Distribution by Tier report provides capacity details for your primary, secondary, and tertiary storage volumes that are allocated for replication on each tier. You can move secondary and tertiary data to lower cost tiers to reduce costs. You can access this report from the Storage Economics category of the report gallery. This report displays the following information: Tier: The tier name. Primary Copy: Total capacity of the primary volumes. CoW: Total capacity of Copy-on-Write volumes. SI: Total capacity of Shadow Image volumes. TC: Total capacity of True Copy volumes. HUR: Total capacity of Universal Replicator volumes. Thin Image: Total capacity of Thin Image volumes. GAD: Total secondary volume capacity for all global-active device S-VOL LDEVs. 294 Report gallery

295 Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Storage economics report gallery on page 293 Asset and Inventory report gallery This module describes each of the asset and inventory reports available in the Asset and Inventory report gallery. Storage system inventory on page 295 Filesystem inventory on page 296 Physical server inventory on page 297 Storage port details on page 298 Capacity by storage class on page 299 Storage System Inventory report The Storage System Inventory report provides physical component and connectivity details about your storage systems in the data center so you are informed of the physical capability of your storage assets. You can access this report from the Asset & Inventory category of the report gallery. This report displays the following information: Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. # Drives: Total number of drives in the storage system. Raw: Total capacity of all drives. # Parity Groups: Number of parity groups (or Array Group Count for EMC systems). # Volumes: Number of volumes. Internal: Total internal capacity of the storage system. External: Total external capacity of the storage system. # Ports: Total number of installed ports in the storage system. Note: By clicking on the # Ports link, you can access the Storage Port Details report that provides detailed information on the storage ports associated with a given storage system. Microcode Level: The microcode version of the storage system. Cache: Total capacity of the cache installed in the storage system. Report gallery 295

296 # WWNs: Total number of WWNs of all hosts connected to the storage system. # Hosts: Total number of hosts connected to the storage system. Note: The External and # Hosts values are not available for EMC systems as indicated by a dash (-). Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Asset and Inventory report gallery on page 295 Related references Storage Port Details report on page 298 Filesystem Inventory report The Filesystem Inventory report provides details about provisioned file systems of the discovered hosts in your environment. This report aids in identification of: file systems with physical volumes that are underutilized, so that you can move physical storage to virtual storage to optimize utilization and performance of available storage. Storage virtualization eliminates the over provisioning of physical storage, in which the storage capacity is allocated to individual hosts but remains unused. With storage virtualization, the existing unused storage can be reclaimed and reused. file systems that are provisioned across multiple tiers, so that you can realign these file systems to a single tier to obtain optimal performance. You can access this report from the Asset & Inventory category of the report gallery. This report displays the following information: Host: Name of the host. OS Details: The host operating system details. IP Address: The IP addresses associated with the host. File System: The name of the file system. Storage Type: The type of storage associated with the host. The storage types can be DAS (Direct Attached Storage), NAS (Network Attached Storage), or SAN (Storage Area Network). Capacity: Total capacity of the underlying volumes associated with the file system. Used: Used capacity of the underlying volumes associated with the file system. 296 Report gallery

297 Free: Free capacity of the underlying volumes associated with the file system. Mirror Status: Indicates whether the underlying volume has an associated secondary volume (S-VOL), which is a replica of the primary volumes (P- VOL) at the time of a backup and is kept on a standby storage system. The valid values are: Yes - All the underlying volumes in the storage system are mirrored volumes (have associated secondary volumes (S-VOL)). No - None of the underlying volumes in the storage system have associated secondary volumes. Partial - Some underlying volumes have associated secondary volumes. hyphen - Not applicable for the DAS file system. Thin Provisioned: Indicates whether the underlying volumes are carved out of the DP Pool (DP-VOL). Yes - All the underlying volumes in the storage system are DP volumes (DP-VOL), that are carved out from one or more DP Pools. No - None of the underlying volumes in the storage system are from the DP Pool. Partial - Some underlying volumes in the storage system are from the DP Pool. hyphen - Not applicable for the DAS file system. Tier: The name of the tier that this volume belongs to in Hitachi Tier Storage Manager (HTSM) tiers. If the underlying volumes are provisioned across tiers, then this field will display multi. For volumes provisioned to a single tier, the name of the tier is displayed. If the Storage System Collector is not configured to obtain tier information from HTSM, this field will display hyphen. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Asset and Inventory report gallery on page 295 Physical Server Inventory report The Physical Server Inventory report provides inventory details of all your physical servers and hypervisors with any of their underlying volumes from a monitored storage system. This list informs you about the types of operating systems, capacities, and applications existent on your servers. You can access this report from the Asset & Inventory category of the report gallery. This report displays the following information: Host: The host name. OS: Type of operating system. Report gallery 297

298 IP Addresses: List of IP addresses. # HBAs: Total capacity of all drives. # CPUs: Number of the CPUs of the host. Memory: Total memory of the host. Total Capacity: Total disk capacity of the host. For ESX hosts, the total capacity is the sum of VMDK capacities for which the user has collected storage system data. # LUNs: Number of LUNs allocated to the host. SAN Capacity: Total capacity allocated from the storage system to host. Applications: Applications mapped to this host. Note: Statistics for Total Capacity, # LUNs, and SAN Capacity are not supported for EMC systems, as indicated by a dash (-). Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Asset and Inventory report gallery on page 295 Storage Port Details report The Storage Port Details report shows the current configuration of all existing storage ports associated with a storage system and is useful when assigning or reallocating ports. You can access this report from the Asset & Inventory category of the Report gallery, as a hyper link from the # Ports column in the Storage System Inventory report, or from the Select a Report drop-down list in the content pane of the Storage Systems business view for all folder and leaf nodes associated with a given storage system. This report provides the following information: Storage System: Name of the storage system. If this name is not specified, the storage system model and serial number are provided. Model: Storage system model type. Port: Storage port name. Role: The role assigned for the port. Note: For EMC systems, the role specifies either Front End or Back End port details. Processor: Name of the Director that owns the port. Additional processor details are provided for EMC systems. 298 Report gallery

299 Note: A dash (-) is shown for VSP, VSP G1000, and HUS VM ports that are dynamically allocated to the microprocessor based on its workload. Fan In: Number of volumes with paths tied to the storage port. Fan Out: Total number of unique WWNs associated with a given storage port. Note: For Fan In and Fan Out, a dash (-) is shown for all ports with Initiator, LCP, RCP, or External Port roles. For EMC systems, a dash is shown for all ports with a Back End role. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Asset and Inventory report gallery on page 295 Capacity by Storage Class report The Capacity by Storage Class report provides capacity details for a given Storage Class including the number of volumes and pools that are capable of contributing storage and the amount of available storage that is being utilized. You can access this report from the Asset & Inventory category of the Report gallery. This report is also available from the Select a Report drop-down list in the content pane of the Storage Systems business view for all folder and leaf nodes associated with a given storage system. This report provides the following information: Storage Class: Storage classification that is defined through Hitachi Command Director based on the grouping of disk characteristics, such as disk type, capacity, speed, RAID level, and number of drives for a given storage system based on its pool usage. Note: For EMC systems, the storage classification is derived from the Disk Group statistics, including the disk type, capacity, and RPM. No RAID level details are provided for EMC Systems. Pools: Total number of pools that are contributing storage for a given Storage Class. Volumes: Number of volumes that are contributing storage for a given Storage Class. For a Storage Class that does not utilize pools, the value represents all of the volumes that are contributing storage. For a Storage Class that utilizes pools, the value represents all of the thin volumes that are contributing storage. Report gallery 299

300 Total Capacity: Total storage system capacity for a given Storage Class. For a Storage Class that does not derive its storage capacity from pools, the value represents the total physical capacity of all the array groups available for contributing storage. For a Storage Class that utilizes pools, the value represents the physical capacity available for all HDP and HDT pools. Allocated: Storage system capacity that is allocated from a given Storage Class. For a Storage Class that does not utilize pools, the value represents the sum of allocated capacity for all array groups. For a Storage Class that utilizes pools, the value represents the sum of all thin volumes that are allocated to hosts. Free Capacity: Free storage system capacity from a given Storage Class. For a Storage Class that does not utilize pools, the value represents the sum of free capacity for all array groups whereas for a Storage Class that utilizes pools, this is the free capacity for all available HDP pool volumes. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Asset and Inventory report gallery on page 295 Chargeback report gallery This module describes each of the chargeback reports available in the Chargeback report gallery. Application storage allocation by tier on page 300 Application storage allocation by pool on page 301 Storage allocation by VMware VMs on page 302 Application Storage Allocation by Tier report The Application Storage Allocation by Tier report provides a daily capacity allocation snapshot for the past 30 days, per tier for each application. This data can be fed into a chargeback system for billing purposes. Additionally, the data can be used to perform ROI analysis to compare internal cost versus external charge. This report also contains tags that enable you to organize the applications with the external tools that consume this type of report data. This report displays a unique combination of date, application, and tier data for each day. You can access this report from the Chargeback category of the report gallery. This report displays the following information: Date: The daily snapshot date and time. Application: The application name. 300 Report gallery

301 LG Path: The logical group hierarchical path as defined in Device Manager. This field will display information when the application was created automatically based on logical groups in Device Manager. For more information about setting the auto create application option, see Creating applications automatically on page 367. Tier: The name of the tier whose volumes are allocated to the application. This column displays a hyphen if this application's volumes are not associated to any tier. Note: Tier information is not applicable for EMC systems, as indicated by a dash (-). Capacity: Total capacity of all the volumes in the application that are associated with this tier for a given type of system (i.e., Hitachi or EMC) or the combined capacity when calculated from multiple types of systems. If the value of the tier is displayed as a dash, then the capacity of all the application volumes that are not associated to any tier is displayed. Tags: Tags assigned to the application. Tag category names are separated by a semi-colon and each tag name associated to the tag category is separated by a comma. Note: The applications that are not assigned to a tier are displayed in a separate row in the report with the tier value displayed as a hyphen. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Related tasks Creating applications automatically on page 367 Chargeback report gallery on page 300 Application Storage Allocation by Pool report The Application Storage Allocation by Pool report provides a daily virtual capacity allocation and consumption snapshot by pool, for the past 30 days, for each application. This data can be fed into a chargeback system for billing purposes. Additionally, the data can be used to perform ROI analysis to compare internal cost versus external charge. The report also contains tags that enable you to organize the applications with external tools that consume this type of report data. Note: For EMC systems, pool storage allocation information is only available when the LUN-owner setting is specified in the Application Settings. When specifying the Logical Group setting, no pool information is provided. Report gallery 301

302 You can access this report from the Chargeback category of the report gallery. This report displays the following information: Date: The daily snapshot date and time. Application: The application name. LG Path: The logical group hierarchical path as defined in Device Manager. This field will display information when the application was created automatically based on logical groups in Device Manager. For more information about setting the auto create application option, see Creating applications automatically on page 367. Storage System: Name of the storage system specified in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model: The storage system model type. Pool: The pool whose volumes are allocated to the application. Pool Name: Pool name specified in Device Manager. If it is not specified, this field displays a hyphen. It will also display a hyphen when the volume is not part of a dynamic provisioning pool. Multi-Tier: Enabled or Disabled for Hitachi Virtual Storage Platform (VSP) pools. For other models, this field is not applicable and displays a hyphen. Allocated: Total capacity of all thin volumes allocated to the application from this pool. Used: The used capacity of all thin volumes allocated to the application from this pool. Tags: Tags assigned to the application. Tag category names are separated by a semi-colon and each tag name associated to the tag category is separated by a comma. Note: For EMC systems, the LG Path, Pool, and Multi-Tier values are not available as indicated by a dash (-). Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Related tasks Creating applications automatically on page 367 Chargeback report gallery on page 300 Storage Allocation by VMware VMs report The Storage Allocation by VMware VMs report lists all the VMware virtual machines gathered by the configured vcenter collector, and provides a daily 302 Report gallery

303 virtual capacity allocation and consumption information for each VM for the past 30 days. You can use this data to review the allocated and used capacities for a specific VM instance, and use it to charge your customers accordingly based on their allocated capacity. You can access this report from the Chargeback category of the report gallery. This report displays the following information: Date: The daily snapshot date and time. VM Instance: The name of the VM instance. MAC Address: MAC address of the VM. If there are multiple MAC addresses, they are separated by commas. IP Address: IP address of the VM. If there are multiple IP addresses, they are separated by commas. OS Details: The OS type of the VM instance. ESX Server: The name of the ESX server. Allocated: Total capacity of all virtual disks allocated to the VM instance for a specific date. Used: The total used capacity of all file systems in the VM instance for a specific date. To obtain this data, VMware Tools must be installed and configured properly on the VMware guest OS; otherwise this value is displayed as a hyphen. For more information about how to install and configure VMware Tools, refer to the relevant VMware documentation. Related concepts Accessing reports on page 303 Features available in the report viewer on page 248 Chargeback report gallery on page 300 Accessing reports View both standard and saved reports from the report gallery, and the application, application folder, and host reports from the Resources tab. Hitachi Command Director (HCmD) provides a comprehensive collection of predefined standard and saved reports that are designed to provide an analysis about the overall health of your enterprise system. Related concepts Features available in the report viewer on page 248 Related references About the report gallery on page 262 Report gallery 303

304 Accessing reports from the report gallery You can access reports for a given category from the report gallery. Procedure 1. Select the Reports tab. The report gallery view is displayed. 2. From the report gallery, select one of the following tabs: Standard Reports: These are system-generated reports about the overall health of the system or provides insight about your storage environment (these are provided by default). My Reports - Saved Reports: This is a customizable report folder that contains your most frequently accessed reports. You can modify any standard report and save it as a new report under a folder that you specify. These reports will appear under this tab. 3. From the Standard Reports tab, select a category type, and click the report link to view it. Choose from one of the following categories: Utilization Performance Storage Economics Asset and Inventory Chargeback 4. After you select the category and click a report to view, use the report viewer buttons to: Refresh your view of the report Schedule the report Export and download the report Save a copy of the report Edit the report Accessing reports from the Resources tab You can access a specific report from the Resources tab. Procedure 1. Select the Resources tab. 2. From the Business Views menu, select a business view. 3. Choose a report from the Select a Report menu in the Content pane. 4. After you select a report to view, you can: Refresh your view of the report Schedule the report Export and download the report Save a copy of the report 304 Report gallery

305 Edit the report Report gallery 305

306 306 Report gallery

307 12 Administering Hitachi Command Director This module describes how storage administrators can perform administration tasks in Hitachi Command Director. Administration tasks overview Managing licenses Configuring Storage System Collectors Configuring Host Collectors Organizing resources by tagging Managing scheduled reports Configuring servers Configuring LUN Owner settings Specifying how applications are automatically created Managing Hitachi Command Director users Administering Hitachi Command Director 307

308 Administration tasks overview Administration tasks allow you to configure settings for Hitachi Command Director (HCmD), including the HCmD Server. Most Administration tasks require the Admin user role. Administration tasks include: Managing licenses and updating the license key when you purchase Hitachi Command Director or update storage capacity. Managing and configuring Storage System Collectors that are used to retrieve performance and configuration data. Managing LUN Owner settings to exclude volumes from the LUN Owner creation process or include them back. Configuring host monitoring profiles to monitor hosts. Managing SLO profiles that group Service Level Objectives (SLOs) and set the thresholds for which the applications are monitored. Managing reports scheduled to run on a recurring basis. Specifying the address and login details of your Simple Mail Transfer Protocol (SMTP) server. Synchronizing user accounts with Hitachi Device Manager. Setting the option to create applications automatically from the discovered hosts by the Host Collector and configured host groups by the Storage System Collectors. Discovering host information. You can use the Host Collector feature to configure Host Collectors and discover the hosts and their connectivity to the storage system arrays. Configuring storage system monitoring profiles to monitor caches, pools, processors, and parity groups. Related concepts Hitachi Command Director licenses on page 309 About LUN Owner configuration on page 356 Host discovery and agentless data gathering mechanism on page 330 About user management on page 369 About storage system data collection on page 312 Related tasks Configuring servers on page 355 Managing scheduled reports on page 354 Monitoring storage systems on page 114 Monitoring hosts on page Administering Hitachi Command Director

309 Managing licenses This module provides information about managing licenses and updating the license key when you purchase Hitachi Command Director. Hitachi Command Director licenses When you use Hitachi Command Director (HCmD) for the first time, you must specify a valid license. Your license must include a license key applicable to the physical disk capacity of the supported Hitachi storage system in your environment. After you perform refresh on the licensed storage systems, if the physical disk capacity exceeds the registered license keys (licensed capacity) you must register additional license keys. However, if you have license for unlimited physical disk capacity of the supported Hitachi storage systems, you will not be alerted to register additional license keys, or a license violation alert shown. When a license expires for a fixed storage capacity, a License Violation alert is displayed in the control bar. License types Related tasks Updating license information on page 310 Related references License types on page 309 The license key you receive from Hitachi Data Systems can be any of the following types: Permanent: Does not expire but is subject to the capacity licensing rules. It can be Permanent with fixed or unlimited storage capacity. AMS licenses are always Permanent licenses with unlimited storage capacity. Temporary: Expires in 120 days but has unlimited capacity. Emergency: Expires in 30 days but has unlimited capacity. Temporary license allows you to use Command Director before you purchase it. Emergency license overrides the capacity of the installed permanent license until you have a chance to upgrade it. Please contact your Hitachi representative to obtain a license. Administering Hitachi Command Director 309

310 Related concepts Hitachi Command Director licenses on page 309 Related tasks Updating license information on page 310 Updating license information You can check the license information to verify that your licenses are up-todate and note when they expire so that you can plan ahead. You can also register licenses or update licenses when they expire or when you add storage capacity. Procedure 1. In the control bar, click License. Figure 12-1 License configuration window 2. Under License Summary, view your general license information: Product: Hitachi Command Director. Version: The current version of the software. License Message: Messages regarding the license. For example, whether the license is expired. 3. Under License Details, view your current license information: Model: Hitachi storage system model. Serial Number: The storage system serial number for the selected model. License Type: Whether the license is permanent, temporary, or an emergency license. 310 Administering Hitachi Command Director

311 License Status: Whether you have the license for the required storage capacity or not. Current Capacity: The storage capacity in terabytes (TB) of your storage system. Licensed Capacity: The storage capacity you can use with the product without exceeding the license limit. However, if you have a license for unlimited storage capacity, this field will display Unlimited. Note: Licenses for Hitachi AMS storage systems and Hitachi Unified storage systems are not capacity based, and always show up as Unlimited after you enter license information for these storage systems. Expiration Date: When you must renew or upgrade your license. 4. Use the Device Manager pane to modify the appropriate license settings for Device Manager. Users with the View role are unable to access the Device Manager pane. IP Address: IP address for Device Manager. Port: Device Manager HTTP or HTTPS port (the default port is for HTTP and for HTTPS). SSL: Select to enable or clear to disable SSL communication between the Command Director server and Device Manager server (when selected, the port automatically changes to 22016). Note: If you want to enable SSL, make sure that SSL is enabled on the Device Manager server before you select the SSL check box. For more information about enabling SSL on the Device Manager server, see the Hitachi Command Suite Configuration Reference Guide. User ID: This is the Device Manager instance user ID, and the user ID is always system (you cannot change it). Password: The password of the system user account for Device Manager. 5. Enter the Hitachi Command Director license key in the Enter License pane. Users with the View role are unable to access the Enter License pane. 6. When you have finished, click OK. 7. Confirm that the license is successfully updated by viewing the displayed message. Related concepts Hitachi Command Director licenses on page 309 Related references License types on page 309 Administering Hitachi Command Director 311

312 Configuring Storage System Collectors This module provides information to set up the various Storage System Collectors for collecting configuration data and storage performance data. About storage system data collection Hitachi Command Director uses storage system collectors to collect storage system data from Hitachi storage systems and supported third-party storage systems. To generate relevant reports, configure your data collection appropriately. Storage System Collectors can be added, modified, removed, and temporarily disabled. Data collection from Hitachi storage systems Hitachi Command Director collects storage system configuration data from a number of SMI-I compliant third-party storage systems. For a list of supported third-party storage systems, see "Supported storage systems" in the Hitachi Command Director Installation and Configuration Guide. This information is then aggregated for SLO monitoring and reporting purposes. Storage System Collectors that retrieve configuration information from Device Manager are referred to as HDvM Data Collectors and must be configured with the host, port, and login credentials of the corresponding HDvM instance. Storage System Collectors that retrieve performance information from the Agent for RAID instances are referred to as Agent for RAID Extension (a component of Hitachi Command Director) and must be installed on the same server that includes Agent for RAID. You must configure a Storage System Collector for every Device Manager and Agent for RAID instance you want to collect data from. Performance data collection based on HTnM and Agent for RAID setup Hitachi Command Director obtains performance data from the Agent for RAID Extension component installed on each of the available Agent for RAID instances in your environment. Based on your system configuration and HTnM environment, the Agent for RAID instance can exist on the same server as the HTnM server, or separately on distinct hosts that connect to a single or multiple HTnM servers. The following figure illustrates the performance data collection mechanism based on how Tuning Manager and Agent for RAID are configured in your environment: 312 Administering Hitachi Command Director

313 In the above diagram: Configuration A illustrates the collection of performance data from storage systems that connect to the Agent for RAID instance installed on the same server as HTnM server and Agent for RAID Extension. HCmD server connects to Agent for RAID Extension to retrieve performance data. Administering Hitachi Command Director 313

314 Configuration B illustrates the collection of performance data from storage systems that connect to the different Agent for RAID instances, which also includes the Agent for RAID Extension installation in each of these instances. HCmD server connects to the various Agent for RAID Extension instances installed on each Agent for RAID host to retrieve performance data. Data collection from supported third-party storage systems Hitachi Command Director collects configuration data from third-party storage systems supported by SMI-S (SNIA Storage Management Initiative Specification). To collect configuration data, SMI-S Providers must be registered in Hitachi Command Director. After registration, the HCmD Data Collector communicates with the SMI-S Provider to collect configuration data from third-party storage systems. For example, the HCmD Data Collector communicates with the EMC SMI-S Providers to obtain configuration data from EMC Symmetrix VMAX SE storage arrays. The SMI-S Provider must be configured with its IP address, port, and login credentials. Data collection management After configuring storage system data collection, you can monitor whether the data was retrieved successfully and when Hitachi Command Director was refreshed. You can also modify the default data refresh frequency. The configuration data is collected every four hours, by default or at user specified interval. The performance data (for Hitachi storage systems only) is collected every five minutes and then correlated with the configuration data available at that point in time with Hitachi Command Director and used to update reports. 314 Administering Hitachi Command Director

315 Related tasks Viewing information about Storage System Collectors on page 315 Configuring Storage System Collectors on page 319 Modifying how often data is refreshed on page 326 Enabling and disabling Storage System Collectors on page 328 Viewing storage system data collection history on page 324 Viewing information about Storage System Collectors You can view a list of your Storage System Collectors and their information, which also includes: Storage information by storage system Storage domain information (for Hitachi storage systems only) To view information about Storage System Collectors: Procedure 1. Select the Administration tab. Administering Hitachi Command Director 315

316 2. Under Data Collection, click Storage System Collectors. The Storage System Collectors window is displayed. Figure 12-2 Storage System Collectors This tab provides information for each configured Storage System Collector. Name Type IP Address Port Item HTnM IP Address (for Agent for RAID Extension only) HTnM Port (for Agent for RAID Extension only) User ID (for Device Manager, Tiered Storage Manager, and SMI-S Provider only) Last Operation Cfg. Data Time Description The name associated with the Storage System Collector. Whether the Storage System Collector belongs to Hitachi Device Manager (HDvM), Agent for RAID Extension, Tiered Storage Manager (HTSM), or SMI-S Provider. The IP address of the host using the Storage System Collector. The port number configured for the Device Manager, Agent for RAID Extension, Tiered Storage Manager, or SMI-S Provider. When a port other than the default is specified during installation or configuration, you can view it here. The IP address of the HTnM server that connects to the Agent for RAID host that includes Agent for RAID Extension. The port number of the HTnM server. The user ID associated with the Device Manager Data Collector or the HCmD Data Collector for SMI-S Provider. Which operation (scan or refresh) was performed and whether it was successful or not. The local date and time when the last configuration occurred on the HCmD Server. Action Enabled (ON): The Storage System Collector is enabled (active). Disabled (OFF): The data collector is disabled (inactive). Edit icon : Click this icon to modify the name, port number, or HCmD Server IP address of a specific Storage System Collector. 3. View your storage information by storage system. In the Storage System Collectors window, select the Storage Systems tab. This tab lists your storage information by storage system. 316 Administering Hitachi Command Director

317 Item Storage System Description For a Hitachi storage system, it is the name of the storage system configured by Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Model Total Capacity For third-party storage system registered using the SMI-S Provider, it is the storage system model and serial number (for example, SYMMETRIX ). The storage system model type. The amount of storage available in the storage system. # Volumes The number of logical devices (storage disks) assigned to the storage system. Configuration Data Collector Performance Data Collector Cfg. Data Time Perf. Data Time Message Action The IP address of the HDvM data collector configured for the storage system. The IP address of the Agent for RAID Extension collector configured for the storage system. Time indicating when the configuration data was last updated. Time indicating when the performance data was last updated. The error messages received from Agent for RAID Extension. Enabled (ON): Storage system is enabled (active). Disabled (OFF): Storage system is disabled (inactive). 4. View storage domain information. In the Storage System Collectors window, select the Storage Domains tab. Note: Storage domain information is displayed for Hitachi Storage Systems only. This tab displays the list of storage domains. Item Description Storage Domains Storage System Model The name of the storage domain. The name of the storage system assigned as the domain controller of the specified storage domain. The storage system model type. # Tiers The number of tiers defined in the specified storage domain. Tier Data Collector Last Execution The Storage System Collector type (HTSM) and its IP address. The local date and time of storage domain data collection operations that were last executed on the HCmD Server. Related tasks Viewing details about a specific Storage System Collector on page 326 Configuring Storage System Collectors on page 319 Modifying Storage System Collectors on page 321 Deleting Storage System Collectors on page 323 Administering Hitachi Command Director 317

318 Enabling and disabling storage systems on page 328 Viewing storage system data collection history on page 324 Modifying how often data is refreshed on page 326 Manually refreshing data on page 327 Enabling and disabling Storage System Collectors on page 328 Prerequisites for configuring Storage System Collectors Before configuring storage system collectors, note the following: For Device Manager, note your Device Manager instance information. For Agent for RAID: An Agent for RAID Extension must be installed on every host on which Agent for RAID is installed. Have available the IP address and port number of every Agent for RAID installed in your environment. The Agent for RAID instances must be configured to run in Storage Logical Partition (SLPR) unrestricted mode. Failing to do so will result in partial data collection for that instance. For details about how to set up the Agent for RAID for this functionality, see the Hitachi Command Suite Tuning Manager Software Installation Guide. Enable the Agent for RAID Extension service using the following steps: On Windows: In the Services panel, select Agent for RAID Extension, right-click, and select Start to start the service. Alternately, to start this service automatically the next time you start the system, right-click, select Properties, and set the Startup type of the service to Automatic. On Linux: Navigate to the AgentforRAIDExtension/bin folder in the <Agent_for_RAID_Installation_Folder> and copy the script AgentforRAIDExtension to the /etc/init.d folder. Modify permission of the executable to grant execute permission to the root user. Then, run the following command to start the Agent for RAID Extension service: #/etc/init.d/agentforraidextension start Run the following command to confirm that the Agent for RAID Extension service is running: #ps aux grep <AgentforRAIDExtension/process name> For HTSM, configure an HDvM Data Collector prior to configuring a corresponding HTSM Data Collector. HTSM uses storage system configuration data from Device Manager. Related tasks Configuring Storage System Collectors on page 319 Enabling and disabling storage systems on page Administering Hitachi Command Director

319 Viewing storage system data collection history on page 324 Configuring Storage System Collectors If during the Hitachi Command Director installation you did not add all the data collectors for Hitachi Device Manager (HDvM), Agent for RAID Extension, Tiered Storage Manager (HTSM), or SMI-S Provider, or there are new ones, you can add them manually. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Storage System Collectors. 3. Click New. The New Storage System Collector dialog box is displayed. Figure 12-3 New Storage System Collector 4. Use the information in the following table to specify information for each data collector type: Table 12-1 New Storage System Collector configuration Type Setting Description Agent for RAID Extension Name IP Address Port Enter the name associated with Agent for RAID Extension. The name must not exceed 50 characters and can include characters a-z, A-Z, digits 0-9, dash(-), or underscore (_). Enter the IP address of the Agent for RAID host where Agent for RAID Extension is installed. If during the installation you specified a port other than the default (25075), enter it here. Note that Hitachi does not recommend that you change the default port number. Administering Hitachi Command Director 319

320 Type Setting Description SSL Select the checkbox to enable SSL communication between the Command Director server and Agent for RAID Extension (Agent for RAID host). Note: Before you select the SSL checkbox, make sure that SSL is enabled on the Agent for RAID host where Agent for RAID Extension is installed. For more information about enabling SSL on the Device Manager server, see Hitachi Command Suite Configuration Reference Guide. To enable SSL on Agent for RAID Extension, see the Hitachi Command Director Installation and Configuration Guide. HTnM IP Address Enter the IP address of the Tuning Manager server that connects to the Agent for RAID host where Agent for RAID Extension is installed. This information is required to support the link and launch capability to display the Tuning Manager Performance Reporter from HCmD. HTnM Port Enter the port number of the Tuning Manager server. HCmD Server IP Address This information is required to support the link and launch capability to display the Tuning Manager Performance Reporter from HCmD. Specify the IP address of the HCmD Server used by Agent for RAID Extension to send performance files every 5 minutes to HCmD. HDvM IP Address Enter the IP address of the host using the Device Manager data collector. Name Port SSL Enter the name associated with the Device Manager data collector. If during the installation you specified a port other than the default (2001), enter it here. Note that Hitachi does not recommend that you change the default port number. Select the checkbox to enable SSL communication between the Command Director server and Device Manager server. Note: Before you select the SSL checkbox, make sure that SSL is enabled on the Device Manager server. For more information about enabling SSL on the Device Manager server, see Hitachi Command Suite Configuration Reference Guide. To enable SSL on Command Director server, see the Hitachi Command Director Installation and Configuration Guide. User ID Password Enter the user ID for Device Manager. The user ID must have access to all the storage systems registered in the Device Manager server. Enter the password for Device Manager. 320 Administering Hitachi Command Director

321 Type Setting Description HTSM IP Address Select the IP address of the host using the Device Manager and Tiered Storage Manager Data Collector. Name Port Enter the name associated with the Tiered Storage Manager Data Collector. Specify the port number published for the remote HTSM CLI client. The default port number is User ID Password If during the installation you specified a port other than the default, enter it here. Note that Hitachi does not recommend that you change the default port number. Enter the user name registered in HTSM. The User ID must have reference and modify permissions. Enter the password for the user registered in HTSM. SMI-S Provider IP Address Enter the IP Address of the SMI-S provider connected to the third-party storage system. For example, the IP address of the supported EMC SMI- S provider v4.2 or 4.3. Name Port SSL Enter the name associated with the SMI-S Provider. If during the installation you specified a port other than the default (5989), enter it here. By default, the SSL communication between the Command Director server and SMI-S Provider is enabled. Click the checkbox to disable SSL communication. User ID Password Enter the user ID for SMI-S Provider. The user should be assigned any of these user roles - Administrator, Manager, Monitor, or Security Administrator. Enter the password for the user registered in SMI-S Provider. 5. When finished specifying the data collector settings, click OK. Related tasks Modifying Storage System Collectors on page 321 Deleting Storage System Collectors on page 323 Viewing information about Storage System Collectors on page 315 Modifying Storage System Collectors If during the installation you did not configure all the data collectors for Device Manager, Agent for RAID Extension, Tiered Storage Manager, or SMI- S Provider, or there have been changes, you can configure them manually. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Storage System Collectors. Administering Hitachi Command Director 321

322 3. Click the Edit icon for the storage system information you are editing. The Edit Storage System Collector dialog box is displayed. Figure 12-4 Edit Storage System Collector 4. Use the information in the following table to modify appropriate information for each data collector type: Table 12-2 Storage System Collector configuration Type Setting Description Agent for RAID Extension Name Port SSL HTnM IP Address HTnM Port HCmD Server IP Address Enter the name associated with Agent for RAID Extension. Enter the port number. Note that Hitachi does not recommend that you change the default port number (25075). Select the checkbox to enable or disable SSL communication between the Command Director server and Agent for RAID Extension (Agent for RAID host). Enter the IP address of the Tuning Manager server that connects to the Agent for RAID host where Agent for RAID Extension is installed. Enter the port number of the Tuning Manager server. Specify the IP address of the HCmD Server used by Agent for RAID Extension. HDvM Name Enter the name associated with the Device Manager data collector. Port Enter the port number. Note that Hitachi does not recommend that you change the default port number (2001). 322 Administering Hitachi Command Director

323 Type Setting Description SSL Select the checkbox to enable or disable SSL communication between the Command Director server and Device Manager server. User ID Password Enter the user ID for Device Manager. The user ID must have access to all the storage systems registered in the Device Manager server. Enter the password for Device Manager. HTSM Name Enter the name associated with the Tiered Storage Manager Data Collector. Port User ID Password Specify the port number published for the remote HTSM CLI client. The default port number is Note that Hitachi does not recommend that you change the default port number. Enter the user name registered in HTSM. The User ID must have reference and modify permissions. Enter the password for the user registered in HTSM. SMI-S Provider Name Enter the name associated with the SMI-S Provider data collector. Port SSL User ID Password 5. When you have finished, click OK. Related tasks Enter the port number. Select the checkbox to enable or disable SSL communication between the Command Directorserver and SMI-S Provider. Enter the user ID for SMI-S Provider. The user should be assigned any of these user roles - Administrator, Manager, Monitor, or Security Administrator. Enter the password for the user registered in SMI-S Provider. Deleting Storage System Collectors on page 323 Viewing information about Storage System Collectors on page 315 Deleting Storage System Collectors Delete Storage System Collectors only when you are certain that you no longer want to collect data from the corresponding Device Manager, Agent for RAID Extension, Tiered Storage Manager, or SMI-S Provider for third-party storage systems. If you only want to temporarily stop storage system data collection for a particular storage system, disable the appropriate Storage System Collector. For more information about disabling data collectors, see Enabling and disabling Storage System Collectors on page 328. Administering Hitachi Command Director 323

324 Procedure 1. Select the Administration tab. 2. Under Data Collection, click Storage System Collectors. 3. Select the check box next to the Storage System Collector you are deleting, and then click Delete. 4. In the Confirmation dialog box, verify that you are deleting the appropriate Storage System Collector, and then click Yes. Related tasks Viewing information about Storage System Collectors on page 315 Viewing storage system data collection history The history log lists attempts by each data collector to collect data and whether the attempt was successful. The log lists manual and scheduled data collections. Note that only the Storage System Collector information is logged; storage system information is not logged. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Storage System Collectors. 324 Administering Hitachi Command Director

325 3. Select the History tab. Figure 12-5 Storage system data collection history The History window displays the following information: Name: The name associated with the Storage System Collector. Type: Whether the Storage System Collector belongs to Hitachi Device Manager (HDvM), Agent for RAID Extension, Tiered Storage Manager (HTSM), or SMI-S Provider. IP Address: The IP address of the host using the Storage System Collector. Operation: Whether the data was scanned or gathered. A Scan operation scans each data collector for registered storage arrays (in the case of HDvM, Agent for RAID Extension, SMI-S Provider) and storage domains managed by HTSM. A Refresh operation collects detailed information about each of the registered storage systems and storage domains. Hitachi Command Director collects data from both the Device Manager and HTSM in one sequence. Start: The date and time when the data from Device Manager, Tiered Storage Manager, Agent for RAID Extension, or SMI-S Provider began to be discovered or gathered. Message: The status. For example, whether the last attempt to retrieve data was successful, or why it failed. 4. View details about the storage system data collection and refresh activity for a specific Storage System Collector. Select the Storage System Collectors whose information you want to view details on. Related tasks Manually refreshing data on page 327 Enabling and disabling Storage System Collectors on page 328 Viewing details about a specific Storage System Collector on page 326 Administering Hitachi Command Director 325

326 Viewing details about a specific Storage System Collector Procedure 1. Select the Administration tab. 2. Under Data Collection, click Storage System Collectors. 3. Select the History tab. 4. Select the Storage System Collector whose details you want to view. Result The information is displayed directly below the main history information that is described above. The detailed information for the selected Storage System Collector is organized as follows: Storage System: Name of the storage system configured by Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). For thirdparty storage system registered using the SMI-S Provider, it is the storage system model and serial number. Model: The storage system model type. Capacity: The storage capacity of the storage system. # Volumes: The number of storage disks assigned to the storage system. Start: The date and time when the selected storage system was scanned or gathered. Status: Whether the last attempt to scan or gather data from the selected storage system was successful. Related tasks Viewing storage system data collection history on page 324 Modifying how often data is refreshed You can specify how often Hitachi Command Director refreshes data collector information for reports. You can only modify the configuration data refresh frequency. The default configuration data refresh frequency is 4 hours. The performance data refresh frequency is always set at 5 minutes. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Storage System Collectors. 326 Administering Hitachi Command Director

327 3. Select the Settings tab. The Storage System Data Collection Settings dialog box is displayed. This dialog box shows you the current Storage System Collector data refresh frequency setting and the date and time of the next data refresh. Figure 12-6 Storage system data collection refresh settings 4. From the Configuration Data Refresh Frequency drop-down list, select how often you want to refresh the configuration data. You have the following refresh frequency options: 1 hour 2 hours 3 hours 4 hours 6 hours 12 hours 24 hours 5. When you have finished, click Save. The Storage System Collectors are temporarily disabled to allow your changes to take effect, and then enabled again. Related tasks Manually refreshing data on page 327 Enabling and disabling Storage System Collectors on page 328 Manually refreshing data You can manually refresh the Storage System Collectors data before the next scheduled collection and update reports with the latest information, or verify whether the Storage System Collectors are configured properly. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Storage System Collectors. 3. Select the Storage System Collectors tab, Storage Systems tab, or Storage Domains tab. 4. Click Refresh. Administering Hitachi Command Director 327

328 Related tasks Modifying how often data is refreshed on page 326 Enabling and disabling Storage System Collectors on page 328 Enabling and disabling Storage System Collectors You can disable (deactivate) Storage System Collectors when you want to stop collecting performance or configuration data from the storage systems managed by the Hitachi Device Manager instance, Agent for RAID Extension instance, and SMI-S Provider. After Storage System Collectors are disabled, you can enable them again and resume collecting data using the steps that follow. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Storage System Collectors. The configured Storage System Collectors are displayed. All Storage System Collectors are enabled by default. 3. Click OFF to disable the Storage System Collector. 4. Click ON to enable a Storage System Collector again. Result After enabling data collection, click Refresh to start collecting data immediately, or wait until the next scheduled collection to update reports with the latest information. Related tasks Viewing information about Storage System Collectors on page 315 Deleting Storage System Collectors on page 323 Enabling and disabling storage systems on page 328 Enabling and disabling storage systems You can stop collecting configuration and performance data from any storage system managed by the Hitachi Device Manager instance, Agent for RAID Extension instance, or SMI-S Provider by disabling it. By disabling a storage system, you choose not to monitor or report on it. You can re-enable disabled storage systems to resume collecting data. Users with the View role can view storage system information on the Storage Systems tab but cannot enable or disable storage systems. Enabling or disabling data collection can impact the information displayed in various reports on storage system capacity and performance. At a given time, the reports may contain data retrieved from both enabled and disabled storage systems up to the time a storage system was disabled. The reports 328 Administering Hitachi Command Director

329 will be populated with new data after the storage systems are enabled again and refreshed either manually or at the scheduled refresh interval. For the period a storage system remains disabled and before it is enabled again, there will be a gap in the information displayed. For example, when a storage system is re-enabled, the reports (such as the ones on the SLO Investigation Unit) that report on storage system performance will not display any data for a few data points after you resume data collection. Various trend charts will show disruption in the data displayed and reports on the storage systems view displaying SLO conformance status will indicate a data hole. For more information about SLO IU reports and storage system reports, see About SLO Investigation Unit on page 103 and Storage system reports on page 217. You cannot enable or disable a Hitachi storage system in the following scenarios if the Action field is grayed out: When either the HDvM data collector or Agent for RAID Extension, or both are not configured and enabled for data collection. When performance or configuration data collection is disabled on any of the storage system collectors. However, the Action field remains active for supported third party storage systems even if Agent for RAID Extension is not configured or disabled to collect performance data. The Action field is grayed out only when the HDvM data collector is not configured or disabled to collect configuration data. Procedure Figure 12-7 Enabling or disabling storage systems 1. Select the Administration tab. 2. Under Data Collection, click Storage Systems. The configured storage systems are displayed. By default, all storage systems are enabled to collect both configuration and performance data Administering Hitachi Command Director 329

330 for Hitachi storage systems and only configuration data for SMI-S Provider. 3. Click OFF to disable data collection or ON to enable data collection for each storage system. Result After enabling data collection, click Refresh to start collecting data immediately, or wait until the next scheduled collection to update reports with the latest information. Related concepts About SLO Investigation Unit on page 103 Storage system reports on page 217 Related tasks Enabling and disabling Storage System Collectors on page 328 Viewing information about Storage System Collectors on page 315 Modifying how often data is refreshed on page 326 Configuring Host Collectors This module describes the use of the HCmD Host Collector feature to agentlessly discover hosts on your network and gather their file system and storage utilization information. Host discovery and agentless data gathering mechanism You can use the HCmD Host Collector to agentlessly discover hosts on your network and gather their file system and storage utilization information. This allows Hitachi Command Director to provide end-to-end mapping of the path from the host to the storage system volumes. For example, let us say that a particular host has two host bus adapters with two ports each. From the point of view of the storage system, the four ports appear as four different WWNs. But when Hitachi Command Director collects the host data, you can see that the volumes provisioned to the four WWNs are actually used by the same host or application. Thus, Hitachi Command Director allows you to see the big picture of how your storage is used. Hitachi Command Director host discovery executes scripts remotely. When absolutely needed, binaries and libraries are copied to target servers, executed, and then cleaned up (including all the files generated during execution). For the details of the Host Collector data gathering mechanism and what privileges are used to perform what functions, as well as the Host Collector s 330 Administering Hitachi Command Director

331 impact on the target environment, see Host Collector in a secure environment on page 374. Hitachi Command Director Host Discovery can discover hosts on the following platforms: Windows Hyper-V ESX hosts using VMware vcenter Server Linux Solaris HP-UX AIX HNAS For information about the hosts and their versions supported by Hitachi Command Director, see Appendix B, Host Collector Support Information, in the Hitachi Command Director Installation and Configuration Guide. Benefits of agentless data gathering mechanism The benefits of the agentless data gathering mechanism used by the Host Collector are: Removes the need for manual installation and upgrades of agents on the target servers. These executables are no different in functionality than executables run by a deployed agent. All data gathering operations are done within the allowed security framework. There is no hacking, no malware, and no Rootkits deployed. The agentless data gathering mechanism uses only open-standard protocols (such as Telnet, SSH, Win Service, WMI). No proprietary protocols are used. Related concepts Host Collector in a secure environment on page 374 Related tasks Viewing Host Collector information on page 332 Enabling host discovery and data collection on page 334 Configuring a new Host Collector on page 335 Deleting Host Collectors on page 342 Refreshing Host Collector data on page 342 Modifying Host Collector on page 341 Launching Host Collector to discover hosts on page 338 Host access requirements The host access requirements for the Host Collector: Administering Hitachi Command Director 331

332 For the host data collection mechanism to work, an Admin-type user is required. To obtain end-to-end device mapping through SCSI enquiry, Root access is required. Only direct Root access is supported. For host data collection on the vcenter Server, an account with read permission is required. Related concepts Host discovery and agentless data gathering mechanism on page 330 Related tasks Viewing Host Collector information on page 332 Enabling host discovery and data collection on page 334 Viewing Host Collector information You can view information about Host Collectors currently configured for your network. Procedure 1. Select the Administration tab. 332 Administering Hitachi Command Director

333 2. Under Data Collection, click Host Collectors. The Host Collectors window is displayed. Figure 12-8 Host Collectors The initial screen presented is the Host Collectors window, which displays the following information: IP Address: The IP address of the server where the Host Collector server software is installed. Name: The name associated with the Host Collector. Version: The software version number of the Host Collector. Port: The port number on the Host Collector Server that communicates with the HCmD server. Last Operation: The most recent operation executed by the Host Collector. Cfg. Data Time: The local date and time when the most recent configuration was completed on the HCmD Server. Message: Status message from the Host Collector. Action: This column displays the following icons: Enabled: The ON status indicates that the Host Collector is enabled. Disabled: The OFF status indicates that the Host Collector is disabled. Edit icon: When you click this icon, you can modify the name and the port number of the Host Collector. Launch icon: When you click this icon, you can launch the selected Host Collector and gather host information. This icon is not displayed for the vcenter Collector as this functionality is not applicable for vcenter. Related tasks Enabling host discovery and data collection on page 334 Configuring a new Host Collector on page 335 Launching Host Collector to discover hosts on page 338 Modifying Host Collector on page 341 Refreshing Host Collector data on page 342 Deleting Host Collectors on page 342 Administering Hitachi Command Director 333

334 Enabling host discovery and data collection You can enable and configure host discovery and data collection for hosts on the local subnet. Hitachi Command Director also supports host discovery on other subnets. You can disable (deactivate) Host Collectors when you want to temporarily stop collecting data from the discovered hosts in your network. When you first open the Host Collector window, a default Host Collector is preconfigured and available for the current subnet. It is disabled by default. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. The Host Collectors tab is displayed. The Action column displays two statuses, one of which is OFF, which indicates that the preconfigured Host Collector is currently disabled. 3. To enable the preconfigured Host Collector, click OFF. Result The status changes to ON, which indicates that the Host Collector is now enabled. To disable a Host Collector, select the Host Collector and click ON. The Host Collector is disabled temporarily and displays the OFF status. Related tasks Viewing Host Collector information on page 332 Refreshing Host Collector data on page 342 Prerequisites for host discovery on other subnets Hitachi Command Director (HCmD) also supports host discovery on other subnets. To discover hosts on a different subnet from the HCmD Server s subnet, do these: Install and start a Host Collector on a host from that subnet, which is also visible to HCmD Server s subnet. See the Installing the Host Collector section in Chapter 2 of the Hitachi Command Director Installation and Configuration Guide. Configure the HCmD Server to connect to this Host Collector. Make sure that your firewall settings allow communication between the Host Collector and HCmD Server. Related concepts Host discovery and agentless data gathering mechanism on page Administering Hitachi Command Director

335 Related tasks Enabling host discovery and data collection on page 334 Configuring a new Host Collector A default Host Collector is preconfigured and available to discover hosts on the HCmD Server s subnet. To access remote hosts on a different subnet and behind a firewall, install Host Collector on a server in each subnet, and make sure that your firewall settings allow communication between the Command Director server and this component. To configure a new VMware vcenter Collector, see Configuring a new vcenter Collector on page 336. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. The Host Collectors window is displayed. 3. From the Host Collectors window, click New. The New Host Collector window appears. Figure 12-9 New Host Collector 4. Enter the information required for the new Host Collector: Name: Enter a unique name for this Host Collector. This name is different than the Host Collector server name. The Host Collector name can be up to 32 characters. Type: Select Host Collector. IP Address: Enter the IP address of the server where the Host Collector Server is installed. Port: The port number specified here is the number of the port on the Host Collector server that communicates with the HCmD Server. Accept the default port number (25046) or enter a new port number. Administering Hitachi Command Director 335

336 HCmD Server IP Address: Enter the IP address of the HCmD Server. The default IP address of the HCmD Server is displayed here. If this server has multiple IP addresses, you can specify a different IP address here. 5. To save the Host Collector information you entered here, click OK. You return to the Host Collector window where the new Host Collector is listed. Related tasks Viewing Host Collector information on page 332 Enabling host discovery and data collection on page 334 Launching Host Collector to discover hosts on page 338 Configuring a new vcenter Collector on page 336 Configuring a new vcenter Collector Configure a new vcenter Collector to utilize vcenters available in your network and to gather information about the ESX servers associated with the vcenter. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. The Host Collectors window is displayed. 3. From the Host Collectors window, click New. The New Host Collector dialog box appears. 4. In the Name field, enter a new name for this Host Collector. 336 Administering Hitachi Command Director

337 5. From the Type drop-down list, select vcenter. The New Host Collector window displays information required for vcenter. Figure New Host Collector for vcenter Server 6. Enter the information required for the new Host Collector: IP Address: Enter the IP address of the vcenter Server. Port: The port (https) on which vcenter is running in your network. If vcenter is not running on the default port number specified in the window, modify it. User ID: Enter the user ID of the vcenter Server. Password: Enter the password of the vcenter Server. Host Collector: Select the Host Collector you want to use to connect to the vcenter Server. The drop-down lists the available active Host Collectors in the system. If the vcenter Server is running on a different subnet, select the appropriate Host Collector that can access that subnet. If the list is empty, use the preconfigured Local Host Collector, which is available in the list only if it is enabled. To enable, see Enabling host discovery and data collection on page To save the Host Collector information you entered here, click OK. You return to the Host Collector window where the new vcenter Collector is listed. Related tasks Viewing Host Collector information on page 332 Enabling host discovery and data collection on page 334 Launching Host Collector to discover hosts on page 338 Viewing information about discovered hosts on page 343 Administering Hitachi Command Director 337

338 Launching Host Collector to discover hosts Launch a configured Host Collector to locate the hosts of interest. Launching helps to discover host information about other subnets and configure the Host Collectors installed on these subnets. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. 3. In the Host Collectors window, select the Host Collector you want to launch. 4. In the Action column, click the Launch icon ( ). The Discover Hosts dialog box appears. Figure Discover hosts 5. You must specify how you want the Host Collector to locate the hosts of interest. You have three options: Discover the hosts on the current subnet. For more information, see Discovering hosts on the current subnet on page 339. Specify a range of host IP addresses. For more information, see Discovering hosts by specifying a range of host IP addresses on page 339. Specify a list of host IP addresses. For more information, see Discovering hosts by specifying a list of host IP addresses on page Select any of the available options, and click Discover. Related tasks Discovering hosts on the current subnet on page 339 Discovering hosts by specifying a range of host IP addresses on page 339 Discovering hosts by specifying a list of host IP addresses on page 340 Viewing Host Collector information on page Administering Hitachi Command Director

339 Discovering hosts on the current subnet When you specify that you want the Host Collector to search the local subnet for hosts of interest, the Host Collector will search the entire IP address range of the current subnet. The IP address of the local subnet is displayed. For example, if the Host Collector IP address is , then the Host Collector will locate all the hosts from to Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. The Host Collectors window opens. 3. Select the Host Collector you want to launch. 4. In the Action column, click the Launch icon. The Discover Hosts window opens. 5. To discover the hosts on the current subnet, select the <IP_address>Subnet option. 6. Click Discover. Command Director proceeds to discover the hosts on the current subnet. Related tasks Launching Host Collector to discover hosts on page 338 Viewing Host Collector information on page 332 Discovering hosts by specifying a range of host IP addresses When you launch a Host Collector, you can specify a range of IP addresses to be searched to discover hosts. Hitachi Command Director validates the range of IP addresses that you enter. The following IP address range formats are supported: Specifying a limited range of addresses. For example: Starting address: Ending address: Employing a wild card IP address range search. For example: Starting address: Ending address: * This wildcard search would discover hosts from to Employing a wild card IP address subnet search. For example: Starting address: * This wild card search would discover hosts from to Administering Hitachi Command Director 339

340 Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. The Host Collectors window is displayed. 3. Select the Host Collector you want to launch. 4. In the Action column, click the Launch icon. The Discover Hosts window appears. 5. To specify a range of host IP addresses, select Host IP Address Range. The Discover Hosts dialog now displays fields for the starting IP address and the ending IP address. 6. In the Starting IP field, enter the IP address for the start of the range. 7. In the Ending IP field, enter the IP address for the end of the range of addresses. 8. When satisfied with your IP address range specification, click Discover. Related tasks Launching Host Collector to discover hosts on page 338 Viewing Host Collector information on page 332 Launching Host Collector to discover hosts on page 338 Viewing Host Collector information on page 332 Discovering hosts by specifying a list of host IP addresses When you launch a Host Collector, you can specify a list of IP addresses to be searched to discover hosts. Hitachi Command Director validates the IP addresses that you enter. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. The Host Collectors window is displayed. 3. Select the Host Collector you want to launch. 4. In the Action column, click the Launch icon. The Discover Hosts dialog box appears. 5. To specify a list of host IP addresses, select List of Host IP Addresses. The Discover Hosts dialog displays a field to enter the desired list of IP address. 6. Enter the list of IP addresses, separated by commas. Tip: To discover HNAS nodes or HNAS clusters, you must specify the IP addresses of the corresponding SMUs. 7. When you satisfied with the list of IP addresses, click Discover. 340 Administering Hitachi Command Director

341 Result If there is no validation error, the newly added Host Collector starts discovering the host information for the specified IP address range or list of IP addresses. All the discovered hosts are listed in the Hosts screen. If the discovery process is successful, the Hosts window displaying the discovered hosts will be presented automatically. All the discovered HNAS nodes and HNAS clusters are displayed in the HNAS window. Modifying Host Collector You can change the name, port number, and HCmD Server IP address of a selected Host Collector. Note that you cannot edit the default Host Collector. For vcenter Collector, you can modify any of its parameters. You cannot change the type of the Host Collector after you have initially set it to either Host Collector or vcenter. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. The Host Collectors window is displayed. 3. Select the Host Collector you want to modify. 4. In the Action column, click the Edit icon. The Edit Host Collector window appears. 5. Change the following information as needed: For Host Collector: Name: Enter a unique name for this Host Collector. This name must be different than the Host Collector server name. The Host Collector name can be up to 32 characters. Port: The port number specified here is the number of the port on the Host Collector Server that communicates with the HCmD Server. HCmD Server IP Address: Enter the IP address of the new HCmD Server if you have changed the HCmD Server after initial installation. For vcenter Collector: Name: Enter a unique name for this Host Collector that does not exceed 32 characters. IP Address: Enter the IP address of the vcenter Server. Port: The port (https) on which the vcenter is running in your network. If the vcenter is not running on the default port number specified in the window, modify it. User ID: Enter the user ID of the vcenter Server. Password: Enter the password of the vcenter Server. Administering Hitachi Command Director 341

342 Host Collector: Select the Host Collector you want to use to connect to the vcenter Server. The drop-down lists the available active Host Collectors in the system. If the list is empty, use the preconfigured Local Host Collector. 6. To save the Host Collector information you entered here, click OK. Related concepts Host discovery and agentless data gathering mechanism on page 330 Related tasks Viewing Host Collector information on page 332 Refreshing Host Collector data You can refresh the Host Collector data on all or selected Host Collectors. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. The Host Collectors window is displayed. 3. Select the Host Collectors you want to refresh. 4. Click Refresh. Result Hitachi Command Director initiates data collection for the selected registered data collectors, including the Host Collector. Related concepts Host discovery and agentless data gathering mechanism on page 330 Related tasks Viewing Host Collector information on page 332 Deleting Host Collectors Delete Host Collectors only when you are certain that you no longer want to collect data from the configured Host Collectors. When you delete a host collector, the hosts discovered by the host collector are also deleted. If you only want to temporarily stop data collection, disable the appropriate Host Collector by clicking OFF in the Action column. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. 342 Administering Hitachi Command Director

343 3. In the Host Collectors window, select the check box next to the Host Collector you are deleting, and then click Delete. 4. In the Confirmation dialog box, verify that you are deleting the appropriate Host Collector, and then click Yes. Related tasks Deleting hosts on page 352 Viewing Host Collector information on page 332 Validating host connectivity on page 347 Modifying host login settings for specific hosts on page 349 Viewing information about discovered HNAS hosts on page 345 Viewing information about discovered ESX hosts on page 344 Viewing information about discovered hosts You can view basic information about each of the discovered hosts in the following tabs of the Host Collectors window: Hosts tab: Displays information about each of the discovered Windows, Solaris, HP-UX, AIX, or Linux hosts. HNAS tab: Displays information about each of the discovered HNAS hosts. ESX tab: Displays information about each of the ESX hosts discovered using vcenter Server. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. The Hosts tab displays by default for users with the View role. Administering Hitachi Command Director 343

344 3. In the Host Collectors window, select the Hosts tab. The Hosts window is displayed. Figure Hosts window This window provides host discovery information and functions: Name: The name of the discovered host. If the Host Collector is unable to detect the name of the host, the Name field displays either UNKNOWN or the IP address of the host. IP Address: The IP address of the discovered host. OS: The operating system of the host. Last Operation: Whether the most recent operation was Refresh, Discover, or Validation. Last Execution: The local date and time of when the most recent Host Collector operation was executed on the HCmD Server. Message: Indicates whether the host discovery operation was successful or it failed. When there is a failure, this field provides a brief description of the failure. Validation errors are also displayed in this field. Note that you can view the entire message by passing your cursor over the Message field to display the flyover Help. Host Collector: The name assigned to the Host Collector. Action: The Action column is available to users with the Admin role. Edit (pencil) icon : When a specific host s login information differs from the default login settings for the hosts, you can modify those settings for one or more specific hosts, thus ensuring proper communication between the Host Collector and the target host(s). Enabled (ON): When the status shows it is enabled, the host is included for data refresh. Disabled (OFF): When the status shows it is disabled, the host is not included for data refresh. Related tasks Viewing information about discovered ESX hosts on page 344 Viewing information about discovered HNAS hosts on page 345 Viewing information about discovered ESX hosts Hitachi Command Director discovers ESX hosts using the vcenter Collector. 344 Administering Hitachi Command Director

345 Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. 3. In the Host Collectors window, select the ESX tab. The ESX window is displayed. Figure ESX window This window provides the following information about ESX hosts: Item ESX Server Name IP Address OS Details vcenter Last Operation Last Execution Message Description The name of the ESX server. If the vcenter Server is unable to provide the name of the ESX server, this field displays UNKNOWN or the IP address of the ESX server. IP address of the ESX server. The operating system details. The name of the vcenter Collector. Whether the most recent operation was Refresh, Scan, or Validation. The local date and time when the most recent operation was executed on the HCmD Server. Indicates whether the host discovery operation was successful or it failed. When there is a failure, this field provides a brief description of the failure. Validation errors are also displayed in this field. Note that you can view the entire message by passing your cursor over the Message field to display the flyover Help. Related concepts Host discovery and agentless data gathering mechanism on page 330 Related tasks Viewing information about discovered HNAS hosts on page 345 Viewing information about discovered hosts on page 343 Specifying data collection refresh frequency on page 351 Viewing information about discovered HNAS hosts You can view basic information about each of the discovered Hitachi NAS Platform (HNAS) hosts. Administering Hitachi Command Director 345

346 Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. 3. In the Host Collectors window, select the HNAS tab. The HNAS window is displayed. Figure HNAS window This window provides host discovery information and functions as described in the following table: Item Description SMU Cluster The name of the SMU (the HNAS management server). If the HNAS Data Collector is unable to detect the name of the SMU, the SMU Name field displays either UNKNOWN or the IP address of the SMU. The name of the HNAS cluster. An HNAS cluster is comprised of two to eight nodes. The nodes share the same storage devices; the network requests can be distributed across cluster nodes. If the HNAS node is not part of any cluster, this field will display a hyphen. Node(s) Collect Performance Data Status The name of the HNAS node. Each HNAS node contains volumes mapped to System Drives regardless of whether those volumes are put in Storage Pools on the HNAS node.if a cluster node fails, its file services and administration functions are transferred to other nodes in the cluster. To enable performance data collection on the selected cluster or standalone node, this check box must be checked (the Collect Performance check box is enabled by default). If you want to disable the collection of performance data, clear the check box. The Status icons indicate whether the HNAS Data Collector is collecting HNAS node performance data. A check Mark: Indicates that the HNAS Data Collector is collecting performance data. A red X: Indicates that the HNAS Data Collector is not collecting performance data. Related concepts Host discovery and agentless data gathering mechanism on page Administering Hitachi Command Director

347 Related tasks Viewing information about discovered ESX hosts on page 344 Viewing information about discovered hosts on page 343 Specifying data collection refresh frequency on page 351 Validating host connectivity You can validate the connectivity between the Host Collector and the target hosts. The system can validate the host connectivity information for all the selected hosts simultaneously. Validation error information is displayed in the Message column for the relevant hosts. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. 3. In the Host Collectors window, select the Hosts tab. 4. In the Discovered Hosts window, select the host you want to validate its connection. 5. Click Validate. Related tasks Modifying host login settings for specific hosts on page 349 Viewing information about discovered hosts on page 343 Specifying host login settings To ensure proper communication between the Host Collector and the remote hosts, you must specify the host login settings, which include the user name and password for the target hosts, as well as the protocol settings for access to the host to allow for the device-file-to-storage mapping discovery process. The host login settings (also called Global OS Settings) are applied by default to each host of a specific OS type that is added to the system. The host login settings set for Windows systems are the same as those for Hyper-V hosts. Note: You do not need to specify host login settings for ESX hosts as this information is obtained from the vcenter Server. The vcenter credentials you provide when you add a vcenter Collector are used to connect to the ESX hosts. For more information, see Configuring a new vcenter Collector on page 336. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. Administering Hitachi Command Director 347

348 3. In the Host Collectors window, select the Host Login Settings tab. The Host Login Settings dialog box is displayed. Figure Host login settings 4. Use the information in the following table to navigate through the various tabs for each discovered host type in this dialog box and specify login settings for these discovered hosts: Tab Setting Description Linux, Solaris, HP- UX, AIX User ID Password Sudo SSH Port Enter the user name that will be used to log in to the hosts. Enter the password used to log in to the hosts. When the Sudo option is enabled, Sudo ( superuser do ), HCmD does not require the user ID to be root to collect data from Linux or UNIX-based servers. Sudo allows a system administrator to work using his own account and switch to root or another user identity available on the system for commands that need it. Any operation performed under Sudo is logged. Specify the port number, if different from the default, for the secure shell protocol used to communicate to the hosts. The default port number of 22 is populated. Windows User ID Enter the user name that will be used to log in to the Windows or Hyper-V hosts. If you have a domain user account, enter the user name in this format: 348 Administering Hitachi Command Director

349 Tab Setting Description <domain>\<user name> Password Windows Service Enter the password used to log in to the Windows or Hyper-V hosts. Specify the appropriate Windows service: Windows Service Management: Uses the Windows Service Manager (also known as Service Control Manager), which is responsible for creating, deleting, and running the service. Windows Management Instrumentation: A Windows service running on the remote server that also allows HCmD to create a task and run an application remotely on that system. When you select one of these Windows Services, HCmD creates the service and runs the required task on the remote server using the specified Windows facility. HNAS SMU SSH User ID Enter the user name to log in to the HNAS SMU using SSH. Note: Do not use the HNAS GUI login credentials to log in to the SMU. Password SSH Port Enter the SSH password used to log in to the HNAS SMU. Specify the port number, if different from the default, for the secure shell protocol used to communicate to the hosts. The default port number of 22 is populated. 5. When finished specifying the host login parameters, click Save. An information window appears confirming successful update of the Global OS Settings for the selected host. Click OK. Related concepts Host discovery and agentless data gathering mechanism on page 330 Related tasks Modifying host login settings for specific hosts on page 349 Modifying host login settings for specific hosts Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. The Host Collector window is displayed. 3. Select the Hosts tab. Administering Hitachi Command Director 349

350 4. Click the Edit icon in the Action column of the host you want to modify. The Edit Host Login Settings dialog box is displayed. Figure Modify host login settings Notice that the login parameters for the selected host are grayed out. This is because the Use Global OS Setting option is selected by default, which indicates that the login information you specified in the Host Login Settings tab is applied globally to this host and all other hosts of the same OS type. 5. To override the global OS settings and specify new login parameters for the selected host, clear the check box for the Use Global OS Setting option. The login parameters are now available for editing. 6. Modify the appropriate login settings for the selected host. 7. When finished modifying the host s login parameters, click OK. Result The modified host login parameters override the Global OS Setting for this host. Related concepts Host discovery and agentless data gathering mechanism on page 330 Related tasks Specifying host login settings on page Administering Hitachi Command Director

351 Specifying data collection refresh frequency You can specify how often Hitachi Command Director refreshes Host Collector and HNAS performance data collection information. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Host Collectors. 3. In the Host Collectors window, select the Settings tab. The Host Data Collection Settings dialog box appears. Figure Data collection refresh frequency This window shows you the current data collection refresh frequency setting and the date and time of the next data refresh. The default scheduled refresh interval is six hours. 4. Set the host data collection frequency from the Data Refresh Frequency list. You can select how often you want to refresh the Host Collector data from the following refresh frequency options: 1 hour 2 hours 3 hours 4 hours 6 hours 12 hours 24 hours 5. When you have finished, click Save. Result The Host, HNAS, and vcenter collectors are temporarily disabled to allow your changes to take effect, and then enabled again. Related concepts Host discovery and agentless data gathering mechanism on page 330 Administering Hitachi Command Director 351

352 Deleting hosts Related tasks Viewing Host Collector information on page 332 Delete hosts only when you want to stop collecting data from this discovered host. If you only want to temporarily stop data collection, disable the appropriate host by clicking OFF in the Action column. Procedure 1. Select the Administration tab. 2. Under Data Collection, click Hosts. 3. Select the check box next to the host you are deleting, and then click Delete. 4. In the Confirmation dialog box, verify that you are deleting the appropriate host, and then click Yes. Related tasks Enabling host discovery and data collection on page 334 Viewing Host Collector information on page 332 Organizing resources by tagging This module describes how to use tags to organize resources. Managing custom tags and tag categories Command Director comes with predefined set of tags and tag categories you can use to create a custom business view that matches your organization structure. If these predefined tag categories do not apply to your business structure, you can modify them or create new to organize your resources according to your business structure. After you create custom tag categories, you can modify them to adapt to changes in your organization resulting from any organization restructuring. Each tag category name must be unique among tag categories, but a tag category name can be used as tag name. Similarly, each tag name must be unique among tags, but a tag name can be used as tag category name. Procedure 1. Select the Administration tab. 352 Administering Hitachi Command Director

353 2. Under Resource Organization, click Tag Management. The Tag Management window appears, displaying the predefined tag categories; Geography and Function. Figure Figure 3-9 Tag Management 3. To view tags under a predefined tag category, click the expand icon. 4. To add a new category, click New Category. 5. Enter the name of the new tag category. The name must not exceed 64 characters and must be unique among tag categories. It can include the characters _ (underscore),. (at symbol) and - (dash). 6. To add a tag to this tag category, click the Create New Tag (+) icon next to the tag category name. 7. Enter the name of the tag. The name must not exceed 64 characters and must be unique among tag names. It can include the characters _ (underscore),. (at symbol) and - (dash). 8. To delete a tag category or tag, click the Delete Tag Category icon. 9. If you delete a tag category, a Confirmation dialog box appears prompting you to confirm your action. Verify that you want to delete the selected category, and click Yes. Note: Deleting a tag category deletes tags associated with this tag category. It also deletes any associations between applications and the deleted tags. 10. In the Resources tab, click New Business View to open the New Business View dialog and create a business view using your new category. For more information, see Creating a new business view on page 77. Related concepts Custom business view on page 65 Related tasks Creating a new business view on page 77 Managing business views on page 79 Administering Hitachi Command Director 353

354 Managing scheduled reports Command Director maintains a scheduled reports list that includes information about every report that is scheduled for generation and delivery. This list allows you to view who scheduled the report, its context (folder, host, or application), and the last report that was generated. Note that if you are the administrator you can delete the report schedules and stop the report from being generated and ed. Procedure 1. Select the Administration tab. 2. Under System Settings & Operations, click Scheduled Reports. The Scheduled Reports window appears. Figure Scheduled reports Users with the View role are able to view only their own scheduled reports. This window displays the following information: Name: The name of the scheduled report. Click the report name link to view it in the format (Excel or XML) you selected in the report viewer. When you click on a report link before the set scheduled time for generation, an error stating that the report is not yet created for generation appears. Type: The type of report. Resource: Whether the report is for an application, host, or folder. Resource Name: The name of the application, host, or folder associated with the report. 354 Administering Hitachi Command Director

355 Note: After upgrading to v7.4.1 and beyond, the Resource Name for reports previously scheduled for the All Storage System node are replaced with Hitachi or the name of some other storage system type if applicable. Schedule: When the report is generated and ed. Recipient(s): The user IDs and the addresses of the persons that receive the report. Last Executed: When the report was last generated and sent. Related tasks Scheduling a report on page 251 Stopping scheduled reports Procedure 1. In the Scheduled Reports window, select the check box next to the report you are deleting and click Remove Schedule. 2. In the Confirmation dialog box, verify that you are deleting the appropriate scheduled report, and then click Yes. Configuring servers Configure the Simple Mail Transfer Protocol (SMTP) server and enable Hitachi Command Director to alerts and reports. If your SMTP server changes, you must update it so that the feature can function. Note: If you are unable to receive alerts or reports via , check your virus scanner software. It may include settings that prevent mailings. If this is the case, you need to reconfigure your virus software to allow the local server to send s. Procedure 1. Select the Administration tab. Administering Hitachi Command Director 355

356 2. Under System Settings & Operations, click Server. The Server dialog box is displayed. Figure Server 3. Modify the appropriate information: IP Address: Enter the IP address of the host using the server. Port: Enter the server port number. The default is To authenticate users and encrypt s sent from the Hitachi Command Director, select Log in as and specify the associated information: User ID: Enter the user ID associated with the SMTP server. Password: Enter the password associated with the SMTP server. Confirm Password: Re-enter the password. 5. When you have finished, click Save. Related tasks Viewing user information on page 370 Configuring LUN Owner settings This module describes the LUN Owner configuration and settings and how to exclude volumes from or include them in LUN Owner creation. About LUN Owner configuration A LUN Owner configuration represents a collection of volumes used by a common set of hosts, clusters, or applications. Command Director derives the mapping from the storage back to a host side entity such as a host, cluster, or an application without an agent that may require host security credentials. During creation of LUN owner configurations in your environment, all volumes, irrespective of whether they are shared or from a common device, are included by default. For example, in some SAN environments, a group of 356 Administering Hitachi Command Director

357 hosts may boot from the same SAN device. In this environment, all Windows hosts may use sanboot from a common volume. You may not want to monitor such volumes or report on them. Command Director enables you to exclude such volumes from LUN Owner creation in your environment. They are not monitored and are excluded from all reports that display storage system capacity information. However, at any point in time, if the shared device is no longer shared and its volumes are available for use, you can include the excluded volumes back in LUN Owner. These volumes are then available for assigning to applications, and also monitored and included in capacity reporting. LUN Owner creation scenarios Storage is used by hosts that may act as a single host or as a node of a cluster of hosts. Command Director treats these hosts as the owners of storage, and represents them as LUN Owner. LUN Owners are derived by analyzing the storage configuration on storage systems, and establishing ownership of volumes based on the configuration data obtained from Device Manager. When the storage system configuration data is refreshed, either manually or at scheduled interval, LUN Owners are created based on the volume allocation information in your storage system configuration. Volumes allocated via host groups to one or more WWNs belong to the same LUN Owner. LUN Owners are created differently in the following scenarios when allocation of a volume to WWNs changes: A volume that is unallocated from one WWN or excluded from LUN Owner creation A volume that is unallocated from multiple WWNs or excluded from LUN Owner creation LUN Owner configuration for volumes mapped to one WWN (basic configuration) The following figure shows a basic LUN Owner configuration of volumes allocated to one WWN. Administering Hitachi Command Director 357

358 Figure Basic LUN Owner configuration In this scenario, after data is refreshed, LUN Owner is created based on the volume allocation information derived from your storage system configuration data. It represents three volumes allocated to WWN1 via the host group HSD1. This is the initial LUN Owner configuration. When you unallocate volume Vol2 from WWN1, this volume is removed from LUN Owner. When you allocate Vol2 back to WWN1, this volume is added again to LUN Owner. LUN Owner configuration for volume mapped to multiple WWNs The following figure shows a LUN Owner configuration with one volume mapped to two different WWNs. 358 Administering Hitachi Command Director

359 Figure Split LUN Owner configuration In this scenario, after data is refreshed, LUN Owner is created based on the volume allocation information derived from your storage system configuration data. It represents three volumes, two of which are allocated to only one WWN and one volume that is allocated to both WWNs. This is the initial LUN Owner configuration. When you unallocate volume Vol2 from WWN1, the initial LUN Owner configuration is split into two different LUN Owner configurations with mappings set from a specific volume to its WWN. When volume is reallocated to WWN1, two distinct LUN Owners are merged into one LUN Owner to represent the initial configuration. Related tasks Excluding volumes from LUN Owner on page 362 Including volumes in LUN Owner on page 364 Related references Impact of LUN Owner configuration changes on applications on page 359 Impact of LUN Owner configuration changes on applications You can create applications automatically from LUN Owners by using the Applications Settings window from the Administration tab. Administering Hitachi Command Director 359

360 When the LUN Owner information changes as a result of allocation or deallocation of volumes to WWN, it affects automatic creation of applications and also the LUN Owner volume assignments in existing applications. All application-related reports in the Resource tab and the Reports gallery are updated to reflect any modifications to applications when volumes are excluded or included. Application impact by changes to basic LUN Owner configuration The following figure shows a basic LUN Owner configuration that includes allocation of volumes to the same WWN, and an application that is assigned volumes from this LUN Owner. Figure Application impact by basic LUN Owner configuration changes When storage system configuration data is refreshed, application App1 is created automatically with LUN Owner information and volumes assigned to it. When the initial LUN Owner configuration changes because the volume Vol2 is unallocated or excluded from LUN owner configuration, this volume is unassigned from App1 after data refresh. When the volume is reallocated to WWN1, Vol2 is reassigned to App1 after data refresh. 360 Administering Hitachi Command Director

361 Application impact by splitting LUN Owner configurations The following figure shows LUN Owner configurations that include allocation of volumes to different WWNs, and an application that is assigned volumes from this LUN Owner. Figure Application impact by splitting LUN Owner configurations When storage system configuration data is refreshed, application App1 is created automatically with LUN Owner information and volumes assigned to it. When the initial LUN Owner configuration changes because the volume Vol2 is unallocated or excluded from LUN Owner configuration, two LUN Owner configurations are created, and a new application (App2) is automatically created. The two remaining volumes are also assigned based on their capacity to applications App1 and App2. The volume with higher capacity remains with App1 while volume with lower capacity is assigned to the new application, App2. When Vol2 is reallocated to WWN1 and WWN2 and the two LUN Owners are merged into one, Vol2 and Vol3 are reassigned to App1. App2 is unassigned, and you can safely delete this application. Related concepts Specifying how applications are automatically created on page 366 Administering Hitachi Command Director 361

362 Related tasks Excluding volumes from LUN Owner on page 362 Including volumes in LUN Owner on page 364 Creating applications automatically on page 367 Deleting applications on page 152 Related references LUN Owner creation scenarios on page 357 Excluding volumes from LUN Owner Command Director allows you to exclude volumes that you do not intend to monitor or report on, from LUN Owner creation. Prerequisites for excluding volumes include: Storage systems are configured. You must have at least one Device Manager and corresponding Agent for RAID Extension collectors configured in Hitachi Command Director. For more information about how to configure storage system collectors, see Configuring Storage System Collectors on page 319. Refresh the configured storage system collectors. You can refresh these collectors manually or at a scheduled interval. For more information about how to refresh storage system collectors, see Manually refreshing data on page 327 and Modifying how often data is refreshed on page 326. Identify the volumes to exclude from LUN Owner and make note of the volume details such as volume ID and the associated storage system. Review Impact of LUN Owner configuration changes on applications on page 359. Procedure 1. Select the Administration tab. 2. Under System Settings and Operations, click LUN Owner Settings. 362 Administering Hitachi Command Director

363 3. In the Search Volume field, enter the volume label or volume ID. You can enter the complete volume name or part of it to display volumes that match the search criteria. Then, click the Search icon. The search results are displayed. If the intended results are not displayed, click Clear to clear the display results and to enter new criteria. The Volumes pane displays the following information: Volume: The volume ID matching the search criteria or a part of it. Volume Label: The volume label as specified in Device Manager. If nothing is specified, this column displays a hyphen. Storage System: Name of the storage system configured in Device Manager. If this name is not specified in Device Manager, it is the storage system model and serial number (for example, VSP 25210). Status: The status of the volume. It can be any of these values: hyphen (-): Volume is not selected for exclusion. Excluded: Volume is excluded. To be Excluded: Volume is selected for exclusion. Remove From List: Volume is removed from the exclusion list and is ready to be included back in LUN Owner. 4. Select the volumes you want to exclude and click Exclude. The Confirmation for Excluding Volumes window displays the list of applications that are affected by the selected volumes. 5. Review the applications affected by the volumes you have selected to exclude. For more information about the affected applications, see List of applications affected by LUN Owner volumes on page Click Confirm to exclude volumes after reviewing details of the affected applications. If no applications are displayed, then the selected volumes are not assigned to any active applications, and you can safely confirm to exclude such volumes. Administering Hitachi Command Director 363

364 7. You are asked to confirm if you want to refresh the LUN Owner to reflect the excluded volumes. Click Yes to refresh the LUN Owner now. The list of excluded volumes appear in the Excluded Volumes pane. LUN Owner can also be refreshed in the following ways: Automatically upon scheduled storage system refresh Manual storage system refresh Using the Refresh LUN Owner button in the LUN Owner Settings window Related tasks Including volumes in LUN Owner on page 364 Related references LUN Owner creation scenarios on page 357 Including volumes in LUN Owner You can select volumes from the exclusion list to include them back in LUN Owner creation, and in turn, reassign them to applications for monitoring and capacity reporting. Procedure 1. From the Excluded Volumes pane, select the volumes you want to include. Then, click Include. Figure Excluded Volumes list The Confirmation For Deleting Excluded Volumes window displays the list of Applications affected by the selected volumes. 2. Review details of the affected applications, and then click Confirm to remove the selected volumes from the excluded list. If no applications are displayed, then the selected volumes are not assigned to any active applications and you can safely confirm to delete such volumes. 3. You are asked to confirm if you want to refresh the LUN Owner to reflect the changes you made to the volumes. Click Yes to refresh the LUN Owner now. The selected volumes are deleted from the list of excluded volumes, and they appear in the Volumes pane. If you click No, the status of the volume appears as Remove From list. The deleted volumes are included in the LUN Owner only after the next 364 Administering Hitachi Command Director

365 manual or scheduled storage system refresh, or after you click the Refresh LUN Owner button in the LUN Owner Settings window. Until the time the refresh is performed, the status of this volume is displayed as To be Excluded. After refresh, the status changes to Excluded. Related tasks Excluding volumes from LUN Owner on page 362 Related references List of applications affected by LUN Owner volumes on page 365 LUN Owner creation scenarios on page 357 List of applications affected by LUN Owner volumes When you select volumes to exclude from or include in LUN Owner creation, a report listing applications affected by the selected volumes are displayed. This report helps you review details of the affected applications before you confirm to exclude or include volumes. To review the affected applications offline, click the Download icon to export and download this report in either an Excel or XML format. You can view this report when you select one of the following in the LUN Owner Settings window: One or more volumes to exclude in the Volumes pane. One or more volumes to remove from the Excluded Volumes pane. This report displays the following information: Application Name: The application name. Days since created: The number of whole days since the application is created. Existing # Volumes: The number of volumes used by the application. To be Excluded/ Included Volumes: The list of volumes to be excluded from or included in LUN Owner. Confirm: To confirm that you want to exclude or remove selected volumes after reviewing details of impacted applications. Cancel: To cancel exclusion or removal of volumes from the exclusion list. Related tasks Excluding volumes from LUN Owner on page 362 Including volumes in LUN Owner on page 364 Related references Impact of LUN Owner configuration changes on applications on page 359 Administering Hitachi Command Director 365

366 Specifying how applications are automatically created After installation of Hitachi Command Director and initial configuration of the Storage System Collectors, Hitachi Command Director creates applications automatically based on the auto-create option set by default to Logical Group. In this option, Hitachi Command Director creates applications from the logical group information obtained from Hitachi Device Manager configured in your environment. You can change the default setting and choose a different auto-create option to create applications from the LUN Owner information or hosts discovered in your environment. You can also choose not to create applications automatically. The following table lists the various options you can choose to create applications in Hitachi Command Director: Option Description Recommendation Logical Group Host LUN Owner This is the default configuration set after fresh installation of the product. This option creates applications automatically for the discovered hosts with storage in your environment. Note: HCmD does not automatically create applications for the discovered HNAS and Hyper-V hosts. This option creates applications automatically based on the volume owner group information derived from your storage system configuration. For more information about LUN Owner configuration, see About LUN Owner configuration on page 356. If you have created logical groups in Hitachi Device Manager that map to your business organization, structure, and volumes on the storage system, Hitachi recommends that you choose this option to import these logical groups into HCmD. After import of logical group hierarchy from Device Manager, a distinct Logical Group business view is automatically created in HCmD. You can use this business view as an easy way to assign SLOs directly to the logical group applications and tag them to further manage them in custom business views. Choose this option if you have visibility to all the servers in your environment. After the hosts are discovered and after successful refresh, HCmD creates applications for the discovered hosts with storage. Choose this option if it is not possible or desirable to connect to hosts in your environment to gather their file system and storage utilization information. HCmD analyzes all storage systems in your environment, checks the hosts that are assigned to host groups, and derives the LUN Owner information to create applications automatically. The applications that are created automatically appear in the All Applications view and they can be tagged to appear in custom business views. 366 Administering Hitachi Command Director

367 Related concepts Impact of switching to a different auto-create option on page 368 Creating applications automatically Hitachi Command Director (HCmD) lets you create applications automatically from Device Manager Logical Groups (default), hosts, or LUN owners in your environment. Initially, no tag categories are assigned to the applications. You must modify these applications to assign relevant tag categories. Once tags are assigned, the applications appear in various business views based on the tag categories that are assigned to the application. For automatic creation of applications, the Host Collectors and Storage System Collectors must be configured in Hitachi Command Director. To configure the various data collectors, see these topics: Enabling host discovery and data collection on page 334 Configuring Storage System Collectors on page 319 Procedure 1. Click the Administration tab. 2. Under System Settings & Operations, click Application Settings. Figure Auto Create Application 3. In the Auto Create Application dialog box, select the appropriate option: Logical Group to create applications from the Device Manager Logical Groups. This is the default selection. Host to create applications from the discovered hosts in your domain. LUN Owner to create applications from the LUN Owner information. Note: If there are two or more LUN Owners sharing one or more volumes or one or more WWNs, the LUN Owner mechanism will merge Administering Hitachi Command Director 367

368 the distinct LUN Owners into one LUN Owner. This merge can affect chargeback to your storage consumers. None to disable automatic creation of applications. 4. Click Save. To understand the impact of switching auto-create options, see Impact of switching to a different auto-create option on page 368. Caution: When you select an option, you are cautioned about losing data regarding auto-created applications. Switching between auto-create options deletes the automatically created applications set for the current option. 5. Click Yes to confirm selection of the new option. 6. In the information dialog box, click OK. Result Applications that are created automatically appear in the All Applications business view; the logical group applications appear in the All Applications view and also in the Logical Group business view. Auto-created applications have the following naming convention: Applications that are created from the Device Manager logical group acquire the logical group names as set in the Device Manager. Applications that are created from a discovered host: hostname, where hostname is the name of the discovered host (server). Applications that are created from a LUN Owner include names of the host groups (or HSDs) that are part of a specific LUN Owner: <HSD1_HDS2...HSD_n> Related concepts Specifying how applications are automatically created on page 366 Impact of switching to a different auto-create option on page 368 Related tasks Creating applications manually on page 135 Displaying business views on page 64 Impact of switching to a different auto-create option By switching to a different auto-create option, the applications that were created automatically in the current option are deleted from Hitachi Command Director. Application configuration such as tag, storage, and SLO assignments are also deleted with the applications. It is therefore recommended to understand the impact clearly before you make the switch to a different auto-create option. 368 Administering Hitachi Command Director

369 The following table describes the impact when you switch to a different option: Switch to <autocreate option> Logical Group Host, LUN Owner, or None Impact All applications - manually (user created) or automatically created using any other option are deleted. Only the automatically created applications are deleted. Manually created applications are retained. Related concepts Application creation process flow on page 133 Related tasks Creating applications automatically on page 367 Creating applications manually on page 135 Managing Hitachi Command Director users This module provides information about Hitachi Command Director users and user management tasks. About user management To log on to Hitachi Command Director, you must first configure Hitachi Device Manager accounts. Hitachi Command Director uses these user accounts: Local, built-in accounts of the Device Manager server. Accounts in LDAP authentication servers managed as a Windows Active Directory (authorization) group in Device Manager. User accounts cannot be modified in Hitachi Command Director. To modify user accounts, log on to the Device Manager and make the appropriate changes. Hitachi Command Director does not use the address available in the user account information in Device Manager. Instead, during initial login, you are prompted to enter an address that is used by Hitachi Command Director to send Service Level Objective (SLO) alerts and scheduled reports. You can modify this address in Hitachi Command Director. When you log on, user name and password are verified against the user accounts in the Device Manager server, and changes are automatically applied in your session. Command Director has two user roles available: Admin and View. Users with the Admin role can perform all tasks and access all of Command Director. Administering Hitachi Command Director 369

370 Users with the View role can view and customize dashboards, view reports, and access business views. User roles are assigned in Device Manager. For more information, see "Setting up users and access control" in the Hitachi Command Suite User Guide. Refer to the following table for additional user role mapping between Command Suite and Command Director. Command Suite role Maps to Commander Director role Command Director actions permitted Admin Admin All access. Modify Admin All access. View View Cannot perform most administrative tasks. Peer Peer Cannot log in. Custom Admin or View Can only log in as Admin if "All Resources" are assigned to the user group in Device Manager and the role assigned is Admin or Modify. For more information, see "Setting up users and access control" in the Hitachi Command Suite User Guide. Related tasks Viewing user information on page 370 Deleting users on page 371 Viewing user information User with the Admin role can view every user account registered to use Hitachi Command Director. User account information is retrieved from the Device Manager. Procedure 1. Select the Administration tab. 370 Administering Hitachi Command Director

371 2. Under System Settings & Operations, click Users. Deleting users Figure User information In the Users window, the following information is displayed: User ID: The user ID associated with the user s password. Name: The user s name. Description: A general description. For example, what operations the user performs. The user s address in Hitachi Command Director, which is used to send alerts and reports to the user. Related concepts About user management on page 369 Related tasks Deleting users on page 371 When any user account - local or Active Directory is deleted from the Device Manager, you must manually delete this user account in Command Director. If redundant users are not deleted, their information will be listed in the Users Window, but they will not be able to log in to Hitachi Command Director. When a user is deleted from Hitachi Command Director, the following information related to this user is also deleted: Dashboard settings Saved reports Recipient of any scheduled report Recipient of any SLO alert Procedure 1. Select the Administration tab. 2. Under System Settings & Operations, click Users. The Users window displaying account information for all registered Hitachi Command Director users appears. 3. Select one or more user accounts to delete and then click Delete Users. Administering Hitachi Command Director 371

372 You can also select multiple user accounts to delete. 4. In the Confirmation dialog box, verify that you are deleting the correct user accounts, and then click Yes. The affected user will be logged out of all active sessions. Related concepts About user management on page 369 Related tasks Viewing user information on page Administering Hitachi Command Director

373 A Using Host Collector in a secure environment This module includes: Host Collector in a secure environment Data gathered with and without root access Ports and services used Connection Protocols Common services that must be enabled Network impact Using Host Collector in a secure environment 373

374 Host Collector in a secure environment The collection of comprehensive host discovery and storage information using the Host Collector can be implemented in a broad range of data center environments with minimal to no intrusiveness. The Host Collector collects information about storage configuration and utilization without requiring installation of agents on the target servers. In order to collect this data, the Host Collector uses an administrative account to access the target hosts. It does not reconfigure the hosts. The Host Collector minimizes its impact on the target hosts and the network while it is gathering data for Hitachi Command Director. Since the Host Collector uses administrative access to perform its functions, some systems administrators and network security personnel may be cautious about using Host Collector in secure environments. The following table summarized Host Collector access and authorization requirements: OS Network Access Service Authorization method Microsoft Windows UNIX Ping Ping SSH/SCP (port 22) Access to IPC$ Share Access to Admin$ Share Windows Service Windows Management Instrumentation Ping A root password Data gathered with and without root access This module lists the data that is gathered from hosts by the Host Collector if the user provides root access to those hosts and also summarizes the set of data available for data collection if root access is not available. If no root access is provided, then only a subset of this data is gathered. Root access indicates that the user is root only and does not belong to user group root. No root access indicates that the user is non-root and belongs to the root users group. Table A-1 Data gathered with and without root access Type of data gathered Data gathered With root access Without root access System OS version, OS type, memory data Y Y 374 Using Host Collector in a secure environment

375 Type of data gathered Data gathered With root access Without root access CPU Type, speed processor number Y Y Export Name, file system name, type, options Y Y File system: Device File Path Information Volume HBA Name, device name, volume name, usage data Device name, vendor ID, product ID, RAID information, HBA PortWWN, HBA NodeWWN, storage data Name, subdisk information, VDisk information, Volume Manager, capacity data Model, vendor, serial, HBA port information, WWN data Network IP address, netmask, MAC address Y N Y Y Y Y Y N N N Ports and services used The Host Collector accesses each host to collect the necessary data for analysis and reporting, and be able to perform the following tasks: Find the target devices (servers, switches, and storage devices). Perform an analysis of configuration and utilization data. As a security precaution in some data centers, port settings may have been changed from their default values and certain services may be disabled. The Host Collector cannot support all configuration customizations. In such cases, the Host Collector attempts to record whatever it encounters and provides feedback about these obstacles. It is also possible to configure the Host Collector to use specific non-default values for each port or service at a server level. There are fundamentally only two services required by the Host Collector; one during initial discovery and one for its analysis ping and SNMP. Ping (Initial discovery) Ping is the UNIX utility for sending Internet Control Message Protocol (ICMP) ECHO_REQUESTs. Typically, Ethernet interface hardware responds directly to pings. If, for any reason, the Host Collector does not receive a response to its ping request, it makes no further attempt to communicate with that device. When the Host Collector receives a ping echo from an IP address, it then proceeds to determine the device type. This is usually an operating system identifier, but it could also be some other identifier indicating a printer, switch, or other Ethernet device. The Host Collector first tries two other protocols to determine the device type SNMP and Telnet. Using Host Collector in a secure environment 375

376 SNMP The first protocol the Host Collector tries is SNMP (Simple Network Management Protocol) on port 161. SNMP was designed to exchange device characteristics over Ethernet. The identity of the device is the most fundamental information provided by an active SNMP agent. SNMP agents often provide a wealth of additional data about a system s component hardware and software. Telnet Not all devices have an SNMP agent, and even if it is present, it may not be active or configured properly. In such cases, the Host Collector next tries to initiate a Telnet session on port 23. If the target device has the Telnet service enabled, it responds first with a Telnet Header that contains the required system identifier. Once this is obtained, the Host Collector cancels the Telnet connection. Connection Protocols The Host Collector does not rely on any installed agents on the targets; therefore, it must have a method of connecting to these servers. The connection services are different for UNIX and Windows. Protocols for UNIX systems On UNIX systems, the Host Collector uses SSH/SCP if it is available (default is port 22). These services do not typically come bundled in an operating system, but they are commonly added for secure connectivity to the host. Protocols for Microsoft Windows systems On Microsoft Windows systems, NetBIOS must be enabled on port 139. If WMI (Windows Management Instrumentation) is available, the Host Collector uses it. Otherwise, the Host Collector installs and executes its routines as Windows Services. Common services that must be enabled To reliably collect comprehensive host discovery and storage information using the Host Collector, the target hosts need to have the following common services enabled. Any credentials provided for Windows and UNIX respectively should have access to the all the services, protocols, and shares listed here. 376 Using Host Collector in a secure environment

377 Services on Windows hosts Windows Service Manager Windows Management Instrumentation Ping Access to IPC$ Share Access to Admin$ Share Service on UNIX hosts SSH/SCP (default on port 22) Network impact Performance impact The Host Collector has two broad methods of probing and reporting metrics from target servers. SNMP is the simpler of the two, and only requires interaction with the SNMP daemon present on the target and only uses SNMP GET operations. The second type involves the remote invocation and execution of a Data Gather routine on the target server. The appropriate routines are automatically copied from the Host Collector host to the targets. These routines perform a one-time collection of the system information and then disappear from the targets as seamlessly as they had arrived. Since it is the execution with administrative permission of these scripts that causes network security concerns, this section addresses only this aspect. The following statistics are average values for a typical Class C network. The performance impact of the Host Collector takes place in two areas: host discovery and the data gathering process. The following tables summarize the Host Collector s performance impact: Metric Value Total Duration 10 minutes Network Traffic Average 9-10K bits per second Peak 100K bits per second Utilization for a 100 Base-T Network Average 0.01% Peak 0.1% Using Host Collector in a secure environment 377

378 Metric Value Total Duration 20 minutes Network Traffic Average K bits per second Peak K bits per second Utilization for a 100 Base-T Network Average 0.12% Peak 0.7% 378 Using Host Collector in a secure environment

379 B Setting up configuration gathering operation using sudo This module describes the setup required on a target Linux, Solaris, AIX, or HP-UX host to allow for a configuration gathering operation using sudo. Configuration gathering operation using sudo Setting up configuration gathering operation using sudo 379

380 Configuration gathering operation using sudo Sudo (su "do") allows a system administrator to delegate authority to give certain users or groups of users the ability to run some or all commands as root or another user while providing an audit trail of the commands and their arguments. An important prerequisite for performing a configuration gathering operation using sudo is the existence of sudo installation on the remote hosts. For more information about installing sudo on host of a specific OS type, refer to the relevant operating system documentation. Hitachi Command Director supports the configuration gathering operation using sudo permissions without password and with user-provided password; sudo permission with root password is not supported. Binary used for configuration gathering operation The following binary gathers configuration information from hosts running Linux, Solaris, AIX, or HP-UX operating system: <Installation_Folder>/lib/native/unix/ FsDataGatherLauncher.Unix.sh The gather binary is copied to the /tmp directory on the target host. Commands used by Gather binary The following tables list the commands used by the Gather binary operation under Solaris, HP-UX, AIX, and Linux. Solaris awk grep powermt uname cat hostname prtvtoc unlink chmod ifconfig psrinfo vxdctl devinfo iscsiadm raidscan vxdg df labelit rm vxdisk dlnkmgr ls sed vxdmpadm dmesg metaset sh vxprint echo metastat sort wc egrep mount sudo zfs exportfs ndd tail zpool format pkginfo tr 380 Setting up configuration gathering operation using sudo

381 HP-UX adb exportfs netstat uname awk grep pvdisplay unlink bash hostname rm vgdisplay cat ifconfig sed vxdctl chmod ioscan sh vxdg df lanadmin sort vxdisk diskinfo lanscan strings vxdmpadm dlnkmgr ls sudo vxprint dmesg lsdev swlist wc echo lvdisplay tail egrep mount tr AIX awk grep lspv sudo bash hostname lsvg svmon bootinfo ifconfig mount tail cat iscsiadm netstat tr chmod ls oslevel uname df lsattr raidscan unlink dlnkmgr lsdev rm wc echo lsfs sed egrep lslpp sh exportfs lslv sort Linux awk exportfs lvs sort cat fdisk lvscan sudo chmod grep mount tail df hostname pvdisplay trun dlnkmgr ifconfig pvs uname dmesg iscsiadm raidscan unlink e2label ls rm vgdisplay echo lsscsi rpm vgs egrep lvdisplay sed wc export lvm sh Setting up configuration gathering operation using sudo 381

382 Requirements for account used for configuration gathering operation The account used for the configuration gathering operation using sudo must have the following privileges: Execute permission for the sudo command using SSH Read, write, and execute permissions to the /tmp directory Execute permission to commands used by the gather binary for the respective OS Note: Make sure the sudo command and commands used by the gather binary are available in the user s PATH environment variable and execute permission has been provided to the user. Sample content of sudoers file Following are examples of the sudo files that are used to access the target host: Note: It is recommended that you run the following examples using the visudo command. Refer to the relevant sudo manual for information. Following is an example of a sudoers file that does not use a password: # Add line below to preserve user environment setting when sudo is used Defaults!env_reset# Add line below to add user sudo permission # <user> <host>=(<user to alias>) NOPASSWD: /tmp/ FsDataGatherLauncher.Unix.sh# Here is an example: hdcadmin ALL=(ALL) NOPASSWD:/tmp/FsDataGatherLauncher.Unix.sh Following is an example of a sudoers file with a user-provided password: ## Add line below to preserve user environment setting when sudo is used?defaults!env_reset??## Do NOT add lines below to set sudo permission for all or particular users with their?## own password instead of root password?## Defaults runaspw? ## Defaults:<user> runaspw?## Add line below to add user sudo permission?## <user> <host>=(<user to alias>)/tmp/ FsDataGatherLauncher.Unix.sh?## Here is an example: hdcadmin ALL=(ALL)/tmp/FsDataGatherLauncher.Unix.sh 382 Setting up configuration gathering operation using sudo

383 Glossary A alert allocated volume application array group An event that is generated when an SLO is violated. You can also set up notifications with the event details. A logical device (LDEV) for which one or more host paths are defined. In Hitachi Command Director, applications represent groups of storage volumes used by an actual application. An application can be defined by volumes belonging to a host group or by storage consumed by a physical host discovered by the HCmD agentless Host Collector. B A set of hard drives in a storage system that have the same capacity and are treated as one RAID unit. An array group contains user data and parity information, which ensures user data integrity in the event of a disk drive failure in the array group. BPS Bits per Second. The standard measure of data transmission speeds. business view A business hierarchy that organizes hosts, applications, and other folders for reporting purposes. Storage capacity and storage type utilization, I/O operations per second (IOPS), and SLO status are summarized for the application and for every folder in the hierarchy. The same applications can be organized according to multiple hierarchies. Glossary 383

384 C capacity The amount of data storage space available on a disk drive, or storage system. Generally measured in MB, but can also use other measurements such as TB and PB, depending on the total storage space. chargeback The storage cost that storage administrators charge their clients. This storage is allocated to the client's applications. CLI Command Line Interface. A method of interacting with software using a command line interpreter. The Command Director CLI is used to generate and save reports, and perform application management operations. CLPR Cache Logical Partition. Refers to partitioned cache memory. CLPRs can be used to segment storage system cache assigned to parity groups. cluster D Multiple-storage servers working together to respond to multiple read and write requests. data collection data drive data pool A method of discovering and gathering information from the Storage System collectors on the Hitachi Device Manager and Agent for RAID servers and the Host Collectors installed on hosts in the network. A physical data storage device that can be either a hard disk drive (HDD) or a flash (solid-state) drive. One or more logical volumes designated to temporarily store original data. When a snapshot is taken of a primary volume, the data pool is used if a data block in the primary volume is to be updated. The original snapshot of the volume is maintained by storing the to-be-changed data blocks in the data pool. 384 Glossary

385 data refresh Collecting information from the data collectors on the Hitachi Device Manager and Agent for RAID servers, and updating the information displayed in the Hitachi Command Director GUI. datastore A datastore represents a storage location for virtual machine files. A storage location can be a VMFS volume, a directory on Network Attached Storage, or a local file system path. A datastore is platform-independent and host-independent. Therefore, datastores do not change when the virtual machines they contain are moved between hosts. The scope of a datastore is a datacenter; the datastore is uniquely named within the datacenter. DB Database. device Refers to the name of a Computer, Storage, IP switch, FC switch in Hitachi IT Operations Analyzer. DP-VOL Dynamic Provisioning (DP) Dynamic Provisioning virtual volume. A virtual volume with no memory space used by Dynamic Provisioning. Presents a virtual pool of shared capacity that is larger than the actual amount of physical storage available. Storage capacity can be allocated to an application without it actually being physically mapped until it is needed, so storage allocations can exceed the amount of storage that is physically installed. E For example, system administrators can deliver capacity on demand by provisioning storage from a virtual pool. This not only reduces administration costs by cutting the time to provision new storage, but also improves application availability by reducing the downtime needed for storage provisioning. external volume A logical volume whose data resides on drives that are physically located outside the storage system. Glossary 385

386 G global-active device A storage system feature that provides high-availability copy pairs to support simultaneous, uninterrupted host and cluster active-active I/O within and across geographically disparate data centers. This feature protects against storage system and site failures by providing continuous access to data. GUI (Graphical User Interface) H The graphical user interface of a software program. HBA Host Bus Adapter. A circuit board and/or integrated circuit adapter installed in a workstation or server that provides input/output processing and physical connectivity between a server and a storage device. An iscsi HBA implements the iscsi and TCP/IP protocols in a combination of a software storage driver and hardware. HDvM Hitachi Device Manager. For version 7.0 and later, this name has changed to Hitachi Command Suite. Allows you to consolidate storage operations and management functionality in a system that contains multiple Hitachi storage systems.device Manager quickly discovers the key configuration attributes of storage systems and allows your organization to begin managing complex and heterogeneous storage environments using a browser-based GUI. High-performance NAS Platform (HNAS)/Hitachi NAS Platform The High-performance NAS Platform is a storage system that provides high-performance read/write access to data through multiple protocols, such as CIFS, NFS, iscsi, and FTP. It is a highly scalable and modular Network Attached Storage (NAS) server, with multi-gigabit throughput from network to disk. Hitachi Command Director (HCmD) For 7.0 and later, new name for Hitachi Storage Command Portal (HSCP). Hitachi Command Suite (HCS) For 7.0 and later, new name for Hitachi Device Manager (HDvM). See HDvM. 386 Glossary

387 host One or more host bus adapter (HBA) world wide names (WWN). Host group A feature that enables the attachment of 1,024 heterogeneous Fibre Channel (FC) host ports to one physical storage port on the storage system. Each FC host connection comes through a virtual port and is assigned its own address space or host storage domain, which cannot be seen or accessed by any other virtual port. This provides the scalability of host connections and safe multi-tenancy, which is required when many applications share the same physical resources in a virtualized environment. A host group can be shared with another virtual port on another physical port for alternate path support. HTnM Hitachi Tuning Manager. A real-time software monitor that can view the current state of the host, file system, database, storage area network, and storage resources. In Tuning Manager, a resource indicates any object that is used by an application. You can compare this information with the normal behavior or the baseline performance stored in the database. The ability to query a historical database for performance and capacity trend analysis on each component of the storage area network lets you correlate the current changes in performance with recent changes to the physical configuration, software, workload, or other environmental changes that may be causing changes in an application's performance. The Tuning Manager series consists of Agents that collect the performance data for each monitored resource and the Tuning Manager program that manages all the Agents. HTSM I Tiered Storage Manager. Tiered Storage Manager is the software that is used to perform migration. The term migration refers to moving the data stored on one volume to another volume. Tiered Storage Manager moves the data on a predefined set of volumes to another set of volumes that have the same characteristics. IO (Input/Output) Input/output. IOPS I/Os per second. Glossary 387

388 IP K Internet Protocol. Specifies the format of packets and addressing scheme. Most networks combine IP with a higher-level protocol called Transmission Control Protocol (TCP), which establishes a virtual connection between a destination and a source. key performance indicator (KPI) L A measurement used to help an organization define and measure progress toward organizational goals. KPIs are used in business intelligence to assess the present state of the business and to prescribe a course of action. KPIs are typically tied to an organization's strategy. LAN Local Area Network. A computer network that spans a relatively small area, such as a single building or group of buildings. logical volume LU (Logical Unit) LUN (Logical Unit Number) LUN Owner An area on a disk consisting of device files that are logically integrated using a volume manager. Also referred to as LDEV. A volume created in a storage system, known as an LU (logical unit) in an open system. A LUN is an address for a disk drive, and the disk device itself. LUNs are used in SCSI protocols to differentiate disk drives within a common SCSI target device, like a storage system. Each LUN is a unique number that identifies a specific logical unit, which may be an end user, a file, or an application program. LUNs are normally not entire disk drives but virtual partitions (or volumes) of a RAID set. LUN Owner represents a collection of volumes (LUNs) used by a common set of hosts, clusters, or applications. It is derived by tracing the path from the storage volume to the storage port and back to the host World Wide Name (WWN). If a set of host WWNs is connected to the same set of volumes, regardless of the number of paths they use, the set of volumes is considered to belong to the same LUN Owner, which maps 388 Glossary

389 back to a host, a cluster, or an application as represented by the set of host WWNs. M By using the LUN Owner method, HCmD derives the mapping from the storage back to a host side entity such as a host, cluster, or an application without an agent that may require host security credentials. By default, a HCmD application has a single LUN Owner. monitored nodes monitoring window Refers to discovered nodes that have been selected for monitoring. These are the nodes for which the IT Operations Analyzer reports any events. Specifies when the application is monitored by the SLO profile. MS IIS (Microsoft Internet Information Services) N A set of internet-based services in a web server, for servers using Microsoft Windows. NAS Network Attached storage. node O Refers to the monitored computer, switch, storage in Hitachi IT Operations Analyzer. owner group P A logical unit (LU) group provisioned to the same set of WWNs. P-VOL (primary volume) The storage volume in a volume pair. It is used as the source of a copy operation. In copy operations a copy source volume is called the P-VOL while the copy destination volume is called S-VOL (secondary volume). Glossary 389

390 parity In computers, parity (from the Latin paritas, equal or equivalent ) refers to a technique of checking whether data has been lost or written over when it is moved from one place in storage to another or when transmitted between computers. parity group RAID groups can contain single or multiple parity groups. You can think of the RAID group as the actual RAID container for data protection, and the parity group as a partition of that container. Using parity groups, multiple LUNs can be created from each RAID group, and ported out to the same or different servers. This allows granularity in LUN sizes being obtained from the RAID group. If each partition (parity group) is assigned to the same server, there should be no contention for the RAID group's disk resources. You can always just use the entire RAID group as a single parity group and create a large LUN. pool A set of volumes that is reserved for storing Copy-on-Write Snapshot data or Dynamic Provisioning write data. pool volume R pool-vol. A logical volume that is reserved for storing snapshot data for Copy-on-Write Snapshot operations or write data for Dynamic Provisioning. RAID (Redundant Array of Independent Disks) A group of disks where part of the physical storage capacity is used to store redundant information about user data stored on the remainder of the storage capacity. The redundant information enables regeneration of user data in the event that a disk, or the access path to it, fails. A RAID appears to the operating system to be a single logical hard disk. RAID employs the technique of disk striping, which involves partitioning each drive's storage space into units ranging from a sector (512 bytes) up to several megabytes. The stripes of all the disks are interleaved and addressed in order. 390 Glossary

391 S S-VOL (secondary volume) SAN SATA A replica of the primary volume (P-VOL) at the time of a backup and is kept on a standby storage system. Recurring differential data updates are performed to keep the data in the S-VOL consistent with data in the P- VOL. Storage Area Network. A network of shared storage devices that contain disks for storing data. Serial ATA. A computer bus technology primarily designed for the transfer of data to and from hard disks and optical drives. SATA is the evolution of the legacy Advanced Technology Attachment (ATA) interface from a parallel bus to serial connection architecture. Service Level Agreement (SLA) An agreement that specifies what service is provided and how it is supported, and the responsibilities of the parties involved. These parties are storage administrators (who provide storage) and their clients (application administrators who request storage). Service Level Objective (SLO) SLO investigation unit A stated level of availability, serviceability, performance, operation, or other attributes of a service (for example, billing and penalties for violations). In Hitachi Command Director, an observed or calculated metric that is compared to a missed or borderline threshold. If the SLO is below its threshold (not in jeopardy), it is not a violation and it has an OK status. SLOs are intended as operational guidelines for the implementation of the service negotiated under the SLA. SLOs comprise SLAs containing service parameters and goals. A dashboard that identifies the potential cause of Application SLO violation using various reports that displays key storage components performance used by the application/sub-application. Glossary 391

392 SLO profile An SLO profile allows you to assign multiple SLO types to an application. You can name a standard set of SLOs (for example, Gold storage type SLOs) and assign them to multiple applications. Only SLO profiles can be assigned to applications. SMTP (Simple Mail Transfer Protocol) A protocol used to receive and store data directly from servers. SPARC (Scalable Processor Architecture) SQL SSL (Secure Sockets Layer) storage class storage system switch A reduced instruction set computer (RISC) architecture developed by Sun Microsystems and used in the Sun workstation family. Structured Query Language used to communicate with a database. A protocol to securely transmit data over the Internet. Two SSL-enabled peers use their private and public keys to establish a secure communication session, with each peer encrypting transmitted data with a randomly generated and agreed-upon symmetric key. A classification based on the grouping of disk characteristics, such as disk type, capacity, speed, RAID level and number of drives in a parity group, across storage systems. The Hitachi enterprise storage box for the Universal Storage Platform (USP, USP-V, USP-VM), Hitachi Unified Storage and the Network Storage Controller (NSC). A network infrastructure component to which multiple nodes attach. Unlike hubs, switches typically have internal bandwidth that is a multiple of link bandwidth, and the ability to rapidly switch node connections from one to another. A typical switch can accommodate several simultaneous full link bandwidth transmissions between different pairs of nodes. 392 Glossary

393 T tag A tag provides more context about an application. It provides all information identifying the application such as who owns it and where it is located. For example, a tag USA indicates that the application is located in the USA. Tags are organized into tag categories. tag category A tag category is a name of a group of related tags. When tags USA and Finance are applied to the same application, USA belongs to the Country tag category while Finance belongs to the Function tag category. tier U A user-friendly descriptor that summarizes the type of storage hardware on which a logical volume resides. Typical storage hardware characteristics that are referred to by a tier are: disk speed, disk capacity, disk type (for example, FC, SCSI), RAID level, storage system model, virtualization level (for example, internal vs. external), and pool type (if relevant). All volumes that share the characteristics summarized by the tier are annotated with that tier's name. unallocated volume V A volume for which no host paths are assigned. V-VOL (virtual volume) VM VMDK File The secondary volume in a Copy-on-Write Snapshot pair. When in PAIR status, the V-VOL is an up-to-date virtual copy of the primary volume (P- VOL). When in SPLIT status, the V-VOL points to data in the P-VOL and to replaced data in the pool, maintaining the point-in-time copy of the P-VOL at the time of the split operation. Virtual Machine. Virtual Machine Disk File. In a virtual machine, the VMDK file is an encapsulation of an entire server or desktop environment in a single file. The VMDK file can be considered as the hard drive for a virtual machine. Glossary 393

394 volume W A logical device (LDEV), or a set of concatenated LDEVs in the case of LUSE, that has been defined to one or more hosts as a single data storage unit. A mainframe volume is called a logical volume image (LVI), and an open-systems volume is called a logical unit. (LU). WWN (World Wide Name) A unique identifier for an open systems host. It consists of a 64-bit physical address (the IEEE 48-bit format with a 12-bit extension and a 4- bit prefix). WWN is essential for defining the SANtinel parameters because it determines whether the open systems host is to be allowed or denied access to a specified logical unit or a group of logical units. 394 Glossary

395 Index A accepting 93 administration 307 Agent for RAID Extension configuring in HCmD 319 data refresh frequency 326 enabling service on Agent for RAID host 318 performance data collection 312 Application capacity by storage class report 239 Application capacity consumption by storage system report 243 Application capacity consumption trend by storage system for application report 245 application reports Application Capacity Comparison Trend report 182 Application Response Time Trend report 168 Application Summary report 159 available in HCmD 157 File System Utilization report 162 IO Utilization Trend report 169 Pool Tier Utilization Trend report 185 Pool Utilization report 173 SLO Details report 40, 163 SLO Status report 160 Storage Allocation Details report 170 Storage Allocation report 161 Storage Allocation Trend report 164 Storage Path report 176 Storage System Performance report 161 Tier Definition report 177 application SLO 83 Application SLO conformance details report 284 Application SLO conformance report 283 Application Storage allocation by Pool report 301 Application Storage Allocation by Tier report 300 Application volume SLO conformance details report (CSV only) 103, 289 applications about 132 bulk management 143, 148 creating automatically 367 creating manually 135 creation workflow 133 deleting 152 B C managing untagged applications 142 modifying 143, 148 modifying multiple 143, 148 Applications with most SLO misses in the last 24 hours 42 asset and inventory report Capacity by storage class 299 file system inventory 296 Physical server inventory 297 Storage port details 298 Storage system inventory 295 asset and inventory report gallery 262 assigning 119 auto create applications 366 options 366 bulk management of applications 143, 148 business views all applications view 73 applications by capacity view 75 applications by pool view 74 creating new 77 custom view 65 deleting 80 displaying 64 file servers view 69 Hierarchical Categories 79 hosts view 68 Logical Group view 66 managing 79 Preview 79 searching in 65, 66, 68, 69, 71, storage systems view 71 chargeback report gallery 262 chargeback reports Application storage allocation by pool 301 Application storage allocation by tier 300 Storage allocation by VMware VMs 302 Index 395

396 configuration gathering operation using sudo 379 creating 116 CSV reports Application volume SLO conformance details 103, 289 E servers default server port number 355 modifying configuration 355 ESX hosts viewing configuration information 344 D dashboard accessing 33 controls 33 customizing 34, 259 default reports global and datacenter 36 layout 35 dashboard reports Applications Missing SLO report 37 Applications with Most SLO Misses report 42 DTR SLO Status report 39 HNAS Capacity Overview report 48 Hyper-V File System Overview report 44 IOPS SLO Status report 38 Pool Capacity Overview 45 Pools 53 Response Time SLO Status report 38 Storage System Capacity Overview report 43 Storage System Performance Overview report 52 Top 5 Busiest HNAS Nodes report 47 VMware Datastore Overview report 43 dashboards default reports Pools 271 default, selecting 35 introducing 32 introduction 31 planning 53 data collection configuration data using HDvM data collector 312 from Hitachi storage systems 312 from third-party storage systems 312 performance data using Agent for RAID Extension 312 data metrics in storage system monitoring profiles 118 default host profile settings assigning and updating 127 default reports 57 default storage system monitoring profile settings assigning and updating 121 deleting 117 documents referenced 13 F G H File Servers business view 69 File System Inventory report 296 Filesystem Utilization Forecast Trend report specifying criteria 209 forecasting reports Filesystem Utilization Forecast Trend report 207 Pool Capacity Forecast Trend 269 graphical user interface using 27 HNAS cluster overview report 49 HNAS reports Storage allocation trend report 164 available in HCmD 198 File System IO Trend report 200 File System Load Trend report 201 Filesystem utilization trend report 206 HNAS File System report 201 HNAS Pool Details report 203 HNAS Pool Summary report 202 HNAS Shares report 204 Protocol Op/s Trend report 204 Total Throughput Trend report 205 Host Capacity Utilization Detail report 58 Host Capacity Utilization Status report 57 Host Collector data gathered with and without root access 374 using in secure environment 374 Host Collectors agentless data gathering mechanism 330 configuring new 335 deleting 342 deleting hosts 352 discovering hosts by IP address 339 discovering hosts by IP address list 340 discovering hosts on subnet 339 host login settings 347 launching 338 modifying 341 refreshing 342 specifying data collection frequency 351 validating connectivity Index

397 I L vcenter collector 336 Host dashboard Host Capacity Utilization Detail report 58 host monitoring profiles assigning 125 creating and managing 123 host reports Storage allocation trend report 164 available in HCmD 192 ESX Server Data Stores report 212 ESX Server VMDKs report 212 Hyper-V Server report 210 Storage Utilization report 195 Volume Manager Group report 197 Hosts dashboard 57 Host Capacity Utilization Status report 57 Hyper-V Server report 210 infrastructure monitoring 113 layout dashboard 35 licenses about 309 managing 309 registering 24 types of 309 unlimited license support 310 updating 310 LUN Owner configuration 356 about 356 basic configuration scenario 357 changes that impact applications 359 creation of LUN Owner 357 excluding volumes 362 including volumes 364 split configuration scenario 357 P Parity group utilization for pool report 275 PDF exporting a dashboard to 36 exporting reports to 252 performance report gallery 262 performance reports Application SLO conformance 283 Application SLO conformance details 284 Application volume SLO conformance details (CSV only) 103, 289 Storage port workload 273 Top 20 busiest parity groups 278 Top 20 busiest storage system ports 275 Top 20 most or least busy volumes 278 Underutilized volumes 281 Physical capacity by Storage Systems report 263 Physical Server Inventory report 297 ping 375 planning dashboard default reports 53 Planning dashboard default reports 227 Pool Capacity by Storage System report 265 Pool Capacity Forecast Trend report 233 specifying criteria 188, 235 Pool Capacity Overview report 45 Pool Detailed Capacity Forecast Trend report specifying criteria for 270 Pool detailed capacity trend for, 268 Pool Detailed Capacity Trend report 264 Pool Storage Performance report 274 Pool Tier Utilization Forecast Trend Report forecasting reports Pool Tier Utilization Forecast Trend 187 Pool Tier Utilization Trend report 185 Pool Usage By Application report 271 Pools dashboard 53 reports, default 53 Storage Pool Health Detail report 56 Storage Pool Health Status report 55 preface 11 M managing 114 modifying 117 monitoring applications 81 monitoring hosts assigning profiles 125 monitoring profiles to storage systems 119 O overview Command Director 17 R recommendation settings monitoring settings 100 notification settings 100 recommendations calculation 84 recommendations, for volumes 93 referenced documents 13 report criteria for Application capacity by storage class report 242 for Application Capacity Comparison Trend report 183 for Application SLO Conformance Details report 286 Index 397

398 S for Pool capacity trend report 233 for Storage system capacity trend 228 for Top 20 Busiest Storage System Ports report 276 for Top 20 Most or Least Busy Volumes report 280 for Underutilized Volumes report 282 specifying 253 supported reports 253 report gallery 262 report gallery categories 262 report viewer pagination controls 249 reports customizing report views 253 exporting and downloading in XLS or XML 252 features of 247 filtering data 253 forecasting 166, 229, 233, 269 managing rows and columns 253 refreshing data 250 report gallery 261 saving 257 scheduling 251 scheduling for report distribution 251 sorting data 250 specifying report criteria 253 Storage Pool Health Status 55 tasks available in report viewer 248 using 247 scheduled reports managing 354 removing 354 scheduling reports stopping 355 search in business views for applications in All Applications view 73 for applications in Application by capacity view 75 for applications in Application by pool view 74 for applications in custom business view 65 for applications in Logical Group view 66 for file servers in File Servers view 69 for hosts in Hosts view 68 for storage systems in Storage Systems view 71 secure sockets layer (SSL) enabling during license registration 24 enabling for Agent for RAID Extension 320, 322 enabling for Device Manager Storage System collector 320, 323 Service Level Objective (SLO) overview 82 types 83 Service Level Objective (SLO) profiles 100 about 85 creating new 88 deleting 91 editing modifying updatiing 90 SLO profile 84 application 86 SLO profile recommendations for volumes sorted by applications 96 for volumes sorted by pools 99 SLO profiles 93 recommendations accepting 91 SLO status data transfer rate 39 SNMP 376 Storage allocation by VMware VMs report 302 Storage Allocation Forecast Trend report 166 specifying criteria for 167 Storage Allocation Trend - HNAS report 164 Storage Allocation Trend - Hyper-V report 164 Storage Allocation Trend - Windows report 164 Storage capacity by pool for storage system report 265 storage class 239 storage economics report gallery 262 storage economics reports Top 10 tiers by capacity 293 Underutilized host file systems 294 Storage Path report 176 Storage Pool Health Detail report 56 Storage Pool Health Status report 55 Storage port details report 298, 299 Storage Port Workload report 273 Storage System Capacity Forecast Trend report 229 specifying criteria 230 Storage System Collectors about 312 configuring 319 deleting 323 disabling 328 enabling 328 modifying 321 modifying refresh frequency 326 Storage System Health Detail report 50 Storage System Health Status report 49 Storage System health threshold about 114 Storage System Inventory report 295 storage system monitoring profile 116, 117 storage system monitoring profiles 114, 115, 117 storage system reports available in HCmD 217 Application capacity by storage class report 239 Application capacity utilization report 238 Applications with most SLO misses Index

399 Performance overview by storage system 226 Pool capacity overview 224 Pool capacity trend report 231 Pool utilization report 236 Storage system capacity overview 223 Storage system capacity trend report 227 Storage system performance overview 222 storage systems 278 enabling 328 Sudo account requirements 382 binaries used for configuration gather operation 380 command used by Gather binary 380 V vcenter collector configuring new 336 viewing ESX hosts 344 viewing 115 Volumes Mapped to ESX Server VMs report 213 T tags and tag categories managing 352 reserved words 352 telnet 376 Thin Vols Capacity for Pool for Storage System, Pool report 265 third-party storage systems data collection 312 supported 312 Physical Capacity by Storage System report in reports tab 263 Storage System Capacity Overview report on dashboard 43 Top 10 Tiers by Capacity report 293 Top 20 Busiest Parity Groups 278 Top 20 Busiest Storage System Ports report 275 Top 20 Pool Utilization by Capacity 53 Top 20 Pool Utilization by Capacity report 53 Tuning Manager performance reporter launching from Volume List in HCmD 103 report display notes 103 Tuning Manager report display notes 278 U Underutilized Host File Systems report 294 Underutilized Volumes report 281 user profile modifying 27 password, changing 27 users deleting accounts 371 Device Manager local, LDAP users 369 viewing user s information 370 utilization report gallery 262 utilization reports Physical capacity by Storage System 263 Utilization tab 264 Pool Detailed Capacity Trend report 264 Index 399

400 400 Index

401

402 Hitachi Data Systems Corporate Headquarters 2845 Lafayette Street Santa Clara, California U.S.A. Regional Contact Information Americas Europe, Middle East, and Africa +44 (0) Asia Pacific MK-90HCMD001-13