OnCommand Balance 4100 Installation and

OnCommand Balance 4.1.
0 Installation and Configuration Guide
NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 463-8277 Web: www.netapp.com Feedback: doccomments@netapp.com Part number 215-07287_A0 December 2012
Table of Contents | 3
Contents
Introduction to OnCommand Balance ....................................................... 5
OnCommand Balance features .................................................................................... 5 Questions you can answer using OnCommand Balance ............................................. 6 OnCommand Balance product documentation ........................................................... 6
Balance installations ..................................................................................... 7

Balance 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 ......................................................................... 13

Balance Proxy host requirements .............................................................................. 14 What a multiprovider is ............................................................................................. 16 Installing the Balance Proxy ..................................................................................... 17 Upgrading the Balance Proxy ................................................................................... 18
Configuring resources for data collection ................................................ 19

VMware 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
4 | OnCommand Balance Installation and Configuration Guide 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 ................................................. 52

Accessing the Advanced Management Tool (AMT) ................................................ 52 Advanced Management Tool configuration options for Balance ............................. 53 Adding network adapters .......................................................................................... 55
Copyright information ............................................................................... 57 Trademark information ............................................................................. 58 Index ............................................................................................................. 59
Introduction to OnCommand Balance

OnCommand Balance provides performance planning, troubleshooting, and optimization for physical and virtual data centers. Balance helps you manage the performance and workloads of your dynamic shared infrastructure. OnCommand Balance is an analytics-based IT management software solution that helps you optimize performance and utilization of virtual machines (VM), physical servers, and storage systems. IT organizations can use Balance to quickly isolate performance problems, reduce infrastructure costs, and enable a service-oriented infrastructure. Balance uses agent-less discovery and collection of statistical data from your monitored resources. It provides multi-vendor, heterogeneous support for Linux and UNIX servers, Windows servers, hypervisors (VMware vSphere and Microsoft Hyper-V), SAN devices, and storage systems.
OnCommand Balance features

OnCommand Balance routinely collects configuration and performance statistics information from your monitored data center. It uses the statistics to predict and identify performance problems, notify you of current or potential problems, and offers recommendations for troubleshooting the root cause of 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.
6 | OnCommand Balance Installation and Configuration Guide
Questions you can answer using OnCommand Balance

Storage and IT administrators can use OnCommand Balance to gain visibility into the overall health of their data centers, troubleshoot performance bottlenecks, optimize resources that are over-utilized or under-utilized, and predict performance impact to new or existing workloads when planning to add or 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? 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? 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?
Optimize performance
Predict problems
OnCommand Balance product documentation

OnCommand Balance is accompanied by a set of guides. OnCommand Balance Installation and Configuration Guide OnCommand Balance User Guide Provides instructions for setting up OnCommand Balance in your data center. It also provides the system requirements and configuration instructions for adding the servers, SAN devices, storage systems, and applications you want to monitor. Provides an overview of how to use OnCommand Balance to analyze and monitor the performance of your data center, including adding and discovering resources, identifying under-utilized and over-utilized resources, using the Performance Index to determine how well a server is handling its current workload, and viewing the topology of associated resources.
Balance installations
Balance is distributed as a self-contained, fully-formed virtual appliance (VA) available in an OVA file, 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 file includes the main software components required to run and operate Balance. The VA contains the Balance software and database. No additional virtual machine (VM) configuration is required to get started. For upgrades from Balance 4.0 or later installations you use the latest ISO file to perform an in-place upgrade on the existing VA.
Balance installation requirements

Before deploying the Balance virtual appliance (VA), you must determine the appropriate minimum resource requirements for your environment and ensure that the VMware ESX or ESXi Server and proxy host meet minimum requirements. The minimum resource requirements for the ESX or ESXi Server on which you deploy the virtual appliance (VA) increase based on the number of servers you plan to monitor. To deploy the VA, you can use the VMware vSphere Client.
Virtual appliance host requirements

The VMware ESX or ESXi server that will host the virtual appliance (VA) must meet minimum resource requirements. Review these requirements before deploying the VA. Resource ESX or ESXi Server Network Virtual CPUs Virtual Memory Minimum Requirements Hardware and software must be 64-bit. 1 Gigabit Ethernet connection for fastest installation (optional). By default, the VA uses DHCP to communicate with the IP network. 2 @ 2.33 GHz 4 GB With this amount of memory, you can add a maximum of 3 proxies to Balance. Increase the memory to twice this value or higher to add more proxies. At least 5 disk spindles in RAID DP or other RAID array.
Disks
8 | OnCommand Balance Installation and Configuration Guide Resource Storage Minimum Requirements Data store requires at least 205 GB of disk capacity, which includes an extra 5 GB for VA memory and additional files (for example, swap). Refer to the virtual appliance resource recommendations for the minimum 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 recommendations

The virtual appliance (VA) resource recommendations listed here are based on the number of servers you 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 not available on the ESX or ESXi Server, the VA might not power on. Monitored servers 1,200 800 600 400 200 100 or less vCPUs CPU Memory reservation (MB) (MHz) 8000 5000 4000 3000 2000 1500 8192 8192 4096 4096 4096 4096 Memory Minimum reservation disks (MB) 8192 8192 4096 4096 4096 4096 12 10 8 6 4 3 Network usage (KBps) 140 120 100 80 60 60
4 4 4 4 2 2
Related concepts

Related tasks
Balance installations | 9
Related references
Virtual appliance host requirements on page 7
Balance web browser requirements

Balance 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 that Compatibility Mode is enabled. See the Microsoft IE online help for information on enabling and disabling Compatibility Mode. For all browsers, we recommend disabling any popup blockers so that all Balance content, such as online help, displays properly. There is a bug with Windows 2003 that prevents IE from displaying the Balance login page. To resolve this problem, use Firefox or apply the following hot fix to the server:
http://support.microsoft.com/kb/938397/
Installing Balance
To install Balance you use a VMware vSphere Client to deploy the virtual appliance (VA) to a VMware 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 Balance
database to efficiently grow to the maximum available capacity as you add resources to your data center. vSphere 4.0 does not have this option. For more information, see the vSphere online help. 6. After the VA has successfully deployed to the ESX or ESXi Server, power on the VA.

Note: If your vCenter has multiple networks specified, check the VA configuration to confirm that the correct network is selected.
7. In the vSphere Client, click the Console tab to monitor the status as the VA powers up, Balance starts, 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 IP address to the VA. You enter this IP address in a web browser to access and use the Balance web client 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 appliance

After deploying the virtual appliance (VA) and powering it on, you can then open a web browser and use the fully-qualified domain name (FQDN) or IP address assigned to the VA to access Balance and begin 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 into Balance the Dashboard page is inactive (empty), but displays a linked list of data center resources that you can discover and monitor. The Dashboard is populated when it has discovered the data center resources in its environment.
Balance installations | 11
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 Balance
Upgrading from Balance 4.0 or later involves using an ISO upgrade file to do an in-place upgrade of the 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 select Downloads > 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 want to 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 to remove any out-of-date information. After you finish
Upgrade the existing Balance Proxies.

Related concepts

Related tasks
Upgrading the Balance Proxy on page 18 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 earlier

Older versions of Balance must be upgraded to version 4.0 before they can be upgraded to version 4.1 or later. Balance version 4.0 introduced several new features and enhancements that required significant changes to the system architecture. If your version of Balance is 4.0 or later, you can use the ISO file to do an in-place upgrade. If you have a version earlier than 4.0, the following upgrade options are available: You can install the 4.0 virtual appliance (VA) and then migrate the historical data and configuration settings from the 3.6 VA to the 4.0 VA. Refer to the 4.0 version of the OnCommand 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 can select Documentation > Product Documentation.
Related tasks
Upgrading Balance on page 11

Related references
13
Balance Proxy installation

The Balance Proxy is required to discover Windows servers and some storage arrays. Balance uses the proxy to perform discovery collections on the monitored resources. You install the proxy on a physical or virtual host and then add the proxy to Balance. The following illustration shows which resources, in green, must be discovered through the proxy and also require a multiprovider or storage array management software. If the Balance virtual appliance (VA) is configured with 4 Gigabytes (GB) of memory, Balance can support a maximum of 3 proxies. If the Balance VA is configured with 8 GB or higher of memory, Balance can support additional proxies.
Related tasks
Installing the Balance Proxy on page 17 Upgrading the Balance Proxy on page 18
Related references
Balance Proxy host requirements on page 14
What a multiprovider is on page 16
Balance Proxy host requirements

The host on which you install the Balance Proxy must meet minimum system requirements based on the number of servers the proxy will monitor. Host requirements The table below lists the minimum system and software requirements for the server on which you install the proxy. Resource Proxy Host Requirement Dedicated physical or virtual machine with Windows Server 2003 SP1 or Windows Server 2008 R2 with User Account Control (UAC) disabled. Other Windows versions are not supported. Do not install other NetApp OnCommand management software products on the host. Storage Java Runtime Array Management Software At least 20 GB of disk space assigned to the proxy, approximately 10 GB should be available after installation. 32-bit version of Java is required for both 32-bit and 64-bit systems. Array management software for the following storage arrays installed on the proxy 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 collect data from these storage arrays. During the proxy installation, you specify the location of the management software on the proxy host. When adding the storage array to Balance, you might need to add a multiprovider.
Note: If you do not install all array management software initially, but install some of them at a later time, you must reinstall the proxy and select the appropriate check boxes for each new management software you add.
Balance Proxy installation | 15 Resource User Account Requirement 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 will not encounter prompts that require user action, such as password expiration notifications or requests for acknowledgment. These prompts will interfere with the proxy data collection process. Antivirus Software If antivirus software is installed on the proxy host, script scan functions must be disabled. If your antivirus software uses script scan, exclude the following directory from virus scan:
C:\Program Files\netapp
Firewall
Firewall is disabled or ports 9443 and 443 are open for incoming and outgoing proxy communication.
Note: The proxy should be accessed by a single Balance VA only.
Proxy host resource limits The table below lists the recommended system requirements based on the number of monitored servers that a single Balance Proxy can support. If the host cannot meet these requirements, or the number of monitored servers exceeds these values, data collections from the proxy can become unreliable. You can add additional proxies to increase the number of servers you want to monitor. Monitored Servers 600 400 300 200 100 Less than 100 vCPUs CPU Reservation (MHz) 2 2 2 2 2 2 4000 3400 2600 1800 1000 500 Memory Reservation (MB) 2,048 2,048 2,048 2,048 2,048 2,048 Minimum Disks 4 4 2 2 1 1 Network Usage (KBps) 360 340 260 180 80 40
Note: Values are based on Windows Server 2003. Windows Server 2008 might require additional resources to support the proxy. You can use the vSphere Client to add additional virtual CPUs. At least 20 GB of disk space should be assigned to the proxy, and approximately 10 GB of disk space should be available after installation.

Related concepts
Balance Proxy installation on page 13

Related tasks
Related references
What a multiprovider is
A multiprovider is a connector that Balance uses to access some storage arrays. Balance uses the multiprovider, or a combination of the multiprovider, proxy, and array management software, to discover 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 the multiprovider 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 following storage arrays: EMC Symmetrix Hitachi Data Systems HP XP
Related tasks
Related references
Balance Proxy host requirements on page 14 EMC CLARiiON and VNX requirements on page 32 EMC Symmetrix requirements on page 32 Engenio requirements on page 35
Balance Proxy installation | 17
HP 3PAR requirements on page 35 HP EVA requirements on page 36 HP XP requirements on page 37 HDS requirements on page 38 Balance Proxy host requirements on page 14
Installing the Balance Proxy

Balance requires the Balance Proxy to discover and communicate with Windows servers and some storage arrays. Depending on the storage array type, you may need to configure a multiprovider and array 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 the proxy. Install the proxy on a Windows Server host separate from Balance. The host must be dedicated to hosting the proxy and any array management software that resides on the proxy host only.
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, which starts the proxy installation wizard. 5. Complete the wizard to install. On the step for installing array management software, the proxy installer displays the default paths where it expects to find management software installed on the proxy host. If any of the paths 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 in Balance.
Note: If you do not install all array management software initially, but install some of them at a later time, you must reinstall the proxy and select the appropriate check boxes for each new management software you add. Related concepts
Balance Proxy installation on page 13

Related references
Balance Proxy host requirements on page 14 What a multiprovider is on page 16
Upgrading the Balance Proxy

If you are upgrading your version of Balance, you must also upgrade your proxies. The proxy installer 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 Balance Proxy. 3. Follow the on-screen instructions to install the latest proxy. The installer file displays and you can choose 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 in Balance to ensure that Balance can communicate with the proxy host. Related concepts

Related tasks
Upgrading Balance on page 11

Related references
Balance Proxy host requirements on page 14 What a multiprovider is on page 16
19
Configuring resources for data collection

Balance supports equipment from several vendors. You must make sure that each resource meets the minimum software requirements for Balance and is properly configured according to the vendor specifications. Before you use Balance to discover and collect performance statistics from your data center resources, check the Balance requirements as well as the configuration requirements from your equipment vendor. If a storage array requires the Balance Proxy, the proxy may require a multiprovider and array management software to discover the storage array. For the latest information on supported system models and required software versions, use the Interoperability Matrix at: support.netapp.com/NOW/products/interoperability
Related concepts
Virtualization software requirements on page 42 Storage system requirements on page 28 Balance communication ports on page 50
Related references
Virtual appliance host requirements on page 7 What a multiprovider is on page 16 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 Server requirements

Balance supports VMware vCenter servers and allows for the discovery of guests associated with ESX 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 role at the data center level (top of the tree) with the Browse Datastore privilege. Balance requires this role to collect statistics for datastores.
VMware vCenter Server requirements

Balance 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.
VMware ESX or ESXi Server requirements

Balance 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 by multiple 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 VMware vCenter 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 requirements

Balance has specific discovery requirements for Microsoft Windows and Hyper-V Servers, including administrator access to the server and at least one Balance Proxy. If you are monitoring Windows or Hyper-V servers that have physical mappings to Symmetrix DMX/V-Max (SE only) arrays, you must install the inq.exe in the following path on the Balance Proxy 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 can access the necessary ports.
Related concepts
Configuring resources for data collection | 21

Related tasks

Related references
What a multiprovider is on page 16 Balance Proxy host requirements on page 14
Windows Server requirements

The following supported versions of Microsoft Windows and the configuration information are required 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 member of 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. Supported drivers include STORport and SCSIport Miniport drivers.
Microsoft cluster multiprovider For Microsoft clusters, create a credential for the Windows servers in your cluster, use an existing Balance Proxy machine, and specify the cluster FQDN or IP address in Balance when adding the Microsoft Cluster multiprovider. Do not configure the individual cluster nodes for discovery. When Balance discovers the Microsoft Cluster multiprovider, all nodes in the cluster appear in Balance as unmonitored. When discovered, each node appears on the Unmonitored Servers page. You can select the check box next to each node you want to monitor and click Monitor Selected to move the nodes to the Servers page.
Related concepts

Related tasks

Related references
Hyper-V Server requirements

Supported versions of Windows Hyper-V Server and the fulfillment of software requirements associated 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 member of 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 requirements

To prepare each Linux and UNIX server for discovery and user authentication, you must configure it for volume monitoring and password configuration or RSA authentication. For Balance to discover Linux or UNIX servers, the server must be configured with one of the following shells: sh, ksh, or bash
Related tasks
Configuring RSA authentication for Linux and UNIX servers on page 27

Related references
Linux and UNIX requirements on page 23 Linux and UNIX configuration for password authentication on page 26 Linux and UNIX configuration for volume monitoring on page 25
Linux and UNIX requirements

To facilitate Balance discovery of your UNIX or Linux servers, you must define the root access and install Secure Shell (SSH) software. Linux platform discovery requirements Linux Type Red Hat Enterprise Linux Requirements Root access to the server or non-root access with sudo, which is a free download, to access restricted commands. SSH installed. Balance uses an SSH login using a password or key exchange to communicate with Linux servers. To map storage from an EMC Symmetrix DMX/V (SE only storage array) to Red Hat Enterprise Linux servers, the servers must have either Veritas 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 free download, to access restricted commands. SSH installed. Balance uses an SSH login using a password or key exchange to communicate with Linux servers.
UNIX platform discovery requirements UNIX Type HP-UX Requirements Root access to the server or non-root access with sudo, which is a free download, to access restricted commands. SSH installed - Balance uses an SSH login using a password or key exchange to communicate with UNIX servers and requires a username and password with read-only permissions on the server. HP OpenView GlancePlus installed.
Note: If the server has volume managers, Balance can use them to discover and collect volume statistics.
24 | OnCommand Balance Installation and Configuration Guide UNIX Type IBM AIX Requirements Root access to the server or non-root access with sudo, which is a free download, to access restricted commands.
Note: Sudo is also in the AIX Toolbox for Linux Applications. Sudo
version 1.6.7p5-3.aix5.1.ppc.rpm is required. For download and installation 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 key exchange to communicate with UNIX servers. SSH is included with the AIX Toolbox for Linux that is distributed with AIX. For more information, go to the IBM web site at http://www.ibm.com/ developerworks/. A volume manager and an appropriate ODM driver for the connected storage array. If the AIX machine is connected to an EMC CLARiiON array, and you have Powerpath installed, Powerpath installs the appropriate ODM driver automatically. If the AIX machine is connected 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 can run the following command:
"lsattr -E -l sys0 -a iostat"
To enable collection of disk statistics on AIX hosts, you can run the following command:
"chdev -l sys0 -a iostat=true"
Solaris
Root access to the server or non-root access with sudo, which is a free download, to access restricted commands. SSH installed. Balance uses an SSH login using a password or key exchange to communicate with Linux servers. Solaris Volume Manager (SVM) or Veritas Volume Manager (VxVM) are required for correct data collection. SVM might be included with your Solaris installation. Balance supports DMP and PowerPath multipathing. 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

Related tasks

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 configuration for volume monitoring

To monitor and collect statistics for volumes on Linux and UNIX servers, Balance can collect from raw volumes or from volume management software. For IBM AIX servers, volume management software is required. To communicate with some volume managers, Balance needs the location of each volume manager on the server and root authentication. Balance uses the sudoers file on each server to locate and monitor the volumes. The following table provides the installation path for each supported volume manager. The sudoers file on each Linux and UNIX server must include the installation path to the volume manager software installed on the server.
Note: To collect statistics from NFS volumes on Linux servers, the servers must have version 2.6.18 or later of the Linux kernel.
Volume Manager Dynamic Link Manager Emulex HBAnyware Inq
Platform IBM AIX Solaris IBM AIX Red Hat
Installation Locations /usr/DynamicLinkManager/bin/dlnkmgr /usr/sbin/hbanyware/hbacmd /usr/local/bin/inq
Logical Volume Manager Managed devices (Linux RAID Software)
Red Hat Solaris SUSE Red Hat
/sbin/lvm
/sbin/mdadm
26 | OnCommand Balance Installation and Configuration Guide Volume Manager Powerpath Platform IBM AIX Red Hat SUSE Solaris QLogic Host Red Hat Bus Adapter SUSE Simple Command Line Solaris Interface (SCLI) Veritas Volume HP-UX Manager IBM AIX Red Hat Solaris SUSE ZFS
Related concepts
Installation Locations /usr/sbin/powermt /sbin/powermt
/etc/powermt /usr/local/bin/scli,/opt/QLogic_Corporation/SANsurferCLI/scsli
/usr/bin/ls/opt/QLogic_Corporation/SANsurferCLI/scli
/usr/lib/vxvm/diag.d/vxdmpinq,/usr/lib/vxvm/diag.d/vxscsiinq /usr/lib/vxvm/diag.d/vxdmpinq,/usr/sbin/vxdisk,/usr/sbin/ vxdmpadm,/usr/lib/vxvm/diag.d/vxscsiinq /usr/lib/vxvm/diag.d/vxdmpinq,/usr/sbin/vxdisk,/usr/lib/vxvm/ diag.d/vxscsiinq
Solaris
/usr/sbin/zfs,/usr/sbin/zpool

Related tasks

Related references
Linux and UNIX requirements on page 23 Linux and UNIX configuration for password authentication on page 26
Linux and UNIX configuration for password authentication

If 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 visudo as root. visudo can be found in /usr/local/sbin.
Configuring resources for data collection | 27 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 to sudo.
The default locations are assumed for these utilities. To enable a password prompt, change NOPASSWD to PASSWD.
Related concepts

Related tasks

Related references
Linux and UNIX requirements on page 23 Linux and UNIX configuration for volume monitoring on page 25
Configuring RSA authentication for Linux and UNIX servers

To use RSA authentication for monitoring Linux or UNIX servers, including self-monitoring of the Balance 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.
28 | OnCommand Balance Installation and Configuration Guide 4. On the Add Credentials page, for RSA File, upload the private side of the RSA keypair to Balance 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 UNIX server contains the correct installation paths to the installed volume managers.
Related concepts

Related references
Linux and UNIX requirements on page 23 Linux and UNIX configuration for password authentication on page 26 Self-monitoring requirements on page 50 Linux and UNIX configuration for volume monitoring on page 25
Storage system requirements

This section lists the requirements for collecting discovery and statistical data from storage systems in your data center. Balance can communicate with some storage systems directly, while others require the Balance Proxy and some require the proxy, a multiprovider, and array management software. See "Balance Proxy host requirements." Balance collects performance statistics from the following storage systems. For storage systems not listed, 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 the Interoperability 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 EMC Symmetrix requirements on page 32
Engenio requirements on page 35 HP EVA requirements on page 36 HP XP requirements on page 37 HDS requirements on page 38 IBM storage array requirements for Balance on page 40 Balance Proxy host requirements on page 14 What a multiprovider is on page 16
NetApp FAS storage system requirements

To discover and collect statistics from NetApp FAS storage systems, Balance has specific requirements 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 following requirements: 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 has the 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
Storage system requirements on page 28

Related tasks
Enabling discovery of Data ONTAP operating in 7-Mode with a user account on page 30
Related references
NetApp V-Series systems requirements on page 31
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 the special 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 to launch 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,apilicense-list-info,api-fcp-adapter-list-info,cli-fcp,api-cf-status,apidisk-list-info,api-aggr-list-info,api-volume-list-info,api-volume-listinfo-iter-start,api-volume-list-info-iter-next,api-volume-list-infoiter-end,api-volume-get-root-name,api-lun-list-info,api-lun-getgeometry,api-lun-map-list-info,api-qtree-list,api-lun-get-serialnumber,api-lun-stats-list-info,api-system-cli,cli-rdfile,cliifconfig,api-vfiler-list-info,security-api-vfiler,api-nfs-status,apinfs-exportfs-list-rules,api-nfs-exportfs-list-rules-2,api-cifsstatus,api-cifs-share-list-iter-start,api-cifs-share-list-iter-next,apicifs-share-list-iter-end,api-perf-object-list-info,api-perf-objectcounter-list-info,api-perf-object-get-instances,api-perf-object-getinstances-iter-start,api-perf-object-get-instances-iter-next,api-perfobject-get-instances-iter-end,api-useradmin-user-list,api-useradmingroup-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 can replace add with modify.
Adding the user role requires all commands to be on one line. You may want to copy the commands 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 were monitoring NetApp clusters previous to Balance 3.0, delete both storage systems and re-add one. You must add the balance_user, listed above, to both storage systems in the cluster. Related concepts

Related references
NetApp V-Series systems requirements on page 31 NetApp FAS storage system requirements on page 29
NetApp V-Series systems requirements

To 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 storage systems. 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 systems and the disk groups from back-end storage. Balance discovers and presents the disk groups that contain 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. Balance does 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 does not include the resources from the back-end storage system. To view discovery and statistical data for 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
NetApp FAS storage system requirements on page 29
Dell EqualLogic requirements

To 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 requirements

To discover and collect statistics from EMC CLARiiON and VNX storage arrays, Balance requires management software, a username with "global scope" rights, and enabling array statistics. Array management software: NaviSECCLI.exe installed on the Balance Proxy host. For CLARiiON arrays, you can install the latest version of EMC Unisphere. See "Proxy host requirements." 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 arrays and connected physical servers. Depending on how you configure the multiprovider, the arrays might display as unmonitored or monitored. All discovered physical servers display on the Unmonitored Servers page.
Note: If the storage arrays in the domain are behind a storage virtualization device, after discovery
the storage virtualization device appears on the Unmonitored Servers page. You should ignore these servers.
Related references
EMC Symmetrix requirements

To discover and collect statistics from EMC Symmetrix DMX or VMAX storage arrays, Balance requires a current Solutions Enabler version and specific settings. Array management software: EMC Solutions Enabler must be installed on the Balance Proxy host. See "Proxy host requirements." On the Solutions Enabler host that is connected to the Symmetrix array, the following services need to be running:
Configuring resources for data collection | 33 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 Symmetrix multiprovider.
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. 7. Select Discovery > Multiproviders. In the Discovery Collection column, when OK appears, the proxy is discovering the array. Once discovered, 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
EMC Symmetrix requirements on page 32
Configuring the proxy for Symmetrix storage arrays For EMC Symmetrix DMX or VMAX (Solutions Enabler only), you can install the Balance Proxy out-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 Solutions Enabler (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 is connected to the array. In-band configuration involves running both the proxy and Solutions Enabler on the same Windows Server host that is connected to the Symmetrix array. The in-band configuration is not recommended because the proxy service can put additional load on the server and the version of Solutions 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 SE host 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 proxy associates this value with the value in the netcnfg file to locate the Solutions Enabler server connected 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.
Configuring resources for data collection | 35 8. Add the EMC Symmetrix storage array as a Symmetrix multiprovider.
Related tasks
Enabling data collection from Symmetrix arrays on page 33

Related references
EMC Symmetrix requirements on page 32 Balance Proxy host requirements on page 14
Engenio requirements
To discover Engenio storage arrays, Balance requires the CIM Agent. Multiprovider: Balance requires that the Engenio/LSI SMI-S CIM Agent is installed on a Windows host and accessible to Balance. To download the SMI-S CIM Agent, go to the NetApp Support site at: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-S multiprovider.
Steps
1. In Balance, select Discovery > Multiproviders. 2. Click Add multiprovider. 3. Add the array as a SMI-S multiprovider. 4. Click Save. 5. Select Discovery > Storage Arrays and click Unmonitored Storage Arrays. 6. Select the array and click Monitor Selected to move the array to the Monitored list.
Related references
Engenio requirements on page 35
HP 3PAR requirements
To discover and collect statistics from HP 3PAR storage arrays, Balance requires the SMI-S Agent and a user account with certain permissions. Multiprovider: Embedded 3PAR SMI-S Agent must be accessible on the IP network to the Balance machine.
36 | OnCommand Balance Installation and Configuration Guide Balance requires the IP address and port number of the 3PAR storage array along with CIM Agent 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 run the following command: startcim
.
Related references
HP EVA requirements
To discover and collect statistics from HP EVA storage arrays, Balance has specific software requirements. Array management software: HP StorageWorks Command View EVA suite is installed on the Balance Proxy host. See "Proxy host requirements." After installing the HP StorageWorks Command View EVA software, install, or reinstall, the Balance 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 not configure more than four. Do not install the Balance Proxy on the same server with StorageWorks Command View EVA that is connected directly to the HP EVA array. Set up a separate dedicated server to host the Balance Proxy and StorageWorks Command View EVA suite. In Balance, the array name you enter in the Array Name field on the Add new storage array page must be identical to the actual array name.
Related concepts

Related references
HP XP requirements
To discover and collect statistics from HP XP storage arrays, Balance has software and LUN requirements. Array management software: HP StorageWorks XP Array Manager (Command View AE) must be 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 then discover 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 default login is system and the default password is manager. 4. Click Save. 5. Select Discovery > Multiproviders. 6. Click Add multiprovider. 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. 10. Select Discovery > Storage Arrays and click Unmonitored Storage Arrays. 11. Select the array and click Monitor Selected to move the array to the Monitored list.

Related tasks
Enabling HP XP statistics collection on page 38

Related references
HP XP requirements on page 37
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 XP array. 2. In Storage Navigator, under Edit Storage Arrays, from the Stat Proxy menu select the Balance Proxy host. 3. In Balance, create a credential based on the Storage Navigator user you created for each HP XP array.
Related tasks
Enabling HP XP discovery collection on page 37

Related references
HP XP requirements on page 37
HDS requirements
To discover and collect statistics from HDS 9900 storage arrays, TagmaStore USP or NSC storage arrays, or AMS storage arrays, you must install High Command Device Manager software and enable discovery and statistics collection. Array management software: High Command Device Manager (HDvM) must be installed on the Balance Proxy host or on a host that is accessible to Balance over the IP network. See "Proxy host requirements." 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 as a 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 for High Command Device Manager. The default login is system and the default password is manager. 4. Click Save. 5. Select Discovery > Multiproviders. 6. Click Add multiprovider. 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. 10. Select Discovery > Storage Arrays and click Unmonitored Storage Arrays. 11. Select the array and click Monitor Selected to move the array to the Monitored list.
Related tasks
Enabling HDS statistics collection on page 39

Related references
HDS requirements on page 38

Enabling HDS statistics collection To collect statistics from HDS storage arrays, you need to install the Hitachi Performance Monitor Export 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.
40 | OnCommand Balance Installation and Configuration Guide 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
HDS requirements on page 38
IBM storage array requirements for Balance

Different 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 to Balance. After installing the agent, you need to configure it. See "Configuring the SMI-S agent for IBM 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 Balance over the IP network. Balance requires the IP address and port number of the XIV along with CIM Agent credentials.
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. 2. Click Add multiprovider. 3. Add the array as a SMI-S multiprovider. 4. Click Save. 5. Select Discovery > Storage Arrays and click Unmonitored Storage Arrays. 6. Select the array and click Monitor Selected to move the array to the Monitored list. 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 storage systems. After installing the agent on a Windows server, you need to configure it to point to each storage 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 than three 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 storage system. 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 requirements

Balance supports virtualization software for HMC, Virtual IO Servers (IBM LPAR), IBM SAN Volume 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) requirements

For 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 options for enabling discovery. The two options to choose from when setting up communication between Balance and HMC VIO servers: You can use an account with root privileges for accessing the HMC and VIO servers and discovering the associated AIX logical partitions (LPAR). You then add the HMC and VIO servers to Balance to monitor the AIX LPARs. You can use a user account to discover the HMC servers, VIO servers, and the associated AIX logical partitions (LPAR). You configure a sudoers file for accessing the VIO servers and copy the file to each VIO server you wan to discover. You then add the HMC and VIO servers to Balance 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 discovering the associated AIX logical partitions (LPAR). You then add the HMC and VIO servers to Balance to monitor 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 each connected storage array. If the VIO server is connected to a CLARiiON storage array, and you have Powerpath installed, the appropriate ODM driver is installed automatically by Powerpath. If the VIO server is connected to an HP EVA storage array, and you have SecurePath installed, the appropriate ODM driver is installed automatically by SecurePath.
About this task
You copy the provided aixhba utility to each VIO server to establish communication between Balance, 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 connected storage 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 Discovery Unmonitored Servers page. 7. On the Discovery Unmonitored Servers page, select the check box next to each AIX LPAR you want to monitor and click Monitor Selected. You will need to select the appropriate credentials for 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 AIX logical partitions (LPAR). You configure a sudoers file for accessing the VIO servers and copy the file to each VIO server you wan to discover. You then add the HMC and VIO servers to Balance to monitor 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 to discover) 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 you have Powerpath installed, the appropriate ODM driver is installed automatically by Powerpath. If the VIO server is connected to an HP EVA storage array, and you have SecurePath installed, the appropriate ODM driver is installed automatically by SecurePath. SSH installed on the HMC and VIO servers. Balance uses an SSH login using a password or key exchange 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 the connected storage arrays. The sudoers file you copy to each VIO server contains entries that specify the location of the aixhba utility file.
Steps
1. Use the visudo command to edit the sudoers file on each VIO server to include the following entries for running the aixhba utility on each VIO server.

Example
The entry you choose depends on your security requirements (password or no password).
Defaults username or Defaults username !env_reset hostname=PASSWD: /tmp/aixhba !env_reset 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 any host. (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 initial discovery, 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 you want to monitor and click Monitor Selected. You will need to select the appropriate credentials for 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) requirements

SVC virtual disks are modeled as server volumes and the managed disks as server LUNs. Crossreference the list of supported storage systems requirements for Balance with IBMs support matrix to determine the storage devices supported for SVC.
46 | OnCommand Balance Installation and Configuration Guide 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 naming
convention.
Related tasks
Configuring RSA authentication for Linux and UNIX servers on page 27 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) requirements

For 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 be accessible on the IP network to the Balance VA. Balance requires the IP address and port number of the SVSP along with CIM Agent credentials. SMI-S is a separate installation option with the SVSP SVM 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 a server or array for which it is in the I/O topology.
Configuring resources for data collection | 47 Refer to your HP SVSP documentation for more information.
SAN device requirements

Balance supports the Brocade and Cisco SAN devices (switches). Balance supports the SNMPv1 and SNMPv2c protocols only. For Balance to communicate with SAN devices that have the SNMPv3 protocol enabled, the v1 and v2c protocols must also be enabled. Brocade Balance has the following Brocade discovery requirements: In Balance, create credentials for accessing the switch. 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 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: 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 Cisco management software to create it. For the FQDN/IP Address field, type the switch IP address.
Database requirements
The Data Topology view in Balance can show the end-to-end topology between the monitored server hosting 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 configureBalance to 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 applications

When you discover a database in Balance, all volumes on the hosting server are assigned to a default application for that server, and the database objects do not automatically appear in the Data Topology view.
About this task
To display database objects in the Data Topology view, complete the following for each database you 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 Application Type, select a DBtype. 5. On the Configuration page for the database application, map the volumes of the hosting server to the 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 discovery collection queries the hosting server to identify changes to the database topology.
Related tasks
Preparing an Oracle database for discovery on page 49 Preparing a MS SQL Server for discovery on page 49
Related references
Database requirements on page 47
Preparing an Oracle database for discovery To prepare an Oracle database for Balance discovery, you need to create a user account with the necessary privileges.
Steps
1. On each Oracle database that you want to monitor, create a user account with the following system rights:
create session select any dictionary
For example, User name: AAPMAP, Password: appmap, and System privileges granted: Create session, select any dictionary. 2. In Balance, create access credentials using the user login credentials.
Related tasks
Preparing a MS SQL Server for discovery on page 49 Enabling topology views of database applications on page 48
Related references

Preparing a MS SQL Server for discovery To prepare a Microsoft SQL Server for discovery, check that the MS SQL authentication service and Mixed 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 help for 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.
50 | OnCommand Balance Installation and Configuration Guide For Method, select Login.
Related tasks
Preparing an Oracle database for discovery on page 49 Enabling topology views of database applications on page 48
Related references
Self-monitoring requirements
To monitor the Balance virtual appliance (VA) in a process referred to as "self-monitoring", or to access the selfmonitor directory on the VA, you need to create a specific credential for accessing the VA. 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 the VA. To change the password, you can use the Advanced Management Tool.
Balance communication ports

The Balance virtual appliance (VA) and the Balance Proxy use different ports to communicate with each resource. The following illustration shows the port number and protocol for each resource type accessed by the VA and the default ports accessed by the proxy after the VA opens port 9443 on the proxy host. For installing 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 firewalls

To communicate with Windows servers, Balance uses the WMI protocols and initially accesses port 445. The first exchanges occur on ports 135-139. After establishing a connection with the servers and creating a remote instance, the communication switches over to other lesser-known ports 1024-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 random port 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
Accessing the Advanced Management Tool (AMT) on page 52 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 Console tab. 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 the default password after logging in.
Related concepts
Advanced Balance configuration options on page 52

Related tasks
Adding network adapters on page 55

Related references
Advanced Balance configuration options | 53
Advanced Management Tool configuration options for Balance

The Advanced Management Tool (AMT) allows you to update Balance, configure and maintain your Balance 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 installed automatically. You can use this option if you need to upgrade the tools to a newer version. Before you 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 ignore
these messages and continue through the installation. After the installation has completed, use the 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 following options are displayed: Display Current Management IP Address Settings - Displays the current network settings for Balance, such as the management IP address, netmask, gateway, etc. Change Management IP Address Settings - Provides options for changing the Balance network settings.
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 appropriate settings. Display Domain Name Search Settings - Searches for servers across multiple domains configured in Change Management IP Address Settings and displays the results. Change Domain Name Search Settings - Provides options for adding or changing domain names you want to use in a search (for example, yourcompany.com, yourcompany.local). Domain names added manually require a space between them, but no commas. If the DHCP server is properly configured, DNS names are added automatically.

Note: The domain names you want to use in a search can be added using this option or through the 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 opportunity to exit without saving your changes before the commit is performed. Ping A Host - Pings a target host for confirming IP address changes or proper DNS configuration.
Balance Backup Options Provides options for backing up the Balance database, which contains the collected data about your data center resources. The following options are displayed: Database Backup and Offload - Packages and encrypts the database as a .gpg file. You can back up the file locally to the /home/selfmonitor/offloadsdirectory or use FTP to transfer it to another location. 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 Database Backup and Offload option. Decrypts the file using the same static pass phrase used during encryption. 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 file name relative to the home FTP directory. Gather Interop Info and Offload - Packages information about discovered resources, including OStype, version, array type, model, and storage array LUN count, into an encrypted .tgz file and then 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 start date. Reboot Operating System - Initiates the correct sequence of events to restart the Balance operating system. Shutdown Operating System - Initiates the correct sequence of events to shutdown the Balance operating 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.
Advanced Balance configuration options | 55

Related concepts

Related tasks
Accessing the Advanced Management Tool (AMT) on page 52 Adding network adapters on page 55
Adding network adapters

You 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 to separate 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 Balance upgrade.
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 the AMT. 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 DHCP cannot 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 to restart Balance.
Related concepts

Related tasks
Accessing the Advanced Management Tool (AMT) on page 52

Related references
57
Copyright information
Copyright 19942012 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 an electronic retrieval systemwithout prior written permission of the copyright owner. Software derived from copyrighted NetApp material is subject to the following license and disclaimer: THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED 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 not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp. 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 to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
Trademark information
NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, Campaign Express, 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 Business Machines Corporation in the United States, other countries, or both. A complete and current list of other 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 States and/or other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft 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 other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks. NetApp, Inc. NetCache is certified RealSystem compatible.
Index | 59
Index
7-Mode discovery requirements 29
C
Cisco discovery requirements 47 clusters discovery requirements 29 Microsoft Windows Server 21 communication ports 50 configuring CLARiiON domain 32 out-of-band proxy 34 resources 19 RSA authentication 27 virtual appliance 10 with Advanced Management Tool (AMT) 53
A
Advanced Management Tool (AMT) adding network adapters 55 options 53 starting 52 applications database 48 arrays Dell EqualLogic 32 Engenio 35 HP XP 37 IBM 40 authentication Linux and UNIX server requirements 22 RSA 27 SQL Server 49
D
dashboard page discovery 9 data collection configuring resources 19 EMC Symmetrix 33 prevent gaps 55 databases applications 48 Balance 9 requirements 47 deploying virtual appliance 9 deployment requirements 7 discovery access 7-Mode systems with a user account 30 Brocade requirements 47 Cisco requirements 47 Dell EqualLogic requirements 32 EMC CLARiiON requirements 32 EMC Symmetrix requirements 32 Engenio requirements 35 Hitachi Data Systems (HDS) requirements 38 HP 3PAR requirements 35 HP EVA requirements 36 IBM requirements 40, 41 IBM SVC requirements 45
B
Balance database 9 features 5 installation requirements 7 installing 7, 9 introduction 5 monitoring the VA 50 questions you can answer 6 upgrading 11 Balance Client requirements 9 Balance Proxy host requirements 14 installing 17 best practices configuring HP EVA 36 Solutions Enabler version requirement 32 Brocade discovery requirements 47

Linux requirements 23 NetApp FAS requirements 29 NetApp V-Series requirements 31 Oracle requirements 47 proxy 13 SAN device requirements 47 SQL Server requirements 47 storage systems supported 28 UNIX requirements 23 vCenter requirements 19 VMware ESX and ESXi Server requirements 20 Windows requirements 21 documentation list of 6
I
IBM configuring SMI-S agent 41 discovery 41 requirements 40 SAN volume statistics 46 IBM DS and ESS multiprovider 40 IBM LPAR discovery requirements 42 IBM SVC discovery requirements 45 IBM Total Storage multiprovider 40 IBM XIV multiprovider 40 installing Balance 7, 9 Balance Proxy 17
E
EMC CLARiiON discovery requirements 32 EMC Symmetrix data collection 33 multiprovider 32, 33 proxy configuration 34 Engenio adding arrays 35 multiprovider 35
J
Java requirements 9
L F
firewalls ports behind 51 Flash player requirements 9 Linux discovery requirements 23 RSA authentication 27 volume monitoring configuration 25
M H
Hitachi Data Systems (HDS) discovery 39 requirements 38 statistics collection 39 HMC VIO servers discovery methods 42 HP SAN virtualization 46 HP XP enabling discovery 37 requirements 37 statistics collection 38 Hyper-V servers 20 memory requirements 8 monitoring the Balance VA 50 multiprovider EMC Symmetrix 32, 33 Engenio 35 for proxy 17, 28 HP 3PAR 35 HP XP 37 IBM 40 IBM SVC 45 Microsoft cluster 21 what it is 16
Index | 61
N
NetApp FAS storage system requirements 29 NetApp FAS storage systems requirements 29 NetApp storage systems create user role for 7-Mode systems 30 V-Series requirements 31 network adapters adding 55
IBM 40 memory 8 proxy 13 SAN devices 47 self-monitoring 50 storage system discovery 28 VA host 7 vCenter server 19 virtualization software 42 Windows servers 20 RSA configuring authentication 27
O
Oracle discovery requirements 47 Oracle database configuring for discovery 49
S
SAN devices requirements 47 self-monitoring 50 servers discovery Hyper-V Server requirements 22 ESX and ESXi Server 19 Hyper-V 22 Linux and UNIX configuration 25 vCenter 19 VMware ESX and ESXi Server 20 Windows 20 SQL Server configuring for discovery 49 discovery requirements 47 enabling topology views 48 statistics collection Hitachi Data Systems (HDS) 39 HP XP 38 IBM SAN volume 46 supported storage systems 28
P
passwords Linux UNIX authentication 26 ports configuring behind Windows firewalls 51 used by virtual appliance 50 product documentation list of 6 proxy EMC Symmetrix 32, 34 host requirements 14 in-band configuration 34 installing 17 multiprovider requirements 16 out-of-band configuration 34 requirements 13 upgrading 18
T R
requirements Balance installation 7 Client system 9 databases 47 Dell EqualLogic 32 EMC CLARiiON 32 EMC Symmetrix 32 Engenio 35 HP SAN virtualization 46 HP XP 37 topology views database application and resources 47 enabling for SQL Server databases 48 Flash player requirement 9
U
UNIX discovery requirements 23 RSA authentication 27 volume monitoring configuration 25

upgrading Balance 4.0+ 11 proxy 18 version 3.6 or earlier 12 user account discovery from 44 deploying 9 ports used 50 resource recommendations 8 virtualization HP SAN platform requirements 46 virtualization software requirements 42 vSphere Client deploying virtual appliance 9
V
VA host requirements requirements 7 vCenter discovery requirements 19 VIO servers discovery requirements 42 virtual appliance configuring 10
W
web browser requirements 9 Windows server requirements 21

OnCommand Balance 4100 Installation and

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OnCommand Balance 4100 Installation and

Uploaded by

Copyright:

Available Formats

OnCommand Balance 4.1.

0 Installation and Configuration Guide

Balance installations ..................................................................................... 7

Balance Proxy installation ......................................................................... 13

Configuring resources for data collection ................................................ 19

Advanced Balance configuration options ................................................. 52

Introduction to OnCommand Balance

OnCommand Balance features

6 | OnCommand Balance Installation and Configuration Guide

Questions you can answer using OnCommand Balance

OnCommand Balance product documentation

Balance installation requirements

Virtual appliance host requirements

Balance communication ports on page 50

Configuring ports behind Windows firewalls on page 51

Virtual appliance resource recommendations on page 8

Virtual appliance resource recommendations

Balance communication ports on page 50

Configuring ports behind Windows firewalls on page 51

Virtual appliance host requirements on page 7

Balance web browser requirements

10 | OnCommand Balance Installation and Configuration Guide

Configure the VA.

Upgrade Balance version 3.6 or earlier on page 12

Virtual appliance host requirements on page 7

Configuring the virtual appliance

Installing the Balance Proxy on page 17

7. Follow the wizard instructions to perform the upgrade.

Upgrade the existing Balance Proxies.

12 | OnCommand Balance Installation and Configuration Guide

Upgrade Balance version 3.6 or earlier on page 12

Advanced Management Tool configuration options for Balance on page 53

Upgrade Balance version 3.6 or earlier

Upgrading Balance on page 11

Virtual appliance host requirements on page 7

Balance Proxy installation

Balance Proxy host requirements on page 14

14 | OnCommand Balance Installation and Configuration Guide

What a multiprovider is on page 16

Balance Proxy host requirements

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

16 | OnCommand Balance Installation and Configuration Guide

Balance Proxy installation on page 13

What a multiprovider is on page 16

Balance Proxy installation | 17

Installing the Balance Proxy

Balance Proxy installation on page 13

18 | OnCommand Balance Installation and Configuration Guide

Balance Proxy host requirements on page 14 What a multiprovider is on page 16

Upgrading the Balance Proxy

Upgrade Balance version 3.6 or earlier on page 12

Upgrading Balance on page 11

Balance Proxy host requirements on page 14 What a multiprovider is on page 16

Configuring resources for data collection

VMware vCenter Server and ESX and ESXi Server requirements

VMware vCenter Server requirements

20 | OnCommand Balance Installation and Configuration Guide

VMware ESX or ESXi Server requirements

Windows and Hyper-V Server requirements

Balance communication ports on page 50

Configuring resources for data collection | 21

Configuring ports behind Windows firewalls on page 51

What a multiprovider is on page 16 Balance Proxy host requirements on page 14