Storage Monitor Installation Guide

Installation and Setup Guide

vFoglight® Storage 1.6.1

© 2012 Quest Software, Inc. ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com email: [email protected]

Refer to our Web site for regional and international office information.

Trademarks

Quest, Quest Software, the Quest Software logo, Foglight, IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD, Tag and Follow, Vintela Single Sign-on for Java, and vFoglight are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software’s trademarks, please see http://www.quest.com/legal/trademark-information.aspx. Other trademarks and registered trademarks are property of their respective owners.

Third Party Contributions

vFoglight Storage contains some third party components. For a complete list, see the License Credits page in vFoglight Storage online help.

Installation and Setup Guide March 2012 Version 1.6.1

http://www.quest.com/legal/trademark-information.aspx

http://www.quest.com/legal/trademark-information.aspx

http://www.quest.com

mailto:[email protected]

Table of Contents

vFoglight Storage: Installation and Setup Guide 3

Introduction to this Guide..................................................................................................................................................6

About Quest Software, Inc. ............................................................................................................................................................. 6

Contacting Quest Software ..................................................................................................................................................... 6

Contacting Quest Support ....................................................................................................................................................... 6

Installation Overview..........................................................................................................................................................8

The Steps Required to Install Configure, or Upgrade vFoglight Storage ........................................................................................ 8

vFoglight Storage Hardware, System, and Database Requirements...........................................................................10

Hardware Requirements ............................................................................................................................................................... 10

Environment Size Definitions ................................................................................................................................................ 11

Hardware Requirements for a Small Environment ................................................................................................................ 11

Hardware Requirements for a Moderate Sized Environment................................................................................................ 12

Hardware Requirements for a Large Environment................................................................................................................ 12

vFoglight Storage Databases Requirements................................................................................................................................. 13

Database Disk Space Requirements ............................................................................................................................................ 13

Network Port Requirements .......................................................................................................................................................... 14

Supported Platforms...................................................................................................................................................................... 15

Using VMware Virtual Machines ........................................................................................................................................... 15

Supported Platforms for the vFoglight Storage Client ........................................................................................................... 15

VMware Platforms ................................................................................................................................................................. 16

Storage Devices ............................................................................................................................................................................ 16

NetApp Filers......................................................................................................................................................................... 17

NetApp Collection Configuration Requirements ............................................................................................................ 17

Required User Account Privileges................................................................................................................................. 17

Storage Arrays ...................................................................................................................................................................... 17

CLARiiON Configuration Requirements ........................................................................................................................ 18

HP EVA Arrays .............................................................................................................................................................. 19

HDS AMS ...................................................................................................................................................................... 19

Fibre Channel Switches ........................................................................................................................................................ 19

Brocade® SAN Switch Collection Configuration Requirements .................................................................................... 20

Cisco® SAN Switch Collection Configuration Requirements ........................................................................................ 20

Installing vFoglight Storage ............................................................................................................................................22

Installation on a Virtual Machine ................................................................................................................................................... 22


Table of Contents

Preparing to Install vFoglight Storage............................................................................................................................................ 22

Installing vFoglight Storage ........................................................................................................................................................... 23

Uninstalling vFoglight Storage ....................................................................................................................................................... 32

Configuring vFoglight Storage to Collect Data ............................................................................................................. 35

Required vCenter User Account Privileges ................................................................................................................................... 35

Configuring Accounts..................................................................................................................................................................... 35

Account Alias ......................................................................................................................................................................... 36

Account Name and Password/Key ................................................................................................................................ 36

Account Types ...................................................................................................................................................................... 36

Operating System Accounts .......................................................................................................................................... 36

Integrated Application Accounts .................................................................................................................................... 36

Setting Up an Account ................................................................................................................................................... 36

Configuring Connections ............................................................................................................................................................... 39

vCenter/vSphere Connection................................................................................................................................................. 39

Setting Up a vCenter Connection ................................................................................................................................. 40

Validating the vCenter Connection ................................................................................................................................ 42

Initiating vCenter Data Collection................................................................................................................................... 43

Fiber Channel (FC) Switch Connection ................................................................................................................................. 44

Setting Up the FC Switch Connection............................................................................................................................ 44

Validating the FC Switch Connection............................................................................................................................. 46

Initiating FC Switch Data Collection .............................................................................................................................. 46

Filers Connection ................................................................................................................................................................... 47

Setting Up a Filer Connection ........................................................................................................................................ 47

Validating a Filer Connection ......................................................................................................................................... 49

Initiating Filer Data Collection ........................................................................................................................................ 50

Storage Array Connection...................................................................................................................................................... 50

EMC CLARiiON ............................................................................................................................................................. 50

Setting up an EMC Array Connection ............................................................................................................................ 51

Validating the EMC Array Connection ........................................................................................................................... 53

Initiating an EMC Clarion Array Connection .................................................................................................................. 54

HP EVA.......................................................................................................................................................................... 55

Setting Up the HP EVA Array ........................................................................................................................................ 55

Validating the HP EVA Connection................................................................................................................................ 58

Initiating HP EVA Data Collection .................................................................................................................................. 59

Hitachi AMS ................................................................................................................................................................... 60

Setting Up the Hitachi AMS Array.................................................................................................................................. 61

Validating the Hitachi AMS Connection ......................................................................................................................... 65

Initiating Hitachi AMS Data Collection ........................................................................................................................... 66

Configuring Collection Schedules.................................................................................................................................................. 67

Selecting an Existing Schedule.............................................................................................................................................. 71


Table of Contents

Blackout Windows.................................................................................................................................................................. 71

Upgrading vFoglight Storage.......................................................................................................................................... 73

Express Upgrade ........................................................................................................................................................................... 74

Advanced Upgrade ........................................................................................................................................................................ 75

Upgrading the Existing Database .......................................................................................................................................... 76

Restore from Archive and Upgrade ....................................................................................................................................... 77

Upgrading vFoglight Storage Version 1.6.0 or Earlier ........................................................................................................... 80

Introduction to this Guide

Welcome to vFoglight Storage. This guide walks you through the procedures to configure, install, and upgrade vFoglight Storage. In addition, it provides details on system, hardware, and database requirements. For detailed procedures on using vFoglight Storage to monitor your database environment, see the vFoglight Storage User Guide.

About Quest Software, Inc.Quest Software (Nasdaq: QSFT) simplifies and reduces the cost of managing IT for more than 100,000 customers worldwide. Our innovative solutions make solving the toughest IT management problems easier, enabling customers to save time and money across physical, virtual and cloud environments. For more information about Quest solutions for administration and automation, data protection, development and optimization, identity and access management, migration and consolidation, and performance monitoring, go to www.quest.com.

Contacting Quest Software

Refer to our Web site for regional and international office information.

Contacting Quest SupportQuest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides

Email [email protected]

Mail Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA

Web site www.quest.com

mailto:[email protected]




Introduction to this Guide

unlimited 24x7 access to our support portal. Visit our support portal at http://www.quest.com/support.

From our support portal, you can do the following:

• Retrieve thousands of solutions from our Knowledge Base

• Download the latest releases and service packs

• Create, update, and review Support cases

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies, and procedures. The guide is available at: http://www.quest.com/support.

http://www.quest.com/support




1

Installation Overview

vFoglight Storage monitors virtual environments, providing performance and capacity management metrics to assist you in:

• Improving management of VMWare environments from host to storage.

• Gaining the information required to optimize storage performance associated with your virtual server environment.

• Ensuring service level agreements are obtained.

• Maintaining high levels of customer satisfaction.

• Avoiding the loss of cost savings already achieved with virtualization.

vFoglight Storage gathers extensive performance metrics and presents that data in a graphical interface utilizing architectural diagrams, graphs, alerts, and drill-down screens to quickly identify virtual and physical storage problems. It fully supports VMware, vCenter, and vSphere environments, allowing users to browse through their virtual infrastructure to identify storage performance, capacity, or topology issues.

The Steps Required to Install Configure, or Upgrade vFoglight Storage

The following provides the steps required to prepare, install, configure, and upgrade vFoglight Storage:

1 Before installing vFoglight Storage, review the required installation components. Ensure that you have the necessary port numbers, server names, and their locations. The following provides details on pre-installation configuration requirements:

a “Hardware Requirements” on page 10.

b “vFoglight Storage Databases Requirements” on page 13.

c “Database Disk Space Requirements” on page 13.

d “Network Port Requirements” on page 14.

e “Supported Platforms” on page 15

f “Supported Platforms for the vFoglight Storage Client” on page 15

g “Storage Devices” on page 16


Chapter 1—Installation Overview

2 “Installing vFoglight Storage” on page 22.

3 Ensure that appropriate credentials and connections are configured on each target from which vFoglight Storage collects data. See “Configuring vFoglight Storage to Collect Data” on page 35.

4 “Upgrading vFoglight Storage” on page 73.

2

vFoglight Storage Hardware, System, and Database Requirements

The hardware, system, and database requirements needed to install Foglight Storage vary depending on the number and type of objects for the type of data being collected. This chapter provides the following pre-installation details:

• Hardware Requirements

• vFoglight Storage Databases Requirements

• Database Disk Space Requirements

• Network Port Requirements

• Supported Platforms

• Storage Devices

Important At a minimum, you are required to provide hardware matching or exceeding the specifications in this chapter. You should not consider doing a production implementation without conducting a proper scoping and sizing exercise. To arrange for a sizing analysis, contact your Quest Software Sales representative.

Hardware RequirementsThe hardware needed to run vFoglight Storage depends on the following factors:

• The number and type of collectors being used.

• The persistence and data-rollup policies. (See the vFoglight Storage User Guide for details on data-rollup policies.)

• Collector configuration settings.

Due to the potential for a large number of objects being collected, analyzed, and maintained by the application, there are several aspects of the underlying server that must be taken into account. The sizing of the supporting server or virtual machine depends upon the size of the underlying environment.


Chapter 2—vFoglight Storage Hardware, System, and Database Requirements

Environment Size Definitions The following provides environment sizing definitions:

• Small Collection Environment—Up to six ESX/ESXi hosts per vCenter.

• Medium Collection Environment—Up to 24 ESX/ESXi hosts per vCenter.

• Large Collection Environment—Up to 60 ESX/ESXi hosts per vCenter.

• Above 60 ESX/EXSi hosts per vCenter—Contact your Quest Sales Engineer.

Sufficient processing power and memory must be present to support effective collection and server data handling and analytics. Collected data is staged in memory prior to passing to the integrated collector database repository. Large filers, arrays, or virtual environments may contain multiple MBs (or GBs) worth of streaming data. During collection, a minimum of one GB of memory is required for the Collector. In addition, the server attempts to retain significant calculation and analytic results in memory to support fast user interface response time. A minimum of 1.5 GBs of memory is required with three GBs recommended. The server and collector are run as individual processes. Two cores are recommended, with each core operating at a minimum of 1.8 GHz.

The following sections provide:

• Hardware Requirements for a Small Environment

• Hardware Requirements for a Moderate Sized Environment

• Hardware Requirements for a Large Environment

Hardware Requirements for a Small EnvironmentThe following table provides hardware requirements for small vFoglight Storage environments.

Example Small Environment

Feature Minimum Recommended

CPU Speed 1.8 GHz 2+GHz

CPU Cores 1 2

Memory 2.0 GB 2+GB

Network 10/100 GE

OS Windows Server 2003

.Net Runtime 3.5 (required)

Disk Space 10 GB 20 GB

# of Spindles 2 4




Hardware Requirements for a Moderate Sized EnvironmentThe following table provides hardware requirements for moderately sized vFoglight Storage environments.

Hardware Requirements for a Large EnvironmentThe following table provides hardware requirements for large vFoglight Storage environments.

Example Moderate Environment


CPU Speed 1.8 GHz 2+ GHz

CPU Cores 2 4

Memory 2.0 GB 4+GB

Network 10/100 GE

OS Windows Server 2008 R2 (x64)



# of Spindles 2 4

Example of a Large Environment


CPU Speed 2.2 GHz 2.5 GHz

CPU Cores 4 6

Memory 4.0 GB 8+ GB

Network 10/100 GE

OS Windows Server 2008 R2 (x64)



# of Spindles 4 4



A minimum of a single 100 BaseT (or equivalent) network is required to support the collection streams. It is recommended that the IP port on the vFoglight Application server be non-shared and fully usable by the application. A Gbit Ethernet network provides the fastest collection.

vFoglight Storage Databases RequirementsvFoglight Storage utilizes three PostgreSQL databases:

• prismdb—this database is used by the vFoglight Storage server. User interface configurations and application analytics use this data.

• hdccs—a temporary collection database used to minimize the impact of collection activity. Data is processed minimally and then imported into the server database.

• hztracedb—a trace database used for logging and trace information.

Important For performance reasons, it is highly recommended that the three vFoglight Storage Databases (prismdb, hztracedb, and hdccs) be installed on separate physical drives or LUNs and not be co-located with the program files. If this is not possible, then separate the vFoglight Storage program files and the prismdb across different physical disks or LUNs, with the hztracedb and hdccs databases being installed on the same physical disk or LUN as the vFoglight Storage program files. The vFoglight Storage program files can be installed on the boot drive of the server being used (C: drive). The install process provides a separate installation path for the PostgreSQL Databases.

Database Disk Space RequirementsTo maintain reasonable memory loads and peak input/output performance, the vFoglight Storage program files and PostgreSQL database should be run on separate physical drives or LUNs. The following disk/spindle partitioning is recommended:

Note For best performance, the Windows page file should not be located on the same disk as the Server database (prismdb).

With Two Physical Disks

• The application, collector DB (hdccs), and trace database (hztracedb) can be co-resident on the first disk (typically Windows System Disk - C:).

• The server database (prismdb) should be on the second disk.

With Three Physical Disks

• The application and trace database (hztracedb) can be co-resident on first disk (typically Windows System Disk - C:).

• The collector database (hdccs) should reside on the second disk.

• The server database (prismdb) should reside on the third disk.



With Four Physical Disks

• The application can reside on the first disk (typically Windows System Disk - C:).

• The collector database (hdccs) should reside on the second disk.

• The server database (prismdb) should reside on the third disk.

• The trace database (hztracedb) should reside on the fourth disk.

The amount of disk space required varies directly with the size of the environment under management. For the previously defined small environment, 8 GBs of space is a minimum with 15 GBs recommended. This memory is apportioned as follows:

• Application— 4-7 GBs (most of this space is consumed by the DB transaction logs).

• Server DB (prismdb):

• Small environments—12 GBs

• Medium environments—36 GBs

• Large environments—360 GBs

Note The server database retains up to 30 days worth of data and is directly proportional to the size of the environment being managed.

• Collector DB (hdccs):



• Large enviroments—10 GBs

Note The collector database is directly proportional to the size of the collected data stream and the number of overlapping collections, dictated by the collection schedule with a default of two days history.

• Trace DB (hztracedb):



• Large environents—4 GBs

Note The trace database is fairly constant and indirectly related to the size of the environment under management with a default of seven days worth of history.

Network Port RequirementsvFoglight Storage makes use of standard TCP/IP ports for its collections. These ports must be opened and traffic allowed between the target (the server or object being collected) and the vFoglight Storage server. The following provides port requirement parameters:

• Cisco—SSH to each switch using the SAN OS/NX OS CLI on port 22.

• Brocade—SMI-S query using 5988/TCP (non-SSL) or 5989/TCP (SSL) to the management host.

• HP EVA—SMI-S query using 5988/TCP (non-SSL) to the management host. This value can be changed during configuration.



• VMware—VI API on port 443/TCP to vCenter/vSphere.

• CLARiiON Unix—Navisphere connection to the management host requires port 22 (SSH).

• CLARiiON Windows—Navisphere connection to the management host via WMI (RPC) using 135/TCP and 445/TCP.

• NaviSecCLI—the default port is 443 (UNIX and Windows). You can change the default port.

Note Mark down this port number so you have it during the installation process.

• NetApp—DataOnTap API query using 80/TCP or 443/TCP to each filer using port 4231.

• vCenter—vCenter SDK uses ports 80 and 443.

• User Interface to Server—general a TCP connection using port 4231.

Note iSCSI must not be configured for any server IP port.

Supported PlatformsvFoglight Storage requires a physical or virtual machine running one of the following operating systems.

Note vFoglight Storage requires Microsoft .NET Framework 3.5 SP1.

• Windows 2003 Server SP2 (x86 or x64)

• Windows Server 2008 SP2 (x86 or x64)

• Windows Server 2008 R2 (x64)

Important The server on which the vFoglight Storage server is installed must be configured to use “English_United States” for both the System Locale and Input Locale.

Using VMware Virtual MachinesWhile the use of VMware virtual machines to host the application is supported, it is recommended that a physical host be used for any large production deployment of vFoglight Storage. The vFoglight Storage application makes extensive use of the underlying PostgreSQL databases and tablespaces. The application requires the same considerations that any production database application receives in terms of input/output and CPU performance.

Supported Platforms for the vFoglight Storage ClientThe vFoglight Storage installer allows for installation of the clients separately from the vFoglight Storage Server. The following provides a list of operating systems supported for installation of the vFoglight Storage Client:



• Windows XP (x86)

• Windows Vista (x86, x64)

• Windows 7 (x86, x64)

• Windows Server 2003 (x86)

• Windows Server 2008 (x86)

VMware PlatformsVMware vCenter Server (formerly VMware VirtualCenter) centrally manages VMware vSphere environments. It is through vCenter (vCenter Server) that vFoglight Storage collects all information about the VMware environment.

vFoglight Storage uses the vCenter vAPI to collect datastore, ESX host, and VM guest information. There is no need to collect separately from ESX Hosts.

The following versions of VMware vCenter are supported:

• VMware vCenter 2.5

• VMware vCenter 2.5 Update 1










Storage DevicesvFoglight Storage collects data from:

• “NetApp Filers” on page 17

• “Storage Arrays” on page 17

• “CLARiiON Configuration Requirements” on page 18

• “HP EVA Arrays” on page 19

• “HDS AMS” on page 19

• “Fibre Channel Switches” on page 19



NetApp FilersvFoglight Storage collects data from NetApp filers. The following provides requirements and privileges.

NetApp Collection Configuration Requirements

vFoglight Storage collects storage inventory, data protection, performance, and association information from NetApp filers by utilizing the native DataONTAP® API (version 7.2.1 or later). This requires an integrated account for collecting from NetApp Filers.

Note When collecting from a MultiStore enabled filer, an account is only required on the physical filer (vFiler0), which should also be the target of collection.

Required User Account Privileges

vFoglight Storage requires an account with the appropriate defined role access capabilities to enable DataONTAP® API:

• Allowed capabilities: login-http-admin

For general access:

• Allowed capabilities: api-*

For limited access, the following are the explicit capabilities required by vFoglight Storage:

• Allowed Capabilities: useradmin role add vfs_collector -a api-system-get-ontapi-version, api-aggr-list-info, api-volume-list-info, api-volume-options-list-info, api-qtree-list, api-quota-report, api-cifs-share-list-iter-start, api-cifs-share-list-iter-next, api-nfs-exportfs-list-rules, api-nfs-exportfs-list-rules-2, api-snapshot-get-reserve, api-snapshot-list-info, api-lun-map-list-info, api-lun-get-occupied-size, api-lun-get-space-reservation-info, api-iscsi-node-get-name, api-fcp-node-get-name, api-portset-list-info, api-snmp-get, api-snmp-get-next, api-vfiler-list-info, login-http-admin, api-system-get-version, api-system-get-info, api-fcp-adapter-list-info, api-disk-list-info, api-volume-get-root-name, security-api-vfiler, api-lun-list-info, api-snapshot-delta-info, api-lun-get-serial-number, api-perf-object-get*, api-cifs-share-list-iter-end, api-snapshot-*, cli-priv, cli-version, api-storage-shelf-list-info, api-iscsi-service-status, api-perf-object-counter-list-info

• Create the Account Alias as type “Other”.

Storage ArraysvFoglight Storage collects storage inventory, data protection, and association information from storage arrays by interfacing with the storage array management system software that ships with the hardware.



CLARiiON Configuration Requirements

vFoglight Storage utilizes the NaviSecCLI interface on the EMC® Management host to collect data from EMC CLARiiON® arrays. A login account on the management host is required along with a Navisphere managed account for the specific service processors to be queried.

Management Host User Account Required Privileges

vFoglight Storage requires user account to access NaviSecCLI utility on the EMC® Management host. The user account must have the following access:

• UNIX—the NaviSecCLI interface requires SSH services with read and execute access to the binaries (sudo if the administrator changed the access privileges).

• Windows®—the NaviSecCLI interface requires read and execute access to the executables. In addition, the following are required for access to Navisphere on a Windows systems:

• Requires ADMIN$, IPC$ as Shares

• Requires RPC service to be enabled

Navisphere Account Privileges

In accessing the specific CLARiiON arrays, vFoglight Storage utilizes the Navisphere management application (via the NaviSecCLI) for collection. In addition to the host account used to access Navisphere, an account is required to access the individual arrays. For vFoglight Storage, an account with “Global” privilege is required. An account with Global privilege has access to all CLARiiON’s in that domain.

Note When using a Navisphere managed SP account with the Global attribute, only a single SP needs to be entered. Since the Global account is known and valid for all SPs, entering a single instance allows vFoglight Storage to recognize all SPs managed by this instance of NaviSphere.

Required Information:

• Username to the EMC® Management Host account

• Password to the EMC® Management Host account

• Username for the Naviseccli account

• Password for the Naviseccli account

• Service Processor IP address (Per CLARiiON® Domain)

Note If CLARiiONs are in one or more Navisphere Domains, then only a single SPIP address is required per Domain. vFoglight Storage determines all other SPs in the domain.



HP EVA Arrays

vFoglight Storage collects information from HP EVA storage arrays using the SMI-S interface to the HP SMI-S EVA component of the Command View management software.

Note HP Command View version 9.0 or later is required for vFoglight Storage to monitor EVA arrays.

Important The SMI-S component should be loaded on the HP Command View server, not on the vFoglight Storage Server.

Instructions for how to install and configure this component are in the HP StorageWorks Command View EVA Installation Guide.

Supported Array Versions

The following versions of HP EVA arrays are supported by vFoglight Storage:

Management Host User Account Required Privileges

By default, all HP Command View EVA users are also HP SMI-S EVA users. Any Command View account is valid for use by vFoglight Storage. This account should be configured as “Other” in vFoglight Storage account setup.

HDS AMS

vFoglight Storage collects information from Hitachi AMS storage arrays using the SMI-S interface of the HiCommand Device Manager component of the Hitachi Command Suite software.

Important Instructions for how to install and configure this component are in the Hitachi Command Suite Installation Guide. The Command Suite and the SMI-S component should be installed on the Hitachi HiCommand server, not on the vFoglight Storage Server.

Fibre Channel SwitchesvFoglight Storage collects data from the following switches:

• “Brocade® SAN Switch Collection Configuration Requirements” on page 20

• “Cisco® SAN Switch Collection Configuration Requirements” on page 20

•3000 Series•4000 Series•4100 Series•4400 Series•5000 Series•6000 Series

•6100 Series•6400 Series•8000 Series•8100 Series•8400 Series



Brocade® SAN Switch Collection Configuration Requirements

vFoglight Storage collects information from Brocade switches via a Brocade SMI Agent on a management host. This requires an account type of “Other”. The account is integrated into the SMI Agent.

The Brocade SMI Agent talks to “proxy” switches, one in each fabric. These “proxy” switches are identified through the use of a configuration tool provided by the SMI Agent. The vFoglight Storage application does not perform any configuration of the Brocade SMI Agent, this must be done by the user.

The Brocade® SMI Agent utilizes a SMI-S interface and requires a CIMOM that is SMI-S 1.1 or 1.2 CTP compliant.

See the following information on acquiring, installing, and setting up the Brocade® SMI Agent:

http://www.brocade.com/services-support/drivers-downloads/smi-agent/index.page

Required User Account Privileges

vFoglight Storage requires a user account with read/write access.

Cisco® SAN Switch Collection Configuration Requirements

The Cisco® MDS 9000 series switches utilize an embedded SAN/NX operating system software. Collecting from a Cisco switch requires a valid user account (with read/write access) on each Cisco switch in the SAN. This is an integrated account (Type is “Other”) when setting up collections within vFoglight Storage). Collecting from a Cisco SAN switch requires a valid SSH interface.

To check for a valid interface, utilize the following steps:

1 Log in to the switch using telnet. At the command line, enter the following (the text you enter is in bold):

switch-name# show ssh server

The response will be either:

ssh is not enabled

or

ssh is enabled.

2 If the server is not enabled, do the following:

switch-name# config t

3 Enter the following configuration commands, one per line.

switch-name(config)# enable ssh server

switch-name(config)# exit

switch-name# show ssh server

ssh is enabled

Version 2 is enabled

4 End with Ctrl/Z.



3

Installing vFoglight Storage

Running the vFoglight Storage application requires the following components:

• vFoglight Storage Server

• vFoglight Storage Client

Installation on a Virtual MachineWhile the use of VMware virtual machines to host the application is supported, it is recommended that some consideration is given to environment size when deploying vFoglight Storage.

For smaller environments (approximately six ESX servers), running vFoglight Storage on a VM should provide acceptable performance. For more information, see “Hardware Requirements for a Small Environment” on page 11.

Note In this configuration, the application databases should be installed on different LUNs.

For larger environments, Quest Software recommends installing the vFoglight Storage server on a physical machine matching the specifications recommended in this guide. For more information, see “Hardware Requirements for a Large Environment” on page 12.

Preparing to Install vFoglight StorageThe requirements for installing vFoglight Storage are:

• A machine to host the vFoglight Storage server and data repository. The server should run on a dedicated machine because it must process and store large volumes of data.

Note Ensure that a host name resolution and reverse lookup are confirmed prior to installing vFoglight Storage.

• Administrator access to the vFoglight Storage server.

• Microsoft .Net Framework 3.5 must be installed on the vFoglight Storage server machine. You will be prompted to install by the application installer if .Net 3.5 is not present.

Note Microsoft .Net Framework 4.0 installed is not fully backwards compatible with .Net 3.5. If .Net 4.0 is installed on the vFoglight Storage machine, you will need to install .Net 3.5.


Chapter 3—Installing vFoglight Storage

• vFoglight Storage requires that the standard Windows Secondary Logon service be enabled. Enabling this service is required for the installer to initiate the underlying PostgreSQL database cluster.

Installing vFoglight StorageThe installation of vFoglight Storage is the same for all supported platforms.

To install vFoglight Storage:

1 Double-click the vFoglight Storage executable.

The vFoglight Storage Install Wizard dialog displays asking you to stop any antivirus programs.

2 Stop any antivirus program and click OK.

3 The InstallShield Wizard appears. After the extraction completes, the vFoglight Storage Installation Wizard dialog box appears.

4 Click Next.

The licenses agreement displays. Read through the License Agreement statement. Print the license agreement for easier viewing.



5 Click Yes to accept the licenses.

The Customer Information dialog appears. The Anyone who uses this computer (all users) radio button is the default.

6 Enter your name and company information.

Note This information is optional.

7 Click Next.



The vFoglight Storage application installation path dialog appears.

8 Accept the default location C:\Program Files\Quest\vFogStorage.

or

Click Browse to select another installation location.

9 Click Next.

10 The vFoglight Storage Setup Type dialog appears. From this dialog, you install the complete vFoglight Storage application (server, database, and desktop client) or only the desktop client (vFoglight Storage Desktop).



11 To install the complete application, select vFoglight Storage Complete Application.

or

If you have the vFoglight server installed on a different host, select vFoglight Storage Desktop.

Note During the vFoglight Storage Desktop installation you will be prompted to provide the name or IP address of the vFoglight Storage server to which the client will connect. The server must have been installed and reachable prior to installing the desktop client.



12 Click Next.

The vFoglight Storage Databases dialog appears.

13 Select the destination for the three different vFoglight Storage databases.

Important It is highly recommended that the databases be separated across different physical disks or LUNs and not be co-located with the program files. If possible, have four disks or LUNs available for the installation. If this is not feasible, have two separate physical disks or LUNs and put the program files with the Collector (hdccsts) and Trace (tracets) databases. Install the Server (prismts) database on a physical disk or LUN by itself. For more information, see “Database Disk Space Requirements” on page 13.

14 Click Next.

The Choose Destination Location dialog appears, allowing you to set the default location for database backups.



15 Accept the default backup location,

or

Click Browse and navigate to the required destination backup location.

16 Click Next to continue.

The Collector Service dialog appears.

Selecting No accepts the default LOCAL SYSTEM account. The application can be setup to run with the LOCAL SYSTEM, workgroup, or domain system accounts. This screen allows you to modify the account to be used.

or

Selecting Yes prompts you to select a different account. Enter the required Domain\Username and password.

17 After selecting the required system account option, click Next.

The Start Copying Files dialog appears.



18 Click Next.

The setup status dialog displays. vFoglight Storage is installed and configured.

19 After installation completes, a dialog displays with the following radio button options:

• I do not have database archives, continue with the default schema.

• I have database archives and I would like to upload them instead of default schema.

20 Select I do not have database archives, continue with the default schema if no database archives need to be installed and proceed to step 27.

Select I have database archives and I would like to upload them instead of default schema to upload a database archive to recover a previous configuration.



21 Click Next.

The Maintenance Utility displays.

22 Click the Restore tab.

23 Click Browse and browse to select the desired archive.

A list of the databases available for recovery is shown.

24 Select the database backups to restore. Click Next.

A list of archives displays.



25 Select the archives to restore and click Next.

The restore process begins and may last several minutes or longer, depending on the size of your database.

26 After installation, the Select options dialog appears.

Select the appropriate option(s).

27 Click Next.

The InstallShield Wizard Complete dialog appears.

28 Click Finish to complete the installation.



For vFoglight Storage configuration procedures, see “Configuring vFoglight Storage to Collect Data” on page 35.

Uninstalling vFoglight StorageRemove vFoglight Storage using the Add/Remove Programs applet in the Windows Control panel.

To uninstall vFoglight Storage:

1 Navigate to the Control Panel.

2 Select Add/Remove programs.

Note This step varies depending on which Windows operating system you are using.

3 Click Change/Remove.

The vFoglight Storage InstallShield Wizard displays, followed by the remove the program dialog.



4 Click Next.

5 A dialog asking if you want to remove vFoglight Storage appears.

6 Click Yes.

The vFoglight Storage uninstall dialog appears followed by the uninstall complete dialog.

Note During the uninstall process, you may encounter a condition where the InstallShield Wizard is unable to remove vFS program directory. Click OK, and delete the directory once the uninstall completes.

7 The Uninstall Complete dialog displays. Click Finish.



4

Configuring vFoglight Storage to Collect Data

To collect data using vFoglight Storage, you set up accounts and then configure the collection.

Required vCenter User Account PrivilegesTo facilitate collecting from vCenter, an account with proper credentials must be provided. The account must be a Windows Operating System account, and can be either a local Windows User or Domain user. Enable the accounts as follows:

• At a minimum, the account has the Read-Only role for the root of inventory.

• Or, the account belongs to a group with this role (typically the Admin group).

Configuring AccountsIn order to collect data from your environment, it is necessary to have a valid account used to communicate with the appropriate management interface. There are two basic attributes of a valid account required by the vFoglight Storage management interface:

• Account Name

• Password or Key

vFoglight Storage uses two attributes to assist in the management and utilization of these accounts:

• “Account Alias” on page 36

• “Account Types” on page 36


Chapter 4—Configuring vFoglight Storage to Collect Data

Account Alias An account alias is a textual name used to represent the account (name and password/key) within the vFoglight Storage application. Typically, this is a logical/representative name for the target and management application.

Important Account aliases must be unique and the account alias is case sensitive.

vFoglight Storage utilizes the alias to match account information to a collection target, or set of collection targets. This allows the user to change the account name and or password/key associated with an alias without having to update each target which uses this account.

Account Name and Password/Key

A valid account name (recognized by the target application and/or the target server hosting the management application) and either a valid password or a set of keys are required.

Important Account names are case sensitive. Account passwords and private keys are stored encrypted.

Account Types There are two account types:

• “Operating System Accounts” on page 36 (Windows or Unix)

• “Integrated Application Accounts” on page 36 (Other)

Operating System Accounts

If the account used to collect target information is recognized and managed by the host (or by a directory service, e.g. Active Directory Service), and is provided with privileges to collect information from the local management application, it is an operating system account type. In this case, vFoglight Storage must understand the type of host operating system (Windows or Unix) being targeted.

Integrated Application Accounts

If the account used to collect target information is not recognized or managed by a Host, but is a native/integrated application (utility or service) account, this is an Integrated Application type (Other). Examples of this are SMI Agent accounts. In this case vFoglight Storage must understand that it is not logging into a server, but communicating directly with the management application through its application program interface (API) or command-line interface (CLI).

Setting Up an Account

Accounts are defined prior to collection device setup by using the Account Setup located in the Data Collection Setup screen.



Or, they can defined as needed using the New button on the Data Collection Setup screen.

To set up an account:

1 From the Menu bar, select Data Collection > Collection Setup.

The Data Collection Setup screen appears.

2 Click Accounts in the upper left pane.

The Account Setup dialog displays.



3 Enter the Account Alias

4 Enter the Account Name.

5 Select the account type from the Account Type from the drop-down.

6 Click the Password field.

The Password Edit dialog displays.

7 Enter the password in the Password and Re-enter password fields. To avoid errors, select Show password when typed to display the typed characters rather than asterisks.

8 Click OK.

9 Click the Key Exchange field.

Note Key Exchange is not applicable to Windows accounts.

The Key Exchange dialog displays.



10 A private key is required. A public key is optional. Click the required Browse button to display the File Open dialog to retrieve the private or public key.

11 Click OK to save the Key Exchange and close the Key Exchange dialog.

12 Click Save.

Configuring ConnectionsUsing the Data Collection Wizard, you configure connections to each of the infrastructure components for data collection. vFoglight Storage provides the following connection types:

• “vCenter/vSphere Connection” on page 39

• “Fiber Channel (FC) Switch Connection” on page 44

• “Filers Connection” on page 47

• “Storage Array Connection” on page 50

vCenter/vSphere ConnectionvFoglight Storage collects datastore, ESX host, and VM guest information from vCenter utilizing vAPIs through the web management interface.

Note Collecting separately from ESX Hosts is not required.

An account for vCenter must be a Windows Operating System account. It must be a local Windows user or Domain user, enabled as follows:

• At a minimum, the account should have the Read-Only role for the root of inventory.

• Or, the account can belong to a group with this role (typically the Admin group).

Configuring a vCenter connection requires the following steps:

1 Setting Up a vCenter Connection



2 Validating the vCenter Connection

3 Initiating vCenter Data Collection

Setting Up a vCenter Connection

When setting up a vCenter Connection, you first configure a connection to the vCenter server.

To configure a vCenter server connection:

1 From Menu bar, select Data Collection > Collection Setup.

The Data Collection Setup dialog displays.

2 Under Device Setup, click vCenters.

3 Select the default Account Alias for the vCenter connection.

• If you have multiple vCenters using the same account information, select it as the default account. Then there is no need to select the account within the grid.

• If an account alias has not yet been defined, click New and use the Windows Account type.



• To edit an existing account, click Edit.

4 Enter either the fully qualified domain name (FQDN) or IP address of the vCenter in the grid.

Note Using the IP Address is preferred. If both the fully qualified domain name and IP address are entered, the IP address is used by vFoglight Storage.



5 Select an Account Alias in the grid only if this vCenter needs a different account than the default account.

Note All entered information automatically saves if you leave this setup screen.

Validating the vCenter Connection

Next, the vCenter Connection credentials must be validated.

To validate the connection:

1 Click Validate All or Validate Selected to validate that the specified account(s) can be used to collect information from the specified vCenters.

Validation may take several minutes. No further actions can be taken until validation completes. Successfully validated entries display in the lower grid. Entries with authentication or validation problems remain in the upper grid.



2 If the validation fails, clicking on the failed icon in the Val? column displays an error indication(s) popup with further information about validation failure.

Initiating vCenter Data Collection

Once a connection to a vCenter is configured and validated, you initiate collecting data from that vCenter.

To initiate vCenter data collection:

1 Click Collect Once to submit the selected entries for an immediate topology collection.

2 Clicking Refresh at the top of this setup screen after a few minutes, allows you to see if the topology collection has completed. A success or failure indication of the collection displays in the Topo? column.



If the topology collection succeeds, the collected entities display in the Explorer tree in the main vFoglight Storage screen after the user interface auto-refreshes.

Note Collect Once is an optional action. Activation of a schedule assigned to an entry automatically performs a topology collection, if needed, before starting performance data collections.

To collect performance and topology data from the entities on a regular basis, assign a schedule to each entity and activate it. The process for selecting or creating a schedule is the same for each type of collection. For more information, see “Configuring Collection Schedules” on page 67.

Fiber Channel (FC) Switch ConnectionvFoglight Storage collect data from Brocade and Cisco switches. The procedure for configuring a connection is similar for both types of switches. Configuring a connection and validating credentials to a FC switch requires the following steps:

1 Setting Up the FC Switch Connection

2 Validating the FC Switch Connection

3 Initiating FC Switch Data Collection

Setting Up the FC Switch Connection

To collect data from a fiber channel switch, you first configure the connection.

To configure a fiber channel connection:



2 Click FC Switches.

3 In the Switch Type column, select Cisco or Brocade.



4 Enter either the fully qualified domain name (FQDN) or IP address. Note the following:

• For Brocade, this is the FQDN or IP address of the server hosting the Brocade SMI Agent. This is not the IP address of an individual switch.

• For Cisco, this is the name or IP address of an individual switch.

• The IP address is preferred. If both FQDN and IP are entered, the IP address is used.

5 Select the Account Alias to use to connect.

• If an Account Alias has not yet been defined, click New Account to create it. Use the Account type “Other”.

6 Enter a port only if the management interfaces are using a non-default port.




Validating the FC Switch Connection

Next, the fiber channel credentials must be validated.

To validate the connection:

1 Click the Validate All or Validate Selected button to validate that the specified account(s) can be used to collect information from the specified switches and that the FQDN or IP address can be resolved.

Validation may take several minutes. No further actions can be taken until validation completes. Successfully validated entries display in the lower grid. Entries with authentication or validation problems remain in the upper grid.

2 If the validation fails, clicking on the icon in the Val? column displays an error indication popup with further information about validation failure.

Initiating FC Switch Data Collection

Once a connection to a switch is configured and validated, you begin collecting data from that switch. Validated entries appear in the lower grid. After validation, the switches collecting are displayed under the management host.

To initiate FC switch data collection:




2 Clicking Refresh at the top of this setup screen after a few minutes, allows you to see if the topology collection has completed. A success or failure indication of the collection displays in the Topo? column. If the topology collection succeeds, the collected entities display in the Explorer tree in the main vFoglight Storage screen after the user interface auto-refreshes.

Note Collect Once is an optional action. Activation of a schedule assigned to an entry will automatically perform a topology collection, if needed, before starting performance data collections.

To collect performance and topology data from the entities on a regular basis, assign a schedule to each entity and activate it. The process for selecting or creating a schedule is the same for each type of collection. For more information, see “Configuring Collection Schedules” on page 67.

Filers ConnectionvFoglight Storage collects data from NetApp. Configuring a filers connection requires the following steps:

1 Setting Up a Filer Connection

2 Validating a Filer Connection

3 Initiating Filer Data Collection

Note If you are using NetApps’s Multistore functionality, ensure that you are configuring collections from the physical filer (vfiler0).

Setting Up a Filer Connection

To collect data from a filer connection, you first configure the connection.

To configure a filer connection:



2 Click Filers.

3 Select the default Account Alias.

• If you have multiple filers that use the same account information, you can select it as the default account. Then there is no need to select the account within the grid.



• If an Account Alias has not yet been defined, click New. Use the Account Type “Other”.

4 Enter either the fully qualified domain name (FQDN) or IP address of the filer in the grid.

Note The IP address is preferred. If both FQDN and IP address are entered, the IP address is used.

5 Select an Account Alias in the grid only if this filer needs a different account than the default account.




Validating a Filer Connection

Once a connection is configured, you need to validate the credentials before beginning data collection.

To validate the filer connection:

1 Click the Validate All or Validate Selected to validate that the specified accounts can be used to collect information from the specified filers.

Note Validation may take several minutes. No further actions can be taken until validation completes.

2 Successfully validated entries display in the lower grid. Entries with Authentication or Validation problems remain in the upper grid.



3 Click on the error indication(s) for further information about a failure.

Initiating Filer Data Collection

Once a Filer data collection connection is configured, you need to validate the credentials before beginning data collection. After validation, the connections display under the management host.

To initiate Filer connection data collection:



Note Collect Once is an optional action. Activation of a schedule assigned to an entry automatically performs a topology collection before starting collection of performance and topology data. Data collection begins automatically whey you assign a schedule to each entity and activate it. The process for selecting or creating a schedule is the same for each type of collection. For more information, see “Configuring Collection Schedules” on page 67.

Storage Array ConnectionvFoglight Storage collects storage inventory, data protection, and association information from storage arrays by interfacing with the storage array management system software that ships with the hardware. Currently, vFoglight Storage supports:

• “EMC CLARiiON” on page 50

• “HP EVA” on page 55

• “Hitachi AMS” on page 60

Note Configuring collections from an EMC CLARiiON array requires that a connection first be configured to the array’s management host. This step also applies to the HDS AMS collection for Tuning Manager configuration process.

EMC CLARiiON

Configuring the EMC Clariion connection requires the following steps:

1 Setting up an EMC Array Connection

2 Validating the EMC Array Connection

3 Initiating an EMC Clarion Array Connection



Setting up an EMC Array Connection

To collect data from an EMC array utilizing the provided credentials and the established connection to the Array management software requires the following steps:

To collect data from an EMC connection:



2 Click Arrays.

3 Select EMC Clarion from the Array type drop-down.

4 Enter either the fully qualified domain name (FQDN) or IP address of the management host.

Note The IP Address is preferred. If both FQDN and IP address are entered, the IP address is used.

5 Select the operating system the host is running.



6 Enter the installation path of the CLI, if it was not installed at the default location.

7 Select the Account Alias to use when connecting to the management host.

• The Account alias drop-down displays only Windows or UNIX accounts based on the operating system selection.

• If an Account alias has not yet been defined, click New to create the alias.

8 After an array management host has been validated, it appears in the Device Setup NavBar, underneath the Arrays entry.



Validating the EMC Array Connection


To validate an EMC Clariion array connection:

1 Click Validate. Validation may take several minutes. No further actions can be taken until validation completes.

If the validation process is successful the Arrays tab displays with the Array management host information at the top.



If validation is not successful, the status box displays information about the failed validation. In either case, the name or IP address of the management host appears in the Device Setup Navigation Bar, for later selection.

Initiating an EMC Clarion Array Connection

Once a connection to the Clarion Management host is configured and validated, you begin collecting data from that array. Validated entries appear in the lower grid. After validation, the arrays collecting data display under the management host.

To initiate EMC Clarion data collection:






HP EVA

vFoglight Storage collects information from HP EVA storage arrays using the SMI-S interface to the HP SMI-S EVA component of the Command View management software.

Note Instructions for how to install and configure this component are in the HP StorageWorks Command View EVA Installation Guide. The SMI-S component should be installed on the HP Command View server, not on the vFoglight Storage Server.

By default all HP Command View EVA users are also HP SMI-S EVA users. Any Command View account is valid for use by vFoglight Storage. This account should be configured as “Other” in vFoglight Storage account setup. Configuring the HP EVA connection requires the following steps:

1 Setting Up the HP EVA Array

2 Validating the HP EVA Connection

3 Initiating HP EVA Data Collection

Setting Up the HP EVA Array

To collect data from an HP EVA array connection, you first configure that connection.

To configure an HP EVA array connection:



2 Click Arrays.



3 Select HP EVA from the array type drop-down.



5 Enter the port number if the SMI-S is not configured to use the default.



6 Select the account alias to use when connecting to the management host. Note the following:

• The account used for collecting AMS arrays is the Command Suite account.

• The Account alias drop-down displays only “Other” type accounts.

• If an account alias has not yet been defined, click New… to create it.

After an array management host has been validated, it appears in the Device Setup Navigation Bar, underneath the Arrays entry.



Validating the HP EVA Connection


To validate an HP EVA array connection:


If the validation process is successful the Arrays tab displays, with the Array management host information at the top.



If validation is not successful, the status box displays information about why the validation failed. The name or IP address of the management host appears in the Device Setup Navigation Bar for later selection.

Initiating HP EVA Data Collection

Once a connection to the EVA Management CIM API has been is configured and validated, you begin collecting data from that array. Validated entries appear in the lower grid. After validation, the arrays collecting data are display under the management host.

To initiate HP EVA data collection:




2 Clicking Refresh at the top of this setup screen after a few minutes, allows you to see if the topology collection has completed. A success or failure indication of the collection displays in the Topo? column. If the topology collection succeeds, the collected entities display in the


The process for selecting or creating a schedule is the same for each type of collection. Refer to “Configuring Collection Schedules” on page 67 for more information.

Hitachi AMS

vFoglight Storage collects information from Hitachi AMS storage arrays using the SMI-S interface of the HiCommand Device Manager component of the Hitachi Command Suite software.

Important Instructions for how to install and configure this component are in the Hitachi Command Suite Installation Guide. The Command Suite and the SMI-S component should be installed on the Hitachi HiCommand server, not on the vFoglight Storage Server.

By default all Hitachi Command Suite users are also SMI-S users. Any Command Suite account is valid for use by vFoglight Storage. This account should be configured as “Other” in vFoglight Storage account setup.

Note Hitachi Command Suite 7.0 or later is required for vFoglight Storage to monitor AMS Arrays.



The metrics that can be collected from standard HiCommand Device Manager are limited. vFoglight Storage provides and option to interface to the Hitachi Tuning Manager for an additional interface to metrics. The following table provides a list of those metrics.

Note Tuning Manager is an additional package, licensed separately within Command Suite 7.0 or higher. Instructions for how to install and configure the Tuning Manager component are in the Hitachi Command Suite Installation Guide. The Tuning Manager component should be installed on the Hitachi HiCommand server, not on the vFoglight Storage Server.

Configuring the Hitachi AMS connection requires the following steps:

1 Setting Up the Hitachi AMS Array

2 Validating the Hitachi AMS Connection

3 Initiating Hitachi AMS Data Collection

Setting Up the Hitachi AMS Array

To collect data from an Hitachi AMS array connection, you first configure that connection.

To configure an Hitachi AMS array connection:



2 Click Arrays.

Collected Entity Metric

Disk • Busy

LUN • Bytes Read

• Bytes Write

• Latency

Controller • Busy

Port (Array) • Ops Read

• Ops Write

• Bytes Read

• Bytes Write



3 Select HDS AMS from the array type drop-down.



5 Enter the port number if the SMI-S is not configured to use the default.



6 Select the account alias to use when connecting to the management host. Note the following:

• The account used for collecting AMS arrays is the Command Suite account.

• The Account alias drop-down displays only “Other” type accounts.

• If an account alias has not yet been defined, click New… to create.

a If simple SMI collections are sufficient, then proceed to Validating the Hitachi AMS Connection.

b If Tuning Manager is to be utilized to collect the additional performance metrics, additional setup steps are required.

7 Click the Use HDS Tuning Manager check box. This enables the remaining setup fields.

Note In vFoglight Storage release 1.6, Tuning Manager is only supported on Window’s hosts.



8 If the path to the Tuning Manager installation directory is not the default location, then enter the path for the Tuning Manager application.

Note This path is needed only if Tuning Manager was installed someplace other than the default location. Therefore, you can leave this field blank. It is filled in by the system after successful validation.

9 Select the Account Alias to use when connecting to the Tuning Manager application.

Note This is the user account on the HiCommand host which has been configured for access to Tuning Manager. This also provides access the Tuning Manager command-line interface to create and run reports. This account must have administrative access on a Window’s host.

10 If an Account Alias has not yet been defined, click New to create the required alias.

After an array management host and the Tuning Manager account has been set up, the setups must be validated.



Validating the Hitachi AMS Connection

Once a connection is configured, you need to validate the credentials before beginning data collection. Validation ensures that the required data can be collected from the Hitachi Command Suite and that the required Tuning Manager commands run with the specified credentials.

Note You can validate just the standard SMI collection setup, or the SMI array collection in conjunction with the Tuning Manager setup.

To validate an Hitachi AMS array connection:


If the validation process is successful the Arrays tab displays, with the Array management host information at the top.

If validation is not successful, the status box displays information about why the validation failed. The name or IP address of the management host appears in the Device Setup Navigation Bar for later selection.



Initiating Hitachi AMS Data Collection

Once a connection to the Hitachi HiCommand CIM API and, as appropriate, the Tuning Manager application have been configured and validated, you begin collecting data from that array. Validated entries appear in the lower grid.

To initiate Hitachi AMS data collection:


2 Clicking Refresh at the top of this setup screen after a few minutes, allows you to see if the topology collection has completed. A success or failure indication of the collection displays in the Topo? column.



3 If the topology collection succeeds, the collected entities display in the

Note Collect Once is an optional action. Activation of a schedule assigned to an entry automatically performs a topology collection before starting collection of performance and topology data. Data collection begins automatically when you assign a schedule to each entity and activate it.

The process for selecting or creating a schedule is the same for each type of collection. Refer to “Configuring Collection Schedules” on page 67 for more information.

Configuring Collection SchedulesWhen configuring collection schedules, you can create a new schedule or assign an existing schedule to a particular data collection.

To create a new schedule:



2 In the Device Setup navigation bar, click the device you want to assign the schedule to.

3 Locate the Assign Schedule to Selected Targets section. For vCenter, FC Switches, and Filers, this feature is located in the lower center of the setup screen.

For array devices, this feature is located in the upper right corner of the setup screen.



4 Click New.

The Collection Schedule editor appears.

5 Complete the Schedule Editor dialog, using the table below as a guide.

Field Description

Name This is an alias/handle by which the schedule will be recognized by the vFoglight Storage application. This name is visible in the Assign Schedule to Selected Targets pull downs and can be any valid text string.

Performance Collection Frequency Target

This field specifies the minimal interval at which the vFoglight Storage application attempts to collect performance data.



6 In the Assign Schedule to Selected Targets section, select the schedule to be assigned from the schedule drop-down. Multi-select the entries to which it should be assigned and click Assign. The name of the assigned schedule will appear in the grid.

Preferred Topology Collection Time

This is an optional field, but it highly recommended that users provide a set topology collection time. This is the guaranteed time during which vFoglight Storage collects data from the the underlying topology. While vFoglight Storage should perform multiple intermediate topology collections, it is possible that some changes in the underlying environment may go unnoticed. By providing this scheduled topology collection time, the vFoglight Storage application catches any previously undetected changes. This value should be set to off-hours whenever possible.

Collection Blackout Schedule If there are known periods during the day or week in which administrative actions are scheduled, it is best to restrict the vFoglight Storage activities for these objects during that time. The collection activities may actually be intrusive during maintenance periods and, due to the fact that the underlying topology may well be undergoing several changes, the vFoglight Storage application will be spending wasted cycles collecting those frequent, intermediate changes. See the section “Blackout Windows” on page 71 for more information.

Field Description



7 Click Save. The name of the assigned schedule appears in the grid.

8 In the Activate/Deactivate Collections section, multi-select the entries to be activated, and click Activate. A check mark appears in the grid next to the schedule name, for each entry that has been activated.



Selecting an Existing ScheduleYou can apply configured schedules to the required collection.

To apply a configured schedule to a collection:

1 From the Assign Schedule to Selected Targets drop-down, select the required schedule.

2 Select the collection target to which you wish to assign a schedule.

3 Click Assign. The selected schedule appears in the selected target.

Blackout WindowsWhen configuring a schedule, you may select one or more time periods during which collection will not occur. You may also add a blackout window to an existing schedule. Blackout windows are configured via the Schedule Editor.

To add a blackout window:

1 Select the required target you want to assign the blackout to.



2 Click the New button to invoke the Schedule Editor.

or

Select a schedule from the drop-down and click Edit.

3 In the Collection Blackout Schedule section, complete required fields.

• Start Time—the time at which the blackout begins.

• Duration—the duration of the blackout.

• Frequency—daily or weekly.

• Week Days—select the days on which the blackout applies. Active only if the Frequency is “weekly”.

4 Repeat as needed.

5 Click Save.

5

Upgrading vFoglight Storage

Running the vFoglight Storage installer upgrades to the latest version.

To upgrade vFoglight Storage:

1 Double-click on the vFoglight Storage executable.

The confirmation dialog appears.

2 Click Yes.

The Welcome screen appears.

Note If you are upgrading from vFoglight Storage version 1.6.0 or earlier, a warning message appears, indicating a special upgrade process is required to migrate the PostgreSQL database from version 8.x to 9.x.

vFoglight Storage: Administration and Configuration Guide 74

Chapter 5—Upgrading vFoglight Storage

For special upgrade procedures, see step 1 of Upgrading vFoglight Storage Version 1.6.0 or Earlier.

3 Click Next.

The install/configuration process begins and the Upgrade Options dialog displays.

4 The next dialog provides the following options:

• Express Upgrade—upgrades the existing application and databases without backing up the current database or providing the option of restoring previous database versions. For more information, see “Express Upgrade” on page 74.

• Advanced Upgrade—allows you to backup the current database and upgrade, or restore the databases from a previous archive. The restored database will be updated to the latest schema. For more information, see “Advanced Upgrade” on page 75.

Express Upgrade1 Select Express Upgrade and click Next.

The upgrade process runs. This process takes several minutes. When complete, the InstallShield Wizard Complete dialog appears.



2 Select the desired option.

3 Click Finish to complete the upgrade process.

Advanced Upgrade 1 Select Advanced Upgrade and click Next.

The Upgrade Options dialog appears.

2 Select the desired upgrade options.



This dialog provides the following options:

• Upgrade the existing database—upgrades the existing database to the latest schema. See “Upgrading the Existing Database” on page 76 to continue this procedure.

• Restore from archive and upgrade—allows you to restore the application databases from a previous archive. The restored databases will be updated to the latest schema. See “Restore from Archive and Upgrade” on page 77 to continue this procedure.

• Back up Database—creates a backup of the databases before upgrading. Backups will be created in the default backup location.

Important To to make sure you have sufficient disk space before beginning the backup.

Upgrading the Existing DatabaseThis procedure continues from Advanced Upgrade after the Upgrade the Existing Database option has been selected.

To upgrade an existing database:

1 Select Upgrade existing database and click Next.

The upgrade process runs. This process takes several minutes.



2 When completed, the InstallShield Wizard Complete dialog appears. Select the required restart option and click Finish to complete the upgrade process

Restore from Archive and UpgradeThis procedure continues from Advanced Upgrade after the Restore from Archive and Upgrade option has been selected.

To use the Restore from archive and update option:

1 Select Restore from archive and upgrade and click Next.



The Select Backup to Restore dialog appears.

2 Select the desired archive from your default backup location and click Next.

or

Click Browse to browse to a different location. Select the desired archive and click Next. A list of the databases available for recovery appears.



3 Select the database backups to restore. Click Next.

A list of archives displays.

4 Select the archives to restore and click Next.

The restore process begins and lasts several minutes. After the restore, the upgrade process runs. When completed, the InstallShield Wizard Complete dialog appears.

5 Select the required option and click Finish.



Upgrading vFoglight Storage Version 1.6.0 or EarlierThese procedures provide steps to upgrade from vFoglight Storage 1.6.0 or earlier versions. They are continued from step 2 of Upgrading vFoglight Storage.

To upgrade vFoglight Storage from version 1.6.0 or earlier versions:

1 Click OK.

The InstallShield Wizard Complete screen appears.



2 Click Finish.

The upgrade installation concludes and the vFoglight Storage Upgrade Helper wizard appears to start the special installation process. This procedure backups the existing 8.x database, uninstalls the existing vFoglight Storage application, installs a new version of vFoglight Storage application (1.6.1 or later version), and restores database backups to the PostgreSQL 9.x database.

3 Click Start.

The database backup screen appears.



4 Provide the directory path to store the database backup. You can use the default location provided from your previous vFoglight Storage installation.

Important Choose a location outside the current vFoglight Storage install hierarchy.

5 Click Next.

6 The database backup process runs. The process may take several minutes to several hours depending on the size of the database. When complete, the vFoglight Storage uninstall screen appears.

Note You must use the Windows "Add or Remove Programs" wizard to manually uninstall the vFoglight Storage application. The upgrade process will not let you proceed until this procedure is complete.

7 Click 1. Click here to open the uninstall screen link.



The “Add or Remove Programs” wizard appears. Follow the procedures to uninstall the vFoglight Storage application. When complete, the Next button activates to continue the process.

8 Click Next.

The vFoglight Storage installer screen appears.

9 Click Exit Without Installing.

or

Start Install

The vFoglight Storage installation process begins. For more information, see “Installing vFoglight Storage” on page 22.


Index

Aaccount privileges

required for vCenter 35

Bblackout window

adding 71why use it 69

Ccollection schedules

configuring 67Configuring

connections 39CLARiiON management host 50

privileges 35schedules 67

blackout windows 71vFoglight Storage 35

configuring accountsalias accounts 36integrated application accounts 36operating system accounts 36overview 35setting up and account 36

configuring connectionsFiber Channel switch connection

initiating FC switch data collection 46setting up the fiber channel switch connection 44validating the FC switch connection 46

filer connectioninitiating filer data collection 50setting up a filer connection 47validating a filer connection 49

storage array connection EMC Clariioninitiating an EMC Clariron Array Connection 54setting up an EMC Array connection 51validating the EMC array connection 53

storage array connection HP EVA Arrayinitiating HP EVA data collection 59, 66validating the HP EVA connection 58, 65

vCenter/vSphere connection 39initiating vCenter data collection 43setting up a vCenter connection 40validating the vCenter connection 42

connection

Fiber Channel 44filer connections 47storage array connections 50vCenter/vSphere 39

Ddatabase

database disk space requirements 13database disk space requirements with four physical

disks 14database disk space requirements with three physical

disks 13database disk space requirements with two physical

disks 13disk space 14types required by vFoglight Storage 13

Eenvironment size definitions 11

FFibre Channel switches 19fibre channel switches

Brocade SAN Switch 20Cisco SAN Switch 20

HHardware Requirements

disk space 13

Iinstallation

installing for first time 23on a virtual machine 22preparation 22procedures 22steps 8uninstalling vFoglight Storage 32

installation on a virtual machine 22

NNetwork Port Requirements 14network port requirements

Brocade 14


Index

Cisco 14CLARiiON Unix 15CLARiion Unix 15HP EVA 14NaviSecCLE 15NetApp 15user interface to server 15

Ppre-installation requirements

database disk space requirements 13database requirements 13hardware requirements 10network port requirements 14storage devices 16supported platforms 15

preparing to install vFoglight Storage 22

RRequired privileges

CLARiiON management hosts 18HP Command View management hosts 19NetApp Filers 17vCenter 35

requirementshardware 10hardware requirements for a large environment 12hardware requirements for a moderate sized

environment 12hardware requirements for a small environment 11

Sstorage devices

Fibre Channel Switches 19HP EVA Arrays 19NetApp Filers 17storage arrays 17

support 7Supported Platforms

monitoring 16Arrays 17Filers 17Switches 19VMware 16

Supported versionsHP EVA 19

Ttechnical support 7

Uuninstalling vFoglight Storage 32upgrading vFoglight Storage 73

VvFoglight Storage

configuring 35installing 23

Storage Monitor Installation Guide

Documents

fully qualified

entry automatically

vmware virtual

selected targets

separate physical

hitachi hicommand

vfoglight

vfoglight