Hitachi COmmand Director

Hitachi Command Suite
Command Director Software

User Guide
FASTFIND LINKS
Document Organization
Product Version
Getting Help
Contents
MK-90HCMD001-03
2011 Hitachi, Ltd., Hitachi Data Systems Corporation. 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. (hereinafter referred to as Hitachi) and
Hitachi Data Systems Corporation (hereinafter referred to as Hitachi Data Systems).
Hitachi and Hitachi Data Systems reserve the right to make changes to this document at any time without
notice and assume 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.
All of the features described in this document may not be currently available. Refer to the most recent
product announcement or contact your local Hitachi Data Systems sales office for information about feature
and product availability.
Notice: Hitachi Data Systems products and services can be ordered only under the terms and conditions of
Hitachi Data Systems applicable agreements. The use of Hitachi Data Systems products is governed by the
terms of your agreements with Hitachi Data Systems.
By using this software, you agree that you are responsible for:
a) acquiring the relevant consents as may be required under local privacy laws or otherwise from employees
and other individuals to access relevant data; and
b) ensuring that data continues to be held, retrieved, deleted or otherwise processed in accordance with
relevant laws.
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 in the United States and other countries.
Hitachi AMS, Hitachi USP, XP Continuous Access Synchronous, ShadowImage and XP Continuous Access
Journal are trademarks of Hitachi Data Systems Corporation in the United States and other countries.
IBM is a trademark of International Business Machines Corporation in the United States, other countries, or
both.
Microsoft is a registered trademark of Microsoft Corporation in the U.S. and other countries.
Microsoft product screen shots reprinted with permission from Microsoft Corporation.
Mozilla is a trademark of the Mozilla Organization.
All other trademarks, service marks, and company names are properties of their respective owners.
ii
Hitachi Command Director User Guide
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
Intended audience. . . . . . . . . . . . . . . . . . .
Product version . . . . . . . . . . . . . . . . . . . . .
Release notes . . . . . . . . . . . . . . . . . . . . . .
Document revision level . . . . . . . . . . . . . . .
Referenced documents. . . . . . . . . . . . . . . .
Document conventions. . . . . . . . . . . . . . . .
Conventions for storage capacity values. . . .
Accessing product documentation . . . . . . . .
Getting help . . . . . . . . . . . . . . . . . . . . . . .
Comments . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
....
....
....
....
....
....
....
....
....
....
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xii
. xii
. xii
. xii
. xii
.xiii
.xiii
.xiv
.xiv
.xiv
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
About Hitachi Command Director (HCmD) . . .
Features . . . . . . . . . . . . . . . . . . . . . . . . . . .
New in Command Director 7.1.1 . . . . . . . . . .
Setup workflow . . . . . . . . . . . . . . . . . . . . . .
Logging in . . . . . . . . . . . . . . . . . . . . . . . . .
Registering a license . . . . . . . . . . . . . . . . . .
Specifying email address when you first log in
Modifying your user profile . . . . . . . . . . . . . .
HCmD graphical user interface . . . . . . . . . . .
Logging out . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
......
......
......
......
......
......
......
......
......
......
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1-2
. 1-2
. 1-3
. 1-5
. 1-6
. 1-7
. 1-9
. 1-9
. 1-9
1-10
Quick access to your application status and storage health . . . . . . 2-1

About the Hitachi Command Director dashboard. .
Accessing the dashboard . . . . . . . . . . . . . . . . . .
Customizing the dashboard . . . . . . . . . . . . . . . .
Dashboard reports. . . . . . . . . . . . . . . . . . . . . . .
Total number of applications with SLO misses.
Response Time SLO status . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-2
2-3
2-3
2-4
2-4
2-5
iii
IOPS SLO status . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Storage system performance overview . . . . . . . . . . . . .
Applications with most SLO misses in the past 24 hours .
Storage system capacity overview . . . . . . . . . . . . . . . . .
VMware datastore overview . . . . . . . . . . . . . . . . . . . . .
Hyper-V file system overview . . . . . . . . . . . . . . . . . . . .
HDP capacity overview. . . . . . . . . . . . . . . . . . . . . . . . .
Top 5 busiest HNAS nodes . . . . . . . . . . . . . . . . . . . . . .
HNAS capacity overview. . . . . . . . . . . . . . . . . . . . . . . .
Storage system performance detailed reports. . . . . . . . . . . .
IOPS distribution by storage system . . . . . . . . . . . . . . .
DTR distribution by Storage System . . . . . . . . . . . . . . .
Average read hit % by storage system . . . . . . . . . . . . .
Average write pending by storage system . . . . . . . . . . .
Average response time by storage system . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2-5
. 2-6
. 2-7
. 2-8
. 2-9
. 2-9
2-10
2-11
2-12
2-12
2-12
2-13
2-14
2-15
2-16
Managing resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

About applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application elements . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic creation of applications. . . . . . . . . . . . . . . . . . . .
Impact of switching to a different auto-create option . . .
Configuring applications. . . . . . . . . . . . . . . . . . . . . . . . . . .
Application creation process flow . . . . . . . . . . . . . . . . .
Application notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating applications manually . . . . . . . . . . . . . . . . . . .
Creating applications automatically . . . . . . . . . . . . . . . .
Managing unassigned applications . . . . . . . . . . . . . . . .
Modifying applications . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting applications . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing custom tags and tag categories . . . . . . . . . . . . . .
About business views . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using business views . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying business views . . . . . . . . . . . . . . . . . . . . . .
Custom business view . . . . . . . . . . . . . . . . . . . . . . . . .
Logical Group view . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hosts view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Servers view . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All Applications view . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a new business view. . . . . . . . . . . . . . . . . . . . . . .
Business view modification restrictions . . . . . . . . . . . . . . . .
Managing business views . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting business views . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3-2
. 3-2
. 3-3
. 3-4
. 3-4
. 3-4
. 3-5
. 3-6
. 3-9
3-10
3-11
3-14
3-15
3-16
3-17
3-17
3-18
3-18
3-19
3-20
3-22
3-22
3-24
3-24
3-24
Monitoring applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

SLO overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
iv
Supported SLO types . . . . . . . . . . . . . . . . . . . .

Application SLO types . . . . . . . . . . . . . . . .
Storage system and host SLO types. . . . . . .
Monitoring storage system health thresholds . . .
Storage system health thresholds . . . . . . . .
Modifying storage system health thresholds .
Managing SLO profiles . . . . . . . . . . . . . . . . . . .
About SLO profiles . . . . . . . . . . . . . . . . . . .
Viewing SLO profiles . . . . . . . . . . . . . . . . .
Creating SLO profiles . . . . . . . . . . . . . . . . .
Modifying SLO profiles . . . . . . . . . . . . . . . .
Removing SLO types . . . . . . . . . . . . . . . . .
Deleting SLO profiles . . . . . . . . . . . . . . . . .
SLO Investigation Unit . . . . . . . . . . . . . . . . . . .
About SLO Investigation Unit . . . . . . . . . . .
Accessing the SLO Investigation Unit . . . . . .
Managing monitoring windows . . . . . . . . . . . . .
About monitoring windows . . . . . . . . . . . . .
Viewing monitoring windows . . . . . . . . . . .
Creating monitoring windows . . . . . . . . . . .
Modifying monitoring windows . . . . . . . . . .
Deleting monitoring windows . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 4-3
. 4-3
. 4-3
. 4-4
. 4-4
. 4-5
. 4-6
. 4-6
. 4-7
. 4-8
. 4-9
4-10
4-11
4-11
4-11
4-14
4-14
4-15
4-15
4-16
4-18
4-19
Reporting on applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Application reports. . . . . . . . . . . . . . . . .
Accessing application reports . . . . . . . . .
Application summary report . . . . . . . . . .
SLO status report . . . . . . . . . . . . . . . . .
Storage system performance report. . . . .
Storage allocation report . . . . . . . . . . . .
File System utilization report. . . . . . . . . .
SLO details report . . . . . . . . . . . . . . . . .
Capacity allocation trend report . . . . . . .
Application response time trend report . .
IO utilization trend report . . . . . . . . . . . .
Storage allocation information . . . . . . . .
Storage allocation details . . . . . . . . .
DP Pool utilization report . . . . . . . . .
Storage path report . . . . . . . . . . . . .
Tier definition report . . . . . . . . . . . .
Storage System and host SLOs reports . .
Storage system & host SLOs report . .
Cache write pending % report . . . . .
DP Pool over provisioning ratio report
DP Pool risk ratio report . . . . . . . . . .
DP Pool used % report . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5-3
. 5-4
. 5-5
. 5-5
. 5-6
. 5-6
. 5-7
. 5-7
. 5-9
. 5-9
5-10
5-11
5-12
5-13
5-15
5-16
5-17
5-17
5-18
5-18
5-19
5-19
v
Parity Group busy % report . . . . . .

Port busy % report . . . . . . . . . . . .
Total number of applications in a folder .
Response Time SLO status . . . . . . . . . .
IOPS SLO status report . . . . . . . . . . . .
Application list . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-20
5-20
5-21
5-21
5-21
5-22
Reporting on hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Host reports . . . . . . . . . . . . . . . . . .
Available summary host reports . . . .
Summary host reports . . . . . . . .
Accessing summary host reports .
Host file system used % report. .
Storage utilization report . . . . . .
Volume manager group report . .
Available HNAS host reports . . . . . . .
HNAS host reports . . . . . . . . . . .
Accessing HNAS host reports . . .
File system IO trend report . . . .
File system load trend report . . .
HNAS file system report . . . . . . .
HNAS pool summary report . . . .
HNAS pool details report . . . . . .
HNAS shares report . . . . . . . . . .
Protocol Op/s trend report . . . . .
Total throughput trend report . . .
Hyper-V server report . . . . . . . . . . .
Accessing Hyper-V server report .
Hyper-V server report . . . . . . . .
VMware host reports . . . . . . . . . . . .
Accessing VMware host reports. .
VMware datastores report . . . . .
ESX server VMDKs report . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
..
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6-2
. 6-3
. 6-3
. 6-3
. 6-3
. 6-4
. 6-5
. 6-6
. 6-6
. 6-7
. 6-7
. 6-8
. 6-8
. 6-9
. 6-9
6-11
6-11
6-12
6-13
6-13
6-14
6-14
6-15
6-15
6-15
Report Gallery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

About the report gallery . . . . . . . . . . . . . . .
Utilization report gallery . . . . . . . . . . . . . . .
Physical capacity by storage system . . .
HDP, HDT capacity by Storage Systems .
HDP, HDT pool usage by application . . .
Performance report gallery . . . . . . . . . . . . .
Storage port workload . . . . . . . . . . . . .
HDP Pool storage performance . . . . . . .
Top 20 busiest storage system ports . . .
Top 20 busiest parity groups. . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
vi
....
....
....
....
....
....
....
....
....
....
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-2
7-3
7-3
7-3
7-6
7-6
7-7
7-7
7-8
7-9
Top 20 busiest volumes . . . . . . . . . .

Application SLO conformance . . . . . .
Storage economics report gallery . . . . . .
Top 10 tiers by capacity . . . . . . . . . .
Underutilized host file systems . . . . .
Application data distribution by tier . .
Asset & Inventory report gallery . . . . . . .
Storage system inventory . . . . . . . . .
File system inventory . . . . . . . . . . . .
Physical server inventory . . . . . . . . .
Chargeback report gallery . . . . . . . . . . .
Application storage allocation by tier .
Application storage allocation by pool
Accessing reports . . . . . . . . . . . . . . . . .
Using reports . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7-9
7-10
7-11
7-11
7-11
7-11
7-12
7-12
7-13
7-14
7-14
7-15
7-15
7-16
7-17
Administering HCmD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Administration tasks overview. . . . . . . . . . . . . . . . . . . . . . . . . .
Managing licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hitachi Command Director licenses . . . . . . . . . . . . . . . . . . .
License types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating license information. . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Storage System Data Collectors . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 8-2
. 8-2
. 8-2
. 8-3
. 8-3
. 8-4
. 8-5
. 8-6
. 8-6
. 8-7
. 8-8
. 8-8
. 8-9
8-10
8-11
8-12
8-13
8-13
8-14
8-14
8-15
8-16
8-17
8-18
8-19
8-21
8-22
8-24
8-24
vii
About storage system data collection . . . . . . . . . . . . . .

Viewing information about 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 . . . . . . . . . . . . . . . . . . . . . . .
Enabling and disabling Storage System Collectors. . . . . .
Managing scheduled reports. . . . . . . . . . . . . . . . . . . . . . . .
Configuring email servers. . . . . . . . . . . . . . . . . . . . . . . . . .
Managing HCmD users. . . . . . . . . . . . . . . . . . . . . . . . . . . .
About user management . . . . . . . . . . . . . . . . . . . . . . .
User details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing user information . . . . . . . . . . . . . . . . . . . . . . .
Synchronizing user information . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-24
8-25
8-27
8-29
8-31
8-31
8-33
8-33
8-34
8-34
8-35
8-36
8-36
8-37
8-37
8-37
8-38
Using Host Collector in a secure environment . . . . . . . . . . . . . . . . A-1

Host Collector in a secure environment . . . . .
Data gathered with and without root access .
Data gathered with root access. . . . . . . .
Data gathered without root access . . . . .
Ports and services used . . . . . . . . . . . . . . . .
Ping (Initial discovery) . . . . . . . . . . . . . .
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. . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
A-2
A-2
A-2
A-3
A-3
A-3
A-4
A-4
A-4
A-4
A-4
A-4
A-4
A-5
A-5
A-5
Setting up configuration gathering operation using sudo . . . . . . . . B-1

Configuration gathering operation using sudo . . . . . . . . . . . . . . . . . . . . . . . .
Binary used for configuration gathering operation. . . . . . . . . . . . . . . . . . .
Commands used by Gather binary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements for account used for configuration gathering operation using
sudo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample content of sudoers file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
B-2
B-2
B-2
B-3
B-3
Glossary
Index
ix
x
Preface
This manual provides information for Hitachi Command Director (HCmD).
Notice: The use of the features and/or products described in this manual
and all other Hitachi Data Systems products is governed by the terms of
your agreements with Hitachi Data Systems.
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
xi
Intended audience
This document is intended for users of the Hitachi Command Director. You
should have the working knowledge of the following:
Hitachi Device Manager, Hitachi Tuning Manager, Hitachi Tiered Storage

Manager
Storage array 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 v7.1.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: https://hdssupport.hds.com/
Document revision level

Revision
Date
Description
MK-90HCMD001-00
November 2010
Initial Release.
MK-90HCMD001-01
December 2010
Revision 1, supersedes and replaces MK90HCMD001-00
MK-90HCMD001-02
May 2011
MK-90HCMD001-03
August 2011
Referenced documents
The following Hitachi referenced documents are available for download from
the Hitachi Data Systems Support Portal: https://hdssupport.hds.com/
xii
Hitachi Command Director Installation and Configuration guide, MK90HCMD002
Hitachi Command Director Release Notes, RN-90HCMD003
Hitachi Command Suite Software Documentation
Hitachi Command Suite Software Tuning Manager Documentation
Hitachi Command Suite Software Tiered Storage Manager

Documentation
Preface
Document conventions
This document uses the following typographic conventions:
Convention
Description
Bold
Indicates text on a window, other than the window title,

including menus, menu options, buttons, fields, and labels.
Example: Click OK.
Italic
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.
screen/code
Indicates text that is displayed on screen or entered by the

user. Example: # pairdisplay -g oradb
< > 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.
This document uses the following icons to draw attention to information:

Icon
Meaning
Description
Tip
Tips provide helpful information, guidelines, or

suggestions for performing tasks more effectively.
Note
Notes emphasize or supplement important points of the

main text.
Caution
Cautions indicate that failure to take a specified action

could result in damage to the software or hardware.
Conventions for storage capacity values

Physical and logical storage capacities of disk drives are calculated based on
the following values:
Logical Units : Block Size - 512 Bytes (Logical Disk Capacity)
1 KB (kilobyte) = 1,024 (210) bytes
1 TB (terabyte) = 1,0244 bytes
1 MB (megabyte) = 1,0242 bytes
1 PB (petabyte) = 1,0245 bytes
1 GB (gigabyte) = 1,0243 bytes
1 EB (exabyte) = 1,0246 bytes
Hard Disk Drives (HDDs) (Physical Disk Capacity)

1 KB = 1,000 bytes
1 TB = 1,0004 bytes
Preface
xiii
Hard Disk Drives (HDDs) (Physical Disk Capacity)

1 MB = 1,0002 bytes
1 PB = 1,0005 bytes
1 GB = 1,0003 bytes
1 EB = 1,0006 bytes
Accessing product documentation

The Hitachi Command Director user documentation is user documentation
is available on the Hitachi Data Systems Portal: https://
hdssupport.hds.com. Check this site for the current documentation,
including important updates that may have been made after the release of
the product.
Getting help
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 Portal for contact information: https://hdssupport.hds.com/.
Comments
Please send us your comments on this document to
doc.comments@hds.com. Include the document title, number, and revision,
and refer to specific sections and paragraphs whenever possible. All
comments become the property of Hitachi Data Systems Corporation.
Thank you!
xiv
Preface
1
Overview
This module describes how to start using Hitachi Command Director.
About Hitachi Command Director (HCmD)
Features
New in Command Director 7.1.1
Setup workflow
Logging in
Registering a license
Modifying your user profile
HCmD graphical user interface
Logging out
Overview
11
About Hitachi Command Director (HCmD)

Hitachi Command Director (HCmD) centralizes storage management
reporting across the Hitachi Storage Suite by providing business application
views of Hitachi storage infrastructures. HCmD 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.
HCmD correlates storage system configuration data from Hitachi Device
Manager (HDvM), performance data from Hitachi Tuning Manager (HTnM),
storage tier data from Hitachi Tiered Storage Manager (HTSM), and storage
utilization data from the hosts (that is, the customers application hosts).
The 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, HCmD 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.
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.
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.
12
The application SLO Investigation Unit that lets storage administrators

quickly identify potential cause of application SLO miss and SLO
violation.
Overview
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 gives
the users the ability to create their 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 analyzes your capacity and
application data used 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/host per tier or per pool
level to chargeback storage consumption to application/host owners.
Storage performance reports that quickly identifies busiest storage
resources across the data center.
Application tagging that provides the user with the flexibility to map
storage and application to their 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 auto creation of new applications when the
HCmD Host Collector feature performs agentless data gather from
remote hosts and storage systems at specific intervals or on demand.
New in Command Director 7.1.1

This section summarizes the new features in Command Director 7.1.1.
Support for secure sockets layer (SSL) version 3

You can configure Command Director to use SSL communications for
secure data transmission to and from the Command Director server.
Based on your Command Director system configuration, you can enable
SSL for the following communication routes:
Communication between the Command Director server and client
(Web UI)
Communication between the Command Director server and Device
Manager server
Communication between the Command Director server and Host
Collector server
For more information, see section, Configuring Command Director in
secure mode, in Chapter 3, Setting up HCmD server, of the Hitachi
Command Director Installation and Configuration Guide.
Overview
13
New HNAS reports added to the File Servers business view report
gallery.
The Protocol Op/s Trend report trends the total operations
resulting from reads or writes for all supported protocol traffic for the
past 24 hours on the HNAS node.
For more information about this report, see Protocol Op/s trend
report on page 6-11.
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.
For more information about this report, see Total throughput trend
New performance report added to the report gallery.

The Application SLO Conformance report in the Performance report
gallery lists all applications and its SLO conformance for the past 30
days.
For more information about this report, see Application SLO

conformance on page 7-10.
Enhanced platform support for host discovery

The HCmD host discovery feature can discover hosts on the IBM AIX
platform.
To know about the AIX versions supported by HCmD, see Appendix B,
Host Collector Support Matrix, in the Hitachi Command Director
Installation and Configuration Guide.
14
Overview
Setup workflow
After installing HCmD software, you must perform initial setup tasks to
configure HCmD for use. The following table summarizes the HCmD initial
setup workflow.
Setup task
Description
Log on to HCmD Web

UI
Initial logon to HCmD Web UI. This

procedure also includes:
Registering the license key
Specifying your email address
Set up email server

and notification
Section reference
Logging in on page 16
Registering a
license on page
1-7
Specifying email
address when
you first log in on
page 1-9
Set up the SMTP server to send
email notifications automatically for

Service Level Objective (SLO) alerts
and scheduled reports.
Set up to receive email notifications.
Configuring
email servers on
page 8-36
Specifying email
address when
you first log in on
page 1-9
Add storage system

data collectors
Configure storage system data collection

to enable HCmD to collect configuration
data from Hitachi Device Manager and
storage system performance data from
Hitachi Tuning Manager
Configuring Storage
System Collectors on
page 8-27
Add Host Collectors
Add/configure Host Collectors to

discover hosts in your network and
gather their file system and storage
utilization information.
Host discovery and

agentless data
gathering
mechanism on page
8-5
Set the option to

create applications
automatically or
create new
applications
manually.
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.
Creating applications
automatically on
page 3-9
or
manually on page 36
Perform manual
refresh to gather
storage system or
host data (optional)
Manual refresh gathers data before the

next scheduled collection and updates
reports with the latest information.
Manually refreshing
data on page 8-34
Overview
15
Setup task
Description
Section reference
Create custom
categories/tags
(optional)
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.
Managing custom
tags and tag
categories on page
3-15
Create new SLO

profiles or modify the
default SLO profile
(optional)
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.
Creating SLO profiles

on page 4-8
or
Modifying SLO
profiles on page 4-9
Create new
monitoring window
or modify the default
monitoring window
(optional)
HCmD provides a default monitoring

window with a set time period when the
SLO in the assigned SLO profile is
monitored.
You can create new monitoring windows
for different time periods and assign
them to applications, or modify the
default monitoring window.
Creating monitoring
windows on page 416
or
Modifying monitoring
windows on page 418
Manage unassigned
applications
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.
manually on page 36
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 3-22
or
Custom business
view on page 3-18
Logging in
To log on to Hitachi Command Director (HCmD), you require the following
information:
16
HCmD Web URL
User ID
Password
License key, if not already registered.
Overview
You can obtain this information from your administrator, who is responsible
for setting up your user account in the Device Manager.
To log on to HCmD:
1. In a Web browser, enter the Hitachi Command Director URL:
http://HCmD-server-address:port-number
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 25015.
2. Enter a user ID and password to log in.
3. Click Login.
The first time you log in, you are required to:
Specify a valid license key.

For more information, see Registering a license on page 1-7.
Enter your email address to receive Service Level Objective (SLO) alerts
and scheduled reports.
For more information, see Specifying email address when you first log in
on page 1-9.
When you log in to HCmD, the dashboard appears.
Registering a license
Register a license in any of the following cases:
You are accessing Hitachi Command Director (HCmD) for the first time
after installation. You can not access the Web UI without a license.
License is not registered.
License is expired.
To add licenses for additional capacity.
To register a license:
1. Enter the HCmD URL.
Note: If you are accessing HCmD for the first time after installation,
the License Configuration window appears. In this case, register the
license key, and then log in.
2. From the login window, click License.
The License Configuration window is displayed.
Overview
17
Figure 1-1 License configuration window

3. In the License Configuration window, specify the following License
Server Configuration information:
For License Server:
IP Address: The IP address or name of the server where the License
Server is installed.
Port: The license server port, default is 25035.
For Device Manager:
User ID: The Device Manager instance user account used by the
License Server. The user ID is always system (you cannot change
it).
Password: The password of the system user account in the Device
Manager instance used by the License Server.
HTTP/HTTPS (Web) Server Port: The Device Manager HTTP or HTTPS
port. The default port is 2001 for HTTP and 2443 for HTTPS.
SSL: Select the checkbox to enable secure sockets layer (SSL)
communication between the Command Director server and Device
Manager server.
Note: Before you select the SSL checkbox, make sure SSL is
enabled on the Device Manager server. For more information about
enabling SSL on the Device Manager server, see Hitachi Command
Suite Software Configuration Reference Guide.
4. Under Enter License, in the Key field, enter the HCmD license key.
18
Overview
5. When you have finished, click OK.

If you are registering the license key for the first time, after your license
information is validated, you are also prompted for your email address.

Your email 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 Email server before you can
specify your email address.
To specify your email address:
1. In the User Email dialog box, enter your email address in the Email field.
2. Click Save.
Modifying your user profile

In your user profile, you can change your name and email address.
Note: You can only manage your own user account. You cannot manage
other users, even if you are an Administrator.
To change your profile:
1. On the Menu bar, click the User ID (system).
2. In the Edit User Profile dialog box, modify the appropriate information.
Note that you cannot change your user ID, Role, and Description.
Name: Your first and last name.
Email: The email address used to send you alerts and reports.
HCmD graphical user interface

The HCmD graphical user interface (GUI) is organized into the following
areas.
Dashboard
When you log in to the Command Director, the initial screen is the
dashboard. You can launch reports that provides you with a quick access to
near, real-time status of your application and storage health of your
enterprise.
You can customize the dashboard to show only the reports you want.
Navigation pane
Use the Navigation pane on the left in the Resources and Administration
tabs to access business views and administration settings.
Overview
19
Content pane
When you select a folder, host, or application in a business view, a
dashboard of reports appear in the Content Pane.
The Content pane also includes a Reports drop-down list that allows you to
view available reports for the selected folder, host, or application.
Menu bar
Use the Menu bar to view and access the following information.
User ID: When you are logged in, your user ID appears to the right of User.
Online Help: To view the Hitachi Command Director online help, click Help.
License violation: The license violation notification appears when the
license expires or the data exceeds the licensed capacity.
Global tabs area

Access the main features of Hitachi Command Director in the Dashboard,
Resources, Reports, and Administration tabs.
Logging out
For security reasons, log out when you have finished using the Hitachi
Command Director.
To log out of HCmD, click Logout on the Menu bar.
110
Overview
2
Quick access to your application status
and storage health
This module introduces the HCmD dashboard, which includes reports that
determine the status or health of your applications, enterprise storage
components, and datastores in your enterprise.
About the Hitachi Command Director dashboard
Accessing the dashboard
Customizing the dashboard
Dashboard reports
Storage system performance detailed reports
Quick access to your application status and storage health

21
About the Hitachi Command Director dashboard

The Hitachi Command Director (HCmD) dashboard provides fast and simple
access to timely, accurate status of your applications and storage health
that allows you to start using Hitachi Command Director right away.
When you log on to the Command Director, the initial screen is the
dashboard.
The dashboard reports on your application health based on real-time
Service Level Objective (SLO) information, 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 HCmD dashboard displays a summary of real-time status information
for all applications that are currently monitored against defined storage
SLO, which is an operation guideline set for the implementation of service
negotiated under SLA (service level agreement).
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 Service Level Objectives and ensure that your storage
infrastructure provides adequate service to your applications and take
timely action when SLO violations occur.
SLO status
SLO violation
OK (green)
None. The application storage is below its threshold (not in

jeopardy) and working normally.
Borderline (yellow)
Warning. The application storage has exceeded its threshold and

is at a greater risk of failing.
Missed (red)
Error. The application storage has exceeded its threshold.

Immediate attention is required.
Unmonitored (gray)
Not applicable. This application has not been assigned any SLO,
and is therefore not monitored.
Hitachi enterprise storage health

The HCmD dashboard provides a real-time 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 HCmD dashboard also provides a quick view into the physical capacity
overview across all storage systems within your company. It helps you gain
insight into your storage capacity, identify unused capacity, and the ability
to track how storage is utilized.
22

HCmD complements the 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 allocate storage effectively and plan new
purchase of storage, if necessary.
Datastore health
The HCmD dashboard provides all information you need to monitor the
health of datastores in the discovered hosts such as Hitachi Highperformance NAS Platform (HNAS), Hyper-V servers, and VMware servers
in your environment.
The dashboard provides you with an insight into storage allocation, usage,
consumption details of each of these datastores. It also provides you with
the current snapshot of your enterprise wide Hitachi Dynamic Provisioning
(HDP) pool capacity and its usage.
Accessing the dashboard

When you log on to Hitachi Command Director, the dashboard appears.
At any time you want to return to the dashboard from any of the other
views, click the Dashboard tab.
Customizing the dashboard

You can customize the dashboard to show only the reports you want.
Hitachi Command Director saves the customizations you make so that the
dashboard displays your customized settings the next time you log in.
To customize the dashboard by using the report title bar:
Drag a report to another location to rearrange the dashboard.
Click the close button.

Reopen a closed report by clicking Dashboard Settings and selecting
the checkbox for the report you want to reopen.
To customize the dashboard to display only the reports you want to

view:
1. Click Dashboard Settings.
2. In the Dashboard options dialog box, unselect the checkbox against a
report name to not display this report. By default, all reports are
displayed on the dashboard.
3. Click OK.
To restore the default view:
1. Click Dashboard Settings.
2. In the Dashboard options dialog box, select to view all reports by clicking
each report name checkbox.

23
3. Click OK.
Dashboard reports
This module describes the various reports available on the Hitachi
Command Director dashboard.
Total number of applications with SLO misses on page 2-4
Response Time SLO status on page 2-5
IOPS SLO status on page 2-5
Storage system performance overview on page 2-6
Applications with most SLO misses in the past 24 hours on page 2-7
Storage system capacity overview on page 2-8
VMware datastore overview on page 2-9
Hyper-V file system overview on page 2-9
HDP capacity overview on page 2-10
Top 5 busiest HNAS nodes on page 2-11
HNAS capacity overview on page 2-12
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 any of the
following Service Level Objectives (SLOs):
Average Response Time
Total IOPS
The displayed number, if above 0 (zero) alerts you on applications that

require your attention.
Figure 2-1 Total number of applications with SLO misses
24

The 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.
To view more details about the applications with SLO misses, view the
Response Time SLO Status and IOPS SLO Status reports displayed on the
dashboard.
Response Time SLO status

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, on borderline, and in
conformation with the Response Time SLO. It also displays the number of
applications that are not currently monitored for this SLO.
Figure 2-2 Response Time SLO status

You can use the displayed information to identify the number of applications
with Response Time SLO misses or on borderline, and address potential
storage performance problems that may arise if these violations are left
unaddressed.
To view further details about the applications that missed the Response
Time SLO or on borderline, click the number link against the Missed field or
the Borderline field.
Review the application SLO details report, SLO details report on page 5-7.
IOPS SLO status

The IOPS SLO Status report on the Hitachi Command Director dashboard
displays the total I/O operations per second (IOPS) SLO status for all
applications in your enterprise. It provides a breakdown of overall

25
application SLO status indicating the number of applications that missed, on

borderline, and in conformance with the Total IOPS SLO. It also displays the
number of applications that are not currently monitored for this SLO.
Figure 2-3 IOPS SLO status

You can use the information displayed in the report to identify applications
with IOPS SLO misses or on borderline, and observe and track the storage
usage. You can use this information to track applications that frequently
violate the defined IOPS SLO threshold.
To view further details about the applications that missed the IOPS SLO or
on borderline, click the number link against the Missed field or the
Borderline field.
Review the application SLO details report, SLO details report on page 5-7.
Storage system performance overview

The Storage System Performance Overview report on the Hitachi Command
Director dashboard provides an overview of the performance of your
enterprise storage. You can use the information to analyze the overall health
of your storage systems.
26

Figure 2-4 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 all
storage systems 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 in your environment.
Total DTR: Total data transfer rate (MB/s) for all storage systems in your
environment.
Avg. Read Hit (in percentage): Average Read Hit % for 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 all storage systems based on cache size. A high write pending %
indicates storage performance issues.
To view further details about any metric on the report, click the number link
against each monitored metric.
Review these reports described in Storage system performance detailed
reports on page 2-12.
Applications with most SLO misses in the past 24 hours

The Application with Most SLO Misses report on the Hitachi Command
Director dashboard lists the top 10 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.

27
Figure 2-5 Applications with most SLO misses

The list is sorted in the ascending order by SLO Miss %. 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 hour. Visual indicators such as the red, yellow, and green
bars indicate the time period when the SLO violations occurred.
SLO Conformance: Indicates the percentage of time when the

application was in conformance with a monitored SLO in the past 24
hours.
Storage system capacity overview

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.
Figure 2-6 Storage system capacity overview

In the report, the Parity Group bar indicates the total usable capacity of disk
drives within the storage system.
28

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.
VMware datastore overview

The VMware Datastore Overview report on the Hitachi Command Director
dashboard provides a quick insight into the total capacity of all your VMware
datastores, available capacity, and used capacity in your enterprise.
The report provides a visual indication of the total available (free) physical
storage capacity of the datastores and total used by the applications.
Figure 2-7 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.
Hyper-V file system overview

The Hyper-V File System Overview report on the Hitachi Command Director
dashboard provides a quick insight into total capacity of all your Hyper-V
datastores and its usage in your enterprise.
The report provides a visual indication of the total available (free) physical
storage capacity of the Hyper-V datastores and total used by the
applications.

29
Figure 2-8 Hyper-V file system 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.
HDP capacity overview

The HDP Capacity Overview report on the Hitachi Command Director
dashboard displays the current snapshot of your enterprise wide HDP pool
capacity and its usage. The report differentiates the used pool and the
subscribed usage across all storage systems within your enterprise.
Figure 2-9 HDP capacity overview

In the report, the Pool bar indicates the volumes in your storage system
used for HDP pool creation. The DP Volumes bar indicates the carved out Vvols 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.
210

You can use the following information displayed alongside the chart to
compare Demand capacity against 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 the user has specified for use. This
value is derived by subtracting the Subscription allocated capacity value
from the Used allocated capacity value.
Free: Indicates the actual available pool capacity. This value is derived
by subtracting the Total Pool capacity from Total used capacity.
Top 5 busiest HNAS nodes

The Top 5 Busiest HNAS Nodes report on the Hitachi Command Director
dashboard lists the top 5 busy Hitachi Network Attached Storage (HNAS)
server nodes in your enterprise and the node details.
Figure 2-10 Top 5 busiest HNAS nodes

The 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.
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.
To view HNAS reports, see HNAS host reports on page 6-6.

211
HNAS capacity overview

The HNAS Capacity Overview report on the Hitachi Command Director
dashboard provides an overview of your Hitachi Network Attached Storage
(HNAS) capacity and usage to help you allocate storage effectively and plan
any new purchase of storage, if necessary.
Figure 2-11 HNAS capacity overview

The 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 the HNAS systems.
Clusters: Total number of HNAS clusters.
Nodes: Total number of HNAS nodes.
You can use the information displayed in the report to analyze the amount
of HNAS resources in your environment.
Storage system performance detailed reports

This module describes reports that are displayed when you access the
various storage performance metrics displayed in the Storage System
Performance Overview report on the Hitachi Command Director dashboard.
IOPS distribution by storage system on page 2-12
DTR distribution by Storage System on page 2-13
Average read hit % by storage system on page 2-14
Average write pending by storage system on page 2-15
Average response time by storage system on page 2-16
IOPS distribution by storage system

Total IOPS (I/0 per second) is an applications total I/O read and write
operations per second for all parity groups when reading from or writing to
a volume on a storage system.
212

Display the total IOPS Distribution By Storage System report by selecting

the Total IOPS link in the Storage System Performance Overview report
Figure 2-12 IOPS distribution by storage system

Hover over the various slices of the pie graph to view storage system
details.
DTR distribution by Storage System

Total Data Transfer Rate (DTR) is the total amount of data an application is
reading and writing (in MBytes per second) for all parity groups. You can
display the total data transfer rate by each Storage System for the past
hour.
Display the DTR Distribution By Storage System report by selecting the
Total DTR link in the Storage System Performance Overview report

213
Figure 2-13 DTR distribution by Storage System

Hover over the various slices of the pie graph to view the absolute DTR value
and storage system details.
Average read hit % by storage system

Read Hit Ratio is the percentage of total read operations that are cache hits
(i.e., read operations accessed from cache) for all parity groups. You can
display the total read hit ratio by each storage system for the past hour.
Display the Read Hit % By Storage System report by selecting the Avg
Read Hit link in the Storage System Performance Overview report
214

Figure 2-14 Read hit % by storage system

Hover over the various bars to view the absolute read hit % value and
storage system details.
Average write pending by storage system

Average write pending percentage is the percentage of data in the cache/
CLPR (Cache Logical Partition) that is to be written to the storage system
disk. You can display the average write pending percentage by each storage
system for the past hour.
Display the Write Pending % By Storage System report by selecting the Avg
Write Pending link in the Storage System Performance Overview report
Figure 2-15 Write pending % by storage system

215
Hover over the various bars to view the absolute CLPR % value and storage
system details.
Average response time by storage system

The average storage response time breakdown provides the weighted
average of the I/O response times for all the storage volumes used by the
application per storage system in the past hour.
Display the Avg Response Time by storage system report by selecting the
Avg Response Time link in the Storage System Performance Overview
report displayed on the dashboard.
Figure 2-16 Response time % by storage system

Hover over the various bars to view the absolute response time value and
storage system details.
216

3
Managing resources
This module describes how to manage your resources efficiently and
configure applications for HCmD usage.
About applications
Automatic creation of applications
Configuring applications
Managing custom tags and tag categories
About business views
Using business views
Creating a new business view
Business view modification restrictions
Managing business views
Deleting business views
Managing resources
31
About applications
An application in Hitachi Command Director (HCmD) is a representation of
an actual application running on a host. It can have the following structure:
1. Application: It represents groups of 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 HCmD agentless
host collector.
2. Sub-application: A subset of storage volumes that belong to an
application. By default, every application in Hitachi Command Director
has at least one sub-application which also has a default SLO profile and
default Monitoring window assigned to it. Multiple sub-applications can
be created for each application to define different SLO profiles against
different parts (or sub-applications) of the application. For example, an
Oracle database sub-application that requires better response time SLO
than the log sub-application that requires more serial read/write and
therefore requires less response time SLO for the same Oracle
application.
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 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 the sub-application so that you can
monitor the application performance against desired thresholds.
For every new application, a sub-application is created by default and is
assigned a default SLO profile. You can modify this default profile. You
can create new SLOs and assign to different sub-applications. SLOs can
only be assigned to applications through SLO profiles. When assigning
SLO profiles, you are also specifying monitoring windows that identify
when the application is monitored against the contained SLO.
32
SLO notifications: HCmD sends email 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.
Managing resources
Automatic creation of applications

After installation of HCmD and initial configuration of the Storage System
Collectors, HCmD creates applications automatically based on the autocreate option set by default to Logical Group. In this option, HCmD creates
applications from the Logical Group information obtained from the 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.
For more information about LUN Owner, see the glossary at the end of this
guide.
You can also choose not to create applications automatically.
The following table lists the various options you can choose to create
applications in HCmD:
Option
Description
Recommendation
Logical Group
This is the default configuration

set after fresh installation of the
product.
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.
Host
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.
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.
LUN Owner
This option creates applications

automatically based on the
volume owner group information
derived from your storage
system configuration.
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.
Managing resources
33
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 HCmD.
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.
The following table describes the impact when you switch to a different
option:
Switch to <autocreate option>
Impact
Logical Group
All applications - manually (user created) or automatically

created using any other option are deleted.
Host, LUN Owner, or

None
Only the automatically created applications are deleted.

Manually created applications are retained.
Configuring applications
This module describes how to configure applications for HCmD usage.
Application creation process flow on page 3-4
Application notes on page 3-5
Creating applications manually on page 3-6
Creating applications automatically on page 3-9
Managing unassigned applications on page 3-10
Modifying applications on page 3-11
Deleting applications on page 3-14
Application creation process flow

The following graphic illustrates the flow for creating applications in HCmD.
34
Managing resources
Application notes
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 the assigned hosts or Host Groups.
Same application can reside in multiple business views.
Managing resources
35
You cannot assign the following types of storage to applications:

CommandDevice
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
Creating applications manually

You can create a new application manually in a custom business view. When
you create an application in Hitachi Command Director (HCmD), you are
creating a representation of actual application running on a host.
Creating an application includes assigning tags to the application, specifying
users who will be notified when SLO violations occur, associating storage to
the application, and assigning a SLO profile to monitor this application.
Before you create a new application:
Choose to enable or disable automatic creation of applications.

Applications are created automatically when you set the auto-create
application option (Administration tab>System Settings &
Operations>General Settings) to Logical Group, LUN Owner, or Host.
When any of these options, except the Logical Group is set, you can
create applications manually.
If you only want to create applications manually, disable the automatic
creation of applications by selecting None in the General Settings
window.
Decide what storage you want to assign to the application.

You can assign storage from the discovered hosts or LUN Owner
information to the application. 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.
To configure Host Collectors, see these sections:
Viewing details about a specific Storage System Collector on page 833
Configuring Storage System Collectors on page 8-27
Review Application notes on page 3-5.
To create a new application:

1. From the Resources tab, select the custom business view where you
are creating the application.
2. Select the appropriate folder in your business view, and from the Action
drop-down menu, select Create Application.
The Manage Application window appears.
36
Managing resources
Figure 3-1 Manage application window

3. Specify the application name.
a. Under Application Details, in the Name text field, click Edit.
b. Enter the application name not exceeding 256 characters.
c. Click Done.
4. Assign tags to the application.
a. Under Application Details, against the Tags field, click Edit.
A list of tags you have created and predefined tags are listed. The
category name for each tag is listed alongside the tag name.
b. Click the check box against the tags you want to assign to your
application.
c. When you are done selecting the tags, click Done.
The tags you selected are displayed in the Tags list.
5. Specify the email addresses of the people whom you want to notify when
SLO violations occur for the application.
a. Under Notification, against the Notify Users field, click Edit.
b. Click the check box against the email addresses of the users you
want to notify.
c. When you are done selecting the email addresses, click Done.
Managing resources
37
The email will be sent to all email recipients added to the Notify list
for the application.
6. Assign storage to the application.
a. Under Assigned Storage, click Edit.
b. Click the Host or LUN Owner radio button.
For Host, review the host details 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.
For LUN Owner, select the LUN Owner and review the host groups
available for the storage system you want to assign to the
application. You can assign multiple LUN Owners to the application.
c. When you are done assigning storage, click Done.
The storage allocation you made to the current application is listed.
Review the list . If you decide to remove the storage allocation for
your application, click Delete in the row that lists your application.
7. Create a new sub-application and assign SLO.
a. Under Resource Mapping, click Add Sub-Application against
Assign SLO.
b.
c.
d.
e.
A new row is added for this component. For every new application, a
sub-application is created by default and is assigned a default SLO
profile. You cannot modify this default profile.
In the Sub-Application column, type the name for the subapplication not exceeding 256 characters.
From the SLO drop-down menu, select an SLO profile you want to
assign to this sub-application. By default, a default SLO Profile is
assigned to the Default sub-application and any new sub-applications
you create. Then, click Add SLO Profile.
From the Monitoring window drop-down menu, select a monitoring
window to specify when the application is monitored for SLO
compliance.
Assign sub-applications to storage volumes to monitor them
separately.
The Sub-Applications pane displays the storage allocations you have
made so far for the application and assigns the default subapplication initially to each storage allocation.
f.
If you want to monitor different parts of an application separately,

you can do so by creating new sub-applications and assigning them
to specific storage volumes. Select the relevant rows, click Edit on
top of this pane, and then select a different sub-application from the
Sub-Applications drop-down menu.
When you are done assigning SLO profiles and monitoring window,
click Done.
8. Click OK to save the information you have entered to create the

application.
9. View the application in the business view.
38
Managing resources
Creating applications automatically

HCmD provides you with an option to create applications automatically from
the Device Manager Logical Groups (default), hosts, or LUN owners in your
environment. A default sub-application is also automatically created which
is monitored by a default SLO profile.
Initially, no tag categories are assigned to the applications. You must modify
these applications to assign relevant tag categories. Once tags are
assigned, application will appear in various business views that uses the tag
categories assigned to the application.
For automatic creation of applications, the Host Collectors and Storage
System Collectors must be configured in HCmD. To configure the various
data collectors, see these modules:
Viewing details about a specific Storage System Collector on page 8-33
To create applications automatically:

1. Click the Administration tab.
2. Under System Settings & Operations, click General Settings.
The Auto Create Application window is displayed.
Figure 3-2 Auto create application

3. In the Auto Create Application window, select any of these options:
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.
None to disable automatic creation of applications.
Managing resources
39
4. When you have finished, click Save.

Caution: Switching to a different auto-create option deletes the autocreated applications set in the current option. Exercise caution when
you make the switch. To understand the impact of switching auto-create
options, see Impact of switching to a different auto-create option on
page 3-4.
5. You are cautioned about losing data regarding auto-created applications
when you select an option. Click Yes to confirm selection of the new
option.
6. Once the option has been selected, it is saved. In the information dialog,
click OK.
Applications that are created automatically appear in the All Applications
business view; the Logical Group applications appear in the All Applications
view as well as in the Logical Group business view.
Auto-created applications have the following naming convention:
Applications created from a discovered host: <host name>, where host

name is the name of the discovered host (server).
Example:
exchange.hds.com where host name is exchange.hds.com.
Applications created from a LUN Owner includes names of the Host

Groups (or HSDs) that are part of a specific LUN Owner:
<HSD1_HDS2.....HSD_n>
Applications created from the Device Manager Logical Group acquire the
Logical Group names as set in the Device Manager.
Managing unassigned applications

The All Applications view displays unassigned applications in these
conditions:
when applications are created automatically from the Device Manager

Logical Groups or during discovery of storage and hosts by HCmD.
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.
To manage unassigned applications:
1. From the Business Views drop-down menu, select the All Applications
view.
2. From the list of applications, select the application, right-click, and select
Manage <Application Name>.
3. In the Manage Application window, assign tags to the application.
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.
310
Managing resources
application.
The tags you have selected are displayed in the Tags list.
4. Click OK.
After the tags are assigned, the application will appear in various business
views of categories that includes these tags.
Modifying applications
For applications created automatically or manually in HCmD, you can
rename them, or modify user notification list for SLO violations, application
storage, or SLO assignment.
However, for the Logical Group applications created automatically by HCmD,
you can perform all modifications except renaming the application and
modifying storage assignments.
To modify an application:
1. From 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 tagged to a specific
category.
2. Select the application, right-click, and select Manage <Application
name>.
The Manage Application window appears.
Managing resources
311
3. Modify the application name.

a. Under Application Details, in the Name text field, click Edit.
b. Enter the application name not exceeding 256 characters.
c. Click Done.
4. Assign tags to a new application or modify tags of an existing
application.
A list of tags you have created and predefined tags are listed. The
category name for each tag is listed alongside the tag name.
application.
The tags you selected are displayed in the Tags list.
5. Specify new or modify existing email addresses of the people whom you
want to notify when SLO violations occur for the application.
a. Under Notification, against the Notify to Users field, click Edit.
312
Managing resources
b. Click the check box against the email addresses of the users you
want to notify.
c. When you are done selecting the email addresses, click Done.
The email will be sent to all email recipients added to the Notify list
for the application.
6. Assign new storage to an application or modify an existing storage
assignment.
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
assignment you cannot modify.
a. Under Assigned Storage, click Edit.
b. Click the Host or LUN Owner radio button.
For Host, review the host details 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.
For LUN Owner, select the LUN Owner and review the host groups
available for the storage system you want to assign to the
application. You can assign multiple LUN Owners to the application.
c. When you are done assigning storage, click Done.
The storage allocation you made to the current application is listed.
Review the list . If you decide to remove the storage allocation for
your application, click Delete in the row that lists your application.
7. Create a new sub-application and assign SLO, or modify an existing subapplication or SLO assignment.
a. Under Resource Mapping, click Add Sub-application against
Assign SLO.
b.
c.
d.
e.
A new row is added for this component. For every new application, a
sub-application is created by default and is assigned a default SLO
profile. You cannot modify or delete this default profile.
In the Sub-application column, type the name for the new subapplication not exceeding 256 characters. To modify the subapplication information, click the Edit icon. To delete the subapplication, click the Delete icon.
From the SLO drop-down menu, select an SLO profile you want to
assign to this sub-application. By default, a default SLO Profile is
assigned to the Default sub-application and any new sub-applications
you create. Then, click Add SLO Profile.
From the Monitoring window drop-down menu, select a monitoring
window to specify when the application is monitored for SLO
compliance.
Assign sub-applications to storage volumes to monitor them
separately.
Managing resources
313
The Sub-Applications pane below displays the storage allocations you

have made so far and the default sub-application that is initially
assigned to each storage allocation.
f.
If you want to monitor different parts of an application separately,

you can do so by creating new sub-applications and assigning them
to specific storage volumes. Select the relevant rows, click Edit on
top of this pane, and then select a different sub-application from the
Sub-Applications drop-down menu.
When you are done assigning SLO profiles and monitoring window,
click Done.
8. Click OK to modify the application.
Deleting applications
In HCmD, you can delete applications:
manually from a custom business or an All Applications view.

When you delete an application from a business view, you delete it from
HCmD. However, the historical data of this application will be preserved
for reporting purposes.
automatically when you switch to a different auto-create option (in

Administration tab>System Settings & Operations>General
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.
To manually delete an application:

1. From the Resources tab, select the business view where you are
deleting applications.
2. Select the application you want to delete, right-click, and select Delete
<Application Name>.
3. In the Confirmation dialog box, verify that you are deleting the correct
application, and then click Yes.
The application is successfully deleted from this business view and all other
business views that includes this application.
314
Managing resources
Managing custom tags and tag categories

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 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.
When you create a new tag category a new custom business view is created
automatically.
After you create custom tag categories you can modify them to adapt to
changes in your organization resulting from any organization restructuring.
To manage categories and tags:
2. Under Resource Organization, click Tag Management.
The Tag Management window appears that displays the predefined tag
categories - Geography and Function.
Figure 3-3 Tag management

3. To view tags under a predefined tag category, click the + icon next to
the tag category.
4. To add a new tag category, click Add Tag Category.
Note: When you create a new tag category a new business view with
the name you specify for the tag category is created automatically and
available in the Business Views drop-down menu in the Resources tab.
5. Enter the name of the new tag category. The name should not exceed
32 characters.
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 should not exceed 32 characters.
8. To delete a tag category or tag, click the Delete Category icon next to
the tag category/tag name.
9. If you delete a tag category, a Confirmation dialog box appears
prompting you to confirm your action. Verify you want to delete the
selected category, and click Yes.
Note: Deleting a tag category deletes tags and applications
associated with this tag category.
Managing resources
315
10.In the Resources tab, review the business view that is created
automatically for the new tag category you have created.
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 Business Views drop-down menu 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 tree-like hierarchy.
HCmD provides predefined tag categories that enables 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,
the tag USA will indicate that the application is located in the USA. The 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, and All
Applications view that are available from the Business View list. These are
read-only views that cannot be created, deleted, or modified.
Hosts business view

Displays the hosts organized by the operating system.
File Servers business view

Displays pertinent information about the discovered HNAS (Hitachi
Network Attached Storage) servers.
316
All Applications business view
Managing resources
Lists every application that is auto-generated, custom, or imported into

HCmD. You can use this view to find any application without navigating
a business view hierarchy.
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.
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.
Displaying business views on page 3-17
Custom business view on page 3-18
Logical Group view on page 3-18
Hosts view on page 3-19
File Servers view on page 3-20
All Applications view on page 3-22
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.
HCmD displays the following business views:
Predefined, custom business views:

Geography
Function
Geography-Function
Function-Geography
Hosts view
File Servers view
All Applications view
Logical Group view
To display a business view:

1. Click the Resources tab.
2. Select a business view from the drop-down menu.
A list of available business views is displayed.
Managing resources
317
Figure 3-4 Business views
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 dropdown menu 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.
Untagged applications
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.
Logical Group view

The Logical Group view allows you to view the Logical Groups from the
Device Manager without having to create them in HCmD. Each Logical
Group contains mapping information to the volumes on the storage system.
318
Managing resources
HCmD 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 HCmD and assign
storage to it.
You can access the Logical Group view from the Business Views drop-down
menu 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 >
General Settings.
The following is an example of folders in a Logical Group view:
Figure 3-5 Logical Group view

Note the following:
Imported folders represent Device Manager Logical Groups and you

cannot modify them in HCmD.
Imported folders are synchronized with Device Manager Logical Groups

at every data refresh and after initial import of this data when you
choose to automatically create applications based on Device Manager
Logical Groups.
Logical Groups without storage association are not imported and

therefore does not appear in the Logical Group Business View in HCmD.
Hosts view
The Hosts view allows you to view the hosts successfully discovered by the
Host Collectors.
Note the Host Group information is not included in the Hosts view
information.
Managing resources
319
You can access the Hosts view from the Business Views drop-down menu in
the Resources tab.
The following is an example of folders in a Hosts view:
Figure 3-6 Hosts view

HCmD organizes the hosts by OS as shown above, with the hosts organized
in the following folders:
Linux
Windows
Solaris
HP-UX
AIX
VMware
ESX
Data Stores
Hyper-V
All VMware host instances are listed under their respective OS folder. ESX
servers and Data Stores servers are listed under the VMware folder.
When a new host is discovered, the Hosts view displays the new host. After
every data refresh, 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), HCmD will not display such devices.
File Servers view

The File Servers view allows you to view pertinent information about the
discovered HNAS (Hitachi Network Attached Storage) servers, file systems,
and storage pools.
320
Managing resources
You can access the File Servers view from the Business Views drop-down
menu in the Resources tab.
The following is an example of the HNAS tree in the File Servers view:
Figure 3-7 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
File Systems
Pools
For a single HNAS node, the following folders are displayed:
File Systems
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.
About HNAS in HCmD

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.
Managing resources
321
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.
All Applications view

The All Applications view is a list of every application that is defined or
imported in the 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.
You can access the All Applications view from the Business Views drop-down
menu in the Resources tab.
The following is an example of a list of applications in an All Applications
view:
Figure 3-8 All applications view
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
menu.
You can create a new business view based on any of the following:
322
Managing resources
Custom tag categories

You must create custom tags and tag categories first before you can use
them to create a new custom business view. When you create a custom
tag category a new custom business view is created automatically.
To create custom tags and tag categories, see Managing custom tags
and tag categories on page 3-15.
Predefined tag categories

HCmD provides the following predefined custom business views derived
from predefined tag categories:
Geography
Function
Geography-Function
Function-Geography
To create a new business view:

2. Next to the Business Views drop-down menu, from the Action drop-down
menu, select New Business View.
The New Business View window is displayed.
Figure 3-9 New business view

3. In the Business View Name field, enter the name for your business view.
4. To select a category for your business view, move it in to the Hierarchical
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.
Managing resources
323
To apply a display order, move the category either up or down in the

Hierarchical Categories list. Click the appropriate arrow on the right side
of this list to set the display order.
6. Click OK to save your business view.
7. Review the new business view by selecting the new custom business
view from the Business Views drop-down menu.
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, and 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 the HCmD
application names.
For the built-in business views such as the Hosts view, File Servers view,
and All Applications view, you cannot create or modify them.
Managing business views

You can modify custom business views only. You can rename this 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 3-24.
To modify a custom business view:
1. From the Resources tab, select the business view you are modifying.
2. Right-click in the business view and select Manage <Business View
name>.
3. Perform the appropriate modification task in the Manage Business View
window that is displayed.
a. To modify categories, move the required category between the
Categories and Hierarchical Categories lists by selecting the category
and clicking an arrow.
b. To rename, enter the new name of the business view in the Business
View Name text field.
c. Click OK to save your modifications.
4. Review the business view modifications you have made on the Business
Views drop-down menu.
Deleting business views

You can delete any business view that is custom, preconfigured, or Logical
Group. However, you cannot delete the last business view in the system.
324
Managing resources
To delete a business view:

1. From the Resources tab, select the business view you are deleting.
2. Right-click in the business view and select Delete <Business View
name>.
3. In the Confirmation dialog box, verify that the business view you are
deleting is correct, then click Yes.
Managing resources
325
326
Managing resources
4
Monitoring applications
This module describes how to monitor applications using storage Service
Level Objectives (SLOs).
SLO overview
Supported SLO types
Monitoring storage system health thresholds
Managing SLO profiles
SLO Investigation Unit
Managing monitoring windows
41
SLO overview
A Service Level Objective (SLO) is a performance or configuration metric of
storage volume or other storage system element with defined threshold
values. 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 two categories of SLOs:
Application SLO
Type of SLO that is measured on volumes that are assigned to the
application. Two metrics are supported - Response Time and IOPS. You
can create multiple SLOs for a given SLO type by assigning different
threshold values.
Storage system and Host SLOs

SLOs defined on predefined set of storage system elements such as port,
HDP, cache that help to monitor the overall storage environment. These
SLOs are global in nature and therefore take only a single set of
threshold values.
An application that exceeds its borderline SLO threshold has a Borderline

violation status. An application that exceeds its missed SLO threshold has a
Missed violation status. An application that is below its borderline SLO
threshold does not have a violation and has an OK status.
To ensure that the storage assigned to an application meets the
applications SLOs, the application must be assigned an SLO profile during
a monitoring window (time period).
Figure 4-1 Monitoring applications diagram
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 service level of an application.
When you assign an SLO profile to an application, you are configuring HCmD
to monitor that application against all the SLOs contained in the SLO profile.
42
Email alerts
You can send email alerts when borderline or missed SLO violations occur
during their monitoring window. SLO violation alerts can be sent to anyone
and are not limited to HCmD user accounts.
Monitoring window
A monitoring window is the set of time periods when the Service Level
Objectives (SLOs) in the assigned SLO Profile are monitored. A monitoring
window can contain multiple time periods and reflects your organizations
activity schedule.
Supported SLO types

The Command Director supports two categories of SLO types:
Application SLO types
Storage System and Host SLO Types
Supported SLO type indicates the ability to monitor a specific type of

metric.
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:
Average Storage Response Time: The Average Storage Response Time

SLO 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 applications average volume
response time, each volume response time is weighted according to the
volumes 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: The Total IOPS SLO monitors an applications total I/O
operations per second when reading from a volume or writing to a
volume.
Storage system and host SLO types

Storage system and host SLOs are global in nature and therefore take only
a single set of threshold values.
The set of storage system and host SLO types are as follows:
43
Cache Write Pending %: Monitors the percentage of data in the CLPR

(Cache Logical Partition) that is to be written to storage system disk.
DP Pool Over Provisioning Ratio: This SLO monitors the over-provisioned

ratio for each DP Pool in the system. The over-provisioned ratio is
calculated as:
(Total DP pool provisioned capacity) /
capacity of DP pool)
(Total physical
DP Pool Risk Ratio: Monitors the DP pool risk ratio for each DP pool in
the system. The DP Pool risk ratio is calculated as:
(Total DP pool provisioned capacity) - (Total consumed
capacity) / (Total free capacity of DP Pool)
DP Pool Used %: Monitors the total consumed capacity of each DP pool.

The total consumed capacity from each DP pool is calculated by
summing the Consumed Capacity attribute of each DP-VOL (that is, the
volumes carved out of the DP pool).
Host File System Used %: Monitors the percentage of the used capacity
in the host file system.
Parity Group Busy %: Monitors the storage systems parity group read
and write activity.
Port Busy %: Monitors the storage systems port microprocessor work

load.
Monitoring storage system health thresholds

This module describes storage system health thresholds and related
management tasks.
Storage system health thresholds on page 4-4
Modifying storage system health thresholds on page 4-5
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 is evaluated by measuring array group
and port microprocessor utilization, and 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, the Hitachi Command
Director storage system health monitoring can proactively alert you to these
problems.
44
Modifying storage system health thresholds

You can change the default storage system health thresholds for array
groups and port microprocessors. However, it is not recommended.
To modify the storage system health thresholds:
2. Under SLO Monitoring, click Storage System and Host SLO.
In the Content pane the threshold settings for the various storage
system and host SLOs are displayed.
Figure 4-2 Storage system health thresholds

3. Modify the appropriate thresholds for warning and error violations.
Port Busy %: Monitors the storage systems port microprocessor
work load.
Hitachi recommends that you keep the port microprocessor busy
percentage under 50 percent.
Parity Group Busy %: Monitors the storage systems parity group
read and write activity.
Hitachi recommends that you keep the parity group busy percentage
under 70 percent.
Cache Write Pending %: Monitors the percentage of data in the CLPR
(Cache Logical Partition) that is to be written to storage system disk.
DP Pool Used %: Monitors the total consumed capacity of each DP
pool. The total consumed capacity from each DP pool is calculated by
summing the Consumed Capacity attribute of each DP-VOL (that is,
the volumes carved out of the DP pool).
DP Pool Over Provisioning Ratio: This SLO monitors the overprovisioned ratio for each DP Pool in the system. The overprovisioned ratio is calculated as:
45
(Total DP pool provisioned capacity) /

capacity of DP pool)
(Total physical
DP Pool Risk Ratio: Monitors the DP pool risk ratio for each DP pool
in the system. The DP Pool risk ratio is calculated as:
(Total DP pool provisioned capacity) - (Total consumed
capacity) / (Total free capacity)
Host File System Used %: Monitors the percentage of the used
capacity in the host file system.
Managing SLO profiles

This module describes SLO profiles and SLO profile management tasks.
About SLO profiles on page 4-6
Viewing SLO profiles on page 4-7
Creating SLO profiles on page 4-8
Modifying SLO profiles on page 4-9
Removing SLO types on page 4-10
Deleting SLO profiles on page 4-11
About 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 an SLO profile, the performance of its storage is monitored to
ensure compliance with every SLO thresholds (borderline and missed)
contained in its profile.
HCmD provides a default SLO profile that has only the Average Storage
Response Time SLO enabled. You can assign this profile to any application
to start monitoring the application.
When you assign an SLO profile to an application, you are configuring the
Hitachi Command Director to monitor that application against all the SLOs
contained in its SLO profile. Note that SLO profiles must be created before
they can be assigned to applications.
Note:
An SLO profile cannot contain more than one SLO of the same type.
SLO profile management notes

When managing SLO profiles, note the following:
46
SLO profiles must have unique names.
An SLO profile cannot contain SLOs of the same type. For example, it
cannot have two Average Response Time SLOs.
SLOs can only be assigned to applications through SLO profiles.
When assigning SLO profiles, you are also specifying monitoring

windows that identify when the application is monitored against the
contained SLO.
Viewing SLO profiles

You can view every SLO profile and its information. You can also view
detailed information for each SLO profile, and which applications it is
assigned to.
To view SLO summary information:
2. Under SLO Monitoring, click SLO Profiles.
The SLO Profiles window is displayed.
Figure 4-3 SLO profiles

This window displays the following information:
Name: The name of the SLO Profile.
Application Assignment(s): The number of applications assigned to
the SLO profile.
Contained SLO(s): The number of SLO types assigned to the SLO
profile.
Action icon (
): This icon lets you edit the selected SLO profile.
3. View detailed SLO profile information. Select the SLO profile whose
details you want to view.
The SLO types assigned to the profile are displayed in the Detail tab and
includes the following information:
Type: The SLOs associated with the profile. For example, Average
Storage Response Time.
Borderline Threshold: The threshold that triggers a warning violation
when the Warning threshold exceeds the set value.
Miss Threshold: The threshold that triggers a miss violation when the
error threshold exceeds the set value.
4. View assigned applications. To view which application the SLO profiles
are assigned to, select the SLO profile whose assignments you want to
view. Then, click the Used By tab.
47
The SLO Profile Used By window appears displaying the following

information:
Application: The name of the application associated with the SLO
profile.
Monitoring Window: The name of the monitoring window during
which the SLO profile is monitoring the application. Multiple
schedules (time periods) can be defined in the same monitoring
window.
Alerts: The people who receive alerts when a violation occurs during
the monitoring window.
Creating SLO profiles

After creating Service Level Objective (SLO) profiles, you can assign them
to applications.
To create a new SLO profile:
Available SLO profiles appear. After initial installation, a default profile is
created with default SLO settings, and this profile is assigned
automatically to an application when it is created. You can not modify
the default profile.
3. Click New.
Figure 4-4 New SLO profile

4. Specify the appropriate information for the new SLO profile.
a. In the Name field, enter the new name of the SLO profile.
b. To add SLO types to the profile, click the check box against the
monitored metric and specify the threshold values for each metric:
48
Monitored Metric: Available metrics are AVG Storage Response

Time and Total IOPS.
Borderline: The threshold that triggers a borderline violation.
Miss: The threshold that triggers a miss violation.
c. Specify the notification criteria that allows you to set the number of
SLO misses within a specific period of time before a borderline or
miss violation is triggered.
In the Notify on field, set the option to receive notifications on Every
Miss of the SLO or enter the notification criteria by specifying the
number of misses and selecting the time.
The allowable ranges for number of SLO misses within a specific time
are:
1 miss in 5 mins
1-2 misses in 10 mins
For example, if you set notification for every 2 SLO misses within 15
mins then any application using this SLO profile will trigger an email
to registered email addresses.
Modifying SLO profiles

When your best-practice Service Level Objective (SLO) monitoring
thresholds change or when you want to change a specific type of monitoring
metric (or SLO type), you can update your SLO profiles.
You can modify all information except the profile name in the default SLO
profile.
To modify SLO profiles:
Available SLO profiles appear.
3. Click to select the SLO profile and then click the Edit icon ( ) next to
the SLO profile you are modifying. The Edit SLO Profile window appears.
49
Figure 4-5 Edit SLO profile

4. Perform the necessary changes. For example, you can change the name
of the SLO profile or the monitoring metric, or set the threshold levels.
a. To change the name, in the Name field, enter the new name of the
SLO profile.
b. To add SLO types to the profile, click the check box against the
monitored metric and specify the threshold values for each metric:
Monitored Metric: Available metrics are Avg Storage Response
Time and Total IOPS.
Borderline: The threshold that triggers a borderline violation.
Miss: The threshold that triggers a miss violation.
c. Modify the notification criteria that allows you to set the number of
SLO misses within a specific period of time before a borderline or
missed violation is triggered.
5. Click OK.
Removing SLO types

When you remove the SLO profile, you are only removing the SLO type
associated with the profile.
To remove SLO types:
Available SLO profiles appear.
3. Select the check box next to the SLO type you are removing, and click
Remove.
410
Deleting SLO profiles

You can permanently delete Service Level Objective (SLO) profiles that are
not in use. When you delete the SLO profile, you also remove all
associations of this profile with an application.
You cannot delete the default SLO profile.
To delete SLO profiles:
Every SLO profile appears.
3. Select the check box next to the SLO profile that you are deleting, and
click Delete.
4.
In the Confirmation dialog box, click Yes.
SLO Investigation Unit

This module describes the Service Level Objective Investigation Unit
(SLOIU), accessing the SLOIU, and interpreting the data from the SLOIU.
About SLO Investigation Unit on page 4-11
Accessing the SLO Investigation Unit on page 4-14
About SLO Investigation Unit

The Service Level Objective Investigation Unit enables you to understand at
a glance any problems with your application or sub-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: If the application/sub-application has been recently created, you
may not have a sufficient amount of data to investigate.
The SLO Investigation Unit includes a time slider, a summary pane, and four
tabular reports that provide in depth information about a specific
application/sub-application:
Data Time time slider on page 4-11
Summary pane on page 4-12
IOPS Distribution: Application vs. Storage System report on page 4-12
DTR Distribution: Application vs. Storage System report on page 4-12
Connected Ports on page 4-13
Volume List on page 4-13
Data Time time slider

The time slider shows the current data point and lets you select any
previous data point to analyze the sub-application at that point in time.
411
Summary pane
Displays a summary about the SLO miss for the sub-application, and for the
selected time period.
Name: The name of the application/sub-application.
Created: The date/time when the application was created.
Total Storage: The total storage capacity.
#Volumes: The number of volumes mapped to the sub-application.
SLO Status: Displays if the SLO status has been met for the investigation
time.
Avg Response Time: The response time for the sub-application.
Total IOPS: Total IOPS of the sub-application.
Tags: Custom tags associated with the application.
Notify: Specifies users who will be notified.
IOPS Distribution: Application vs. Storage System report

This 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.
The report includes the following information:
Storage System: The model and serial number of the storage system.
All Ports IOPS: Total IOPS for all the ports in the storage system.
App Ports IOPS: Total IOPS for the storage system ports the application
is using.
App IOPS: Total IOPS for all the volumes mapped to the sub-application.
App vs. All Ports: The ratio of sub-application IOPS against the storage
system IOPS.
App vs. App Ports: The ratio of sub-application IOPS to application port
IOPS.
DTR Distribution: Application vs. Storage System report

This report enables you to quickly compare the data transfer rate (DTR) and
its throughput performance generated by 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.
412
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 mapped to the sub-application.
App vs. All Ports: The ratio of sub-application DTR against the storage
system DTR.
App vs. App Ports: The ratio of sub-application DTR to application port
DTR.
Connected Ports
This 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
sub-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/violation. If there are
multiple ports you can also determine if there are any workload imbalance
among ports, for example one port is much more busier than others.
Port: The storage system port name.
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.
Volume List
This report lists a set of volumes associated with the sub-application.
Looking at the performance of these volumes may indicate a potential cause
of the sub-application SLO miss.
Use this report to quickly identify the volumes that are causing the SLO
miss/violation. You can also check the Storage Tier that includes this to
determine if the tier might be the cause for SLO violation. For example, if
the volume is on a SATA tier which is a lower storage tier and it is not
performing well, you may want to consider promoting this volume to a
higher storage tier.
Volume: The volume name.
Capacity: The capacity of the volume.
Parity Group: The Parity Group of the volume.
413
Total IOPS: Total IOPS of the volume.
Avg Response Time: The response time of the volume.
Read IOPS: Read IOPS of the volume.
Read Response Time: The read response of the volume.
Write IOPS: The write IOPS of the volume.
Write Response Time: The write response of the volume.
Read Hit: The read hit % of the volume.
Storage Tier: The storage tier of the volume.
Accessing the SLO Investigation Unit

The Service Level Objective Investigation Unit enables you to quickly
identify the potential cause of Application SLO violation by looking at key
storage components performance used by the application/sub-application.
You can launch the SLO Investigation Unit from the Dashboard or Resources
tab.
To access the SLO Investigation Unit from the Dashboard:
1. Click the Dashboard tab.
2. Click any of the SLO missed or borderline links to display the SLO
Details report.
3. In the SLO Details report, click on the Sub-application (link) of interest
to display the SLO Investigation Unit.
To access the SLO Investigation Unit from 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 Details report and click the Sub-application (link) of
interest to display the SLO Investigation Unit.
Managing monitoring windows

This module describes monitoring windows and its management tasks.
414
About monitoring windows on page 4-15
Viewing monitoring windows on page 4-15
Creating monitoring windows on page 4-16
Modifying monitoring windows on page 4-18
Deleting monitoring windows on page 4-19
About monitoring windows

Monitoring windows specify the time periods when the application SLOs are
monitored. A monitoring window can contain multiple time periods and
reflects your organizations 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
this application is not running and therefore does not require a monitoring
window.
HCmD provides a default monitoring with a set schedule you can use to set
the monitoring window for a defined SLO profile. The default monitoring
window is set for a 24x7 time window.
Monitoring windows can have multiple schedules (time periods) when they
run. For example, a monitoring window can have two schedules: one for the
first week in a month, and one for the last week in a month.
Monitoring windows can be defined for the following instances:
Consecutive hours within 24-hour time window.

For example 10:00 - 12:00, 22:00 - 04:00.
Consecutive hours within a specific day.

For example 22:00 Saturday - 04:00 Sunday.
Consecutive hours for specific days of a week.

For example 22:00 - 00:00 for the last 3 days of a week.
Consecutive hours for a specific day of a month.

For example 22:00 - 00:00 for the last day of month.
Consecutive hours for a specific month of a year.

For example 22:00 - 00:00 for the last month of a year.
Monitoring window management notes
Monitoring window names must be unique. The names can be changed

as long as they remain unique.
Monitoring windows can only be removed when they are not used by an
SLO profile.
Multiple schedules can be assigned to the same monitoring window.
Viewing monitoring windows

You can view every monitoring window and its information. You can also
view detailed information for each monitoring window, and which SLO
profiles it is assigned to.
After initial installation, a default monitoring window defined for 24-hour
time window is created, and is assigned to the sub-application when you
create a new application.
To view a monitoring window and its information:
415
2. Under SLO Monitoring, click Monitoring Windows.

General information about every monitoring window appears, organized
as follows:
Name: The name of the monitoring window.
Description: The purpose of the monitoring window.
Monitored Application(s): The number of applications that use the
monitoring window.
Figure 4-6 Monitoring Windows

3. View detailed information about the monitoring window. Select the
monitoring window whose details you want to view.
The schedules (time periods) assigned to the monitoring window appear,
organized as follows:
From: When the application starts being monitored for SLO
compliance.
To: When the application stops being monitored for SLO compliance.
Type: The monitoring frequency (daily, weekly, monthly, or yearly).
Value: The day and month associated with the monitoring frequency
(type).
4. View which SLO profiles the monitoring windows are assigned to. Select
the monitoring window whose associations you want to view, and click
the Used By tab.
The associations for the monitoring window are organized as follows:
Application: The name of the application being monitored.
SLO Profile: The name of the profile used for monitoring.
Alerts: People who receive alerts when an SLO violation occurs
during its monitoring window.
5. At any time you want to go back to the main monitoring window from
any of the detailed views, click Back.
Creating monitoring windows

When you create a monitoring window, you can assign multiple schedules
(time periods) to it. For example, a monitoring window can have two
schedules: one for the first week in a month, and one for the last week in a
month.
416
HCmD provides a default monitoring window scheduled to monitor the

application 24X7.
To create a new monitoring window:
3. In the displayed Monitoring Windows window, click New.
The New Monitoring Window dialog box appears.
Figure 4-7 New monitoring window

4. In the Name field, type the name of the new monitoring window.
Note: Monitoring window names must be unique. The names can be
changed as long as they remain unique.
5. In the Description field, type a description so that you can recognize
what the monitoring window is used for.
6. Click Add Schedule.
7. From the From drop-down menu, select when the schedule begins.
8. From the To drop-down menu, select when the schedule ends.
9. Under Recurrence Type, select the monitoring frequency (daily, weekly,
monthly, or yearly).
If you select Weekly, Monthly, or Yearly, specify when you want to
monitor the application in that time period.
417
10.Click OK.
You can add multiple schedules to the same monitoring window.
11.To remove schedules, select the check box next to the schedule you are
removing, and click Remove.
Note that you are not deleting the monitoring window; you are only
removing the time period that has been assigned.
12.When you have finished, click OK.
Modifying monitoring windows

You can change monitoring window details, and add or remove the
schedules (time periods) assigned to the monitoring window.
You can modify all information except the monitoring window name in the
default monitoring window.
To modify monitoring windows:
The default monitoring window and those you have created new are
displayed.
3. Click the Edit icon (
modifying.
) next to the monitoring window you are
4. In the Edit Monitoring Window that appears, perform the necessary

changes. For example, change the name or description of the monitoring
window, and add or delete schedules (time periods).
a. Change the name or description.
To change the name of the monitoring window, in the Name field,
enter the new name.
To change the description of the monitoring window, in the
Description field, enter the new description so that you can recognize
what the updated monitoring window is used for.
b. To add schedules, click Add Schedule.
On the From drop-down menu, select when the schedule begins. On
the To drop-down menu, select when the schedule ends.
c. Under Recurrence, select the monitoring frequency (daily, weekly,
monthly, or yearly).
If you select Weekly, Monthly, or Yearly, specify when you want to
monitor the application in that time period.
d. Click Apply. You can add multiple schedules to the same monitoring
window.
e. To remove schedules, select the check box next to the monitoring
window you are removing, and click Remove.
Note that you are not deleting the monitoring window; you are only
removing the time period that has been assigned.
418
Deleting monitoring windows

Monitoring windows can only be deleted when they are not being used to
monitor applications, or not used by an SLO profile.
To delete monitoring windows:
The default monitoring window and those you have created new are
displayed.
3. Select the check box next to the monitoring window you are deleting,
and click Delete.
4. In the Confirmation dialog box, click Yes.
419
420
5
Reporting on applications
This module provides information about application reports available in
HCmD.
Application reports
Accessing application reports
Application summary report
SLO status report
Storage system performance report
Storage allocation report
File System utilization report
SLO details report
Capacity allocation trend report
Application response time trend report
IO utilization trend report
Storage allocation information
Storage System and host SLOs reports
Total number of applications in a folder
51
52
IOPS SLO status report
Application list
Application reports
Application reports are available for a selected application or for all
applications within a folder (folder level) in the business view.
HCmD provides you with a set of predefined standard reports for
applications or application folder. You can modify the report definitions of
standard 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:
Report name
Description
Summary
Provides a quick overview of the application SLO

status and associated tags, if any.
See Application summary report on page 5-5.
SLO Status
Displays the application SLO status for the past 24

hours.
See SLO status report on page 5-5.
SLO Details
Lists every storage Service Level Objective (SLO)

monitored over a period of time for the selected
application.
See SLO details report on page 5-7.
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 5-10.
Total applications
Indicates the total number of applications in a

selected folder.
See Application list on page 5-22.
IOPS SLO Status
Displays the total IO operations per second SLO

status for all applications in the selected folder.
See IOPS SLO status report on page 5-21.
Response Time SLO

status
Displays the response time SLO status for all

applications in the selected folder.
See Response Time SLO status on page 5-21.
Application List
A list of top 20 applications in a selected folder that

violated the set SLO threshold in the past 24 hours.
See Application list on page 5-22.
Available for
application,
application folder,
or both
Application
Application folder
53
Report name
Description
Available for
application,
application folder,
or both
Storage System & Host

SLOs
Both
Set of reports that track storage system and host
resource utilization.
See Storage system & host SLOs report on page 5-17.
Storage System
Performance
Displays the current storage performance metrics.

See Storage system performance report on page 5-6.
Storage Allocation
Provides the current snapshot of your storage

allocation.
See Storage allocation report on page 5-6.
File System Utilization
Reports on file system utilization by a host-based

application.
See File System utilization report on page 5-7.
Storage Allocation Details 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.
See Storage allocation details on page 5-12.
Capacity Allocation Trend Displays application capacity allocation trend for the
past 90 days.
See Capacity allocation trend report on page 5-9.
Application Response
Time Trend
Provides response time breakdown over the past 24

hours.
See Application response time trend report on page 59.
Accessing application reports

You can access application reports at the application level or folder level in
a business view.
To access application reports for a selected application:
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.
To access application reports at the folder level in a business view:
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 dropdown list. The drop-down list also includes your saved reports.
54
Application summary report

The Application Summary report provides a quick overview of the
application SLO status and application details.
Figure 5-1 Application summary report

The report displays the following information:
Name: The application name.
Status: Indicates the SLO status whether the application is in

conformation with SLO (OK), missed the SLO (Missed), on borderline
(Borderline), or unmonitored.
Tags: Tags assigned to the application. No tags are displayed for

applications that are not assigned any tags.
SLO status report

The SLO Status report provides a quick overview of the application SLO
status for the past 24 hours.
Figure 5-2 SLO status report
55
The 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.
It also indicates the percentage of time when the application was in
conformance with the monitored SLO in the past 24 hours.
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 5-3 Storage system performance report

The 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.
Storage allocation report

The Storage Allocation report provides a quick insight into the total physical
storage capacity over total virtual storage capacity for a selected application
or all applications within a selected folder in the business view.
56
Figure 5-4 Storage allocation report
File System utilization report

The File System 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.
Figure 5-5 File system utilization report
SLO details report

The SLO Details report lists every storage Service Level Objective (SLO)
monitored over a period of time for all applications in your environment or
a selected application.
The report is displayed when you select any of these:
Missed or Borderline links in the Response Time SLO Status report on the
dashboard.
57
Missed or Borderline links in the IOPS SLO Status report on the

dashboard.
An application in a business view in the Resources tab.
Figure 5-6 SLO details report

This report provides the following information:
Note: The SLO Details report displays all metrics for an application you
selected in the Resources tab. For this report displayed from the dashboard,
certain metrics are displayed/hidden based on the report link. These
metrics are identified accordingly.
Sub-application: The sub-application name.
Application: The application name.
Status: Indicates the current sub-application SLO status.
Response Time: The current response time for the sub-application.
IOPS: The current I/O operations per second for the sub-application.
DTR: The current Data Transfer Rate for the sub-application.
Missed RT Threshold: Indicates the value (in percentage) the subapplication has exceeded the Miss Response Time SLO threshold.
This metric is only displayed when you select the Missed link in the
Response Time SLO Status report on the dashboard.
Borderline RT Threshold: Indicates the value (in percentage) the subapplication has exceeded the Borderline Response Time SLO threshold.
This metric is displayed when you select the Borderline link in the
Missed IOPS Threshold: Indicates the value (in percentage) the subapplication has exceeded the I/O operations per second threshold.
This metric is only displayed when you select the Missed link in the IOPS
SLO Status report on the dashboard.
Borderline IOPS Threshold: Indicates the value (in percentage) the subapplication has exceeded the Borderline I/O operations per second SLO
threshold value.
This metric is only displayed when you select the Borderline link in the
IOPS SLO Status report on the dashboard.
58
Total Volumes: The total number of volumes associated with the subapplication.
Missed RT Volumes: The number of volumes that have exceeded the

Response Time Miss threshold.
This metric is only displayed when you select the Missed link in the
Borderline RT Volumes: The number of volumes that have exceeded the

Response Time Borderline threshold.
Missed IOPS Volumes: The number of volumes that have exceeded the
IOPS Miss threshold.
This metric is only displayed when you select the Missed link in the IOPS
SLO Status report on the dashboard.
Borderline IOPS Volumes: The number of volumes that have exceeded

the IOPS Borderline threshold.
IOPS SLO Status report on the dashboard.
Capacity allocation trend report

The Capacity Allocation Trend report displays capacity allocation trend, for
a selected application or all applications within a selected folder in the
business view, for the past 90 days.
Figure 5-7 Capacity allocation trend report

The reports provides the following information:
Physical: Total capacity for all physical volumes allocated to the

application.
Virtual: Total capacity for all virtual volumes (DP-VOLs) allocated to the
application.
Application response time trend report

The Application Response Time Trend report provides information on the
response time breakdown over the past 24 hours for a selected application
or all applications within a selected folder in the business view.
59
Figure 5-8 Application response time trend report

The report displays the total response time for each read/write operation
request.
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 6-4.
510
Figure 5-9 IO utilization trend report

Total IOPS: The total number of IO operations per second.
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
(i.e., read operations that are accessed from the cache rather than from
the disk).
Storage allocation information

This module describes the Storage Allocation Details report available in
HCmD.
Storage allocation details on page 5-12
DP Pool utilization report on page 5-13
Storage path report on page 5-15
Tier definition report on page 5-16
511
Storage allocation details

The Storage Allocation Details report reports on the storage volumes to
which the host file systems are mapped.
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), HCmD will not display such devices.
Content pane.
The Storage Allocation Details report reports on the amount and type of
primary storage capacity an application is using. Results can be grouped,
sorted, and filtered by tier, physical disk details, or logical volume type
attribute.
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.
The Storage Allocation Details report provides the following information:
LDEV: The volume (storage disk) ID.
Label (optional): The label that has been assigned to the storage disk
from the Hitachi Device Manager.
Storage System: The storage system model and serial number.
# of Paths: Displays the total number of paths for this volume. The
number displayed is a navigable link to the Storage Path report.
To review the Storage Path report, see Storage path report on page 515.
Vol Type: Displays the type of volume; for example, standard, CVS,
LUSE, DP-VOL, CoW-VOL.
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.
DP-VOL: 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.
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.
512
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
DP Pool: When the volume is part of a dynamic provisioning pool, this

column displays the DP pool name. The DP pool name is a navigable link
to the DP Pool Utilization report.
To review the DP Pool Utilization report, see DP Pool utilization report on
page 5-13.
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 Snapshot VDEV; for external
volumes, this is the External Array Group. The name is a navigable link
to the Health Array Group Detail report for this array group.
Parity Group: The name of the parity group.
RAID Level: The volume RAID level expressed in 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, 688
GB 7200 SATA.
Tier: Displays the name of the tiers that this volume belongs to in HTSM
tiers. The volume can be part of more than one tier. Each tier name is a
navigable link to the Tier Definition report.
To review the DP Pool Utilization report, see Tier definition report on
page 5-16.
Capacity: The total storage capacity of the volume.
Consumed Capacity: Displays the currently consumed capacity of the

volume. For DP-Volumes, the capacity that is consumed from the
Dynamic Provisioning Pool (DP-Pool).
SI Capacity: Displays the total S-VOL (secondary volume) capacity of

type Shadow Image. The P-VOL (primary volume) capacity is not
included.
CoW Capacity: Displays the total S-VOL capacity of type CoW (Copy on
Write). The P-VOL capacity is not included.
External LDEV: Number of the external volume (in hexadecimal format).
External Storage System: Model and serial number of the external

storage system.
DP Pool utilization report

This report provides detailed information about the DP pool utilization for
the selected application or host.
You can access this report from the DP Pool column in the Storage
Allocation Details report.
513
Figure 5-10 DP Pool utilization report

The DP Pool Utilization report is organized into three sections:
DP Pool Properties
DP Pool Volumes
DP Volumes
DP Pool properties
The DP Pool Properties section lists the following properties and their
values:
514
DP Pool Name: The name of the DP Pool (which is the number assigned
to this DP pool).
Storage System: The name of the storage system where this DP pool
resides.
Tier: The name of the Tier that this Pool belongs to in the Hitachi Tiered
Storage Manager (HTSM).
# of DP-VOLs: The total number of DP-VOLs in this pool.
# of DP Pool-VOLs: The total number of Pool-VOLs in this pool.
DP Pool Capacity: Total physical capacity of this pool.
Sum of DP-VOL Capacities: Total capacity of all DP-VOLs.
DP Pool Free: Unconsumed DP Pool capacity.
DP Pool Used %: Consumed capacity as a percentage of DP Pool physical

capacity.
Over Provisioning Ratio: Refer to the Over Provisioning Ratio SLO for its
calculation.
Risk Ratio: Refer to the Pool Risk Ratio SLO for its calculation.
Status: Displays pool status: Three types of pool status are supported:
Normal, Blocked, and Over Threshold.
DP Pool Volumes section

The DP Pool Volumes section provides the following information about each
of the DP Pool-VOLs in this pool:
LDEV: Name of the volume.
Label: The Device Manager label name for the volume.
Array Group: The name of the Array Group of this volume.
Volume Type: The type of volume (for example, Standard, external,

CVS, LUSE, DP Pool VOL).
Capacity: Allocated capacity of this volume.
Disk Type: Disk type expressed in 130GB 10K FC format.
RAID Level: RAID level in Raid 5 (3D+1P) format.
Emulation: Type of emulation (for example, Open-V).
DP Volumes section
The DP Volumes section provides the following information about each of
the DP-VOLs in this pool:
LDEV: The name of the volume.
Label: The Device Manager label name for the volume.
Tier: The name of the tier that this Pool belongs to in the Hitachi Tier
Storage Manager (HTSM).
Array Group: The name of the Array Group of this volume.
Volume Role: Indicates whether the volume is an S-VOL (secondary

volume) or P-VOL (primary volume).
Capacity: Allocated capacity of this volume.
Consumed Capacity: Capacity consumed from the DP pool.
Storage path report

The Storage Path report provides path information for a specific volume. If
the volume has more than one path, each path is listed separately.
You can access this report from the # of Paths column in the Storage
Allocation Details report.
515
Figure 5-11 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 provisioned.
HSD: The Host Group name.
Host: 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 provisioned to multiple HBA WWNs in the same Host
Group, this report will display this information.
HDvM Host Name: The name of the host in the Hitachi Device Manager
(HDvM).
Host Name: The gathered name of the host.
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.
Figure 5-12 Tier definition report

The report provides the following information:
516
Tier Name: The name of the tier.
Tier Definition: A string containing the search conditions that define a

tier in HTSM.
Storage System and host SLOs reports

This module describes the various Storage System and host SLOs reports
available in HCmD.
Storage system & host SLOs report on page 5-17
Cache write pending % report on page 5-18
DP Pool over provisioning ratio report on page 5-18
DP Pool risk ratio report on page 5-19
DP Pool used % report on page 5-19
Parity Group busy % report on page 5-20
Port busy % report on page 5-20
Storage system & host SLOs report

The Storage System & Host SLOs report track storage system resource
utilization.
Content pane.
The reports alerts you when your storage system performance is not
optimal. and are used for the following reasons:
When a resource is highly utilized, it cannot handle the I/O workload

spikes that occur from time to time.
At high utilization levels, the storage system throttles performance to

maintain data integrity and to avoid catastrophic failures.
Typically, performance hot spots are caused by unbalanced loads rather

than storage system over utilization (if your storage system is over utilized,
you can add capacity). If your storage performance is not optimal, you can
balance the port microprocessor and parity group loads.
SLO: Lists the following reports:

Cache Write Pending % report
To review the Cache Write Pending % report, see Cache write
pending % report on page 5-18.
DP Pool Over Provisioning Ratio report
To review the DP Pool Over Provisioning Ratio report, see DP Pool
over provisioning ratio report on page 5-18.
DP Pool Risk Ratio report:
To review the DP Pool Risk Ratio report, see DP Pool risk ratio report
on page 5-19.
DP Pool Used % report:
To review the DP Pool Used % report, see DP Pool used % report on
page 5-19.
517
If the storage system includes parity groups or port microprocessors,

this column provides links to the Parity Group Busy % report and the
Port Busy % report.
To review the Parity Group related reports, see Parity Group busy %
report on page 5-20 and Port busy % report on page 5-20.
Red: How many resources have exceeded their red threshold. This
means that the storage system performance can degrade at any time.
Yellow: How many resources have exceeded their yellow threshold. If a

workload spike or path failure occurs, the storage system performance
can degrade.
Green: How many resources do not have violations. The port

microprocessors, cache, or parity groups are below their thresholds and
not in jeopardy of developing hot-spots or performance degradation. If
a failure occurs, the storage system performance is not going to
degrade.
Cache write pending % report

Reports the percentage of data in the CLPR that is to be written to the
storage system disk.
You can access this report from the SLO column in the Storage System &
Host SLOs report.
This report displays the following information:
CLPR Number: The number of the Cache Logical Partition on the storage
system.
Storage System: The storage system the CLPR belongs to.
Red Zone (Time): The percentage of time that the resource has been
above its red utilization threshold.
Yellow Zone (Time): The percentage of time that the resource has been
above its yellow utilization threshold.
Green Zone (Time): The percentage of time that the resource has been
below its yellow utilization threshold (no violation).
DP Pool over provisioning ratio report

Reports the over-provisioned ratio for each DP Pool in the system.
Host SLOs report.
DP Pool: The name (i.e., the assigned number) of the DP pool on the
Storage System.
Storage System: The Storage System that the DP pool belongs to.
Status:
Green indicates that the DP pools over-provisioning ratio is below its
SLO threshold and there is no violation.
518
Yellow indicates that the DP pools over-provisioning ratio has

exceeded the warning threshold.
Red indicates that the DP pools over-provisioning ratio is in violation
of the SLO threshold.
Time: The date and time of the violation.
DP Pool risk ratio report

Reports the DP pool risk ratio for each DP pool in the system.
Host SLOs report.
Figure 5-13 DP Pool SLO details

storage system.
Storage System: The storage system that the DP pool belongs to.
Status:
Green indicates that the DP pools risk ratio is below its SLO threshold
and there is no violation.
Yellow indicates that the DP pools risk ratio has exceeded the
warning threshold.
Red indicates that the DP pools risk ratio is in violation of the SLO
threshold.
DP Pool used % report

Reports the total consumed capacity of each DP pool.
Host SLOs report.
The total consumed capacity from each DP pool is calculated by summing
the Consumed Capacity attribute of each DP-VOL (that is, the volumes
carved out of the DP pool).
519
storage system.
Storage System: The storage system that the DP pool resides on.
Status:
Green indicates that the DP pools over-provisioning ratio is below its
SLO threshold and there is no violation.
Yellow indicates that the DP pools over-provisioning ratio has
exceeded the warning threshold.
Red indicates that the DP pools over-provisioning ratio is in violation
of the SLO threshold.
Parity Group busy % report

Reports the storage systems parity group read and write activity.
Host SLOs report.
Parity Group: The name of the parity group on the storage

system.Storage System: The storage system that the parity group
belongs to.
Port busy % report

Reports the storage systems port microprocessor work load.
Host SLOs report.
Parity Group. The name of the parity group on the storage system.
520
Storage System: The storage system that the parity group belongs to.
Total number of applications in a folder

The Total Applications report displays the total number of applications within
a selected application folder.
Figure 5-14 Total applications

The Response Time SLO Status report displays the response time SLO
status for all applications within a selected folder.
Figure 5-15 Response time SLO status

The report provides a breakdown of overall application SLO status indicating
the number of applications that missed (in red), on borderline (in yellow),
and in conformance (in green) with the response time SLO. It also displays
the number of applications that are not currently monitored for this SLO (in
gray).
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.
521
Figure 5-16 IOPS SLO status report

The report provides a breakdown of overall application SLO status indicating
the number of applications that missed (in red), on borderline (in yellow),
and in conformance (in green) with the Total IOPS SLO. It also displays the
number of applications that are not currently monitored for this SLO (in
gray).
Application list
The Application List provides details about all applications within a selected
folder.
Figure 5-17 Application list

The report provides the following information:
522
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
the sub-applications state.
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.
523
524
6
Reporting on hosts
This module describes the HCmD reports on the hosts discovered by HCmD.
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
61
Host reports
You can view reports for the hosts successfully discovered by the 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 Network Attached Storage (HNAS) servers, VMware ESX
servers, and Hyper-V servers.
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 host reports available to you are:
Summary host reports

See Summary host reports on page 6-3.
HNAS host reports

See HNAS host reports on page 6-6.

See Hyper-V server report on page 6-14.
VMware host reports

See VMware datastores report on page 6-15 and ESX server VMDKs
Reports that are available when you select any host folder and/or host
application:
Storage System and Host SLOs report
Track Storage System resource utilization and monitor host SLOs.
See Storage system & host SLOs report on page 5-17.
Storage Allocation Details report
Reports on the storage volumes to which the host file systems are
mapped.
See Storage allocation details on page 5-12.
Capacity Allocation Trend report
Displays capacity allocation trend for the selected host node in the
past 90 days.
See Capacity allocation trend report on page 5-9.
Application Response Time Trend report
Provides response time breakdown over the past 24 hours.See
Application response time trend report on page 5-9.
IO Utilization Trend report
Displays the total application or host I/O operations per second
(IOPS) over a period of time.
See IO utilization trend report on page 5-10.
62
Reporting on hosts
Available summary host reports

This module describes each of the summary host reports available in HCmD.
Summary host reports on page 6-3
Host file system used % report on page 6-3
Storage utilization report on page 6-4
Volume manager group report on page 6-5
Summary host reports

You can view these summary host reports available in HCmD:
Storage utilization report

Reports on storage utilization of file systems.
See Storage utilization report on page 6-4.
Host file system used % report

Monitors the percentage of the used capacity in the host file system.
See Host file system used % report on page 6-3.
Volume manager group report

Provides volume group summary and information about each of the
provisioned volumes and storage volume.
See Volume manager group report on page 6-5.
Accessing summary host reports

To access the summary host reports:
2. From the Business Views drop-down menu, 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 menu in the content pane, select a summary host report you want
to view.
Host file system used % report

The Host File System Used % report monitors the percentage of the used
capacity in the host file system.
Host SLOs report.
You can set the borderline and miss thresholds for this report using the
instructions described in Modifying storage system health thresholds on
page 4-5.
Reporting on hosts
63
Figure 6-1 Host file system used % report

Filesystem: Name of the file system that has been violated.
Host: Name of the associated host (server).
Status: Displays Borderline status or Miss status.
Time: The data and time of the violation.
Storage utilization report

The Storage Utilization report reports on file systems rather than the
volumes to which those file systems are mapped.
64
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.
FS Capacity: Total storage capacity of the file system.
FS Free %: Percentage of the file systems free capacity.
Vol Mgr: The name of the volume manager. If the file system is not from
Volume Manager, this field is blank.
Vol Mgr Type: Type of volume manager (for example, Veritas volume
manager, LVM, SVM).
Storage System: Displays the storage system model and serial number
(for example, USP 15050).
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.
Reporting on hosts
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.
Vol Capacity: Total capacity of the volume.
Vol Free %: The percentage of the volumes total unpartitioned capacity.
Vol Role: Displays the volume role.
Vol Type: Display the type of volume (for example, standard, CVS, LUSE,
DP-VOL, CoW-VOL, External).
DP Pool: If the volume is part of any DP pool, this field displays the HDP
pool name; otherwise, this field displays -. The DP Pool name is a
navigable link to the DP Pool Utilization report.
Array Group: Displays the array group name.
Parity Group: Displays the Parity Group name.
Volume manager group report

You can access the Volume Manager Group report from the Vol Mgr column
in the Storage Utilization report.
Volume group summary

The Volume Group Summary section has the following columns:
DiskGroup/Datastore Name: If it is an ESX server, this displays the name

of the disk group or data store.
# Provisioned Volumes: Total number for 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 data store.
Free Capacity: If it is an ESX server, this displays the capacity free in this
disk group or data store.
% 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 name of the host itself.
Capacity: Total capacity of the volume.
Reporting on hosts
65
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.
Emulation: Type of emulation used (for example, Open-V).
Disk Type: The size and type of disk expressed in 130GB 10K FC
format.
Capacity: Total storage capacity of the volume.
Available HNAS host reports

This module describes each of the HNAS reports available in HCmD.
HNAS host reports on page 6-6
Accessing HNAS host reports on page 6-7
File system IO trend report on page 6-7
File system load trend report on page 6-8
HNAS file system report on page 6-8
HNAS pool summary report on page 6-9
HNAS pool details report on page 6-9
HNAS shares report on page 6-11
Protocol Op/s trend report on page 6-11
Total throughput trend report on page 6-12
HNAS host reports

You can view these HNAS host reports available in HCmD:
File System 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 File system IO trend report on page 6-7.
File System Load Trend report

Trends the total percentage of the file system load on the HNAS CPU over
a period of time.
See File system load trend report on page 6-8.
66
HNAS File System report
Reporting on hosts
Lists all the file systems under each HNAS server and its associated Pool
information.
See HNAS file system report on page 6-8.
HNAS Pool Summary report

Provides an overview of each of the storage pools controlled by the
selected SMU.
See HNAS pool summary report on page 6-9.
HNAS Pool Details report

Provides HNAS pool details for HNAS server nodes.
See HNAS pool details report on page 6-9.
HNAS Shares report

Displays key information for all the shares by each file system in the
HNAS server.
See HNAS shares report on page 6-11.
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 6-11.
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 6-12.
Accessing HNAS host reports

To access the HNAS host reports:
2. From the Business Views drop-down menu, 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 select the file system of interest.
To view the HNAS Nodes report, expand the Nodes folder under the
SMU folder, and select the HNAS node of interest.
4. View the report in the Content pane or from the Select a Report dropdown menu in the content pane, select a HNAS host report you want to
view.
File system IO trend report

The File System 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.
Reporting on hosts
67
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.
File system load trend report

The File System 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 File System 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
(Titan Model only if board A is available).
FSB Load %: File system load percentage on board B of the HNAS CPU
(Titan Model only if board B is available).
FS Load %: File system load percentage on the HNAS CPU (available

only for the Eclair model).
HNAS file system report

The HNAS File System report is available for Hitachi Network-Attached
Storage (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 6-2 HNAS file system report

The HNAS File System report contains the following information about each
HNAS file system:
FS: The name of the HNAS file system. This item is a link to the HNAS
Shares report, which lists all the shares in the selected file system.
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 link to the
HNAS Pool Details report.
View HNAS Pool Details report in HNAS pool details report on page 6-9.
68
Reporting on hosts
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.
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 File System
report.
Figure 6-3 HNAS pool summary

This report provides the following information about each file system:
Pool: Name of the storage pool.
# of LDEVs: The number of volumes that have been provisioned 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 pools condition is currently healthy or not.
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 File System report or HNAS Pool Summary report.
Reporting on hosts
69
Figure 6-4 HNAS pool details

The topmost 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: Filesystems and Volumes.
File Systems tab

The Filesystems 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:
610
FS: Name of the file system.
Capacity: Total storage capacity of the file system.
Used: Capacity of the file system that is being used currently.
Free: Free storage capacity of the file system.
Free %: The percentage of the file systems free storage capacity.
EVS: The name of the EVS server.
EVS IP: The IP address of the EVS server.
Reporting on hosts
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 HCmD
does not gather information on AMS/WMS storage and the volume
information in this report is gathered from the HNAS server itself.
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 GBs).
Storage System: Name and model of the storage system.
HNAS shares report

The HNAS Shares report displays key information for all the shares by each
file system in the HNAS server.
Figure 6-5 HNAS shares report

The report provides the following information for each share:
Share Name: 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.
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.
This report is available for HNAS nodes in the File Servers business view,
and can be accessed from the Select a Report dropdown menu in the
content pane.
Reporting on hosts
611
Figure 6-6 Protocol Op/s Trend report
Total throughput 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 dropdown menu in the
content pane.
The following diagram illustrates the data transfer through Ethernet and FC
for an HNAS node.
This report displays a line chart showing data transfer received and sent
through Ethernet and FC for the past 24 hours.
612
Reporting on hosts
Figure 6-7 Total Throughput Trend report

This module describes the Hyper-V server report available in HCmD.
Accessing Hyper-V server report on page 6-13
Hyper-V server report on page 6-14
Accessing Hyper-V server report

The Hyper-V Server report lists each VM (virtual machine) instance in a
separate row. This report is available both on the Hyper-V folder node and
Hyper-V Server application node.
To access the Hyper-V server report:
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 menu in the content pane, select Hyper-V Server Report.
Reporting on hosts
613

The Hyper-V Server report allows you to see:
Which data stores are used by that Hyper-V Server.
Which VMs (i.e., virtual machine guest operating systems) are running
on that Hyper-V Server.
Which VMDKs are used on that Hyper-V Server.
Figure 6-8 Hyper-V server report

The Hyper-V Server report presents the following columns:
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.
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: 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 dash (-).
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.
Free %: The percentage of free space for the allocated capacity of the
VM instance from the selected Hyper-V server. This data will be available
only when the Host Data collection is complete on this VM instance;
otherwise this value is displayed as a dash (-).
Free: Free capacity of the allocated capacity of the VM instance from the
selected Hyper-V server. This data will be available only when the Host
Data collection is complete on this VM instance; otherwise this value is
displayed as a dash (-).
VMware host reports

This module describes each VMware host report available in HCmD.
614
Accessing VMware host reports on page 6-15
VMware datastores report on page 6-15
ESX server VMDKs report on page 6-15
Reporting on hosts
Accessing VMware host reports

You can view these summary host reports available in HCmD:
ESX Server Data Stores Report

Provides basic information about the data stores for each ESX server.
ESX Server VMDKS Report

Reports the mapping information between the Virtual Machine Disk
(VMDK), the data store, and the Virtual Machine (VM) instance.
To access the VMware host reports:

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 menu in the content pane, select a VMware host report you want
to view.
VMware datastores report

The VMware Datastores report provides basic information about the
datastores for each VMware server.
Figure 6-9 VMware datastores report

This report contains the following information about each ESX datastore:
Datastore: Name of the datastore.
Free %: The percentage of the datastores 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.
ESX server VMDKs report

This report provides the mapping information between the Virtual Machine
Disk (VMDK), the datastore, and the Virtual Machine (VM) instance.
Reporting on hosts
615
Figure 6-10 ESX server VMDKs report

The ESX Server VMDKs report provides the following information:
616
VMDK: The name of the VMDK.
VMDK Capacity: The total storage capacity (in GBs) 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.
Reporting on hosts
7
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 & Inventory report gallery
Chargeback report gallery
Accessing reports
Using reports
Report Gallery
71
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 7-3
HDP, HDT capacity by Storage Systems on page 7-3
HDP, HDT pool usage by application on page 7-6
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 7-7
HDP Pool storage performance on page 7-7
Top 20 busiest storage system ports on page 7-8
Top 20 busiest parity groups on page 7-9
Top 20 busiest volumes on page 7-9
Application SLO conformance on page 7-10
Storage Economics: Includes reports that help you optimize storage

utilization by utilizing Hitachis Tiered Storage technology.
Top 10 tiers by capacity on page 7-11
Underutilized host file systems on page 7-11
Application data distribution by tier on page 7-11
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 7-12
File system inventory on page 7-13
Physical server inventory on page 7-14
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.
Note: Although the chargeback reports provide enough data for you
to charge back the application/host owners, further processing is
needed to generate a complete, final chargeback report.
Application storage allocation by tier on page 7-15
Application storage allocation by pool on page 7-15
72
Report Gallery
Utilization report gallery

This module describes each of the utilization reports available in the
Utilization report gallery.
Physical capacity by storage system on page 7-3
HDP, HDT capacity by Storage Systems on page 7-3
HDP, HDT pool usage by application on page 7-6
Physical capacity by storage system

The Physical Capacity by Storage System report informs you of the physical
capacity usage of your storage array to confirm that the array utilization is
in balance. If the arrays are not in balance, you could potentially balance
the uneven usage by off-loading data to less utilized storage systems or
confine new applications only to the less used storage systems.
You can access this report from the Utilization category in the report
gallery.
Model: The storage system model type.
Serial: The storage system serial number.
Internal: Total capacity of the physical parity group.
External: Total capacity of the external parity group.
Allocated: Total allocated capacity that includes both internal and

external capacity.
Unallocated: Total unallocated capacity that includes both internal and

external unallocated capacity.
Reserved: Total reserved capacity that includes both internal and

external reserved capacity.
Total Parity Group Free: Total free space that includes both internal and
external free capacity.
HDP, HDT capacity by Storage Systems

The HDP, HDT Capacity by Storage Systems 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 Hitachi Dynamic
Provisioning (HDP) or Hitachi Dynamic Tiering (HDT) Pools.
gallery.
Pool Capacity: Total HDP, HDT pool capacity for the storage system.
Used: The sum of all DP volumes consumed capacity for a volume.
Report Gallery
73
Free: Total HDP, HDT pool free capacity for the storage system.
Used%: Percentage of used capacity by pool capacity.
Subscribed: Total capacity of the DP volumes subscribing to the pool.

Includes both allocated and unallocated volumes.
Subscribed%: Percentage of subscribed volumes by pool capacity.
# HDP Pools: Total number of HDP pools.
# HDT Pools: Total number of HDP pools that are HDT enabled.
Storage capacity by HDP, HDT pool for Storage System <storage
system>
Click the Serial link in the HDP, HDT Capacity by Storage Systems report to
view the storage capacity by HDP pool details for a specific storage system.
The following information is displayed:
74
Pool ID: The HDP, HDT pool ID.
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 HDP, HDT pool.
Used: Total HDP, HDT pool free capacity.
Free: Total HDP pool free capacity .
Demand: The subscription capacity.
Used%: Percentage of total pool capacity by used capacity.
Threshold1: The user defined threshold of the consumed capacity.
Threshold2: The system defined threshold of the consumed capacity.
#DP Volumes: Total number of HDP 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 HDP volumes that have at least one path.
Allocated Used: The consumed capacity of HDP volumes that have at

least one path.
Unallocated: The capacity of HDP volumes that have no path.
Unallocated Used: The consumed capacity of HDP volumes that have no

path.
# Applications: Total number of applications that have allocated volumes

from this HDP, HDT pool.
# Pool Tiers: Total number of tiers on this pool. Applicable only for VSP
(hyphen).
Tier Management: Auto or Manual for VSP pools. For other models, this
field is not applicable and displays a - (hyphen).
Report Gallery
HDP, HDT pool capacity trend for Storage System <storage
system>, Pool ID <pool ID>
Click the Pool ID link in the Storage Capacity by HDP, HDT Pool for Storage
System report to view a bar char that displays the DP volumes capacity
trend for the past 30 days.
The bar chart reports the following:
Tier type: It can be any of the following:

SSD: If it is a tier-enabled pool and of SSD disk type, then a stack
bar of SSD capacity and consumed capacity is displayed.
SAS/<RPM>: If it is a tier-enabled pool and of SAS disk type with
disk speed <RPM> of 10K or 15K, then a stack bar of the SAS/
<RPM> capacity and consumed capacity is displayed.
SATA/<RPM>: If it is a tier-enabled pool and of SATA disk type with
7.2K of disk speed <RPM>, then a stack bar of the SATA/<RPM>
capacity and consumed capacity is displayed.
Used: If the Storage system is not a VSP, or is a VSP with tier control
disabled then this report will display HDP Pool consumed capacity.
Free: If the Storage system is not a VSP, or is a VSP with tier control
disabled then this report will display HDP Pool free 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.
Consumed: Total consumed capacity of all DP volumes on this pool.
Allocated: Total DP volume capacity of the pool that has at least one
path.
Subscribed: Total DP volume capacity of the pool.
DP Volumes capacity for HDP Pool for Storage System <storage

system>, Pool ID <pool ID>
Click the #DP Volumes link in the Storage Capacity by HDP/HDT Pool for
Storage System report to gain an indepth knowledge of all DP volumes of a
specific pool. It also helps you to determine the DP volumes on any
application.
Volume: The HDP volume name.
Volume Capacity: DP volume capacity.
Consumed Capacity: DP volume consumed capacity.
Application: Applications that have the DP volume as its member. If this

DP volume is not a member of any application then a - (hyphen) is
displayed.
Report Gallery
75
HDP, HDT pool usage by application

The HDP, HDT Pool Usage by Application report provides information about
pool capacity usage by applications. The utilization and subscription ratio
inform you about your consumption of virtual capacity or if you are at risk
of over-subscribing Hitachi Dynamic Provisioning (HDP) or Hitachi Dynamic
Tiering (HDT) Pools.
gallery.
Pool ID: The HDP, HDT pool name.

(hyphen).
#DP Volumes: Number of DP volumes from this pool that are associated
with the application.
Allocated: Total capacity of all DP volumes that have at least one path
and are associated with the application.
Used: The consumed capacity of all DP volumes that are associated with
the application.
SSD Used: The consumed capacity of the pools DP volumes associated

with the application, and mapped to the pool tier with disk type as SSD.
The value will be a - (hyphen) if it s not a VSP or if there is no SSD disk
type in this HDT pool.
SAS Used: The consumed capacity of the pools DP volumes associated

with the application, and mapped to the pool tier with disk type as SAS.
SATA Used: The consumed capacity of the pools DP volumes associated

with the application, and mapped to the pool tier with disk type as SATA.
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.
Performance report gallery

This module describes each of the performance reports available in the
Performance report gallery.
76
Storage port workload on page 7-7
HDP Pool storage performance on page 7-7
Report Gallery
Top 20 busiest storage system ports on page 7-8
Top 20 busiest parity groups on page 7-9
Top 20 busiest volumes on page 7-9
Application SLO conformance on page 7-10
Storage port workload

The Storage Port Workload report shows the current workload on existing
storage ports thus enabling the storage administrator to assign the best
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 in the report
gallery.
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 IO data read IOPS and write IOPS.
DTR: Sum of port total read data transfer rate and write data transfer
rate.
Processor: The port processor associated with the storage port.
Busy %: The port processor utilization/performance rate.
HDP Pool storage performance

The HDP 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 (IOPS, DTR, etc.)
gallery.
Pool ID: The storage pool name.
Pool Capacity: Total capacity of HDP, HDT pool.
Free: Total HDP pool free capacity.
Total IOPS: Total IOPS (sum of Read IOPS and Write IOPS) for all DP
volumes in the pool.
Report Gallery
77
Response Time: The weighted average response time for all DP volumes
in the pool.
Read IOPS: The average read IOPS for all DP volumes in the pool.
Read Response Time: The read response time for all DP volumes in the
pool.
Read Hit %: The weighted read hit % for all DP volumes in the pool.
Write IOPS: The write IOPS for all DP volumes in the pool.
Write Response Time: The write response time for all DP volumes in the
pool.
Total DTR: Total throughput (DTR) for all DP volumes in the pool
Parity Group utilization for Pool ID <Pool ID>

Click the Pool ID link in the HDP Pool Storage Performance report to view
the Parity Group utilization report for a specific storage pool.
Parity Group: The parity group name.
RAID Type: RAID level in Raid 5 (3D+1P) format.
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

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.
gallery.
78
Port: The storage port name.
Role: The role of the port such as target and RCU target ports.
Processor: The port processor associated with the storage port.
IOPS: Total IOPS (Read IOPS and Write IOPS) for the storage port.
Max IOPS: Maximum IOPS for the storage port.
DTR: Total DTR for the storage port.
Report Gallery
Max DTR: Maximum DTR for the storage port.
Busy %: The port processor busy percentage.
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 busy storage system port.
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.
Top 20 busiest parity groups

The Top 20 Busiest Parity Groups report provides information about the 20
busiest parity groups that could potentially impact backend storage
performance, applications, or the storage pools that serve your
applications.
gallery.
Parity Group: The parity group name.
RAID Type: RAID level in Raid 5 (3D+1P) format.
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 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 volumes

The Top 20 Busiest Volumes report provides information about the 20
busiest volumes that could impact backend storage performance,
applications, or the storage pools that serve your applications.
Report Gallery
79
gallery.
Volume: The HDP volume name.
Parity Group: The parity group that includes the volume.
Pool ID: The pool ID the volume belongs to.
Tier: The storage tier the volume belongs to.
Total IOPS: Total IOPS for the volume.
IOPS Contribution: Percentage of the IOPS contribution against the

entire storage system.
Avg Response Time: The weighted average response time for the
volume.
Read IOPS: The read IOPS for the volume.
Read Response Time: The read response time for the volume.
Read Hit %: The percentage of read hit for the volume.
Write IOPS: The write IOPS for the volume.
Write Response Time: The write response time for the volume.
Total DTR: Total throughput (DTR) for the volume.
Application SLO conformance

The Application SLO Conformance report lists all applications and its SLO
conformance for the past 30 days. For each of the monitored application in
the Command Director environment, this report displays the percentage of
time when the application was in conformance with a monitored SLO. 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.
gallery.
This report is sorted by the Application Name and displays the following
information:
710
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.
Report Gallery
SLO Conformance: Indicates the percentage of time when the

application was in conformance with a monitored SLO in the past 30
days.
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 7-11
Underutilized host file systems on page 7-11
Application data distribution by tier on page 7-11
Top 10 tiers by capacity

The Top 10 Tiers by Capacity report shows the total capacity for the top 10
tiers for your data center so you are informed about the tier composition in
your data center. Having this information may aid you in planning updates
to your tier to better address your business needs.
You can access this report from the Storage Economics category in the
report gallery.
Displays a bar chart that reports the top 10 tiers with each bar in the graph
representing a tier and the total capacity for this tier.
Underutilized host file systems

The Underutilized Host File Systems report aids in identification of under
utilized hosts so you can reclaim storage from the hosts or deploy data to
them if warranted.
report gallery.
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 provisioned to this host.
Used: Used capacity of all the volumes provisioned to this host.
Free: Free capacity of all the volumes provisioned to this host.
Free %: Percentage of free capacity by total capacity.
Application data distribution by tier

The Application Data Distribution by Tier report identifies where your
primary, secondary, and tertiary application data are located on each tier.
You can move secondary and tertiary application data off to lower cost tiers
to reduce costs.
Report Gallery
711
report gallery.
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 Hitachi Universal Replicator volumes.
Asset & Inventory report gallery

This module describes each of the asset and inventory reports available in
the Asset & Inventory report gallery.
Storage system inventory on page 7-12
File system inventory on page 7-13
Physical server inventory on page 7-14
Storage system inventory

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 in the
report gallery.
712
#Drives: Total number of drives in the storage system.
Raw: Total capacity of all drives.
#Parity Groups: Number of parity groups.
#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.
Microcode Level: The microcode version of the storage system.
Cache: Total capacity of the cache installed in the storage system.
#WWNs: Total number of WWNs of the connected hosts.
#Hosts: Total number of hosts connected to the storage system.
Report Gallery
File system inventory

The File System 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 under utilized, so that you
can move the physical storage to virtual storage to optimize utilization
and performance of available storage. Storage virtualization eliminates
the overprovisioning of physical storage, in which storage capacity is
allocated to individual hosts but remains unused. With storage
virtualization, 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.
report gallery.
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.
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 multiple DP
Pools.
Report Gallery
713
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 tiers that this volume belongs to in the 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).
Physical server inventory

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.
report gallery.
Host: The host name.
OS: The storage system serial number.
IP Addresses: Total number of drives in the storage system.
# 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.
Chargeback report gallery

This module describes each of the chargeback reports available in the
Chargeback report gallery.
714
Application storage allocation by tier on page 7-15
Application storage allocation by pool on page 7-15
Report Gallery
Application storage allocation by tier

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 vs.
external charge. The 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
combination data for each day. You can access this report from the
Chargeback category in the report gallery.
Date: The daily snapshot date and time.
Tier: The name of the tier whose member volume(s) are also member(s)
of the application. This column displays a - (hyphen) if this
application's member volumes are not associated to any tier.
Capacity: Total capacity of all the member volumes in the application

associated to this tier. If the value of the tier is displayed as a -
(hyphen) then the capacity of all the member volumes of the application
that are not associated to any tier is displayed.
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).
Application storage allocation by pool

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 vs. external charge. The report also contains tags
that enable you to organize the applications with the external tools that
consume this type of report data.
You can access this report from the Chargeback category in the report
gallery.
Date: The daily snapshot date and time.
Report Gallery
715
Pool: The HDP, HDT pool whose DP volumes are member volumes of the
application.

(hyphen).
Allocated: Total capacity of all DP volumes allocated to the application

from this pool.
Used: The used capacity of all DP volumes allocated to the application

from this pool.
by a comma.
Accessing reports
You can view the standard and saved reports available from the report
gallery, and the application, application folder, and host reports from the
Resources tab.
To access reports from the report gallery:
1. Click the Reports tab.
The report gallery view is displayed.
2. From the report gallery, click one of the following tabs:
Standard Reports: Reports on the overall heath of the system or
provide insight into your storage environment. These are systemgenerated and provided by default.
Saved Reports: Customizable report folder to include your most
frequently accessed reports.
You modify any standard report and save the modifications in a new
report under a folder you specify. Those reports appear under this
tab.
3. From the Standard report type, select a category and click a report link
to view.
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, you can:
Refresh your view of the report
Schedule a report
Export a report
Save copy of the report
716
Report Gallery
Edit the report

To access reports from the Resources tab:
2. From the Business Views drop-down menu, select any business view.
3. Choose a report from the Select a Report dropdown in the Content pane.
4. After you select a report to view, you can:
Refresh your view of the report
Schedule a report
Export a report
Save copy of the report
Edit the report
Using reports
After you access your report of interest you can view the following buttons
on the report viewer:
Refreshing the report view on page 7-17
Scheduling a report on page 7-17
Exporting a report on page 7-18
Saving a report on page 7-18
Editing a report on page 7-18
Note: The button functionality described above may not be available on

all reports.
Refreshing the report view

When you are in the report view, click Refresh to obtain the latest view and
data.
Scheduling a report
You can automatically generate and send reports by email by scheduling
and specifying the report format.
To schedule and email reports:
1. Select and click Schedule.
The Schedule Report options appear.
2. Enter the report name in the Report Name field.
3. On the Recipient(s) list, select the users whom you are sending the
reports to.
If you want to send the report to users who are not in HCmD and do not
appear on this list, add their email addresses, one at a time, in the
Recipient Email(s) field, and then click Add.
Report Gallery
717
4. Under Format, select Excel or XML.

5. Under When, do any of the following:
To send the report one time only, select Now.
To send the report on a recurring basis, select Schedule and then
specify when the report is emailed.
On the Time drop-down menu, select the time of day when the
report is emailed.
Under Recurrence Type, select how often the report is emailed
(daily, weekly, monthly, or yearly). If you select Weekly, Monthly, or
Yearly, specify when you want to send the report in that time period.
6. When you have finished, click Send/Schedule.
Exporting a report
You can select to export a report of interest in either Excel or XML formats.
To export a report:
1. Click Export.
2. Select either Excel or XML format.
3. Click Export to export the file.
Saving a report
You can select to save a report of interest.
To save a report:
1. Click Save Copy.
2. Enter the name of the copy in the Save Report As field.
3. In the Save In field, enter one of the following:
Save in New Folder: enter name of the folder.
User Folder: use existing folder.
Editing a report
You can select to edit a report of interest.
To edit reports:
1. Click Edit Report on the report screen.
2.
Do any of the following. Note that some options are not available for
every report.
To change how the information is grouped:
Click Aggregate By, select how you want the information organized,
and then click Apply.
To hide information:
Click Display, clear the check boxes next to the columns that you
want to hide, and then click Apply.
718
Report Gallery
To show information:
Click Display, select the check boxes next to the columns that you
want to show, and then click Apply.
3. When you have finished, click Done.
Report Gallery
719
720
Report Gallery
8
Administering HCmD
This module describes how storage administrators can perform
administration tasks in Hitachi Command Director.
Administration tasks overview
Managing licenses
Configuring Host Collectors
Configuring Storage System Data Collectors
Managing scheduled reports
Configuring email servers
Managing HCmD users
Administering HCmD
81
Administration tasks overview

Administration tasks allow you to configure settings for the Hitachi
Command Director (HCmD), including the HCmD Server.
Administration tasks include:
Managing licenses and updating the license key when you purchase
HCmD or additional data collector licenses.
Discovering host information. You can use the Host Collector feature to
configure Host Collectors and discover the hosts and their connectivity
to the subsystem storage arrays.
Managing and configuring Storage System Collectors used to retrieve

performance and configuration data.
Managing SLO profiles that group Service Level Objectives (SLOs) and
set the thresholds against which applications are monitored.
Managing monitoring windows that specify the time periods during

which the application SLOs 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.
Managing licenses
This module provides information about managing licenses and updating
the license key when you purchase Hitachi Command Director.
Hitachi Command Director licenses on page 8-2
License types on page 8-3
Updating license information on page 8-3
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.
When a license expires, a License Violation alert (shown below) is displayed
below the Menu bar.
82
Administering HCmD
License types
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.
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 valid license.
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 license or update licenses when they expire or when you add
storage capacity.
To view/update license information:
1. From the Menu bar, click License.
The License Configuration window (shown in Figure 1-1 License
configuration window on page 1-8) appears:
2. Under License Summary, view your general license information:
Model: 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.
License Status: Whether you have the license for the required
storage capacity or not.
Current Capacity: The storage capacity (in TB) of your storage
system.
Administering HCmD
83
Licensed Capacity: The storage capacity you can use with the
product without exceeding the license limit.
Expiration Date: When you must renew or upgrade your license.
4. Under License Server Configuration, modify the appropriate
information:
For License Server:
IP Address: The IP address or name of the server where the License
Server is installed.
Port: The license server port, default is 25035.
For Device Manager:
User ID: The Device Manager instance user account used by the
License Server. The user ID is always system (you cannot change
it).
Password: The password of the system user account in the Device
Manager instance used by the License Server.
HTTP/HTTPS (Web) Server Port: The Device Manager HTTP or
HTTPS port. The default port is 2001 for HTTP and 2443 for HTTPS.
SSL: Enable or disable SSL communication between the Command
Director server and Device Manager server.
Note: If you want to enable SSL, make sure SSL is enabled on the
Device Manager server before you select the SSL checkbox. For
more information about enabling SSL on the Device Manager server,
see Hitachi Command Suite Software Configuration Reference
Guide.
5. Under Enter License, in the Key field, enter the Hitachi Command
Director license key.
7. Confirm the license is successfully updated by viewing the displayed
message.
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.
84
Host discovery and agentless data gathering mechanism on page 8-5
Host access requirements on page 8-6
Viewing Host Collector information on page 8-6
Viewing details about a specific Storage System Collector on page 8-33
Configuring a new Host Collector on page 8-8
Configuring a new vCenter Collector on page 8-9
Launching Host Collector to discover hosts on page 8-10
Discovering hosts on the current subnet on page 8-11
Administering HCmD
Discovering hosts by specifying a range of host IP addresses on page 812
Discovering hosts by specifying a list of host IP addresses on page 8-13
Modifying Host Collector on page 8-13
Refreshing Host Collector data on page 8-14
Deleting Host Collectors on page 8-14
Viewing information about discovered hosts on page 8-15
Viewing information about discovered ESX hosts on page 8-16
Viewing information about discovered HNAS hosts on page 8-17
Validating host connectivity on page 8-18
Specifying host login settings on page 8-19
Modifying host login settings for specific hosts on page 8-21
Specifying data collection refresh frequency on page 8-22
Deleting hosts on page 8-24
Host discovery and agentless data gathering mechanism

You can use the Host Collector feature to agentlessly discover hosts on your
network and gather their file system and storage utilization information.
This allows HCmD to provide end-to-end mapping of the path from the host
to the subsystem volumes.
For example, lets 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 HCmD 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, HCmD allows you to see the big
picture of how your storage is used.
HCmD 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 Collectors
impact on the target environment, see Host Collector in a secure
environment on page A-2.
HCmD Host Discovery can discover hosts on the following platforms:
Windows
Hyper-V
ESX hosts using VMware vCenter Server
Linux
Solaris
HP-UX
AIX
Administering HCmD
85
HNAS
For information about the hosts and their versions supported by HCmD, see
Appendix A, Host Collector Support Matrix, 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, etc.). No proprietary
protocols are used.
Host access requirements

The host access requirements for the Host Collector:
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.
Viewing Host Collector information

You can view information about the Host Collectors currently configured for
your network.
To view information about all configured Host Collectors:
2. Under Data Collection, click Host Collectors.
The Host Collectors window is displayed.
86
Administering HCmD
Figure 8-1 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.
Last Execution: The local date and time when the most recent
operation was executed 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 the host information. This icon is
not displayed for the vCenter Collector as this functionality is not
applicable for vCenter.
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.
Administering HCmD
87
To enable the preconfigured Host Collector:

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.
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.
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 Servers
subnet, do these:
Install and start a Host Collector on a host from that subnet, which is
also visible to HCmD Servers subnet. See the Installing the Host
Collector Server on Other Subnets 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.
Configuring a new Host Collector

A default Host Collector is preconfigured and available to discover hosts on
the HCmD servers subnet. If you would also like to discover hosts on other
subnets, you must install and configure an Host Collector for each subnet.
To configure a new VMware vCenter Collector, see Configuring a new
vCenter Collector on page 8-9.
To configure a new Host Collector on a subnet in your network:
3. From the Host Collectors window, click New. The New Host Collector
dialog box appears.
88
Administering HCmD
Figure 8-2 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 Data 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.
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.
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.
To configure a new vCenter Collector:
3. From the Host Collectors window, click New. The New Host Data
Collector dialog box appears.
4. In the Name field, enter a unique name for this Host Collector that does
not exceed 32 characters.
Administering HCmD
89
5. From the Type drop-down menu, select vCenter.

The New Host Data Collector window displays information required for
vCenter.
Figure 8-3 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 the subnet.
If the list is empty, use the preconfigured Local Host Collector.
You return to the Host Collector window where the new vCenter Collector
is listed.
Launching Host Collector to discover hosts

Launch a configured Host Collector to locate the hosts of interest. Launching
helps to discover host information on other subnets and configure the Host
Collectors installed on these subnets.
To launch a Host Collector to discover hosts:
810
Administering HCmD
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 8-4 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 8-11.
Specify a range of host IP addresses.
For more information, see Discovering hosts by specifying a range of
host IP addresses on page 8-12.
Specify a list of host IP addresses.
For more information, see Discovering hosts by specifying a list of
host IP addresses on page 8-13.
6. Select any of the available options, and click Discover.
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 172.17.75.200, then the
Host Collector will locate all the hosts from 172.17.75.0 to 172.17.75.255.
To discover the hosts on the current subnet:
3. Select the Host Collector you want to launch.
).
Administering HCmD
811
5. To discover the hosts on the current subnet, select the <IP_address>

Subnet option.
6. Click Discover.
The Command Director proceeds to discover the hosts on the current
subnet.
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. HCmD 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: 172.17.75.12
Ending address: 172.17.75.25
Employing a wild card IP address range search. For example:

Starting address: 172.17.75.12
Ending address: *
This wildcard search would discover hosts from172.17.75.12 to
172.17.75.255.
Employing a wild card IP address subnet search. For example:

Starting address: 172.17.75.*
This wild card search would discover hosts from172.17.75.0 to
172.17.75.255
To specify a range of host IP addresses:

).

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.
812
Administering HCmD
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. HCmD validates the IP addresses that you
enter.
To specify a list of host IP addresses:
).

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.
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.
To change the name or port number of a selected Host Collector:
3. Select the Host Collector you want to modify.
4. In the Action column, click the Edit icon (
Administering HCmD
).
813
The Edit Host Collector dialog box 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 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.
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.
Refreshing Host Collector data

You can refresh the Host Collector data on all or selected Host Collectors.
To refresh the Host Collector data:
3. Select the Host Collectors you want to refresh.
4. Click Refresh.
HCmD initiates data collection for the selected registered data collectors,
including the Host Collector.
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.
814
Administering HCmD
To delete Host Collectors:

3. In the Host Collectors window, select the check box next to the Host
Collector you are deleting, then click Delete.
4. In the Confirmation dialog box, verify that you are deleting the
appropriate Host Collector, then click Yes.
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.
The information displayed in this tab is described in Viewing information
about discovered HNAS hosts on page 8-17.
ESX tab: Displays information about each of the ESX hosts discovered
using vCenter Server.
The information displayed in this tab is described in Viewing information
about discovered ESX hosts on page 8-16.
To view information about the discovered hosts:

3. In the Host Collectors window, click the Hosts tab.
The Hosts window is displayed.
Figure 8-5 Hosts window

This window provides host discovery information and functions:
Administering HCmD
815
Item
Description
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
Edit icon ( ): When a specific hosts 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.
Viewing information about discovered ESX hosts

HCmD discovers ESX hosts using the vCenter Collector.
To view information about discovered ESX hosts:
3. In the Host Collectors window, click the ESX tab.
The ESX window is displayed.
816
Administering HCmD
Figure 8-6 ESX window

This window provides the following information about ESX hosts:
Item
Description
ESX Server Name
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
IP address of the ESX server.
OS Details
The operating system details.
vCenter
The name of the vCenter Collector.
Last Operation
Whether the most recent operation was Refresh,

Scan, or Validation.
Last Execution
The local date and time when the most recent

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.
Viewing information about discovered HNAS hosts

You can view basic information about each of the discovered HNAS (Hitachi
NAS Platform) hosts.
To view information about discovered HNAS hosts:
3. In the Host Collectors window, click the HNAS tab.
The HNAS window is displayed.
Administering HCmD
817
Figure 8-7 HNAS window

This window provides host discovery information and functions as
described in the following table:
Item
Description
SMU
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.
Cluster
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 dash (-).
Node (s)
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.
Collect Performance
To enable performance data collection on the selected

cluster or standalone node, this checkbox must be
checked (the Collect Performance checkbox is enabled
by default). If you want to disable the collection of
performance data, click the checkbox to remove the
checkmark.
Status
The Status icons indicate whether the HNAS Data

Collector is collecting HNAS node performance data.
(
): Indicates that the HNAS Data Collector is
collecting performance data.
(
): Indicates that the HNAS Data Collector is
not collecting performance data.
Validating host connectivity

You can validate the connectivity between the Host Collector(s) 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.
818
Administering HCmD
To validate host connectivity:

3. In the Host Collectors window, click the Hosts tab.
4. In the Discovered Hosts window, select the host you want to validate its
connection.
5. Click Validate.
Specifying host login settings

To ensure proper communication between the Host Collector and the
remote hosts, you must specify the host login settings, which includes 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 logon 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 8-9.
To specify host login settings:
3. In the Host Collectors window, click the Host Login Settings tab.
The Host Login Settings dialog box is displayed.
Administering HCmD
819
Figure 8-8 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
Linux, Solaris,
HP-UX, AIX
820
Description
User ID
Enter the user name that will be used to log

on to the hosts.
Password
Enter the password used to log on to the

hosts.
Sudo
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.
SSH Port
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.
Administering HCmD
Tab
Windows
HNAS SMU
Setting
Description
User ID

on to the Windows or Hyper-V hosts.
If you have a domain user account, enter the
user name in this format:
<domain>\<user name>
Password

Windows or Hyper-V hosts.
Windows
Service
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.
User ID

on to the HNAS hosts.
Password

HNAS hosts.
SSH Port
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.
Modifying host login settings for specific hosts

To modify the host login settings for one or more specific hosts:
The Host Collector window is displayed.
3. Click the Hosts tab.
modify.
) in the Action column of the host you want to
The Edit Host Login Settings dialog box is displayed.
Administering HCmD
821
Figure 8-9 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, click the checkmark to disable 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 hosts login parameters, click OK.
The modified host login parameters overrides the Global OS Setting for this
host.
Specifying data collection refresh frequency

You can specify how often HCmD refreshes Data Collector and HNAS
performance data collection information.
To specify data collection refresh frequency:
3. In the Host Collectors window, click the Settings tab.
The Host Data Collection Settings dialog box appears.
822
Administering HCmD
Figure 8-10 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 in the Host Data Collection
Settings pane.
From the Data Refresh Frequency list, select how often you want to
refresh the Host Collector data. You have the following refresh frequency
options:
3 hours
4 hours
6 hours
12 hours
24 hours
5. Set the HNAS performance data collection in the HNAS Performance
Data Collection Settings pane.
From the Data Refresh Frequency list, select how often you want to
refresh the Host Collector data. You have the following refresh frequency
options:
1 hour
2 hours
3 hours
4 hours
6 hours
The host, HNAS, and vCenter data collectors are temporarily disabled to
allow your changes to take effect, and then enabled again.
Administering HCmD
823
Deleting hosts
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.
To delete hosts:
2. Under Data Collection, click Hosts.
3. Select the check box next to the host you are deleting, then click
Delete.
appropriate host, then click Yes.
Configuring Storage System Data Collectors

This module provides information to set up the various Storage System
Data Collectors for collecting configuration data and storage performance
data.
About storage system data collection on page 8-24
Viewing information about Storage System Collectors on page 8-25
Modifying Storage System Collectors on page 8-29
Deleting Storage System Collectors on page 8-31
Viewing storage system data collection history on page 8-31
Modifying how often data is refreshed on page 8-33
Manually refreshing data on page 8-34
Enabling and disabling Storage System Collectors on page 8-34
About storage system data collection

The Hitachi Command Director collects configuration data from Hitachi
Device Manager (HDvM), storage system performance data from Hitachi
Tuning Manager (HTnM), and tier information from Hitachi Tiered Storage
Manager (HTSM) every five minutes. This information is then aggregated for
SLO monitoring and reporting purposes.
Storage System Data Collectors that retrieve information from Tuning
Manager are referred to as HTnM Data Collectors and must be installed on
the same servers where Tuning Manager resides.
Storage System Data Collectors that retrieve 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.
824
Administering HCmD
You can view Storage System Collector information from Device Manager,
Tiered Storage Manager, and Tuning Manager by collector (collector view),
storage system (subsystems view), and activity (history log).
To generate relevant reports, configure your data collection appropriately.
Storage System Collectors can be added, modified, removed, and
temporarily disabled. You must configure a Storage System Collector for
every Device Manager and Tuning Manager instance you want to collect data
from.
Data collection management

After configuring storage system data collection, you can monitor whether
the data was retrieved successfully and when the Hitachi Command Director
(HCmD) 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 is collected every five minutes and
then correlated with the configuration data available at that point in time
with HCmD and used to update reports.
Figure 8-11 Data Collection diagram
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
To view information about Storage System Collectors:

Administering HCmD
825
2. Under Data Collection, click Storage System Collectors.

The Storage System Collectors window is displayed.
Figure 8-12 Storage System Collectors

This tab provides information for each Storage System Collector.
Item
Description
Name
The name associated with the Storage System Collector.
Type
Whether the Storage System Collector belongs to

Hitachi Device Manager (HDvM), Hitachi Tuning
Manager (HTnM), or the Hitachi Tiered Storage Manager
(HTSM).
IP Address
The IP address of the host using the Storage System

Collector.
Port
The port number for the Device Manager, Tuning

Manager, or Tiered Storage Manager. When a port other
then the default is specified during installation or
configuration, you can view it here.
User ID (for Device

Manager only)
The user ID associated with the Device Manager Data

Collector.
Last Operation
Which operation (scan or refresh) was performed and

whether it was successful or not.
Last Execution
The local date and time when the last operation

occurred on the HCmD Server.
Action
826
Enabled (ON): The Storage System Collector is

enabled (active).
To disable a Storage System Collector, click the ON
status for the appropriate data collector. The
selected data collector will be disabled, and the
status will change to OFF.
Disabled (OFF): The data collector is disabled
(inactive).
To enable a disabled Storage System Collector, click
the OFF status for the appropriate data collector.
The data collector will be enabled, and the status
icon will change to ON.
Edit icon ( ): Click this icon to modify the name,
port number, or HCmD Server IP address of a
specific Storage System Collector.
Administering HCmD
3. View your storage information by storage array. In the Storage System

Collectors window, click the Storage Systems tab.
This tab lists your storage information by storage array.
Item
Description
Storage System
The model and serial number of the storage array.
Total Capacity
The amount of storage available in the storage array.
# Volumes
The number of logical devices (storage disks) assigned

to the storage system.
Configuration Data (for

Hitachi Device Manager
only)
This column displays whether the Device Manager Data

Collector is enabled, whether the last attempt to
retrieve data was successful, any error messages, and
the data collectors IP address.
Performance Data (for

Hitachi Tuning Manager
only)
This column displays whether the Tuning Manager Data

Collector is enabled, whether the last attempt to
retrieve data was successful, any error messages, and
the Tuning Manager Data Collectors IP address.
Last Execution
The local date and time of the HCmD Server when the
data was last retrieved.
4. View storage domain information. In the Storage System Collectors

window, click the Storage Domains tab.
This tab displays the list of storage domains.
Item
Description
Storage Domains
The name of the storage domain.
Storage System
The name of the storage system assigned as the domain

controller of the specified storage domain.
# Tiers
The number of tiers defined in the specified storage

domain.
Tier Data Collector
The Storage System Collector type (HTSM) and its IP

address.
Last Execution
The local date and time of storage domain data

collection operations on the HCmD Server.
Configuring Storage System Collectors

If during the Hitachi Command Director installation you did not add all the
Hitachi Device Manager (HDvM), Hitachi Tuning Manager (HTnM), or Hitachi
Tiered Storage Manager (HTSM) data collectors, or there are new ones, you
can add them manually.
To add/configure Storage System Collectors:
3. Click New.
The New Data Collector dialog box is displayed.
Administering HCmD
827
Figure 8-13 New Storage System Collector

4. Use the information in the following table to specify information for each
data collector type:
Table 8-1 Host login settings

Type
HDvM
828
Setting
Description
IP Address
Type the IP address of the host using the

Device Manager Data Collector.
Name
Type the name associated with the Device

Manager Data Collector.
Port
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.
SSL
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 SSL is enabled on the Device
Manager server. For more information about
enabling SSL on the Device Manager server,
see Hitachi Command Suite Software
Configuration Reference Guide.
User ID
Type the user ID for Device Manager. The user

ID must have access to all the storage
systems registered in the Device Manager
server.
Password
Type the password for Device Manager.
Administering HCmD
Type
HTnM Data
Collector
HTSM
Setting
Description
IP Address
Type the IP address of the host using the

Tuning Manager Data Collector.
Name
Type the name associated with the Tuning

Port

HCmD Server IP
Address
Specify the IP address of the HCmD Server

used by the Tuning Manager Data Collector.
Password

IP Address
Select the IP address of the host using the

Device Manager and Tiered Storage Manager
Data Collector.
Name
Type the name associated with the Tiered

Storage Manager Data Collector.
Port
Specify the port number published for the

remote HTSM CLI client. The default port
number is 20352.
User ID
Enter the user name registered in HTSM. The

User ID must have reference and modify
permission.
Password
Enter the password for the user registered in

HTSM.
5. When finished specifying the data collector settings, click OK.
Modifying Storage System Collectors

If during the installation you did not configure all the Hitachi Device
Manager (HDvM), Hitachi Tuning Manager (HTnM), and Tiered Storage
Manager data collectors for the Hitachi Command Director, or there have
been changes, you can configure them manually.
To modify Storage System Collectors:
editing.
) for the storage system information you are
The Edit Storage System Collector dialog box is displayed.
Administering HCmD
829
Figure 8-14 Edit Storage System Collector

4. Use the information in the following table to modify appropriate
information for each data collector type:
Table 8-2 Host login settings

Type
HDvM
HTnM Data
Collector
830
Setting
Description
Name
Type the name associated with the Device

Port

User ID
Type the user ID for Device Manager. The user

ID must have access to all the storage
systems registered in the Device Manager
server.
Password
Type the password for Device Manager.
Name
Type the name associated with the Tuning

Port

HCmD Server IP
Address
Specify the IP address of the HCmD Server

used by the Tuning Manager Data Collector.
Password

Administering HCmD
Type
HTSM
Setting
Description
Name
Type the name associated with the Tiered

Storage Manager Data Collector.
Port
Specify the port number published for the

remote HTSM CLI client. The default port
number is 20352.
User ID
Enter the user name registered in HTSM. The

User ID must have reference and modify
permission.
Password
Enter the password for the user registered in

HTSM.
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, Tuning
Manager, or Tiered Storage Manager instance. 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 8-34.
To permanently delete Storage System Collectors:
3. Select the check box next to the Storage System Collector you are
deleting, then click Delete.
appropriate Storage System Collector, then click Yes.
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 Storage System Collector information is logged; storage
system information is not logged.
To view the storage system data collection and refresh activity history:
3. Click the History tab.
Administering HCmD
831
Figure 8-15 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), Hitachi Tuning Manager (HTnM), or the
Hitachi Tiered Storage Manager (HTSM).
IP Address: The server name or 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 HTnM and HDvM) and storage domains
managed by HTSM.
A Refresh operation collects detailed information about each of
the registered storage arrays and storage domains. HCmD collects
data from both the Device Manager and HTSM in one sequence.
Start: The date and time when the data from Device Manager or
Tuning Manager 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.
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: The model and serial number of the storage system
(storage array).
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 Collector
began to be scanned or gathered.
832
Administering HCmD
Status: Whether the last attempt to scan or gather data was

successful.
Viewing details about a specific Storage System Collector

To view details about the storage system data collection and refresh activity
for a specific Storage System Collector:
3. Click the History tab.
4. Select the Storage System Collectors whose information you want to
view details on.
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: The model and serial number of the storage system
(storage array).
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 Collector
began to be scanned or gathered.
Status: Whether the last attempt to scan or gather data was successful.
Modifying how often data is refreshed

To specify how often HCmD refreshes Data Collector information for reports,
follow these steps.
3. Click the Settings tab.
The 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.
Administering HCmD
833
Figure 8-16 Storage system data collection refresh settings

4. From the Data Refresh Frequency drop-down menu, select how often
you want to refresh the Data Collector data. You have the following
refresh frequency options:
1 hour
2 hours
3 hours
4 hours
6 hours
12 hours
24 hours
The Storage System Collectors are temporarily disabled to allow your
changes to take effect, and then enabled again.
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.
To manually refresh Storage System Collectors data:
3. Select the Storage System Collectors tab, Storage System tab, or
Storage Domains tab.
4. Click Refresh.
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 and Hitachi Tuning Manager
instances.
834
Administering HCmD
After Storage System Collectors are disabled, you can enable them again
and resume collecting data using the steps that follow.
Note that disabling collectors does not delete them.
To enable/disable specific Storage System Collectors:
2.
Under Data Collection, click Storage System Collectors.

The configured Storage System Collectors are displayed.
If a Storage System Collector is disabled, the Inactive icon (
next to it.
)appears
3. Click OFF to enable the Storage System Collector.

If a Storage System Collector is enabled, the Active icon (
next to it.
) appears
4. To disable a Storage System Collector, click ON to disable the Storage

System Collector.
Managing scheduled reports

The Scheduled Reports list includes information on every report that is
scheduled for generation and email 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 Administrators can delete the report
schedules and stop the report from being generated and emailed.
To view scheduled reports:
2. Under System Settings & Operations, click Scheduled Reports.
The Scheduled Reports window appears displaying the following
information:
Name: The name of the scheduled report.
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.
Schedule: When the report is generated and emailed.
Recipient(s): The user IDs and the email addresses of the persons
that receive the report.
Last Executed: When the report was last generated and sent
To stop scheduled reports:
1. In the Scheduled Reports window, select the check box next to the
report you are deleting and click Remove Schedule.
appropriate scheduled report, and then click Yes.
Administering HCmD
835
Configuring email servers

Configure the Simple Mail Transfer Protocol (SMTP) server and enable
HCmD to email alerts and reports.
If your SMTP email server changes, you must update it so that the email
feature can function.
To modify your email server:
2. Under System Settings & Operations, click Email Server.
The Email Server window is displayed.
Figure 8-17 Email server information

3. Modify the appropriate information:
IP Address: Enter the IP address or Domain Name System (DNS)
name of the host using the email server.
Port: Enter the email server port number. The default is 25.
4. To authenticate users and encrypt emails sent from the Hitachi
Command Director, enable 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.
Managing HCmD users

This module provides information about HCmD users, user roles, and user
management tasks.
836
About user management on page 8-37
User details on page 8-37
Viewing user information on page 8-37
Synchronizing user information on page 8-38
Administering HCmD
About user management

You must have a user account configured in Hitachi Device Manager to log
into Hitachi Command Director (HCmD). HCmD utilizes the user accounts
and passwords of the Hitachi Device Manager (HDvM) instance where you
installed the License Server.
User accounts (except email addresses) cannot be modified in HCmD. To
modify user accounts, log into the HDvM instance used by the License
Server and make the appropriate changes. Then, synchronize users in
HCmD.
User details
Hitachi Command Director (HCmD) utilizes the user accounts and
passwords of the Hitachi Device Manager instance where you installed the
License Server.
Note: All HCmD users are assigned an Admin role; Modify and View user
roles are not supported at this time.
HCmD user passwords

Passwords are case-sensitive and can have 256 characters. You can use the
following characters in HCmD user passwords:
A-Z
a-z
0-9
!#$%&'()*+-.=@\^_|
HCmD user IDs

User IDs (login names) can have 256 characters and are not case-sensitive.
You can use the following characters in HCmD user IDs:
A-Z
a-z
0-9
#+-_.@
Viewing user information

You can view every user account registered to use HCmD. User account
information is retrieved from the Device Manager instance where the
License Server resides.
To view HCmD users information:
2. Under System Settings & Operations, click Users.
The User window is displayed
Administering HCmD
837
Figure 8-18 User information

In the User window, the following information is displayed:
User ID: The user ID associated with the users password. You cannot
change user IDs.
Name: The users first and last name.
Description: A general description. For example, what operations the
user performs.
Role: The users role (Admin, Manage, or View). You cannot change
roles. HCmD, at this time, only supports the Admin user role.
Email: The email address used to send alerts and reports to the user.
Status:
Active icon (
(active).
): The users email address resides in HCmD.
Inactive icon (
HCmD (inactive).
): The users email address does not reside in
Synchronizing user information

You must synchronize user information with Device Manager to update the
user information in HCmD.
HCmD performs synchronization of user information automatically once
every day. You can also, if needed, perform synchronization manually.
To synchronize user accounts manually:
2. Under Systems Settings & Operations, click Users.
The Users window displaying account information for all registered
HCmD users appears.
3. In the User window, click Synchronize User Accounts.
A message indicating successful synchronization of user accounts with
HDvM appears.
838
Administering HCmD
4. Click OK to close the message dialog.

The user information from Device Manager is updated in HCmD.
Administering HCmD
839
840
Administering HCmD
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

A1
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 HCmD.
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:
Network Access
Service
OS
Microsoft Windows Ping
Authorization method
UNIX
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 section 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.
Data gathered with root access

The data gathered by the Host Collector if the user provides root access is
as follows:
A2
System: OS version, OS type, memory data
CPU: Type, speed, processor number
Device File Path Information: Device name, vendor ID, product ID, RAID
information, HBA PortWWN, HBA NodeWWN, storage data

Volume: Name, subdisk information, VDisk information, Volume

Manager, capacity data
Export: Name, file system name, type, options
HBA: Model, vendor, serial, HBA port information, WWN data
File System: Name, device name, volume name, usage data
Network: IP address, netmask, MAC address
Data gathered without root access

The data gathered by the Host Collector if the user does not provide root
access is as follows:
System: OS version, OS type, memory data
CPU: Type, speed, processor number
Export: Name, file system name, type, options
File System: Name, device name, volume name, usage data
Ports and services used

The Host Collector accesses each host to collect the necessary data for
analysis and reporting. It needs to 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 analysisping 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 typeSNMP and Telnet.

A3
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 systems 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.
Services on Windows hosts
A4
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
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 executionwith administrative permissionof 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.
Performance impact
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 Collectors performance impact:
Metric
Total Duration
Value
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%
Metric
Total Duration
Value
20 minutes
Network Traffic
Average
Peak
Utilization for a 100 Base-T Network

Average
0.12%
Peak
0.7%

A5
A6

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

B1
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.
HCmD 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
ifconfig
ndd
vxdctl
cat
ioctl
pkginfo
vxdg
devinfo
iscsiadm
powermt
vxdisk
df
labelit
prtvtoc
vxprint
echo
ls
sed
zfs
egrep
metaset
sharetab
zpool
format
metastat
uname
grep
mii-tool
vxdct
HP-UX
B2
awk
exportfs
lvdisplay
cat
grep
sed
df
ioscan
swlist
diskinfo
lanscan
uname

vgdisplay
AIX
awk
lsattr
lspv
svmon
cat
lsdev
lsvg
sed
df
lsfs
netstat
uname
grep
lslv
oslevel
Linux
awk
fdisk
lvdisplay
sed
cat
iconfig
lvscan
vgdisplay
chmod
iscsiadm
pvdisplay
vgs
df
ls
pvs
vxdct
e2label
lsdev
rpm
vxdisk
egrep
lsscsi
sort
grep
lvm
uname
Requirements for account used for configuration gathering

operation using sudo
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 users PATH environment variable and
execute permission has been provided to the user.
Sample content of sudoers file

The following are the examples of the sudo files used to access the target
host:
Note: It is recommended to run the following examples using the visudo
command. Refer to the relevant sudo manual for more information.
sudoers file without 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# e.g. In case of "hdcadmin" user
hdcadmin
ALL=(ALL) NOPASSWD:/tmp/FsDataGatherLauncher.Unix.sh

B3
sudoers file with 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?## e.g. In case of "hdcadmin"
user?hdcadmin ALL=(ALL) /tmp/FsDataGatherLauncher.Unix.sh?
B4

Glossary
This glossary defines some terms used in this document. Click a letter at the
bottom of a page to display the terms that start with that letter.
A
alert
An event that is generated when an SLO is violated. You can also set up
email notifications with the event details.
allocated volume
A logical device (LDEV) for which one or more host paths are defined.
application
In Hitachi Command Director, applications represent groups of storage
volumes used by an actual application. An application can be defined by
LDEVs belonging to a Host Group or by storage consumed by a physical
host discovered by the HCmD agentless Host Collector.
sub-application
A sub-application is a subset of storage volumes that belong to an
application. By default, every application in Hitachi Command Director
has at least one sub-application. Multiple sub-applications can be
created for each application to define different SLO profiles against
different parts of the application. For example, an Oracle Database subapplication has very different performance SLO from the Log Application
sub-application.
array group
A set of hard disk drives in a storage system (storage array) 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.
# A B C D E F
G H II
K L
M N O P Q R S T U V W X Y Z
Glossary1
B
BPS
A folder hierarchy of hosts, applications, and other folders organized 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.
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.
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.
cluster
Multiple-storage servers working together to respond to multiple read
and write requests.
CLI
Command Line Interface. A method of interacting with an operating
system or software using a command line interpreter. With Hitachis
Storage Navigator Modular Command Line Interface, CLI is used to
interact with and manage Hitachi storage and replication systems.
CLPR
Cache Logical Partition. Refers to partitioned cache memory. CLPRs can
be used to segment storage array cache assigned to parity groups.
D
data collection
A method of discovering and gathering information from the Storage
System collectors on the Hitachi Device Manager and Hitachi Tuning
# A B C D E F
G H II
K L
Glossary2
Manager servers and the Host Collectors installed on hosts in the

network.
data drive
A physical data storage device that can be either a hard disk drive (HDD)
or a flash (solid-state) drive.
data pool
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.
data refresh
Collecting information from the data collectors on the Hitachi Device
Manager and Hitachi Tuning Manager 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.
DP-VOL
Dynamic Provisioning virtual volume. A virtual volume with no memory
space used by Dynamic Provisioning.
Dynamic Provisioning (DP)

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.
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.
# A B C D E F
G H II
K L
Glossary3
E
external volume
A logical volume whose data resides on drives that are physically located
outside the storage system.
G
GUI (Graphical User Interface)
The graphical user interface of a software program.
H
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.
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.
High-performance NAS Platform (HNAS)

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.
host
One or more host bus adapter (HBA) world wide names (WWN).
# A B C D E F
G H II
K L
Glossary4
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
array. 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
Hitachi Tiered Storage Manager. Tiered Storage Manager is 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.
I
IO (Input/Output)
Input/output.
IOPS
I/Os per second.
IP
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.
# A B C D E F
G H II
K L
Glossary5
K
key performance indicator (KPI)
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.
L
LAN
Local Area Network. A computer network that spans a relatively small
area, such as a single building or group of buildings.
logical volume
An area on a disk consisting of device files that are logically integrated
using a volume manager. Also referred to as LDEV.
LU (Logical Unit)
A volume created in a storage system, known as an LU (logical unit) in
an open system.
LUN (Logical Unit Number)

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 array. 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
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 are 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
back to a host, a cluster, or an application as represented by the set of
host WWNs.
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.
# A B C D E F
G H II
K L
Glossary6
M
monitoring window
Specifies when the application is monitored by the SLO profile. Multiple
schedules (time periods) can be assigned to the same monitoring
window.
MS IIS (Microsoft Internet Information Services)

A set of Internet-based services in a web server, for servers using
Microsoft Windows.
N
NAS
Network Attached storage.
High-performance NAS Platform/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.
O
owner group
A logical unit (LU) group provisioned to the same set of WWNs.
P
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
# A B C D E F
G H II
K L
Glossary7
always just use the entire RAID group as a single parity group and create
one big LUN.
pool
A set of volumes that are reserved for storing Copy-on-Write Snapshot
data or Dynamic Provisioning write data.
pool volume
pool-VOL. A logical volume that is reserved for storing snapshot data for
Copy-on-Write Snapshot operations or write data for Dynamic
Provisioning.
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).
R
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.
S
SAN
Storage Area Network. A network of shared storage devices that contain
disks for storing data.
SATA
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
# A B C D E F
G H II
K L
Glossary8
are storage administrators (who provide storage) and their clients

(application administrators who request storage).
Service Level Objective (SLO)

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.
SLO investigation unit

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.
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 email data directly from email
servers.
SPARC (Scalable Processor Architecture)

A reduced instruction set computer (RISC) architecture developed by
Sun Microsystems and used in the Sun workstation family.
SQL
Structured Query Language used to communicate with a database.
SSL (Secure Sockets Layer)

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.
Subsystem
The Hitachi enterprise storage box for the Universal Storage Platform
(USP, USP-V, USP-VM) and the Network Storage Controller (NSC).
# A B C D E F
G H II
K L
Glossary9
S-VOL (secondary volume)

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.
switch
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.
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
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, subsystem
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.
U
unallocated volume
An volume for which no host paths are assigned.
V
VM
Virtual Machine.
# A B C D E F
G H II
K L
Glossary10
VMDK File
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.
V-VOL (virtual volume)

The secondary volume in a Snapshot pair. When in PAIR status, the VVOL 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.
volume
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).
W
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). The 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.
# A B C D E F
G H II
K L
Glossary11
# A B C D E F
G H II
K L
Glossary12
Index
A
options 33
Application Data Distribution by Tier report 711

application reports
Application Response Time Trend report 59
Application Summary report 55
available in HCmD 53
Cache Write Pending % report 518
Capacity Allocation Trend report 59
DP Pool Over Provisioning Ratio report 518
DP Pool Risk Ratio report 519
DP Pool Used % report 519
DP Pool Utilization report 513
File System Utilization report 57
IO Utilization Trend report 510
Parity Group Busy % report 520
Port Busy % report 520
SLO Details report 57
SLO Status report 55
Storage Allocation Details report 512
Storage Allocation report 56
Storage Paths report 515
Storage System and Host SLOs report 517
Storage System Performance report 56
Tier Definition report 516
Application SLO 43
Application SLO conformance report 710
Application Storage Allocation by Tier
report 715
Application Storage by Pool report 715
applications
about 32
creating automatically 39
creating manually 36
deleting 314
modifying 311
asset and inventory report
file system inventory 713
Physical server inventory 714
Storage system inventory 712
asset and inventory report gallery 72
auto create
applications 33
B
business views
all applications view 322
creating new 322
custom 318
deleting 324
displaying 317
file servers view 320
hosts view 319
Logical Group view 318
managing 324
C
chargeback report gallery 72
chargeback reports
Application storage allocation by tier 715
Application storage by pool 715
D
dashboard
about 22
accessing 23
customizing 23
dashboard reports
Applications Missing SLO report 24
Applications with Most SLO Misses report 27
HDP Capacity Overview report 210
HNAS Capacity Overview report 212
Hyper-V File System Overview report 29
IOPS SLO Status report 25
Response Time SLO Status report 25
Storage System Capacity Overview
report 28
Storage System Performance Overview
report 26
Top 5 Busiest HNAS Nodes report 211
VMware Datastore Overview report 29
Index-1
updating 83
email servers
default server port number 836
modifying configuration 836
ESH hosts
viewing configuration information 816
M
monitoring windows
about 415
creating new 416
deleting 419
modifying 418
File System Inventory report 713
performance reporst
Top 20 busiest storage system ports 78
performance report
Application SLO conformance 710
performance report gallery 72
performance reports
HDP Pool storage performance 77
Storage port workload 77
Top 20 busiest parity groups 79
Top 20 busiest volumes 79
Physical capacity by Storage Systems report 73
Physical Server Inventory report 714
ping A3
HDP Pool Storage Performance report 77

HDP, HDT capacity by Storage Systems
report 73
HDP, HDT pool usage by application report 76
HNAS reports
File System IO Trend report 67
File System Load Trend report 68
HNAS File System report 68
HNAS Pool Details report 69
HNAS Pool Summary report 69
HNAS Shares report 611
Protocol Op/s Trend report 611
Total Throughput Trend report 612
Host Collector
data gathered with and without root
access A2
using in secure environment A2
Host Collectors
agentless data gathering mechanism 85
configuring new 88
deleting 814
deleting hosts 824
discovering hosts by IP address 812
discovering hosts by IP address list 813
discovering hosts on subnet 811
host login settings 819
launching 810
modifying 813
refreshing 814
specifying data collection frequency 822
validating connectivity 818
vCenter collector 89
host reports
ESX Server Data Stores report 615
ESX Server VMDKs report 615
Host File System Used % report 63
Hyper-V Server report 614
Storage Utilization report 64
Volume Manager Group report 65
L
licenses
about 82
registering 17
types of 83
R
report gallery 72
report gallery categories 72
S
scheduled reports
removing 835
scheduling 835
secure sockets layer (SSL)
enabling during license registration 18
enabling for Device Manager Storage System
collector 828
Service Level Objective (SLO)
overview 42
types 43
Service Level Objective (SLO) profiles
about 46
creating new 48
deleting 411
modifying 49
Service Level Objective (SLO) types
removing 410
SNMP A4
storage economics report gallery 72
storage economics reports
Application data distribution by tier 711
Top 10 tiers by capacity 711
Underutilized host file systems 711
Storage Port Workload report 77
Storage System and host SLO 43
Storage System Collectors
about 824
configuring 827
deleting 831
Index-2
disabling 834
enabling 834
modifying 829
modifying refresh frequency 833
Storage System health threshold
about 44
modifying 45
Storage System Inventory report 712
storage system performance reports
DTR Distribution by Storage System
report 213
IOPS Distribution by Storage System
report 212
Read Hit % by Storage System report 214
Response Time % by Storage System
report 216
Write Pending % by Storage System
report 215
Sudo
account requirements B3
binaries used for configuration gather
operation B2
command used by Gather binary B2
T
tags and tag categories
managing 315
telnet A4
Top 10 Tiers by Capacity report 711
Top 20 Busiest Parity Groups 79
Top 20 Busiest Storage System Ports report 78
Top 20 Busiest Volumes report 79
U
Underutilized Host File Systems report 711
user passwords 837
user profile
modifying 19
password, changing 19
user roles 837
users
viewing users information 837
users accounts
synchronizing 838
utilization report gallery 72
utilization reports
HDP, HDT capacity by Storage Systems 73
HDP, HDT pool usage by application 76
Physical capacity by Storage System 73
V
vCenter collector
configuring new 89
viewing ESX hosts 816
Index-3
Index-4
1
Hitachi Data Systems

Corporate Headquarters
750 Central Expressway
Santa Clara, California 95050-2627
U.S.A.
Phone: 1 408 970 1000
www.hds.com
info@hds.com
Asia Pacific and Americas
750 Central Expressway
Santa Clara, California 95050-2627
U.S.A.
Phone: 1 408 970 1000
info@hds.com
Europe Headquarters
Sefton Park
Stoke Poges
Buckinghamshire SL2 4HD
United Kingdom
Phone: + 44 (0)1753 618000
info.eu@hds.com
MK-90HCMD001-03

Hitachi COmmand Director

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Hitachi COmmand Director

Hochgeladen von

Copyright:

Verfügbare Formate

Hitachi Command Suite

Command Director Software

Quick access to your application status and storage health . . . . . . 2-1

IOPS SLO status . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Managing resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Monitoring applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Supported SLO types . . . . . . . . . . . . . . . . . . . .

Reporting on applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Parity Group busy % report . . . . . .

Reporting on hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Report Gallery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Top 20 busiest volumes . . . . . . . . . .

Administering HCmD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

About storage system data collection . . . . . . . . . . . . . .

Using Host Collector in a secure environment . . . . . . . . . . . . . . . . A-1

Setting up configuration gathering operation using sudo . . . . . . . . B-1

Document revision level

Conventions for storage capacity values

Accessing product documentation

Hitachi Device Manager, Hitachi Tuning Manager, Hitachi Tiered Storage

Storage array and performance concepts

Service Level Objectives (SLOs) and Service Level Agreements (SLAs)

Document revision level

Revision 1, supersedes and replaces MK90HCMD001-00

Revision 2, supersedes and replaces MK90HCMD001-01

Revision 3, supersedes and replaces MK90HCMD001-02

Hitachi Command Director Installation and Configuration guide, MK90HCMD002

Hitachi Command Director Release Notes, RN-90HCMD003

Hitachi Command Suite Software Documentation

Hitachi Command Suite Software Tuning Manager Documentation

Hitachi Command Suite Software Tiered Storage Manager

Indicates text on a window, other than the window title,

Indicates a variable, which is a placeholder for actual text

Indicates text that is displayed on screen or entered by the

< > angled brackets

Indicates a variable, which is a placeholder for actual text

Indicates optional values. Example: [ a | b ] indicates that you

This document uses the following icons to draw attention to information:

Tips provide helpful information, guidelines, or

Notes emphasize or supplement important points of the

Cautions indicate that failure to take a specified action

Conventions for storage capacity values

1 TB (terabyte) = 1,0244 bytes

1 MB (megabyte) = 1,0242 bytes

1 PB (petabyte) = 1,0245 bytes

1 GB (gigabyte) = 1,0243 bytes

1 EB (exabyte) = 1,0246 bytes

Hard Disk Drives (HDDs) (Physical Disk Capacity)

Hard Disk Drives (HDDs) (Physical Disk Capacity)

Accessing product documentation

About Hitachi Command Director (HCmD)

New in Command Director 7.1.1

Specifying email address when you first log in

Modifying your user profile

HCmD graphical user interface

About Hitachi Command Director (HCmD)

Monitoring application storage. Define corporate-wide standard Service

Monitoring Hitachi enterprise storage health. You can detect potential

Generating Key Performance Indicator reports that align your storage

A global dashboard that provides you access to real-time enterprise

The application SLO Investigation Unit that lets storage administrators

An option to create applications automatically from the LUN Owner

New in Command Director 7.1.1