OnCommand Balance 4100 Installation And

OnCommand® Balance 4.1.0Installation and Configuration Guide

NetApp, Inc.495 East Java DriveSunnyvale, CA 94089 U.S.Telephone: +1 (408) 822-6000Fax: +1 (408) 822-4501Support telephone: +1 (888) 463-8277Web: www.netapp.comFeedback: [email protected]

Part number 215-07287_A0December 2012

2

Contents

Introduction to OnCommand Balance ....................................................... 5OnCommand Balance features .................................................................................... 5

Questions you can answer using OnCommand Balance ............................................. 6

OnCommand Balance product documentation ........................................................... 6

Balance installations ..................................................................................... 7Balance installation requirements ............................................................................... 7

Virtual appliance host requirements ................................................................ 7

Virtual appliance resource recommendations ................................................. 8

Balance web browser requirements ................................................................. 9

Installing Balance ........................................................................................................ 9

Configuring the virtual appliance .................................................................. 10

Upgrading Balance .................................................................................................... 11

Upgrade Balance version 3.6 or earlier ..................................................................... 12

Balance Proxy installation ......................................................................... 13Balance Proxy host requirements .............................................................................. 14

What a multiprovider is ............................................................................................. 16

Installing the Balance Proxy ..................................................................................... 17

Upgrading the Balance Proxy ................................................................................... 18

Configuring resources for data collection ................................................ 19VMware vCenter Server and ESX and ESXi Server requirements .......................... 19

VMware vCenter Server requirements .......................................................... 19

VMware ESX or ESXi Server requirements ................................................. 20

Windows and Hyper-V Server requirements ............................................................ 20

Windows Server requirements ...................................................................... 21

Hyper-V Server requirements ....................................................................... 22

Linux and UNIX server requirements ....................................................................... 22

Linux and UNIX requirements ...................................................................... 23

Linux and UNIX configuration for volume monitoring ................................ 25

Linux and UNIX configuration for password authentication ........................ 26

Configuring RSA authentication for Linux and UNIX servers ..................... 27

Storage system requirements ..................................................................................... 28

NetApp FAS storage system requirements ................................................... 29

Table of Contents | 3

NetApp V-Series systems requirements ........................................................ 31

Dell EqualLogic requirements ...................................................................... 32

EMC CLARiiON and VNX requirements .................................................... 32

EMC Symmetrix requirements ...................................................................... 32

Engenio requirements .................................................................................... 35

HP 3PAR requirements ................................................................................. 35

HP EVA requirements ................................................................................... 36

HP XP requirements ...................................................................................... 37

HDS requirements ......................................................................................... 38

IBM storage array requirements for Balance ................................................ 40

Virtualization software requirements ........................................................................ 42

HMC Virtual IO Servers (IBM LPAR) requirements ................................... 42

IBM SAN Volume Controller (SVC) requirements ...................................... 45

HP SAN Virtualization Storage Platform (SVSP) requirements .................. 46

SAN device requirements .......................................................................................... 47

Database requirements .............................................................................................. 47

Enabling topology views of database applications ....................................... 48

Self-monitoring requirements ................................................................................... 50

Balance communication ports ................................................................................... 50

Configuring ports behind Windows firewalls ............................................... 51

Advanced Balance configuration options ................................................. 52Accessing the Advanced Management Tool (AMT) ................................................ 52

Advanced Management Tool configuration options for Balance ............................. 53

Adding network adapters .......................................................................................... 55

Copyright information ............................................................................... 57Trademark information ............................................................................. 58Index ............................................................................................................. 59

4 | OnCommand Balance Installation and Configuration Guide

Introduction to OnCommand Balance

OnCommand Balance provides performance planning, troubleshooting, and optimization for physicaland virtual data centers. Balance helps you manage the performance and workloads of your dynamicshared infrastructure.

OnCommand Balance is an analytics-based IT management software solution that helps youoptimize performance and utilization of virtual machines (VM), physical servers, and storagesystems. IT organizations can use Balance to quickly isolate performance problems, reduceinfrastructure costs, and enable a service-oriented infrastructure. Balance uses agent-less discoveryand collection of statistical data from your monitored resources. It provides multi-vendor,heterogeneous support for Linux and UNIX servers, Windows servers, hypervisors (VMwarevSphere and Microsoft Hyper-V), SAN devices, and storage systems.

OnCommand Balance featuresOnCommand Balance routinely collects configuration and performance statistics information fromyour monitored data center. It uses the statistics to predict and identify performance problems, notifyyou of current or potential problems, and offers recommendations for troubleshooting the root causeof performance problems and optimizing your data center resources.

OnCommand Balance includes the following features:

• Operates as an agent-less virtual appliance (VA) that runs on an ESX Server.• Discovers and collects performance statistics from heterogeneous data centers.• Discovers and collects performance statistics from NetApp storage systems with Data ONTAP

operating in 7-Mode and Cluster-Mode.• Analyzes statistics to make recommendations for identifying and troubleshooting performance

problems.• Uses Key Performance Indicators (KPI) to help you determine if server workloads are operating

at optimal efficiency.• Provides detailed graphs that plot performance activity over time, including I/O throughput

(IOPS), response time, and resource utilization.• Includes configurable thresholds that notify you when capacity or utilization levels reach a

critical point.• Displays topology views that map the end-to-end I/O path between associated resources and

applications.• Includes customizable reports and scorecards that offer best practices, analyze trends, and

highlight performance problems.

5

Questions you can answer using OnCommand BalanceStorage and IT administrators can use OnCommand Balance to gain visibility into the overall healthof their data centers, troubleshoot performance bottlenecks, optimize resources that are over-utilizedor under-utilized, and predict performance impact to new or existing workloads when planning to addor change resources.

The following questions can be answered:

Troubleshoot issues • Is the source of the issue at the virtual machine (VM), server, or storage?• Which workloads are victims and which are bullies?• Which servers have misaligned storage?

Optimizeperformance

• How much headroom do I have?• Where can I put my VM or application for best performance?• Can I reclaim memory, CPU, or storage resources?• How can I better balance my workloads?• Are LUNs and VMDK partitions misaligned?• Which workloads are contending for resources?

Predict problems • How can I proactively avoid bottlenecks?• How can I head off issues?• Can I add VMs or workloads without impacting performance?• When will I run out of storage?

OnCommand Balance product documentationOnCommand Balance is accompanied by a set of guides.

OnCommandBalance Installationand ConfigurationGuide

Provides instructions for setting up OnCommand Balance in your datacenter. It also provides the system requirements and configurationinstructions for adding the servers, SAN devices, storage systems, andapplications you want to monitor.

OnCommandBalance User Guide

Provides an overview of how to use OnCommand Balance to analyze andmonitor the performance of your data center, including adding anddiscovering resources, identifying under-utilized and over-utilizedresources, using the Performance Index to determine how well a server ishandling its current workload, and viewing the topology of associatedresources.


Balance installations

Balance is distributed as a self-contained, fully-formed virtual appliance (VA) available in an OVAfile, for new installations, and an ISO file, for in-place upgrades from version 4.0 or later.

For new installations you deploy the OVA file on a VMware ESX or ESXi Server. The OVA fileincludes the main software components required to run and operate Balance. The VA contains theBalance software and database. No additional virtual machine (VM) configuration is required to getstarted.

For upgrades from Balance 4.0 or later installations you use the latest ISO file to perform an in-placeupgrade on the existing VA.

Balance installation requirementsBefore deploying the Balance virtual appliance (VA), you must determine the appropriate minimumresource requirements for your environment and ensure that the VMware ESX or ESXi Server andproxy host meet minimum requirements.

The minimum resource requirements for the ESX or ESXi Server on which you deploy the virtualappliance (VA) increase based on the number of servers you plan to monitor. To deploy the VA, youcan use the VMware vSphere Client.

Virtual appliance host requirementsThe VMware ESX or ESXi server that will host the virtual appliance (VA) must meet minimumresource requirements. Review these requirements before deploying the VA.

Resource Minimum Requirements

ESX or ESXi Server Hardware and software must be 64-bit.

Network 1 Gigabit Ethernet connection for fastest installation (optional). Bydefault, the VA uses DHCP to communicate with the IP network.

Virtual CPUs 2 @ 2.33 GHz

Virtual Memory 4 GB

With this amount of memory, you can add a maximum of 3 proxies toBalance. Increase the memory to twice this value or higher to add moreproxies.

Disks At least 5 disk spindles in RAID DP or other RAID array.

7

Resource Minimum Requirements

Storage Data store requires at least 205 GB of disk capacity, which includes anextra 5 GB for VA memory and additional files (for example, swap).Refer to the virtual appliance resource recommendations for theminimum number of disks required.

Related concepts

Balance communication ports on page 50

Related tasks

Configuring ports behind Windows firewalls on page 51

Related references

Virtual appliance resource recommendations on page 8

Virtual appliance resource recommendationsThe virtual appliance (VA) resource recommendations listed here are based on the number of serversyou plan to monitor. Additional virtual CPUs can be added through the vSphere Client.

The VA has a minimum memory reservation of 4,096 MB (default). If this amount of memory is notavailable on the ESX or ESXi Server, the VA might not power on.

Monitoredservers

vCPUs CPUreservation(MHz)

Memory(MB)

Memoryreservation(MB)

Minimumdisks

Networkusage(KBps)

1,200 4 8000 8192 8192 12 140

800 4 5000 8192 8192 10 120

600 4 4000 4096 4096 8 100

400 4 3000 4096 4096 6 80

200 2 2000 4096 4096 4 60

100 or less 2 1500 4096 4096 3 60

Related concepts


Related tasks



Related references

Virtual appliance host requirements on page 7

Balance web browser requirementsBalance requires specific web browsers and plugins to properly display the web-based interface.

Balance requires the following browsers and plugins:

• Mozilla Firefox 6.0 or later.• Microsoft Internet Explorer (IE) 7 or later. IE 8 or 9 are recommended.• Java Runtime Environment (JRE) and Adobe Flash Player plugins that are compatible with your

browser. The latest versions of these plugins are recommended.

For IE 8, ensure that Compatibility Mode (Compatibility View) is disabled. For IE 9, ensure thatCompatibility Mode is enabled. See the Microsoft IE online help for information on enabling anddisabling Compatibility Mode.

For all browsers, we recommend disabling any popup blockers so that all Balance content, such asonline help, displays properly.

There is a bug with Windows 2003 that prevents IE from displaying the Balance login page. Toresolve this problem, use Firefox or apply the following hot fix to the server:

http://support.microsoft.com/kb/938397/

Installing BalanceTo install Balance you use a VMware vSphere Client to deploy the virtual appliance (VA) to aVMware ESX or ESXi Server. The vSphere Client converts the VA to a virtual machine (VM).

Steps

1. Ensure that the ESX or ESXi Server that will host the VA meets the requirements.

2. Download the latest VA, available as an OVA file, from the NetApp Support Website at www.netapp.com/us/support.

3. Save the OVA file to a local or network location that is accessible to your vSphere Client.

4. In the vSphere Client, select File > Deploy OVF Template.

5. Complete the Deploy OVF Template wizard to deploy the VA.

Note: For the VM disk format, select Thin Provisioned. Thin provisioning allows the Balancedatabase to efficiently grow to the maximum available capacity as you add resources to yourdata center. vSphere 4.0 does not have this option. For more information, see the vSphereonline help.

6. After the VA has successfully deployed to the ESX or ESXi Server, power on the VA.

Balance installations | 9

http://support.microsoft.com/kb/938397/

http://www.netapp.com/us/support

Note: If your vCenter has multiple networks specified, check the VA configuration to confirmthat the correct network is selected.

7. In the vSphere Client, click the Console tab to monitor the status as the VA powers up, Balancestarts, and Balance uses DHCP to assign an IP address to the VA.

If DHCP is not detected, you are prompted to specify the network settings for assigning an IPaddress to the VA. You enter this IP address in a web browser to access and use the Balance webclient to configure the VA.

After you finish

Configure the VA.

Related concepts

Upgrade Balance version 3.6 or earlier on page 12

Related tasks

Configuring the virtual appliance on page 10

Upgrading the Balance Proxy on page 18

Related references


Configuring the virtual applianceAfter deploying the virtual appliance (VA) and powering it on, you can then open a web browser anduse the fully-qualified domain name (FQDN) or IP address assigned to the VA to access Balance andbegin the configuration.

Steps

1. Open a web browser that meets the minimum client system requirements.

2. In the address bar, enter the FQDN or IP address assigned to the VA when it was deployed.

3. Follow the on-screen instructions to configure the VA.

After you complete the configuration, the Balance login page is displayed.

4. Enter your login credentials. The default is the following (all lowercase):

• User: admin• Password: password

Note: A minimum configuration is required to start using Balance. The first time you log intoBalance the Dashboard page is inactive (empty), but displays a linked list of data centerresources that you can discover and monitor. The Dashboard is populated when it hasdiscovered the data center resources in its environment.


After you finish

Install the Balance Proxy to discover Windows servers and certain storage systems.

Related concepts

Balance web browser requirements on page 9

Configuring resources for data collection on page 19

Related tasks

Installing the Balance Proxy on page 17

Upgrading BalanceUpgrading from Balance 4.0 or later involves using an ISO upgrade file to do an in-place upgrade ofthe existing Balance virtual appliance (VA) and upgrading the proxies.

Before you begin

• The existing VA to be upgraded is version 4.0 or later.• There is a clone or backup of the existing VA.

Steps

1. To download the upgrade image, go to the NetApp Support site at support.netapp.com and selectDownloads > Software.

2. Save the upgrade image (ISO) file to a location that is accessible to a vSphere Client.

3. In the vSphere Client, access the VMware ESX or ESXi Server hosting the Balance VA you wantto upgrade.

4. Mount and connect the upgrade image file to the Balance VA.

5. Select the Console tab to access the Advanced Management Tool (AMT).

6. Log in to the AMT and select the Update Balance option to launch the wizard.

Note: Default username and password is netapp (all lowercase).

7. Follow the wizard instructions to perform the upgrade.

Note: When you log in to Balance for the first time after upgrading, clear the browser cache toremove any out-of-date information.

After you finish

Upgrade the existing Balance Proxies.

Balance installations | 11

HTTP://support.netapp.com

Related concepts


Related tasks


Accessing the Advanced Management Tool (AMT) on page 52

Related references

Advanced Management Tool configuration options for Balance on page 53

Upgrade Balance version 3.6 or earlierOlder versions of Balance must be upgraded to version 4.0 before they can be upgraded to version4.1 or later.

Balance version 4.0 introduced several new features and enhancements that required significantchanges to the system architecture. If your version of Balance is 4.0 or later, you can use the ISO fileto do an in-place upgrade. If you have a version earlier than 4.0, the following upgrade options areavailable:

• You can install the 4.0 virtual appliance (VA) and then migrate the historical data andconfiguration settings from the 3.6 VA to the 4.0 VA. Refer to the 4.0 version of theOnCommand Balance Installation and Configuration Guide for complete upgrade instructions.You can then use the ISO file to upgrade to the latest version.

• For versions earlier than 3.6, you can contact NetApp Customer Support for upgrade options.

You can download the Balance 4.0 installation files from the NetApp Support site at support.netapp.com, and select Downloads > Software. To download the documentation, you canselect Documentation > Product Documentation.

Related tasks

Upgrading Balance on page 11

Related references



HTTP://support.netapp.com

Balance Proxy installation

The Balance Proxy is required to discover Windows servers and some storage arrays. Balance usesthe proxy to perform discovery collections on the monitored resources. You install the proxy on aphysical or virtual host and then add the proxy to Balance.

The following illustration shows which resources, in green, must be discovered through the proxyand also require a multiprovider or storage array management software. If the Balance virtualappliance (VA) is configured with 4 Gigabytes (GB) of memory, Balance can support a maximum of3 proxies. If the Balance VA is configured with 8 GB or higher of memory, Balance can supportadditional proxies.

Related tasks



Related references

Balance Proxy host requirements on page 14

13

What a multiprovider is on page 16

Balance Proxy host requirementsThe host on which you install the Balance Proxy must meet minimum system requirements based onthe number of servers the proxy will monitor.

Host requirementsThe table below lists the minimum system and software requirements for the server on which youinstall the proxy.

Resource Requirement

Proxy Host Dedicated physical or virtual machine with Windows Server 2003 SP1 orWindows Server 2008 R2 with User Account Control (UAC) disabled.

Other Windows versions are not supported. Do not install other NetAppOnCommand management software products on the host.

Storage At least 20 GB of disk space assigned to the proxy, approximately 10 GB shouldbe available after installation.

Java Runtime 32-bit version of Java is required for both 32-bit and 64-bit systems.

ArrayManagementSoftware

Array management software for the following storage arrays installed on theproxy host:

• EMC CLARiiON: NaviSECCLI.exe or Unisphere• EMC VNX: NaviSECCLI.exe• EMC Symmetrix: EMC Solutions Enabler• HDS: High Command Device Manager (HDvM)• HP EVA: HP StorageWorks Command View EVA• HP XP: HP StorageWorks XP Array Manager (Command View AE)

Balance uses the proxy and the management software to discover and collectdata from these storage arrays. During the proxy installation, you specify thelocation of the management software on the proxy host. When adding thestorage array to Balance, you might need to add a multiprovider.

Note: If you do not install all array management software initially, but installsome of them at a later time, you must reinstall the proxy and select theappropriate check boxes for each new management software you add.


Resource Requirement

User Account A user account with local administrative privileges on the proxy host.

The account can be a domain or group user, but make sure that the account willnot encounter prompts that require user action, such as password expirationnotifications or requests for acknowledgment. These prompts will interfere withthe proxy data collection process.

AntivirusSoftware

If antivirus software is installed on the proxy host, script scan functions must bedisabled. If your antivirus software uses script scan, exclude the followingdirectory from virus scan:

C:\Program Files\netapp

Firewall Firewall is disabled or ports 9443 and 443 are open for incoming and outgoingproxy communication.

Note: The proxy should be accessed by a single Balance VA only.

Proxy host resource limitsThe table below lists the recommended system requirements based on the number of monitoredservers that a single Balance Proxy can support. If the host cannot meet these requirements, or thenumber of monitored servers exceeds these values, data collections from the proxy can becomeunreliable. You can add additional proxies to increase the number of servers you want to monitor.

MonitoredServers

vCPUs CPUReservation(MHz)

MemoryReservation(MB)

MinimumDisks

NetworkUsage (KBps)

600 2 4000 2,048 4 360

400 2 3400 2,048 4 340

300 2 2600 2,048 2 260

200 2 1800 2,048 2 180

100 2 1000 2,048 1 80

Less than 100 2 500 2,048 1 40

Note: Values are based on Windows Server 2003. Windows Server 2008 might require additionalresources to support the proxy. You can use the vSphere Client to add additional virtual CPUs. Atleast 20 GB of disk space should be assigned to the proxy, and approximately 10 GB of disk spaceshould be available after installation.

Balance Proxy installation | 15

Related concepts

Balance Proxy installation on page 13

Related tasks



Related references


What a multiprovider isA multiprovider is a connector that Balance uses to access some storage arrays. Balance uses themultiprovider, or a combination of the multiprovider, proxy, and array management software, todiscover the storage array and enable data collection. You can add a multiprovider in Balance.

When you add a multiprovider to Balance, Balance uses the configuration information in themultiprovider record to discover the storage system.

Balance uses a multiprovider to access the following storage arrays:

• Engenio• HP 3PAR• IBM AIX, VIO, and LPAR• IBM DS or SVC

Balance uses a multiprovider, the proxy, and array management software to access the followingstorage arrays:

• EMC Symmetrix• Hitachi Data Systems• HP XP

Related tasks



Related references


EMC CLARiiON and VNX requirements on page 32

EMC Symmetrix requirements on page 32

Engenio requirements on page 35


HP 3PAR requirements on page 35

HP EVA requirements on page 36

HP XP requirements on page 37

HDS requirements on page 38


Installing the Balance ProxyBalance requires the Balance Proxy to discover and communicate with Windows servers and somestorage arrays. Depending on the storage array type, you may need to configure a multiprovider andarray management software, which the proxy uses to communicate with some storage arrays.

About this task

Balance creates a record for the proxy and uses the record to discover and communicate with theproxy. Install the proxy on a Windows Server host separate from Balance. The host must bededicated to hosting the proxy and any array management software that resides on the proxy hostonly.

Steps

1. Log in to the Windows Server on which you want to install the proxy.

2. Open a web browser and log in to Balance.

3. On the Discovery menu, select Proxies > Add proxy.

4. Follow the on-screen instructions to install the proxy.

The installer file displays and you can choose to open and run the proxyinstall.jnlp file, whichstarts the proxy installation wizard.

5. Complete the wizard to install.

On the step for installing array management software, the proxy installer displays the defaultpaths where it expects to find management software installed on the proxy host. If any of thepaths are incorrect, click Browse to locate the management software and update the path.

After you complete the installation wizard, the proxy is now selectable when adding a resource inBalance.

Note: If you do not install all array management software initially, but install some of them at alater time, you must reinstall the proxy and select the appropriate check boxes for each newmanagement software you add.

Related concepts

Balance Proxy installation on page 13

Balance Proxy installation | 17

Related references



Upgrading the Balance ProxyIf you are upgrading your version of Balance, you must also upgrade your proxies. The proxyinstaller does an in-place upgrade of the existing proxy.

Before you begin

The host on which you are installing the proxy meets the minimum system requirements.

Steps

1. In a web browser, log in to the proxy host and Balance.

2. To launch the proxy installation file, select Admin > Advanced > Install/Upgrade BalanceProxy.

3. Follow the on-screen instructions to install the latest proxy. The installer file displays and you canchoose to open and run the proxyinstall.jnlp file, which starts the proxy installation wizard.

4. Complete the wizard to perform the upgrade.

5. Repeat this procedure for each proxy host.

Note: To confirm that the upgrade completed successfully, you can rediscover the proxy inBalance to ensure that Balance can communicate with the proxy host.

Related concepts


Related tasks

Upgrading Balance on page 11

Related references




Configuring resources for data collection

Balance supports equipment from several vendors. You must make sure that each resource meets theminimum software requirements for Balance and is properly configured according to the vendorspecifications.

Before you use Balance to discover and collect performance statistics from your data centerresources, check the Balance requirements as well as the configuration requirements from yourequipment vendor. If a storage array requires the Balance Proxy, the proxy may require amultiprovider and array management software to discover the storage array.

For the latest information on supported system models and required software versions, use theInteroperability Matrix at: support.netapp.com/NOW/products/interoperability

Related concepts

Virtualization software requirements on page 42

Storage system requirements on page 28


Related references



Windows Server requirements on page 21

Linux and UNIX requirements on page 23

Database requirements on page 47

SAN device requirements on page 47

VMware vCenter Server and ESX and ESXi Serverrequirements

Balance supports VMware vCenter servers and allows for the discovery of guests associated withESX or ESXi Servers. It can also track VMotion activity.

The user account for accessing the vCenter Server, ESX Server, or ESXi Server must have a user roleat the data center level (top of the tree) with the Browse Datastore privilege. Balance requires thisrole to collect statistics for datastores.

VMware vCenter Server requirementsBalance supports monitoring of VMware vCenter Server and the hosted guest operating systems.

Each vCenter Server you add to Balance must have a unique vCenter ID.

19

http://support.netapp.com/NOW/products/interoperability/

VMware ESX or ESXi Server requirementsBalance supports standalone VMware ESX or ESXi Server.

To discover ESX or ESXi Servers, Balance has the following discovery requirements:

• FQDN, Hostname, or IP address of the server.• Username and password for the server.

Note: VM guests must have VMware Tools installed before they can be monitored.

ESX and ESXi servers have the following limitations:

• ESX hostd process stops and restarts with "exceed hard limit" memory errors when monitored bymultiple Balance systems. A patch from VMWare is required. The patch is available at: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012543

• VMware Tools must be installed and up-to-date on all guests for statistics gathering.• Balance uses the VMware SDK (Software Development Kit) to communicate with VMware ESX

servers (installed by default on most systems). You can download the SDK at: http://www.vmware.com/download/sdk/The SDK retrieves data via SOAP requests over HTTP.

If you want to configure this host or its cluster for vCenter Server discovery, see the VMwarevCenter Server requirements and the VMware ESX and ESXi Server requirements.

Note: Balance only supports Raw Disk Mappings (RDM) in physical compatibility mode.

Windows and Hyper-V Server requirementsBalance has specific discovery requirements for Microsoft Windows and Hyper-V Servers, includingadministrator access to the server and at least one Balance Proxy.

If you are monitoring Windows or Hyper-V servers that have physical mappings to SymmetrixDMX/V-Max (SE only) arrays, you must install the inq.exe in the following path on the BalanceProxy host:

c:\ProgramFiles\NetApp\bin

Balance uses WMI to discover Windows and Hyper-V servers. If the servers are behind a firewall,follow the instructions to configure ports behind Windows firewalls to ensure that Balance canaccess the necessary ports.

Related concepts



http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012543



http://www.vmware.com/download/sdk/

http://www.vmware.com/download/sdk/

Related tasks


Related references



Windows Server requirementsThe following supported versions of Microsoft Windows and the configuration information arerequired to discover each Windows server as a standalone or physical server.

Windows Server has the following discovery requirements:

• Have a local user account or domain account with valid username and password that is a memberof the administrators group.

• Be accessible to the Balance Proxy.• Have firewall disabled or open ports 9443 and 443 for incoming and outgoing proxy

communication.• You can optionally use these tools:

• FCINFO (Fibre Channel Info Tool)• Multipathing software (for example, Powerpath, SecurePath, and MPIO are supported)

Note: If you are using STORport Miniport drivers, multipathing software is required. Supporteddrivers include STORport and SCSIport Miniport drivers.

Microsoft cluster multiprovider

For Microsoft clusters, create a credential for the Windows servers in your cluster, use an existingBalance Proxy machine, and specify the cluster FQDN or IP address in Balance when adding theMicrosoft Cluster multiprovider. Do not configure the individual cluster nodes for discovery. WhenBalance discovers the Microsoft Cluster multiprovider, all nodes in the cluster appear in Balance asunmonitored.

When discovered, each node appears on the Unmonitored Servers page. You can select the check boxnext to each node you want to monitor and click Monitor Selected to move the nodes to the Serverspage.

Related concepts


Related tasks


Configuring resources for data collection | 21

Related references


Hyper-V Server requirementsSupported versions of Windows Hyper-V Server and the fulfillment of software requirementsassociated with the server are required to enable server discovery.

Balance does not support clustering for Hyper-V. Balance discovers Hyper-V virtual machines (VM)and adds Windows guests to the Unmonitored Server page.

Windows Hyper-V Server has the following discovery requirements:

• Have a local user account or domain account with valid username and password that is a memberof the administrators group.

• Be accessible to the Balance Proxy.• Have firewall disabled or open ports 9443 and 443 for incoming and outgoing proxy

communication.

Note: STORport Miniport drivers are supported by default.

You can optionally use these tools:

• FCINFO (Fibre Channel Info Tool)• Multipathing software (for example, Powerpath, SecurePath, or MPIO are supported)

Related concepts


Related tasks


Related references


Linux and UNIX server requirementsTo prepare each Linux and UNIX server for discovery and user authentication, you must configure itfor volume monitoring and password configuration or RSA authentication.

For Balance to discover Linux or UNIX servers, the server must be configured with one of thefollowing shells: sh, ksh, or bash

Related tasks

Configuring RSA authentication for Linux and UNIX servers on page 27


Related references


Linux and UNIX configuration for password authentication on page 26

Linux and UNIX configuration for volume monitoring on page 25

Linux and UNIX requirementsTo facilitate Balance discovery of your UNIX or Linux servers, you must define the root access andinstall Secure Shell (SSH) software.

Linux platform discovery requirements

Linux Type Requirements

Red Hat EnterpriseLinux

• Root access to the server or non-root access with sudo, which is a freedownload, to access restricted commands.

• SSH installed. Balance uses an SSH login using a password or keyexchange to communicate with Linux servers.

• To map storage from an EMC Symmetrix DMX/V (SE only storagearray) to Red Hat Enterprise Linux servers, the servers must have eitherVeritas Volume Manager or Inq installed.

Note: Oracle Automatic Storage Management (ASM) is supported,including the option for multipathing. RAC is not supported.

SUSE • Root access to the server or non-root access with sudo, which is a freedownload, to access restricted commands.


UNIX platform discovery requirements

UNIX Type Requirements

HP-UX • Root access to the server or non-root access with sudo, which is a freedownload, to access restricted commands.

• SSH installed - Balance uses an SSH login using a password or keyexchange to communicate with UNIX servers and requires a usernameand password with read-only permissions on the server.

• HP OpenView GlancePlus installed.

Note: If the server has volume managers, Balance can use them todiscover and collect volume statistics.


UNIX Type Requirements

IBM AIX • Root access to the server or non-root access with sudo, which is a freedownload, to access restricted commands.

Note: Sudo is also in the AIX Toolbox for Linux Applications. Sudoversion 1.6.7p5-3.aix5.1.ppc.rpm is required. For download andinstallation instructions, go to the IBM web site at: http://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.html

• SSH installed. Balance uses an SSH login using a password or keyexchange to communicate with UNIX servers. SSH is included with theAIX Toolbox for Linux that is distributed with AIX. For moreinformation, go to the IBM web site at http://www.ibm.com/developerworks/.

• A volume manager and an appropriate ODM driver for the connectedstorage array. If the AIX machine is connected to an EMC CLARiiONarray, and you have Powerpath installed, Powerpath installs theappropriate ODM driver automatically. If the AIX machine isconnected to an HP EVA array, and you have SecurePath installed,SecurePath installs the appropriate ODM driver automatically.

• Disk statistics collection enabled. To check the current setting, you canrun the following command:

"lsattr -E -l sys0 -a iostat"

To enable collection of disk statistics on AIX hosts, you can run thefollowing command:

"chdev -l sys0 -a iostat=true"

Solaris • Root access to the server or non-root access with sudo, which is a freedownload, to access restricted commands.


• Solaris Volume Manager (SVM) or Veritas Volume Manager (VxVM)are required for correct data collection. SVM might be included withyour Solaris installation. Balance supports DMP and PowerPathmultipathing.

• Sun::Solaris::Kstat Perl module (kstat) installed.• prtvtoc command in the sudoers file to provide access privileges for

discovering disk partitions.

Related concepts

Linux and UNIX server requirements on page 22


http://www-03.ibm.com/systems/power/software/aix/linux/toolbox/download.html



http://www.ibm.com/developerworks/

http://www.ibm.com/developerworks/

Related tasks


Related references



Linux and UNIX configuration for volume monitoringTo monitor and collect statistics for volumes on Linux and UNIX servers, Balance can collect fromraw volumes or from volume management software. For IBM AIX servers, volume managementsoftware is required.

To communicate with some volume managers, Balance needs the location of each volume manageron the server and root authentication. Balance uses the sudoers file on each server to locate andmonitor the volumes. The following table provides the installation path for each supported volumemanager. The sudoers file on each Linux and UNIX server must include the installation path to thevolume manager software installed on the server.

Note: To collect statistics from NFS volumes on Linux servers, the servers must have version2.6.18 or later of the Linux kernel.

VolumeManager

Platform Installation Locations

Dynamic LinkManager

IBM AIX /usr/DynamicLinkManager/bin/dlnkmgr

EmulexHBAnyware

Solaris /usr/sbin/hbanyware/hbacmd

Inq IBM AIX /usr/local/bin/inq

Red Hat

LogicalVolumeManager

Red Hat /sbin/lvm

Solaris

SUSE

Manageddevices (LinuxRAIDSoftware)

Red Hat /sbin/mdadm


VolumeManager

Platform Installation Locations

Powerpath IBM AIX /usr/sbin/powermt

Red Hat /sbin/powermt

SUSE

Solaris /etc/powermt

QLogic HostBus AdapterSimpleCommand LineInterface(SCLI)

Red Hat /usr/local/bin/scli,/opt/QLogic_Corporation/SANsurferCLI/scsli

SUSE

Solaris /usr/bin/ls/opt/QLogic_Corporation/SANsurferCLI/scli

Veritas VolumeManager

HP-UX /usr/lib/vxvm/diag.d/vxdmpinq,/usr/lib/vxvm/diag.d/vxscsiinq

IBM AIX /usr/lib/vxvm/diag.d/vxdmpinq,/usr/sbin/vxdisk,/usr/sbin/vxdmpadm,/usr/lib/vxvm/diag.d/vxscsiinq

Red Hat /usr/lib/vxvm/diag.d/vxdmpinq,/usr/sbin/vxdisk,/usr/lib/vxvm/diag.d/vxscsiinq

Solaris

SUSE

ZFS Solaris /usr/sbin/zfs,/usr/sbin/zpool

Related concepts


Related tasks


Related references



Linux and UNIX configuration for password authenticationIf you are using password authentication with a Linux or UNIX server, add the Balance user to /etc/sudoers using the visudo command.

The following entries must be in your sudoers file, which can only be modified by running visudoas root. visudo can be found in /usr/local/sbin.


Syntax:

Defaults !env_reset

username hostname=NOPASSWD: /sbin/fdisk,/sbin/scsi_id,/lib/udev/

scsi_id,/usr/local/bin/inq,/sbin/powermt,/usr/lib/vxvm/diag.d/

vxdmpinq,/usr/lib/vxvm/diag.d/vxscsiinq,/usr/sbin/vxdisk,/sbin/

dmsetup,/bin/mdadm,/sbin/lvm,/usr/local/bin/scsli,/opt/QLogic_Corporation/

SANsurferCLI/scsli

where:

• username is the username for accessing the Linux or UNIX server.• hostname is the FQDN or IP address of the Linux or UNIX server. The hostname can be ALL to

allow a connection from any host. (ALL) after the “=” is the UID with which you are allowed tosudo.

The default locations are assumed for these utilities. To enable a password prompt, changeNOPASSWD to PASSWD.

Related concepts


Related tasks


Related references



Configuring RSA authentication for Linux and UNIX serversTo use RSA authentication for monitoring Linux or UNIX servers, including self-monitoring of theBalance virtual appliance (VA), you need to create RSA keys and RSA credentials in Balance.

Steps

1. Create the following RSA keys:

• To monitor (self-monitor) the Balance VA, use the read-only self-monitor credentials.• To monitor Linux or UNIX servers, create an RSA keypair using the ssh-keygen program

from the read-only Balance user account.

Do not use a third-party key generator, such as PuTTy, to create the RSA keys.

2. In the user directory on each Linux or UNIX server you want to monitor, or on the Balance VA,copy or rename the id_rsa.pub key to .ssh/authorized_keys.

3. In Balance, create the RSA credentials.


4. On the Add Credentials page, for RSA File, upload the private side of the RSA keypair toBalance and specify the RSA key to use.

Note: The private key must be accessible to Balance.

5. If you are using a read-only user account, ensure that the sudoers file on each Linux or UNIXserver contains the correct installation paths to the installed volume managers.

Related concepts


Related references



Self-monitoring requirements on page 50


Storage system requirementsThis section lists the requirements for collecting discovery and statistical data from storage systemsin your data center.

Balance can communicate with some storage systems directly, while others require the BalanceProxy and some require the proxy, a multiprovider, and array management software. See "BalanceProxy host requirements."

Balance collects performance statistics from the following storage systems. For storage systems notlisted, Balance collects the statistics from the connected servers.

• NetApp• Dell EqualLogic• EMC CLARiiON and VNX• Hewlett Packard EVA• Hitachi Data Systems

For the latest information on supported system models and required software versions, use theInteroperability Matrix at: support.netapp.com/NOW/products/interoperability

Related references

NetApp FAS storage system requirements on page 29

NetApp V-Series systems requirements on page 31

Dell EqualLogic requirements on page 32

EMC CLARiiON and VNX requirements on page 32



http://support.netapp.com/NOW/products/interoperability/


HP EVA requirements on page 36



IBM storage array requirements for Balance on page 40



NetApp FAS storage system requirementsTo discover and collect statistics from NetApp FAS storage systems, Balance has specificrequirements depending on the Data ONTAP version and mode configuration.

Data ONTAP operating in 7-Mode

For NetApp storage systems with Data ONTAP operating in 7-Mode, Balance has the followingrequirements:

• Data ONTAP operating in 7-Mode.• Administrator (root) account.

Data ONTAP operating in Cluster-Mode

For NetApp storage systems (clusters) with Data ONTAP operating in Cluster-Mode, Balance hasthe following requirements:

• Data ONTAP operating in Cluster-Mode.• Cluster Vserver administrator (root) account with ontapi Application access and the read-only

role.• Cluster Management IP (LIF) to discover all nodes in the cluster.

Related concepts


Related tasks

Enabling discovery of Data ONTAP operating in 7-Mode with a user account on page 30

Related references



Enabling discovery of Data ONTAP operating in 7-Mode with a user account

For NetApp storage systems with Data ONTAP operating in 7-Mode, you can use a user account,instead of a standard administrator (root) account, to give Balance to access your storage systems.

About this task

You use a command line interface in FilerView and copy the command in this procedure to create thespecial user role.

Steps

1. Log into Data ONTAP on the NetApp storage system.

Note: In Balance, on the Storage page for a selected storage system, you can click Console tolaunch FilerView.

2. Enter the following command to create the user role:

useradmin role add balance_user

-a login-http-admin,api-system-get-info,api-system-get-version,api-license-list-info,api-fcp-adapter-list-info,cli-fcp,api-cf-status,api-disk-list-info,api-aggr-list-info,api-volume-list-info,api-volume-list-info-iter-start,api-volume-list-info-iter-next,api-volume-list-info-iter-end,api-volume-get-root-name,api-lun-list-info,api-lun-get-geometry,api-lun-map-list-info,api-qtree-list,api-lun-get-serial-number,api-lun-stats-list-info,api-system-cli,cli-rdfile,cli-ifconfig,api-vfiler-list-info,security-api-vfiler,api-nfs-status,api-nfs-exportfs-list-rules,api-nfs-exportfs-list-rules-2,api-cifs-status,api-cifs-share-list-iter-start,api-cifs-share-list-iter-next,api-cifs-share-list-iter-end,api-perf-object-list-info,api-perf-object-counter-list-info,api-perf-object-get-instances,api-perf-object-get-instances-iter-start,api-perf-object-get-instances-iter-next,api-perf-object-get-instances-iter-end,api-useradmin-user-list,api-useradmin-group-list,api-useradmin-role-list

where balance_user is the name of your user role.

Note: If you previously added a balance_user, you only need to update the role. You canreplace add with modify.

Adding the user role requires all commands to be on one line. You may want to copy thecommands to a .txt file, with Wordwrap disabled, and then copy into the Use Command Line.

3. Enter the following command to create the user group:

useradmin group add group -r balance_user

where, group is the name of the user group.

4. Enter the following command to add the user role to the user group:


useradmin user add balance_user -g group

Note: For NetApp clusters, only enter the FQDN or IP address for one of the storage systems;both are monitored and summarized information displays for the NetApp Cluster. If you weremonitoring NetApp clusters previous to Balance 3.0, delete both storage systems and re-addone. You must add the balance_user, listed above, to both storage systems in the cluster.

Related concepts


Related references



NetApp V-Series systems requirementsTo discover and collect statistics from NetApp V-Series systems and the back-end storage systems,Balance has specific requirements.

• Apply a Controller license to the V-Series systems and a Capacity license to the back-end storagesystems.

• Configure each back-end storage system for discovery and statistics collection, if supported.• Discover the V-Series systems and the back-end storage systems separately.

When Balance discovers NetApp V-Series systems, it discovers the local disk groups on the systemsand the disk groups from back-end storage. Balance discovers and presents the disk groups thatcontain LUNs from back-end storage as virtual disk groups.

For the local disk groups on V-Series systems, Balance can display the storage capacity, disk count,disk model, RAID level, and the topology mapping to other resources in the data center. Balancedoes not display this information for disk groups from back-end storage.

Analysis for V-Series systems is limited to the local storage resources on the physical system. It doesnot include the resources from the back-end storage system. To view discovery and statistical datafor the back-end storage, go to the Storage page and select the name of the storage system.

Related concepts


Related tasks

Enabling discovery of Data ONTAP operating in 7-Mode with a user account on page 30

Related references



Dell EqualLogic requirementsTo discover Dell EqualLogic storage arrays, Balance has the following requirements:

• In Balance, create credentials for accessing the storage array. On the Add credentials page:

• Leave the Login field blank.• For the Password field, type the SNMP community name password. Default is public. If an

SNMP community name does not exist, use the EqualLogic management software to create it.• In Balance, on the Add storage array page, for the FQDN/IP Address field, type the storage array

IP address, also referred to as the Group IP address.

EMC CLARiiON and VNX requirementsTo discover and collect statistics from EMC CLARiiON and VNX storage arrays, Balance requiresmanagement software, a username with "global scope" rights, and enabling array statistics.

• Array management software: NaviSECCLI.exe installed on the Balance Proxy host. ForCLARiiON arrays, you can install the latest version of EMC Unisphere. See "Proxy hostrequirements."

• A valid username with "global scope" monitoring rights.• Use Unisphere or Navisphere to enable array statistics logins.

You add EMC VNX arrays to Balance as CLARiiON arrays.

CLARiiON domain

Add the CLARiiON domain multiprovider so that Balance can discover all associated storage arraysand connected physical servers. Depending on how you configure the multiprovider, the arrays mightdisplay as unmonitored or monitored. All discovered physical servers display on the UnmonitoredServers page.

Note: If the storage arrays in the domain are behind a storage virtualization device, after discoverythe storage virtualization device appears on the Unmonitored Servers page. You should ignorethese “servers.”

Related references


EMC Symmetrix requirementsTo discover and collect statistics from EMC Symmetrix DMX or VMAX storage arrays, Balancerequires a current Solutions Enabler version and specific settings.

• Array management software: EMC Solutions Enabler must be installed on the Balance Proxyhost. See "Proxy host requirements."

• On the Solutions Enabler host that is connected to the Symmetrix array, the following servicesneed to be running:


• EMC storapid• EMC storsrvd

Best Practice: Ensure that the Solutions Enabler version matches the version of the remote client.Collection errors might occur if different versions are used.

Related tasks

Enabling data collection from Symmetrix arrays on page 33

Configuring the proxy for Symmetrix storage arrays on page 34

Related references


Enabling data collection from Symmetrix arrays

To enable data collection from Symmetrix arrays, add each storage array as a Symmetrixmultiprovider.

Steps

1. Select Discovery > Multiproviders.

2. Click Add multiprovider.

3. For Type, select Symmetrix.

4. For Multiprovider Name, type a name for the multiprovider.

5. For Proxy, select the proxy host with SYMCLI.

6. Click Save.


In the Discovery Collection column, when OK appears, the proxy is discovering the array. Oncediscovered, the array appears on the Unmonitored Storage Arrays page.

8. Select Discovery > Storage Arrays and click Unmonitored Storage Arrays.

9. Select the array and click Monitor Selected to move the array to the Monitored list.

Related tasks

Configuring the proxy for Symmetrix storage arrays on page 34

Related references



Configuring the proxy for Symmetrix storage arrays

For EMC Symmetrix DMX or VMAX (Solutions Enabler only), you can install the Balance Proxyout-of-band or in-band of the Symmetrix storage array.

About this task

• Out-of-band configuration (recommended) involves running the proxy and a copy of SolutionsEnabler (SE) on a dedicated Windows Server host that is not connected to the Symmetrix array.The proxy communicates with the Symmetrix array by communicating through the SE host that isconnected to the array.

• In-band configuration involves running both the proxy and Solutions Enabler on the sameWindows Server host that is connected to the Symmetrix array. The in-band configuration is notrecommended because the proxy service can put additional load on the server and the version ofSolutions Enabler.

Steps

1. On the proxy host, locate the following configuration file:

C:\ProgramFiles\EMC\SYMAPI\config\netcnfg

2. In a text editor, open the netcnfg file.

3. Add the following line, or edit one of the examples, to specify the name and address of the SEhost that is connected to the Symmetrix storage array:

SE_Host - TCPIP node001 SE_IP SE_Port -

where,

• SE_Host is the name of the SE host.• SE_IP is the IP address of the SE host.• SE_Port is the port on the SE host.

4. Add the following Windows System Variables:

SYMCLI_CONNECT_TYPE=REMOTE SYMCLI_CONNECT=SE_Host

where SE_Host matches the value for SE_Host added previously in this procedure. The proxyassociates this value with the value in the netcnfg file to locate the Solutions Enabler serverconnected to the Symmetrix storage array.

5. Restart the Balance Proxy service.

6. To validate the out-of-band configuration, open a command prompt and type the following:

symcfg list

The list of EMC Symmetrix storage arrays is displayed.

7. In Balance, select Discovery > Multiprovider.


8. Add the EMC Symmetrix storage array as a Symmetrix multiprovider.

Related tasks

Enabling data collection from Symmetrix arrays on page 33

Related references



Engenio requirementsTo discover Engenio storage arrays, Balance requires the CIM Agent.

Multiprovider: Balance requires that the Engenio/LSI SMI-S CIM Agent is installed on a Windowshost and accessible to Balance. To download the SMI-S CIM Agent, go to the NetApp Support siteat:http://support.netapp.com/NOW/download/software/eseries_providers/10.80.x4.51/

Related tasks

Enabling Engenio discovery collection on page 35

Enabling Engenio discovery collection

To enable discovery collection for Engenio storage arrays, you must add the array as a SMI-Smultiprovider.

Steps

1. In Balance, select Discovery > Multiproviders.


3. Add the array as a SMI-S multiprovider.

4. Click Save.



Related references


HP 3PAR requirementsTo discover and collect statistics from HP 3PAR storage arrays, Balance requires the SMI-S Agentand a user account with certain permissions.

• Multiprovider: Embedded 3PAR SMI-S Agent must be accessible on the IP network to theBalance machine.


http://support.netapp.com/NOW/download/software/eseries_providers/10.80.x4.51/

• Balance requires the IP address and port number of the 3PAR storage array along with CIMAgent credentials.

• A user account with Super permission level.

Note: The 3PAR CIM server is disabled by default. To enable the 3PAR CIM server, you can runthe following command:

startcim

.

Related references


HP EVA requirementsTo discover and collect statistics from HP EVA storage arrays, Balance has specific softwarerequirements.

• Array management software: HP StorageWorks Command View EVA suite is installed on theBalance Proxy host. See "Proxy host requirements."

• After installing the HP StorageWorks Command View EVA software, install, or reinstall, theBalance Proxy and select the following Command View files in the installation wizard:

• EVAPerf - Enterprise Virtual Array Performance Monitor (EVA Perf) for statistics collection.• SSSU - Storage System Scripting Utility (SSSU) for discovery collection.

Best Practice: Although HP supports up to 16 EVAs per Command View server, you should notconfigure more than four.

Do not install the Balance Proxy on the same server with StorageWorks Command View EVA that isconnected directly to the HP EVA array. Set up a separate dedicated server to host the Balance Proxyand StorageWorks Command View EVA suite.

In Balance, the array name you enter in the Array Name field on the Add new storage array pagemust be identical to the actual array name.

Related concepts


Related references



HP XP requirementsTo discover and collect statistics from HP XP storage arrays, Balance has software and LUNrequirements.

• Array management software: HP StorageWorks XP Array Manager (Command View AE) mustbe installed on the Balance Proxy host. See "Proxy host requirements."

• For statistics collection, the array must have LUSE LUNs.• Enable discovery and statistics collection.

Related tasks

Enabling HP XP discovery collection on page 37

Enabling HP XP statistics collection on page 38

Related references


Enabling HP XP discovery collection

To enable discovery collection for HP XP arrays, you must add credentials and software and thendiscover the proxy and the storage array.

Steps

1. In Balance, select Discovery > Credentials.

2. Click Add credentials.

3. Add credentials for discovery collection, which is the login for Command View AE. The defaultlogin is system and the default password is manager.

4. Click Save.



7. Add the array as a Hitachi multiprovider.

8. Click Save.

9. Select Discovery > Proxies.

In the Discovery Collection column, when Up is displayed, the proxy is discovering the array.Once discovered, the array is displayed on the Unmonitored Storage Arrays page.




Related tasks

Enabling HP XP statistics collection on page 38

Related references


Enabling HP XP statistics collection

To collect statistics for HP XP, only LUSE LUNs are supported.

Steps

1. Install the HP XP Export Tool and the following JAR files on the Balance Proxy host:

• JSanExport.jar• JSanRmiServerEx.jar

You must install the export tool from the exact RAID Manager CD that shipped with your HP XParray.

2. In Storage Navigator, under Edit Storage Arrays, from the Stat Proxy menu select the BalanceProxy host.

3. In Balance, create a credential based on the Storage Navigator user you created for each HP XParray.

Related tasks

Enabling HP XP discovery collection on page 37

Related references


HDS requirementsTo discover and collect statistics from HDS 9900 storage arrays, TagmaStore USP or NSC storagearrays, or AMS storage arrays, you must install High Command Device Manager software andenable discovery and statistics collection.

• Array management software: High Command Device Manager (HDvM) must be installed on theBalance Proxy host or on a host that is accessible to Balance over the IP network. See "Proxy hostrequirements."

• Discovery and statistics collection must be enabled.

Related tasks

Enabling HDS discovery collection on page 39

Enabling HDS statistics collection on page 39


Related references


Enabling HDS discovery collection

To enable discovery collection for HDS storage arrays, you must add credentials and add the array asa Hitachi multiprovider.

Steps

1. In Balance, select Discovery > Credentials.

2. Click Add credentials.

3. Add credentials for discovery collection with a minimum of Peer privileges. This is the login forHigh Command Device Manager. The default login is system and the default password ismanager.

4. Click Save.



7. Add the array as a Hitachi multiprovider.

8. Click Save.

9. Select Discovery > Proxies.

In the Discovery Collection column, when Up is displayed, the proxy is discovering the array.Once discovered, the array is displayed on the Unmonitored Storage Arrays page.



Related tasks

Enabling HDS statistics collection on page 39

Related references


Enabling HDS statistics collection

To collect statistics from HDS storage arrays, you need to install the Hitachi Performance MonitorExport Tool and create a user. Only arrays with LUSE LUNs are supported.

Steps

1. Install the Hitachi Performance Monitor Export Tool on the Balance Proxy host.


You must install the export tool from the CD that shipped with your TagmaStore array.

2. On the storage array, create a user in Storage Navigator.

3. In Balance, create a credential and edit your storage array for statistics collection.

Related tasks

Enabling HDS discovery collection on page 39

Related references


IBM storage array requirements for BalanceDifferent types of IBM storage arrays have different requirements.

IBM Total Storage DS4000 and DS5000 series/FAStT

Multiprovider: Engenio/LSI SMI-S CIM Agent is installed on a Windows host and accessible toBalance. After installing the agent, you need to configure it. See "Configuring the SMI-S agent forIBM DS4000 and DS5000 storage systems."

IBM DS6000, DS8000, and ESS storage systems

Multiprovider:

• DS Open API SMI is installed on a host connected to DS6000 or ESS storage systems.• CIM Agent is installed on a host connected to DS8000 storage systems.

The multiprovider host must be accessible to Balance over the IP network.

Balance requires the IP address and port number of the agent along with CIM Agent credentials.Refer to the following web site for installation and configuration details:http://www-1.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=D400&uid=ssg1S4000665&loc=en_US&cs=utf-8%E2%8C%A9=en.

IBM XIV

Multiprovider: SMI-S CIM Agent integrated into the XIV. The XIV must be accessible to Balanceover the IP network.

Balance requires the IP address and port number of the XIV along with CIM Agent credentials.


http://www-1.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=D400&uid=ssg1S4000665&loc=en_US&cs=utf-8⟨=en




Enabling IBM discovery collection

To enable discovery collection for an IBM array, add the array to Balance as a SMI-S multiprovider.

Steps

1. In Balance, select Discovery > Multiproviders.


3. Add the array as a SMI-S multiprovider.

4. Click Save.



Configuring the SMI-S agent for IBM DS4000 and DS5000 storage systems

Balance requires the SMI-S CIM Agent to discover IBM Total Storage DS4000 and DS5000 storagesystems. After installing the agent on a Windows server, you need to configure it to point to eachstorage system that you want to discover in Balance.

About this task

You can add a maximum of three storage systems to the SMI-S agent. If you need to add more thanthree storage systems, install another SMI-S agent on a different server.

Steps

1. Download the SMI-S CIM Agent from the NetApp Support site at:http://support.netapp.com/NOW/download/software/eseries_providers/10.80.x4.51/

2. Install the SMI-S CIM Agent on a Windows server that is accessible to Balance.

The agent is installed in C:\Program Files\EngenioProvider

3. At a DOS prompt, change directory to the following location:

C:\Program Files\EngenioProvider\SMI_SProvider\bin

4. Enter the following command to run the ProviderUtil utilty: providerutil

5. Enter root for the username and password.

Note: Only enter a port number if the default has changed.

6. Select option 1 to add a device (storage system).

7. Enter the IP address of a storage system controller.

8. Enter the password for the storage system controller.




Note: If there is no password, leave the value blank (default).

The storage system is added to the ProviderUtil utlity, which Balance uses to discover the storagesystem. To add additional storage systems, repeat steps 6 through 8.

9. In Balance, add the SMI-S agent as a multiprovider. See "Enabling IBM discovery collection."

Virtualization software requirementsBalance supports virtualization software for HMC, Virtual IO Servers (IBM LPAR), IBM SANVolume Controller (SVC), and HP SAN Virtualization Storage Platform (SVSP).

Related concepts

IBM SAN Volume Controller (SVC) requirements on page 45

HP SAN Virtualization Storage Platform (SVSP) requirements on page 46

Related references

HMC Virtual IO Servers (IBM LPAR) requirements on page 42

HMC Virtual IO Servers (IBM LPAR) requirementsFor Balance to discover, HMC servers, VIO servers, and the associated AIX logical partitions(LPAR), Balance requires specific software is installed on each VIO server. There are two optionsfor enabling discovery.

The two options to choose from when setting up communication between Balance and HMC VIOservers:

• You can use an account with root privileges for accessing the HMC and VIO servers anddiscovering the associated AIX logical partitions (LPAR). You then add the HMC and VIOservers to Balance to monitor the AIX LPARs.

• You can use a user account to discover the HMC servers, VIO servers, and the associated AIXlogical partitions (LPAR). You configure a sudoers file for accessing the VIO servers and copythe file to each VIO server you wan to discover. You then add the HMC and VIO servers toBalance to monitor the AIX LPARs.

Related concepts


Related tasks

Enabling HMC and VIO discovery using root on page 43

Enabling HMC and VIO discovery using a user account on page 44


Enabling HMC and VIO discovery using root

You can use an account with root privileges for accessing the HMC and VIO servers and discoveringthe associated AIX logical partitions (LPAR). You then add the HMC and VIO servers to Balance tomonitor the AIX LPARs.

Before you begin

• Balance has root access for the following resources:

• HMC Server: hscroot and password• VIO Server: username (padmin) and password (must be the same for all VIO servers)• AIX LPARs: username and password

• Latest ODM driver installed on each VIO server for the servers to communicate with eachconnected storage array. If the VIO server is connected to a CLARiiON storage array, and youhave Powerpath installed, the appropriate ODM driver is installed automatically by Powerpath. Ifthe VIO server is connected to an HP EVA storage array, and you have SecurePath installed, theappropriate ODM driver is installed automatically by SecurePath.

About this task

You copy the provided aixhba utility to each VIO server to establish communication betweenBalance, the HMC servers, the VIO servers, and their associated AIX logical partitions (LPARs).Balance uses the aixhba utility to map the data topology from each VIO server to the connectedstorage arrays.

Steps

1. Use Secure Shell (SSH) to log in to the Balance virtual appliance (VA). The default directory is /home/selfmonitor.

2. Copy the aixhba utility to the /usr/bin directory on each VIO server.

3. In Balance, select Discovery > Multiproviders > Add new multiprovider.

4. Enter the IP address of the HMC server.

5. Select the credentials for the HMC server and VIO servers.

6. Click Save to create the multiprovider record.

Balance discovers each HMC server and VIO server. Each AIX LPAR appears on the DiscoveryUnmonitored Servers page.

7. On the Discovery Unmonitored Servers page, select the check box next to each AIX LPAR youwant to monitor and click Monitor Selected. You will need to select the appropriate credentialsfor each AIX LPAR.

Each AIX LPAR moves to the Discovery Servers page.


Related concepts


Related references


Enabling HMC and VIO discovery using a user account

You can use a user account to discover the HMC servers, VIO servers, and the associated AIXlogical partitions (LPAR). You configure a sudoers file for accessing the VIO servers and copy thefile to each VIO server you wan to discover. You then add the HMC and VIO servers to Balance tomonitor the AIX LPARs.

Before you begin

• Balance has credentials for the following resources:

• HMC Server: username and password. The username must be a member of the “staff” group.The recommended HMC Task Role is "hmcviewer."

• VIO Server: username and password (must be the same for all VIO servers you plan todiscover)

• AIX LPARs: username and password• Latest ODM driver installed on each VIO server for the servers to communicate with each

connected storage array. If the VIO server is connected to a CLARiiON storage array, and youhave Powerpath installed, the appropriate ODM driver is installed automatically by Powerpath. Ifthe VIO server is connected to an HP EVA storage array, and you have SecurePath installed, theappropriate ODM driver is installed automatically by SecurePath.

• SSH installed on the HMC and VIO servers. Balance uses an SSH login using a password or keyexchange to communicate with HMC and VIO servers.

• Sudo installed on each VIO server. You can download the required version of sudo here: www.bullfreeware.com/download/wpar_tt/sudo-1.6.7p5-3.aix5.1.ppc.rpm

About this task

Balance uses the provided aixhba utility to map the data topology from each VIO server to theconnected storage arrays. The sudoers file you copy to each VIO server contains entries that specifythe location of the aixhba utility file.

Steps

1. Use the visudo command to edit the sudoers file on each VIO server to include the followingentries for running the aixhba utility on each VIO server.


Example

The entry you choose depends on your security requirements (password or no password).

Defaults !env_resetusername hostname=PASSWD: /tmp/aixhbaorDefaults !env_resetusername hostname=NOPASSWD: /tmp/aixhba

where:

• username is the username for accessing the VIO server.• hostname is the fully-qualified name (FQDN) or IP address of the Balance virtual appliance

(VA) accessing the VIO server. The hostname can be ALL to allow a connection from anyhost. (ALL) after the “=” is the UID with which you are allowed to sudo.

• /tmp/aixhba is the default location where the aixhba utility is copied to the VIO server.

Note: To enable a password prompt, change NOPASSWD to PASSWD.

2. In Balance, select Discovery > Multiproviders > Add new multiprovider.

3. On the Type menu, select IBM HMC.

4. Enter the IP address of the HMC server.

5. Select the credentials for the HMC server and VIO servers.

6. Click Save to create the multiprovider record.

Balance discovers each HMC server and VIO server that you specified. During the initialdiscovery, Balance automatically copies the aixhba utility from the VA to each VIO server.Each AIX LPAR appears on the Discovery Unmonitored Servers page.

7. On the Discovery Unmonitored Servers page, select the check box next to each AIX LPAR youwant to monitor and click Monitor Selected. You will need to select the appropriate credentialsfor each AIX LPAR.

Each AIX LPAR moves to the Discovery Servers page.

Related tasks

Enabling HMC and VIO discovery using root on page 43

Related references


IBM SAN Volume Controller (SVC) requirementsSVC virtual disks are modeled as server volumes and the managed disks as server LUNs. Cross-reference the list of supported storage systems requirements for Balance with IBM’s support matrixto determine the storage devices supported for SVC.


Balance uses SSH login by key exchange to communicate with IBM SVC (SAN Volume Controller);SVC requires a public and private SSH RSA key for an account on the server, logging in with"admin" for the username.

Note: The "admin" username does not provide administrative privileges; it is simply a namingconvention.

Related tasks


Enabling IBM SAN Volume Controller statistics collection on page 46

Enabling IBM SAN Volume Controller statistics collection

To enable SVC statistics collection, use the SVL command line interface (CLI).

Steps

1. Open the SVL CLI.

2. Type the following command to start statistics generation at an interval of one minute:

svctask startstats -interval 1

3. In Balance, select Discovery > SAN Devices.

4. Click the name link of the SVC device.

5. On the SAN Device Summary page, click Edit.

6. On the Edit SAN Device page, select the Statistics collection enabled check box.

Related concepts

IBM SAN Volume Controller (SVC) requirements on page 45

Related tasks


HP SAN Virtualization Storage Platform (SVSP) requirementsFor the HP SAN Virtualization Storage Platform (SVSP), Balance requires the SMI-S CIM Agent.

Balance communicates with the SMI-S CIM Agent integrated into the SVSP. The SVSP must beaccessible on the IP network to the Balance VA. Balance requires the IP address and port number ofthe SVSP along with CIM Agent credentials. SMI-S is a separate installation option with the SVSPSVM which requires assistance from an HP representative to configure.

The HP SVSP has no detail page in Balance and will only manifest itself in the topology view of aserver or array for which it is in the I/O topology.


Refer to your HP SVSP documentation for more information.

SAN device requirementsBalance supports the Brocade and Cisco SAN devices (switches).

Balance supports the SNMPv1 and SNMPv2c protocols only. For Balance to communicate withSAN devices that have the SNMPv3 protocol enabled, the v1 and v2c protocols must also beenabled.

Brocade

Balance has the following Brocade discovery requirements:

• In Balance, create credentials for accessing the switch. On the Add credentials page:


SNMP community name does not exist, use the Brocade management software to create it.• For the FQDN/IP Address field, type the switch IP address.

Cisco

Balance has the following Cisco discovery requirements:

• In Balance, create credentials for accessing the switch. On the Add credentials page:


SNMP community name does not exist, use the Cisco management software to create it.• For the FQDN/IP Address field, type the switch IP address.

Database requirementsThe Data Topology view in Balance can show the end-to-end topology between the monitored serverhosting a database application and its associated resources, such as connected storage arrays.

To display database topology objects, such as the schema and data types, you must configureBalanceto discover the database as an application.

Note: Balance does not monitor applications hosted on Microsoft clusters.

Balance support Oracle and Microsoft SQL Server database applications.

Related tasks

Enabling topology views of database applications on page 48


Preparing an Oracle database for discovery on page 49

Preparing a MS SQL Server for discovery on page 49

Enabling topology views of database applicationsWhen you discover a database in Balance, all volumes on the hosting server are assigned to a defaultapplication for that server, and the database objects do not automatically appear in the Data Topologyview.

About this task

To display database objects in the Data Topology view, complete the following for each databaseyou want to monitor, in this order:

Steps

1. In Balance, add and discover each storage array associated with the database.

2. Add and discover the server hosting the database.

3. Prepare each database for discovery.

4. Select Applications > Add Application and add each database as an application. For ApplicationType, select a DBtype.

5. On the Configuration page for the database application, map the volumes of the hosting server tothe database.

6. Discover each database, or wait for the next discovery collection.

Result

Balance discovers each database topology and populates the Data Topology view. Each discoverycollection queries the hosting server to identify changes to the database topology.

Related tasks



Related references



Preparing an Oracle database for discovery

To prepare an Oracle database for Balance discovery, you need to create a user account with thenecessary privileges.

Steps

1. On each Oracle database that you want to monitor, create a user account with the followingsystem rights:

create session select any dictionary

For example, User name: AAPMAP, Password: appmap, and System privileges granted: Createsession, select any dictionary.

2. In Balance, create access credentials using the user login credentials.

Related tasks



Related references


Preparing a MS SQL Server for discovery

To prepare a Microsoft SQL Server for discovery, check that the MS SQL authentication service andMixed Mode are enabled. On the SQL server, create a local, read-only user login.

Steps

1. Ensure that the MS SQL authentication service is enabled.

Balance cannot use Windows authentication to communicate with MS SQL Server.

2. Ensure that Mixed Mode is enabled (default) on each MS SQL database.

Changing the mode might require a full restart of the SQL server. See the MS SQL online helpfor instructions.

3. On the MS SQL Server, create a local, read-only user login.

4. Add the following user mapping permissions to each login:

• db_reader• public

5. In Balance, create access credentials using the user login credentials from the previous steps.


For Method, select Login.

Related tasks



Related references


Self-monitoring requirementsTo monitor the Balance virtual appliance (VA) in a process referred to as "self-monitoring", or toaccess the selfmonitor directory on the VA, you need to create a specific credential for accessing theVA.

The selfmonitor credential has the following requirements:

• User: selfmonitor• Password: h1ghlys3cure

The username and password are case-sensitive. A Balance Proxy is not required for discovering theVA. To change the password, you can use the Advanced Management Tool.

Balance communication portsThe Balance virtual appliance (VA) and the Balance Proxy use different ports to communicate witheach resource.

The following illustration shows the port number and protocol for each resource type accessed by theVA and the default ports accessed by the proxy after the VA opens port 9443 on the proxy host. Forinstalling Java on the proxy server, you access the Java installer from the Balance VA using port 443.Two port numbers separated by an ellipsis (...) indicate the first and second ports that the VA opens.


Configuring ports behind Windows firewallsTo communicate with Windows servers, Balance uses the WMI protocols and initially accesses port445. The first exchanges occur on ports 135-139. After establishing a connection with the servers andcreating a remote instance, the communication switches over to other lesser-known ports1024-65535.This process ensures that well-known ports are free for other applications.

About this task

To see the current port settings on a Windows server, select Control Panel > Windows Firewall >Exceptions tab > File and Printer Sharing and click Edit.

Steps

1. To configure ports behind a Windows firewall, open up TCP port 135 in the firewall.

2. Configure a port range for DCOM protocols.

3. Open up the same port range in the Windows firewall.

Result

For the return communications, WMI ports are assigned by DCOM, and they can use any randomport between 1024 and 66535. No port exception is required.


Advanced Balance configuration options

You use the Advanced Management Tool (AMT) to perform more complex configuration operations,such as configuring network settings and backing up the Balance database.

Related tasks


Adding network adapters on page 55

Related references


Accessing the Advanced Management Tool (AMT)You can access the Advanced Management Tool (AMT) using the vSphere Client or the Secure Shell(SSH).

Step

1. To access the AMT, use either of these methods:

• vSphere Client - In a vSphere Client, select the virtual appliance and then select the Consoletab. Click inside the console to login. If you are upgrading Balance using the upgrade ISO file,you must use the vSphere Client to access the console.

• SSH - Log into the IP address or fully-qualified domain name (FQDN) of eth0.

The username and password for both methods is netapp (all lowercase). You can change thedefault password after logging in.

Related concepts

Advanced Balance configuration options on page 52

Related tasks


Related references



Advanced Management Tool configuration options forBalance

The Advanced Management Tool (AMT) allows you to update Balance, configure and maintain yourBalance network settings, and backup Balance.

When you first log into the AMT, the Main Menu displays the following options:

Update Balance

Initiates the Balance virtual appliance (VA) upgrade.

Hypervisor Tools

Provides options for installing and uninstalling VMware Tools on the VA.

• Install - Installs VMware Tools on the VA. During a new Balance installation, tools are installedautomatically. You can use this option if you need to upgrade the tools to a newer version. Beforeyou can use this option, use the vSphere Client to install the VMware Tools ISO on the VA:Right-click the VA and select Guest > Install/Upgrade VMware Tools.

Note: During the tools installation, informational messages might display. You can ignorethese messages and continue through the installation. After the installation has completed, usethe vSphere Client to check the status of the tools.

• Uninstall - Uninstalls VMware Tools from the VA. Use this option for diagnostic purposes only.

IP Management Options

Provides options for configuring and maintaining your Balance network settings. The followingoptions are displayed:

• Display Current Management IP Address Settings - Displays the current network settings forBalance, such as the management IP address, netmask, gateway, etc.

• Change Management IP Address Settings - Provides options for changing the Balance networksettings.

Note: If you want to change the IP address and Balance has obtained its address using DHCP,in Balance, select Admin > Configuration > Network tab and enter or change the appropriatesettings.

• Display Domain Name Search Settings - Searches for servers across multiple domainsconfigured in Change Management IP Address Settings and displays the results.

• Change Domain Name Search Settings - Provides options for adding or changing domainnames you want to use in a search (for example, yourcompany.com, yourcompany.local). Domainnames added manually require a space between them, but no commas. If the DHCP server isproperly configured, DNS names are added automatically.

Advanced Balance configuration options | 53

Note: The domain names you want to use in a search can be added using this option or throughthe Balance web client in the Network Adapter section at Admin > Configuration > Network.Balance must then be restarted.

• Display Static Routes - Displays configured static IP routes.• Modify Static Routes - Provides options for configuring static IP routes.• Disable Interface - Provides options for disabling network adapters.• Enable Interface - Provides options for enabling disabled network adapters.• Commit Changes - Applies any changes made in the options above. Changes do not take effect

until you commit them with this option. After selecting this option, you are given the opportunityto exit without saving your changes before the commit is performed.

• Ping A Host - Pings a target host for confirming IP address changes or proper DNSconfiguration.

Balance Backup Options

Provides options for backing up the Balance database, which contains the collected data about yourdata center resources. The following options are displayed:

• Database Backup and Offload - Packages and encrypts the database as a .gpg file. You can backup the file locally to the /home/selfmonitor/offloadsdirectory or use FTP to transfer it to anotherlocation. The file is encrypted with a static password.

Note: If you back up the file locally, you could use SCP to transfer the file to another location.

• Database Restore and Retrieve - Restores the encrypted .gpg file backed up using the DatabaseBackup and Offload option. Decrypts the file using the same static pass phrase used duringencryption. If you restore locally, you are prompted to specify the file name relative to the /home/selfmonitor/offloads directory. If you are retrieving a remote backup using FTP, specify the filename relative to the home FTP directory.

• Gather Interop Info and Offload - Packages information about discovered resources, includingOStype, version, array type, model, and storage array LUN count, into an encrypted .tgz file andthen uses FTP to send the file to a specified location.

System Configuration

Provides options for managing Balance. The following options are displayed:

• Display Balance Status - Determines whether the Balance monitor is running and the exact startdate.

• Reboot Operating System - Initiates the correct sequence of events to restart the Balanceoperating system.

• Shutdown Operating System - Initiates the correct sequence of events to shutdown the Balanceoperating system.

• Change Management Tool Password - Changes the password for accessing the AMT.• Change ‘selfmonitor’ Password - Changes the password for discovering the Balance virtual

appliance. Monitoring the virtual appliance in Balance is referred to as self-monitoring.


Related concepts


Related tasks



Adding network adaptersYou use the Advanced Management Tool (AMT) to add a network adapter to the virtual appliance(VA) and configure Balance to detect the network adapter. You might need an additional adapter toseparate network traffic. This procedure involves restarting Balance.

Before you begin

To prevent gaps in data collection, you should perform this procedure before you start a Balanceupgrade.

Steps

1. Use a vSphere Client to add the network adapter to the VA.

Note: See the vSphere online help for instructions.

2. After adding the network adapter, select the VA and then select the Console tab to access theAMT.

3. Log into the AMT.

4. Select IP Management Options > Change Management IP Address Settings.

5. Select the new network adapter (for example, eth1).

6. When prompted to enable the network adapter, type y (Yes).

Note: If DHCP is enabled, the AMT attempts to obtain an IP address automatically. If DHCPcannot be detected, you are prompted to specify the network settings.

7. Optionally, change the network settings to use a static IP address.

8. On the IP Management Menu, type 9 to commit the changes to program memory.

9. Type b (Back) to return to the Main Menu.

10. To complete the configuration, select System Configuration > Reboot Operating System torestart Balance.

Related concepts


Advanced Balance configuration options | 55

Related tasks


Related references



Copyright information

Copyright © 1994–2012 NetApp, Inc. All rights reserved. Printed in the U.S.

No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in anelectronic retrieval system—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license anddisclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice.NetApp assumes no responsibility or liability arising from the use of products described herein,except as expressly agreed to in writing by NetApp. The use or purchase of this product does notconvey a license under any patent rights, trademark rights, or any other intellectual property rights ofNetApp.

The product described in this manual may be protected by one or more U.S. patents, foreign patents,or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject torestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

57

Trademark information

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri,ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, CampaignExpress, ComplianceClock, Cryptainer, CryptoShred, Data ONTAP, DataFabric, DataFort, Decru,Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful,gFiler, Go further, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault,Manage ONTAP, MetroCluster, MultiStore, NearStore, NetCache, NOW (NetApp on the Web),Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX, SANscreen,SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service Builder, Shadow Tape,Simplicity, Simulate ONTAP, SnapCopy, SnapDirector, SnapDrive, SnapFilter, SnapLock,SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot,SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror,Tech OnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL,Web Filer, and XBB are trademarks or registered trademarks of NetApp, Inc. in the United States,other countries, or both.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. A complete and current list ofother IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United Statesand/or other countries. Microsoft is a registered trademark and Windows Media is a trademark ofMicrosoft Corporation in the United States and/or other countries. RealAudio, RealNetworks,RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia,RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or othercountries.

All other brands or products are trademarks or registered trademarks of their respective holders andshould be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.


http://www.ibm.com/legal/copytrade.shtml

Index

7-Modediscovery requirements 29

A

Advanced Management Tool (AMT)adding network adapters 55options 53starting 52

applicationsdatabase 48

arraysDell EqualLogic 32Engenio 35HP XP 37IBM 40

authenticationLinux and UNIX server requirements 22RSA 27SQL Server 49

B

Balancedatabase 9features 5installation requirements 7installing 7, 9introduction 5monitoring the VA 50questions you can answer 6upgrading 11

Balance Clientrequirements 9

Balance Proxyhost requirements 14installing 17

best practicesconfiguring HP EVA 36Solutions Enabler version requirement 32

Brocadediscovery requirements 47

C

Ciscodiscovery requirements 47

clustersdiscovery requirements 29Microsoft Windows Server 21

communicationports 50

configuringCLARiiON domain 32out-of-band proxy 34resources 19RSA authentication 27virtual appliance 10with Advanced Management Tool (AMT) 53

D

dashboard pagediscovery 9

data collectionconfiguring resources 19EMC Symmetrix 33prevent gaps 55

databasesapplications 48Balance 9requirements 47

deployingvirtual appliance 9

deploymentrequirements 7

discoveryaccess 7-Mode systems with a user account 30Brocade requirements 47Cisco requirements 47Dell EqualLogic requirements 32EMC CLARiiON requirements 32EMC Symmetrix requirements 32Engenio requirements 35Hitachi Data Systems (HDS) requirements 38HP 3PAR requirements 35HP EVA requirements 36IBM requirements 40, 41IBM SVC requirements 45

Index | 59

Linux requirements 23NetApp FAS requirements 29NetApp V-Series requirements 31Oracle requirements 47proxy 13SAN device requirements 47SQL Server requirements 47storage systems supported 28UNIX requirements 23vCenter requirements 19VMware ESX and ESXi Server requirements 20Windows requirements 21

documentationlist of 6

E

EMC CLARiiONdiscovery requirements 32

EMC Symmetrixdata collection 33multiprovider 32, 33proxy configuration 34

Engenioadding arrays 35multiprovider 35

F

firewallsports behind 51

Flash playerrequirements 9

H

Hitachi Data Systems (HDS)discovery 39requirements 38statistics collection 39

HMC VIO serversdiscovery methods 42

HP SANvirtualization 46

HP XPenabling discovery 37requirements 37statistics collection 38

Hyper-Vservers 20

I

IBMconfiguring SMI-S agent 41discovery 41requirements 40SAN volume statistics 46

IBM DS and ESSmultiprovider 40

IBM LPARdiscovery requirements 42

IBM SVCdiscovery requirements 45

IBM Total Storagemultiprovider 40

IBM XIVmultiprovider 40

installingBalance 7, 9Balance Proxy 17

J

Javarequirements 9

L

Linuxdiscovery requirements 23RSA authentication 27volume monitoring configuration 25

M

memoryrequirements 8

monitoringthe Balance VA 50

multiproviderEMC Symmetrix 32, 33Engenio 35for proxy 17, 28HP 3PAR 35HP XP 37IBM 40IBM SVC 45Microsoft cluster 21what it is 16


N

NetAppFAS storage system requirements 29

NetApp FAS storage systemsrequirements 29

NetApp storage systemscreate user role for 7-Mode systems 30V-Series requirements 31

network adaptersadding 55

O

Oraclediscovery requirements 47

Oracle databaseconfiguring for discovery 49

P

passwordsLinux UNIX authentication 26

portsconfiguring behind Windows firewalls 51used by virtual appliance 50

product documentationlist of 6

proxyEMC Symmetrix 32, 34host requirements 14in-band configuration 34installing 17multiprovider requirements 16out-of-band configuration 34requirements 13upgrading 18

R

requirementsBalance installation 7Client system 9databases 47Dell EqualLogic 32EMC CLARiiON 32EMC Symmetrix 32Engenio 35HP SAN virtualization 46HP XP 37

IBM 40memory 8proxy 13SAN devices 47self-monitoring 50storage system discovery 28VA host 7vCenter server 19virtualization software 42Windows servers 20

RSAconfiguring authentication 27

S

SAN devicesrequirements 47

self-monitoring 50servers

discoveryHyper-V Server requirements 22

ESX and ESXi Server 19Hyper-V 22Linux and UNIX configuration 25vCenter 19VMware ESX and ESXi Server 20Windows 20

SQL Serverconfiguring for discovery 49discovery requirements 47enabling topology views 48

statistics collectionHitachi Data Systems (HDS) 39HP XP 38IBM SAN volume 46supported storage systems 28

T

topology viewsdatabase application and resources 47enabling for SQL Server databases 48Flash player requirement 9

U

UNIXdiscovery requirements 23RSA authentication 27volume monitoring configuration 25

Index | 61

upgradingBalance 4.0+ 11proxy 18version 3.6 or earlier 12

user accountdiscovery from 44

V

VA host requirementsrequirements 7

vCenterdiscovery requirements 19

VIO serversdiscovery requirements 42

virtual applianceconfiguring 10

deploying 9ports used 50resource recommendations 8

virtualizationHP SAN platform requirements 46

virtualization softwarerequirements 42

vSphere Clientdeploying virtual appliance 9

W

web browserrequirements 9

Windowsserver requirements 21


Date post:	02-Jan-2016
Category:	Documents
Upload:	tekkie
View:	257 times
Download:	4 times

OnCommand Balance 4100 Installation And

Documents