OnCommand Balance Installation and Configuration Guide

Transcription

1 OnCommand Balance Installation and Configuration Guide NetApp, Inc. 495 East Java Drive Sunnyvale, CA U.S. Telephone: +1 (408) Fax: +1 (408) Support telephone: +1 (888) Web: Feedback: Part number _A0 March 2012

2 2

3 Contents Contents Chapter 1 Introduction... 5 Balance overview... 6 Functionality... 6 Discovery... 6 Data collection... 6 Analysis... 6 Data reporting... 7 Conventions... 7 Technical documentation... 8 Chapter 2 Setting up Balance... 9 Installation overview New installation Upgrade Virtual appliance requirements vsphere requirements ESX Server requirements VA resource recommendations Deploying the virtual appliance Configuring the virtual appliance Setting up the Balance Proxy About multiproviders Proxy host requirements Proxy host requirements based on the number of monitored servers Installing the Balance Proxy Client system requirements Web browser Java Runtime Environment Flash Player Chapter 3 Configuring resources for data collection VMware vcenter Server and ESX/ESXi Server requirements vcenter Server VMware ESX/ESXi Server Windows and Hyper-V Server requirements Windows Server Microsoft cluster multiprovider Hyper-V Server Linux/UNIX server requirements Linux/UNIX discovery requirements Configuring password authentication for Linux/UNIX servers Configuring RSA authentication for Linux/UNIX servers Storage system requirements Statistics collection support NetApp /6/123

4 Contents Discovering a NetApp storage system with a user account Dell EqualLogic EMC CLARiiON CLARiiON Domain EMC Symmetrix Enabling data collection Configuring the proxy for Symmetrix DMX/VMAX arrays Engenio Enabling discovery collection HP EVA HP XP Enabling discovery collection Enabling statistics collection Hitachi Data Systems Enabling discovery collection Enabling statistics collection IBM IBM TotalStorage DS4000 and 5000 series/fastt IBM DS6000, DS8000, and ESS storage IBM XIV Enabling discovery collection Virtualization software requirements HMC, Virtual IO Servers, IBM LPAR Preparing HMC VIO servers for discovery Enabling discovery using a user account Enabling discovery using root IBM SAN Volume Controller (SVC) Enabling statistics collection HP SAN Virtualization Storage Platform (SVSP) SAN device requirements Brocade Cisco Database requirements Oracle Microsoft SQL Server Enabling topology views of database applications Preparing an Oracle database for discovery Preparing a MS SQL Server for discovery Communication ports Configuring Ports Behind Windows Firewalls Chapter 4 Advanced configuration options Accessing the AMT Using the AMT Adding network adapters to Balance Index 4

5 1 Introduction This guide explains how to set up OnCommand Balance in your data center. It also describes the minimum requirements for discovering and collecting data from each data center resource you want to monitor. 5

6 Balance overview Functionality Balance is a software solution that exists on the Balance virtual appliance (VA). Balance provides a complete, end-to-end view of your data center, from the physical storage that holds your data to the applications that process and control that data. It monitors your data center to identify and alert you to performance bottlenecks, such as latency, storage contention, and over-utilization, before they occur, so that you can take corrective action. It also allows you to plan data center configurations, such as adding or removing servers or storage systems, to determine the potential impact to overall data center performance. For a more detailed product overview, see the OnCommand Balance User Guide. The main Balance functionality is discovery, data collection, analysis, and data reporting. Balance provides access to configure Balance and begin discovery using the Hypertext Transfer Protocol (HTTP) or Secure Hypertext Transfer Protocol (HTTPS). Discovery Balance uses the IP network to discover data center resources. To add resources to Balance, you can import a seed list or manually add each resource you want to discover and monitor. During discovery, Balance collects information about the resource, such as the resource configuration and its relationship to other data center resources. Balance uses the information to build a topology that maps the path between each monitored application, server, and the connected storage systems. Data collection After the resources have been discovered, Balance begins to collect their operational data into its database. The data includes information such as disk IOPS, disk latency, and server CPU and memory usage. If IOPS, for example, jump during a discrete time period on a particular LUN, Balance captures this information. Within a few hours of discovery, Balance can begin performance analysis against the collected data. As Balance collects more data the analysis beings to provide more accurate and meaningful performance statistics. Analysis The word analysis, as used by NetApp, refers to actions that Balance performs when examining data center statistics for performance issues. Balance collects quantitative data such as IOPS, latency, and memory paging, then uses the data to determine whether there are any problems with operations in the data center. If Balance identifies an existing or potential problem, it provides recommendations that you can use to resolve the problem. 6

7 Data reporting Balance provides several reports that display configuration information for each monitored resource, including with statistics that show the current and trending performance. Balance analyzes these trends and provides recommendations for resolving potential problems it identifies. You can analyze the reported trends and make changes based on those trends at any time. Conventions Textual conventions used throughout this guide are described in Table on page 7 and Table on page 7. Table 1. Conventions Symbol Meaning Description Note: Important!! Indicates additional information or helpful suggestions. Stresses the necessity to follow the associated information exactly as it is detailed. Caution: Warning: See Meaning. See Meaning. Notifies the reader to proceed carefully to avoid possible equipment damage or data loss. Notifies the reader to proceed carefully to avoid possible personal injury. Table 2. Text conventions Convention Meaning Description Screen and keyboard button callouts User input and screen display, including pathnames and filenames. Book/document reference titles other than the current book/document you are reading. Appear in bold type. Always appears Courier New typeface. Appear in italic typeface. default policy user input Balance User Guide 3/6/127

8 Technical documentation The technical documents for installing, configuring, administering, and using the Balance VA and Balance software are detailed in Table 3 on page 8. To provide comments on this document, see How to send your comments on page 55. Note: For the latest electronic versions of Balance user documentation in PDF format, visit the NetApp Support Web site: Table 3. Balance technical documentation Document Name Release Notes Installation and Configuration Guide User Guide Description Current release information, known problems, and workarounds. Procedures for installing the VA on a VMware ESX Server and discovery requirements for each supported data center resource you want to monitor. Available in both PDF and online Help format, the User Guide explains how to configure, manage, and use Balance. 8

9 2 Setting up Balance This chapter explains how to install Balance in your data center. See the following sections: Installation overview on page 10 Virtual appliance requirements on page 12 Deploying the virtual appliance on page 13 Configuring the virtual appliance on page 14 Setting up the Balance Proxy on page 15 Client system requirements on page 18 9

10 Installation overview New installation Balance is distributed as a virtual appliance (VA) in the OVA format. You can download the OVA from the NetApp Support Web site at: To install Balance, you deploy the OVA to an ESX Server from your vsphere Client. During deployment, the OVA converts to a virtual machine (VM). You then log in to Balance through a Web browser to configure the VA as a new installation or to upgrade an existing 3.6 VA. Setting up a new Balance VA involves the following tasks: 1. Ensure that the ESX Server that will host the VA meets the minimum requirements. See Virtual appliance requirements on page Deploy the VA to an ESX Server. See Deploying the virtual appliance on page In a Web browser, access Balance and select the option to configure it as a new server. See Configuring the virtual appliance on page Install and configure the Balance Proxy. Balance requires the proxy to discover Windows servers and some storage arrays. Depending on the storage array type, you may need to install and configure multiprovider software in addition to the proxy. See Setting up the Balance Proxy on page Add data center resources you want to discover and monitor. For the minimum requirements for discovering each resource, see Chapter 3, Configuring resources for data collection. 10

11 Upgrade Upgrading an existing Balance 3.6 VA involves deploying the VA and then migrating the historical data and configuration settings from the 3.6 VA to the VA. Important! Before proceeding, we strongly recommend that you clone or back up the VA. Upgrading involves the following tasks: 1. Ensure that the ESX Server that will host the VA meets the minimum requirements. See Virtual appliance requirements on page Deploy the VA to an ESX Server. See Deploying the virtual appliance on page If you need to configure an additional network adapter on the VA, to separate network traffic, for example, you must do so before you proceed with the upgrade. Important! Adding a network adapter involves restarting Balance on the VA. During the upgrade, Balance must remain powered-on until the data migration from the 3.6 VA has completed, or you risk data loss. See Adding network adapters to Balance on page In a Web browser, log in to Balance to configure the VA and select the option to migrate historical data and configuration settings from a 3.6 VA. You specify the name and admin credentials for the 3.6 VA from which to migrate data to the VA. Note: If you specify credentials for an Active Directory account, the upgrade might fail to access the 3.6 VA. The configuration settings migrate first, at which time the 3.6 VA is temporarily unavailable, and then the VA begins data collection. The historical data migrates over time. You can still log in to the 3.6 VA, but it will no longer collect and display new data. See Configuring the virtual appliance on page On the Balance Dashboard, use the instructions in the data migration section, on the right, to upgrade the existing Balance Proxies to be compatible with Balance Note: To ensure that the proxies meet the minimum host and resources requirements, review the minimum requirements in Setting up the Balance Proxy on page 15. 3/6/1211

12 Virtual appliance requirements The ESX Server on which you deploy the VA must meet minimum resource requirements. The VA resource requirements increase based on the number of servers you plan to monitor. vsphere requirements For deploying the VA, you can use VMware vsphere Client version 4.0, 4.1, or 5.0. ESX Server requirements Table 4 on page 12 lists the minimum requirements for the VMware ESX Server that will host the VA. Table 4. ESX Server requirements Resource Minimum Requirements ESX Server Versions 4.0, 4.1, or 5.0. Hardware and software must be 64-bit. Network Virtual CPUs Virtual Memory Disks Storage 1 Gigabit Ethernet connection for fastest installation (optional). DHCP recommended for the VA (default) GHz 3.6 GB At least 5 disk spindles in RAID DP or other RAID array. Datastore 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 VA resource recommendations on page 12 for the minimum number of recommended disks. VA resource recommendations Table 5 on page 13 lists the VA resource recommendations 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 4000MB (the default). If this amount is not available on the ESX Server, the VA might not power on. You can lower the memory settings of the VA in an environment with 100 monitored servers or less. 12

13 Table 5. VA resource recommendations Monitored Servers vcpus CPU Reservation (MHz) Memory (MB) Memory Reservation (MB) Minimum Disks Network Usage (KBps) or less 2 a a For non-production/demo usage, you can configure Balance with 1 vcpu; this configuration is not otherwise recommended. Deploying the virtual appliance This section explains how to use a VMware vsphere Client to deploy the VA to an ESX Server. The vsphere Client converts the VA to a virtual machine (VM). Important! If you are upgrading from a 3.6 VA, we strongly recommend that you clone or back up the VA before proceeding. To deploy the VA: 1. Download the VA from the NetApp Support Web site at 2. Save the OVA file to a local or network location that is accessible to your vsphere Client. 3. In the vsphere Client, on the File menu, select Deploy OVF Template. 4. Complete the Deploy OVF Template wizard to deploy the VA. Note: For the VM disk format, we recommend selecting 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 information on thin provisioning, see the online help for your vsphere Client. 5. After the VA has successfully deployed to the ESX Server, power on the VA. 6. In vsphere, click the Console tab to monitor the power-on status: VA powers up. Balance starts up. 3/6/1213

14 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. 7. Proceed to Configuring the virtual appliance on page 14. Configuring the virtual appliance After deploying the VA and powering it on, you can then open a Web browser and use the IP address assigned to the VA to access Balance and begin the configuration. When you first log in, you can select to set up Balance as a new server or migrate configuration settings and historical data from an existing Balance 3.6 VA to the new VA. Note: If you are migrating settings and data from an existing Balance 3.6 VA, ensure that the existing VA is powered on. If you have changed the root password on the existing VA from the default, you will be prompted to enter the root password during the upgrade. To configure the VA: 1. Open a Web browser. Note: For the minimum client system requirements, see Client system requirements on page In the address bar, enter the FQDN/IP address assigned to the VA when it was deployed. 3. Follow the on-screen instructions to configure a new VA or upgrade an existing VA. After you complete the configuration, the login page appears. 4. Enter your login credentials. If upgrading, enter the credentials for the 3.6 VA. Default is the following (all lowercase): User: admin Password: password For new installations, the Welcome page appears. Note: If you choose to migrate settings and data from an existing VA, the data continues to migrate in the background. Balance and the existing source Balance VA both display the migration status, but Balance is more accurate. 5. In Balance, click Help and complete the tasks listed in the topic Getting started with Balance for instructions on configuring Balance and adding data center resources you want to monitor. 14

15 Setting up the Balance Proxy The Balance Proxy is required to discover Windows servers and some storage arrays. Install the proxy on a physical or virtual host. Balance uses the proxy to perform discovery collections on the monitored resources. Figure 1 on page 15 shows which resources, in green, must be discovered through the Balance Proxy and which resources also require a multiprovider, either standalone or in addition to the proxy. Figure 1. Resources Requiring a Proxy or Multiproviders 3/6/1215

16 About multiproviders To discover and collect data from some storage arrays, Balance requires multiprovider software, either standalone or in addition to the Balance Proxy. Depending on the storage array type, the multiprovider must be on either the Balance Proxy server or on a server accessible to Balance. To reach the storage array, Balance can communicate with the appropriate multiprovider directly or communicate with the proxy, which communicates with the multiprovider. During the proxy installation, you can browse to the location of some multiprovider software that is installed on the proxy host, while other multiproviders require more advanced configuration. The following storage systems require multiproviders: EMC CLARiiON on page 31 EMC Symmetrix on page 32 Engenio on page 34 HP EVA on page 34 HP XP on page 35 Proxy host requirements Hitachi Data Systems on page 36 The host on which you install the Balance Proxy must meet the following minimum requirements: Dedicated Windows Server 2003 SP1 or greater. Dedicated Windows Server 2008 R2 with User Account Control (UAC) disabled. Note: Other Windows versions are not supported. Firewall disabled or open port 9443 for proxy communication. See Communication ports on page bit version of Java is required for both 32- and 64-bit systems. See Java Runtime Environment on page 19. At least 20 GB of disk space assigned to the proxy, approximately 10 GB should be available after installation. If antivirus software is installed on the proxy host, script scan functions must be disabled. We recommend excluding the following directory from virus scan: C:\Program Files\netapp 16

17 The proxy should be accessed by a single Balance VA only. Proxy host requirements based on the number of monitored servers Table 6 on page 17 lists the resource limitations for the Windows Server hosting the Balance Proxy. The values are based on the number of servers (physical and virtual) that you plan to monitor. Note: Values apply specifically to Windows Server 2003 hosts. Values for Windows Server 2008 hosts might be higher. Table 6. Proxy host requirements Monitored Servers vcpus CPU Reservation (MHz) Memory Reservation (MB) Minimum Disks Network Usage (KBps) or less There is a Microsoft bug where the lsass.exe process consumes 100% of Java CPU. This causes a slow response logging into the Balance Proxy as well alerts regarding high CPU utilization from the Virtual Center hosting the proxy. This problem was found on Windows 2003 and 2008 standard. However, Windows 2008 r2 is not affected. For information about Windows 2003 lsass.exe, see the Knowledge Base article at AntiVirus script scan capability might also cause high CPU utilization. Disable the script scan on the Balance Proxy. 3/6/1217

18 Installing the Balance Proxy This section explains how to install or upgrade the Balance Proxy. You use a wizard that steps you through installing the proxy and specifying the multiproviders that the proxy requires to communicate with some resources. For a list of resources that require multiproviders, see About multiproviders on page 16. To install or upgrade the proxy: 1. Review the proxy host requirements in Proxy host requirements on page Open a Web browser window and log in to Balance. 3. On the Discovery menu, select Proxies > Add proxy. Note: If upgrading a 3.6 VA, the Dashboard displays instructions for upgrading the existing proxies. 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. Select to open the installer file. 6. Use the wizard to install or upgrade the proxy. On the step for installing multiproviders, the proxy installer displays the default paths where it expects to find multiproviders installed on the proxy host. If any of the paths are incorrect, click Browse to locate the multiprovider and update the path. Important! If you do not install all multiproviders initially, but install them at a later time, you must reinstall the proxy and select the appropriate check boxes for each new multiprovider you added. Client system requirements Web browser This section lists the client system requirements for accessing Balance through a Web browser. To ensure that the Balance interface displays properly, use one of the following browsers: Mozilla Firefox 6.0 or greater. Microsoft Internet Explorer (IE) 7 or greater. IE 8 or 9 recommended. Note: For IE 8, ensure Compatibility Mode (Compatibility View) is disabled. For IE 9, ensure Compatibility Mode is enabled. See the Microsoft IE online help for information on enabling and disabling Compatibility Mode. 18

19 Java Runtime Environment Flash Player Balance requires a minimum of JRE v1.6 with update 24 or greater for optimal graphing capabilities. To display the Data Topology pages in Balance, the client system must have Adobe Flash Player or greater. 3/6/1219

20 20

21 3 Configuring resources for data collection Before Balance can discover and collect performance statistics from your data center resources, you must make sure that each resource meets the minimum software requirements. If the resource requires the Balance Proxy, the proxy may require multiprovider software to discover the resource. Balance supports equipment from several vendors. See the following sections to ensure that each of your resources meet the minimum requirements for discovery: VMware vcenter Server and ESX/ESXi Server requirements on page 22 Windows and Hyper-V Server requirements on page 23 Linux/UNIX server requirements on page 25 Storage system requirements on page 29 Virtualization software requirements on page 39 SAN device requirements on page 42 Database requirements on page 43 Communication ports on page 47 21

22 VMware vcenter Server and ESX/ESXi Server requirements vcenter Server VMware ESX/ESXi Server Balance supports VMware vcenter Servers and allows for the discovery of hosts and guests associated with physical ESX servers. You can also add ESX Servers as standalone hosts. Important! The user account for accessing the vcenter Server or ESX/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 VM datastores. Balance supports monitoring of the following versions of vcenter Server: vcenter 5.0 (for ESX 4.0.x and 4.1.x ESX hosts) vcenter 4.0 and 4.1 (for ESX 4.0.x, and 4.1.x ESX hosts) vcenter Server 2.5 (for ESX 3.5.x hosts) Note: Each vcenter Server you add to Balance must have a unique vcenter ID. Balance supports standalone VMware ESX/ESXi Server 4.0 or greater. It can also track VMotion activity. To discover ESX/ESXi Servers, Balance has the following discovery requirements: FQDN/IP address of the server. Username and password for the server. Note: VM guests must have VMTools installed before they can be monitored. ESX/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: d=displaykc&externalid= VMware Tools must be installed and up-to-date on all guests for statistics gathering. See the Hypervisor Tools section of Accessing the AMT on page 49 for more information. 22

23 Balance uses the VMware SDK (Software Development Kit) to communicate with VMware ESX servers (installed by default on most systems). The SDK retrieves data via SOAP requests over HTTP. Note: If you want to configure this host or its cluster for vcenter Server discovery, see VMware vcenter Server and ESX/ESXi Server requirements on page 22. Important! Balance only supports Raw Disk Mappings (RDM) in physical compatibility mode. Windows and Hyper-V Server requirements Windows Server See the following sections for Window and Hyper-V discovery requirements: Windows Server on page 23 Hyper-V Server on page 25 Important! 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:\program Files\NetApp\bin Note: Balance uses WMI to discover Windows and Hyper-V servers. If the servers are behind a firewall, see Configuring Ports Behind Windows Firewalls on page 47 to ensure that Balance can access the necessary ports. Table 7 on page 24 lists the supported versions of Windows and the configuration requirements for discovering each server as a standalone or physical server. Note: If your Windows server is part of a cluster, see Microsoft cluster multiprovider on page 24. 3/6/1223

24 Table 7. Windows Server requirements Version Windows Server 2008 with SP1 or SP2 Windows Server 2008 R2 Windows Server 2003 with SP2 Software Requirements Have a local user account or domain account with valid username and password that is a member of the administrators group. Have firewall disabled or open port See Communication ports on page 47. Be accessible to the Balance Proxy. You can optionally run the following: FCINFO (Fibre Channel Info Tool) Multipathing software (for example, Powerpath, SecurePath, or MPIO are supported). Have a valid username and password with local administrator permissions on the server or domain administrator permissions. Have firewall disabled or open port See Communication ports on page 47. Be accessible to the Balance Proxy. You can optionally run the following: FCINFO (Fibre Channel Info Tool) Multipathing software (for example, Powerpath, SecurePath, or MPIO are supported). Note: If you are using STORport Miniport drivers, multipathing software is required (for example, Powerpath, SecurePath, or MPIO are supported). Supported drivers include STORport and SCSIport Miniport drivers. Microsoft cluster multiprovider For Microsoft clusters, create a credential for the Windows 2003/2008 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 will appear in Balance as unmonitored. You will need to manually change each node to monitored. 24

25 Hyper-V Server Table 8 on page 25 lists the supported versions of Windows Hyper-V Server and the software requirements for discovering the server. Note: Balance does not support clustering for Hyper-V. Balance discovers Hyper-V virtual machines and adds Windows guests to the Unmonitored list. Table 8. Hyper-V Server requirements Version Software Requirements Windows Server 2008 R2 Have a local user account or domain account with valid username and password that is a member of the administrators group. Have firewall disabled or open port See Communication ports on page 47. Be accessible to the Balance Proxy. You can optionally run the following: FCINFO (Fibre Channel Info Tool) Multipathing software (for example, Powerpath, SecurePath, or MPIO are supported). Note: STORport Miniport drivers are supported by default. Linux/UNIX server requirements To prepare each Linux/UNIX server for discovery and user authentication, see the following sections: Linux/UNIX discovery requirements on page 25 Configuring password authentication for Linux/UNIX servers on page 28 Configuring RSA authentication for Linux/UNIX servers on page 29 Linux/UNIX discovery requirements Table 9 on page 26 lists the system requirements for discovering physical (standalone) Linux/UNIX servers. For Balance to discover Linux/Unix servers, the server must be configured with one of the following shells: sh, ksh, bash 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. 3/6/1225

26 Table 9. Linux/UNIX discovery requirements Platform Type Requirements Linux Red Hat Enterprise Linux version ES4 or ES5 SUSE version 9, 10, or 11 Solaris 9 on SPARC, Solaris 10 on SPARC or x86 Root access to the server or a valid credentials for the sudo account. The username must be entered in the sudoers file or equivalent in PowerBroker. Balance uses an ssh login via password or key exchange to communicate with Linux servers. SSH installed. Oracle Automatic Storage Management (ASM) is currently supported for Red Hat Enterprise Linux, including the option for multipathing. RAC is not supported. See Database requirements on page 43. Root access to the server or a valid credentials for the sudo account. The username must be entered in the sudoers file or equivalent in PowerBroker. Balance uses an ssh login via password or key exchange to communicate with Linux servers. SSH installed. Root access to the server or a valid credentials for the sudo account. The username must be entered in the sudoers file or equivalent in PowerBroker. Balance uses an ssh login via password or key exchange to communicate with Linux servers. Solaris Volume Manager (SVM) and Veritas Volume Manager (VxVM) 3.5 or higher are required for correct data collection. If you have incorporated multipathing, Balance supports DMP and/or PowerPath. SSH installed. HBA software utilities, such as Emulex HBAnyware or QLogic SanSurfer: hbanyware/hbacmd CLI suite of tools installed, for data collection from Emulex HBAs. SANsurfer (scli) suite of tools installed, which facilitates the gathering of configuration and statistical data for Q-Logic HBAs. PowerBroker (or sudo installed for Balance to gain root privileges while running HBA tools. The sudo utility does not come standard with Solaris, but is available free online. Sun::Solaris::Kstat Perl module (kstat) installed. prtvtoc command in either the sudoers file or PowerBroker to provide access privileges for discovering disk partitions. 26

27 Table 9. Linux/UNIX discovery requirements Platform Type Requirements UNIX HP-UX 11i v1 (11.11) HP-UX 11i v2 (11.23) HP-UX 11i v3 (11.31) IBM AIX 5.2, 5.3, & 6.1 Root access to the server or a valid credentials for the sudo account. The username must be entered in the sudoers file or equivalent in PowerBroker. Balance uses an ssh login via password or key exchange to communicate with UNIX servers. Have SSH installed - Balance uses an ssh login via password or key exchange to communicate with HP-UX servers and requires a username and password with read-only permissions on the server. Be running HP-UX / HP-UX with Logical Volume Manager (LVM). Have HP OpenView GlancePlus installed. You can optionally install HBA software utilities (i.e. Emulex HBAnyware or QLogic SanSurfer). You will not get HBA and FCPort information without installing the utilities. Root access to the server or a valid credentials for the sudo account. The username must be entered in the sudoers file or equivalent in PowerBroker. Balance uses an ssh login via password or key exchange to communicate with UNIX servers. Note: Sudo is also in the AIX Toolbox for Linux Applications. Have SSH installed. This is included with the AIX Toolbox for Linux that is distributed with AIX. For more information, go to the IBM Web site at: Have disk collection enabled. You can run 'lsattr -E -l sys0 -a iostat' to check the current setting. Run the command 'chdev -l sys0 -a iostat=true' on the AIX host to enable collection of disk statistics. A volume manager and an appropriate ODM driver for the connected Storage Array. If the AIX machine is connected to a CLARiiON array, and you have Powerpath installed, the appropriate ODM driver is installed automatically by Powerpath. If the AIX machine is connected to an HP EVA array, and you have SecurePath installed, the appropriate ODM driver is installed automatically by SecurePath. 3/6/1227

28 Configuring password authentication for Linux/UNIX servers If you are using password authentication with a Linux/UNIX server, add the Balance user to /etc/sudoers using the visudo command. Important! 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 Defaults!env_reset Syntax: username hostname = NOPASSWD: /sbin/lvm,/sbin/scsi_id,/sbin/dmsetup,/sbin/fdisk where: username is the username for accessing the Linux/UNIX server. hostname is the FQDN/IP of the Linux/UNIX server. If you are using one or more of the following tools, add their associated paths to your sudoers file. QLogic Host Bus Adapter Simple Command Line Interface (SCLI): /usr/local/bin/scli Powerpath: /sbin/powermt Veritas Volume Manager: /usr/lib/vxvm/diag.d/vxdmpinq,/usr/sbin/vxdisk Note: When running Veritas Volume Manager 5.1 or greater, replace the use of the vxdmpinq utility, with the vxscsiinq utility. MD devices: /sbin/mdadm 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. Replace username and hostname with the appropriate values. Note that the default locations are assumed for these utilities. Note: To enable a password prompt, change NOPASSWD to PASSWD in the previous sudo entry. 28

29 Configuring RSA authentication for Linux/UNIX servers If you are using RSA authentication with Linux/UNIX, perform the following steps: 1. Do one of the following to create the RSA keys: For RSA authentication on the Balance VA, use the read-only self monitor credentials. For RSA authentication on Linux/UNIX servers, create an RSA keypair using the ssh-keygen program from the read-only Balance user account. Important! Do not use a third-party key generator, such as PuTTy, to create the RSA keys. 2. In the user directory where the newly created RSA keys are located, copy or rename the id_rsa.pub key to authorized_keys. The private id_rsa key file or the ASCII contents of this file will be used when creating the RSA credential on Balance. Note: If you created the RSA keys on the Balance VA, copy the public key file to all Linux/UNIX hosts that will use RSA authentication. 3. In Balance, create the RSA credentials. 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. 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 with multiprovider software. Statistics collection support Balance collects performance statistics for the following storage systems. For storage systems not listed, Balance collects the statistics from the connected servers. NetApp on page 30 EMC CLARiiON on page 31 HP EVA on page 34 Hitachi Data Systems on page 36 IBM SAN Volume Controller (SVC) on page 41 3/6/1229

30 NetApp To discover and collect statistics from NetApp FAS storage systems, Balance has the following requirements: Data OnTap or greater. To discover the storage system, use the administrator (root) account. To use a user account, see Discovering a NetApp storage system with a user account on page 30. Discovering a NetApp storage system with a user account To have Balance access your NetApp storage system with a user account and not an administrator (root) account: 1. Log in to the Data OnTap operating system on the NetApp storage system. 2. Select the NetApp storage system and click Use Command Line. 3. Enter the following command to create the user role: useradmin role add balance_user -a login-http-admin,api-system-get-info,api-system-get-version,api-fcp-adapte r-list-info,cli-ifconfig,api-lun-list-info,api-lun-get-geometry,api-aggr-l ist-info,api-disk-list-info,api-lun-map-list-info,api-volume-list-info,api -qtree-list,api-lun-get-serial-number,api-lun-stats-list-info,api-cifs-sha re-list-iter-start,api-nfs-exportfs-list-rules,api-nfs-exportfs-list-rules -2,api-cifs-share-list-iter-next,api-cifs-share-list-iter-end,api-perf-obj ect-list-info,api-perf-object-counter-list-info,api-perf-object-get-instan ces,api-perf-object-get-instances-iter-start,api-perf-object-get-instances -iter-next,api-perf-object-get-instances-iter-end,api-license-list-info,ap i-cf-status,api-cifs-status,api-nfs-status,api-volume-get-root-name,api-sy stem-cli,api-useradmin-role-list,api-useradmin-group-list,api-useradmin-us er-list,cli-rdfile,cli-fcp,api-vfiler-list-info,security-api-vfiler 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. Important! 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. 4. Enter the following command to create the user group: useradmin group add group -r balance_user where, group is name of the user group. 5. Enter the following command to add the user role to the user group: useradmin user add balance_user -g group 30

31 Dell EqualLogic EMC CLARiiON Note: For NetApp clusters, only enter the FQDN/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. 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. To discover and collect statistics from EMC CLARiiON storage arrays, Balance has the following requirements: Multiprovider: Latest version of EMC Unisphere or NaviSECCLI.exe 6.19 or greater installed on the Balance Proxy host. A valid username with global scope monitor rights. Recommended: Use Unisphere or Navisphere to enable array statistics logins. 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 may display as unmonitored or monitored. All discovered physical servers display on the Unmonitored Servers page. For adding hosts and guests associated with an ESX server, see VMware vcenter Server and ESX/ESXi Server requirements on page 22. Note: If the CLARiiON 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. 3/6/1231

32 EMC Symmetrix To discover and collect statistics from EMC Symmetrix DMX/VMAX storage arrays, Balance has the following requirements: Multiprovider: EMC Solutions Enabler 6.4 or greater installed on the Balance Proxy host. On the Solutions Enabler host that is connected to the Symmetrix array, the following services are running: EMC storapid EMC storsrvd As a best practice, ensure that the Solutions Enabler version is consistent with the remote client. Collection errors might occur if different versions are used. Enabling data collection To enable data collection for Symmetrix arrays, add the storage array as a Symmetrix multiprovider: 1. In Balance, select Discovery > Credentials. 2. Select Discovery > Multiproviders. 3. Click Add multiprovider. 4. Add the array as a Symmetrix multiprovider. 5. Click Save. 6. Select Discovery > Proxies. In the Discovery Collection column, when Up appears, the proxy is discovering the array. Once discovered, the array appears on the Unmonitored Storage Arrays page. 7. Select Discovery > Storage Arrays. and click Unmonitored Storage Arrays. 8. Select the array and click Monitor Selected to move the array to the Monitored list. Configuring the proxy for Symmetrix DMX/VMAX arrays For EMC Symmetrix DMX/VMAX (SE only), you can install the proxy out-of-band or in-band of the Symmetrix array: Out-of-band configuration (recommended) involves running the proxy and a copy of Solutions Enabler 6.4 or greater 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 Solutions Enabler host that is connected to the array. 32

33 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 since the proxy service can put additional load on the server and the version of Solutions Enabler must be 6.4 or greater. To configure out-of-band communication: 1. On the Balance Proxy host, locate the following configuration file: C:\Program Files\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 Solutions Enabler host that is connected to the Symmetrix array: SE_Host - TCPIP node001 SE_IP SE_Port - where, SE_Host is the name of the Solutions Enabler host connected to the Symmetrix array. SE_IP is the IP address of the Solutions Enabler host connected to the Symmetrix array. SE_Port is the port on the Solutions Enabler host connected to the Symmetrix array. 4. Add the following Windows System Variables: SYMCLI_CONNECT_TYPE = REMOTE SYMCLI_CONNECT = SE_Host where, SE_Host matches the value for SE_Host in step 3 on page The proxy associates this value with the value in the netcnfg file to locate the Solutions Enabler server connected to the Symmetrix 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 Symmetrix arrays appears. Note: To discover Symmetrix DMX/V-Max volumes on an ESX 3.0 host, set the SPC-2 bit. 7. In Balance, select Discovery > Multiprovider. 8. Add the Symmetrix as a Symmetrix multiprovider. 3/6/1233

34 Engenio To discover Engenio storage arrays, Balance has the following requirements: Multiprovider: Engenio/LSI SMI-S CIM Agent is accessible to Balance. To download the SMI-S CIM Agent, go to the LSI Web site at: oftware/smis_provider/index.html Note: Search the Engenio Web site for information about downloading, installing, and operating the Engenio SMI-S Provider (Legacy version). Enabling discovery collection To enable discovery collection for Engenio storage arrays: 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. HP EVA To discover and collect statistics from HP EVA storage arrays, Balance has the following requirements: Multiprovider: HP StorageWorks Command View EVA or greater suite is installed on the Balance Proxy host. 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 (EVAPerf) for statistics collection. SSSU Storage System Scripting Utility (SSSU) for discovery collection. Although HP supports up to 16 EVAs per Command View server, a best practice is to configure no more than four. Important! 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. 34

35 Important! 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. HP XP To discover and collect statistics from HP XP storage arrays, Balance has the following requirements: Multiprovider: HP StorageWorks XP Array Manager (Command View Ae) is installed on the Balance Proxy host. For statistics collection, the array must have LUSE LUNs. Enable discovery and statistics collection: Enabling discovery collection on page 35. Enabling statistics collection on page 36. Enabling discovery collection To enable discovery collection for HP XP arrays: 1. In Balance, select Discovery > Credentials. 2. Click Add credentials. 3. Add credentials for discovery collection, which is the login for Command View AE. Default login is system and 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 appears, the proxy is discovering the array. Once discovered, the array appears 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. 3/6/1235

36 Enabling statistics collection Only HP XP arrays with LUSE LUNs are supported. To enable statistics collection for HP XP storage arrays: 1. Install the HP XP Export Tool and the following JAR files on the Balance Proxy host: JSanExport.jar JSanRmiServerEx.jar Important! 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 point to the Balance Proxy host. 3. In Balance, create a credential based on the Storage Navigator user you created for each HP XP array. Hitachi Data Systems To discover and collect statistics from HDS 9900 or TagmaStore USP/NSC storage arrays, Balance has the following requirements: Multiprovider: High Command Device Manager (HDvM) 5.1 or greater is installed on the Balance Proxy host or is installed on a host that is accessible to Balance over the IP network. Enable discovery and statistics collection: Enabling discovery collection on page 36. Enabling statistics collection on page 37. Enabling discovery collection To enable discovery collection for HDS storage arrays: 1. In Balance, select Discovery > Credentials. 2. Click Add credentials. 3. Add credentials for discovery collection, which is the login for High Command Device Manager. Default login is system and 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. 36

37 9. Select Discovery > Proxies. In the Discovery Collection column, when Up appears, the proxy is discovering the array. Once discovered, the array appears 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. Enabling statistics collection To collect statistics from HDS storage arrays: Note: Arrays with LUSE LUNs are supported. 1. Install the Hitachi Performance Monitor Export Tool on the Balance Proxy host. Important! You must install the export tool from the exact 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. IBM To discover IBM storage arrays, Balance has the following requirements: IBM TotalStorage DS4000 and 5000 series/fastt Multiprovider: Engenio/LSI SMI-S v1.1 CIM Agent installed on a host that is accessible to Balance over the IP network. To download the SMI-S CIM Agent, go to the LSI Web site at: oftware/smis_provider/index.html IBM DS6000, DS8000, and ESS storage Multiprovider: DS Open API SMI-S v1.1 for DS6000 and ESS storage and v1.2 for DS8000 CIM Agent is installed on a host that is 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: dc=d400&uid=ssg1s &loc=en_us&cs=utf-8%e2%8c%a9=en 3/6/1237

38 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. Refer to the following Web site for installation and configuration details. Enabling discovery collection To enable discovery collection for IBM arrays, add the array to Balance as a SMI-S multiprovider: 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. 38

39 Virtualization software requirements Balance supports the following virtualization software: HMC, Virtual IO Servers, IBM LPAR on page 39 IBM SAN Volume Controller (SVC) on page 41 HP SAN Virtualization Storage Platform (SVSP) on page 42 HMC, Virtual IO Servers, IBM LPAR The following minimum versions are recommended when using IBM LPAR & VIOS on an IBM pseries for HMC and VIOS for proper interaction with Balance: HMC - v6.1.2 VIOS - v , v fp Preparing HMC VIO servers for discovery There are two options to choose from when setting up communication between Balance and HMC VIO servers: Enabling discovery using a user account on page 40 Enabling discovery using root on page 40 For IBM LPAR configuration, see Linux/UNIX server requirements on page 25. For either option, VIOS requires an appropriate ODM driver for the connected Storage Array. If the VIOS machine is connected to a CLARiiON array, and you have Powerpath installed, the appropriate ODM driver is installed automatically by Powerpath. If the VIOS machine is connected to an HP EVA array, and you have SecurePath installed, the appropriate ODM driver is installed automatically by SecurePath. Important! The latest VIOS should have the latest ODM drivers. If you run into any issues, you should upgrade to the latest VIOS (i.e. v fp-20.1). 3/6/1239

40 Enabling discovery using a user account To communicate with HMC and VIO servers, Balance has the following requirements: Install sudo on all VIO servers to be monitored; sudo is not required on the HMC. Have a valid username and password for access to the HMC and VIO servers. On the VIO Servers, the username must be listed in the sudoers file or equivalent in PowerBroker, and be a member of the staff group. The recommended HMC Task Role is "hmcviewer". Note: The accounts (username and password) for HMC and VIO servers do not need to be the same. However, the same VIO server account must be used on all VIO servers for a given HMC. Have SSH installed on the HMC and VIO servers. Balance uses an ssh login via password or key exchange to communicate with HMC and VIO servers. Add the Balance user to /etc/sudoers using the sudoedit command. Important! The following entries must be in your sudoers file, which you modify by running sudoedit as root. Sudoedit is generally found in /usr/bin. The entry you choose depends on your security requirements (password or no password). Defaults!env_reset username hostname = PASSWD: /tmp/aixhba or Defaults!env_reset username hostname = NOPASSWD: /tmp/aixhba Enabling discovery using root To communicate with HMC and VIO servers, Balance requires the following root privileges: VIO Server: username (padmin) and password. HMC Server: hscroot and password Note: All VIO servers must have the same root account credentials. At least one of the following prerequisites is also required: Copy the aixhba utility to all VIO servers in the /usr/bin directory. INQ: /usr/local/bin/inq 40

41 Note: Part of the previous Inq path (/usr/local/bin/inq) must be a symbolic link to the location where symcli is installed, due to the fact that your particular version cannot be hard coded. See the following example for clarification: ln -s /usr/bin/inq /usr/local/bin/inq IBM SAN Volume Controller (SVC) SVC virtual disks are modeled as server volumes and the managed disks as server LUNs. Cross-reference the list of supported storage systems in Storage system requirements on page 29 and IBM s support matrix to determine the storage devices supported for SVC. The minimum supported SVC version to collect statistics is Balance uses ssh login via key exchange to communicate with IBM SVC (SAN Volume Controller); SVC requires public/private SSH RSA key for an account on the server, logging in with the username, admin; note that this username does not provide administrative privileges; it is simply a naming convention. To configure RSA authentication, see Configuring RSA authentication for Linux/UNIX servers on page 29. Refer to IBM documentation for SVC setup ( Multiprovider: IBM SVC installs an SMI-S provider by default. If you are using IBM storage, its SMI-S provider must be installed on a separate system from the SVC and its SMI-S provider since both utilize port Enabling statistics collection To enable SVC statistics collection: 1. Open the SVL CLI interface. 2. Type the following command to start statistics generation at an interval of 1 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. 3/6/1241

42 HP SAN Virtualization Storage Platform (SVSP) Balance has the following requirements for HP SVSP: Multiprovider: 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 in which it is in the I/O topology. Refer to your HP SVSP documentation for further detail. SAN device requirements Brocade Balance supports the following SAN devices (switches): Brocade on page 42 Cisco on page 43 Note: Balance supports the SNMPv1 and SNMPv2c protocols only. For Balance to communicate with SAN devices that have the SNMPv3 protocol enabled, the v1 and/or v2c protocols must also be enabled. Balance has the following 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. 42

43 Cisco Balance has the following 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 Oracle 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 configure Balance to discover the database as an application. Note: Balance does not monitor applications hosted on Microsoft clusters. Balance supports the following Oracle database versions: Oracle 9i & 10g are supported on: Sun Solaris 9 IBM AIX 5.2 (or greater) Red Hat Enterprise Linux 4 Windows 2003 and 2008 Oracle 9i on Windows 2003 Oracle 11g on Windows 2008 To view the database in the Data Topology view, see Enabling topology views of database applications on page 44. 3/6/1243

44 Microsoft SQL Server Balance supports the following versions of MS SQL Server: Microsoft SQL Server 2005 Microsoft SQL Server 2008 To view the database in the Data Topology view, see Enabling topology views of database applications on page 44. 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 appears in the Data Topology view. To display database objects in the Data Topology view, complete the following for each database you want to monitor, in this order: 1. In Balance, add and discover each storage array associated with the database. 2. In Balance, add and discover the server hosting the database. 3. Prepare each database for discovery: Preparing an Oracle database for discovery on page 45. Preparing a MS SQL Server for discovery on page In Balance, on the Applications > Add Application page, add each database as an application. For Application Type, select a DB type. 5. In Balance, 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. 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. 44

45 Preparing an Oracle database for discovery To prepare an Oracle database for discovery: 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: APPMAP Password: appmap System Privileges Granted: CREATE SESSION, SELECT ANY DICTIONARY 2. In Balance, create access credentials using the user login credentials from step 3 on page For Method, select Login. Preparing a MS SQL Server for discovery To prepare a MS SQL Server for discovery: 1. Ensure that the MS SQL authentication service is enabled. Balance cannot use Windows authentication to communicate with MS SQL Server. 2. Ensure 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 Figure 2, MS SQL user mapping permissions, on page 46 shows an example of the user mapping permissions in SQL Server /6/1245

46 Figure 2. MS SQL user mapping permissions 5. In Balance, create access credentials using the user login credentials from step 3 on page For Method, select Login. 46

47 Communication ports The Balance VA and the Balance Proxy use different ports to communicate with each resource. Figure 3 on page 47 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. Two port numbers separated by an ellipsis indicates the first and second ports that the VA opens. Figure 3. Resource Ports accessed by Balance 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 After establishing a connection with the servers, and a remote instance has been created, the communication switches over to other lesser-known ports This process ensures that well-known ports are free for other applications. For the return communications, WMI ports are assigned by DCOM and they can use any random port between 1024~ No port exception is required. To configure ports behind a Windows firewall: 1. 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. Note: To see the current port settings on a Windows server, select Control Panel > Windows Firewall > Exceptions tab > File and Printer Sharing, and click Edit. 3/6/1247

48 48

49 4 Advanced configuration options This section explains using the Advanced Management Tool (AMT) to perform advanced configuration options, such as configuring network settings and backing up the Balance database. Accessing the AMT You can use the following methods to access the AMT: vsphere Client - In a vsphere Client, select the VA and then select the Console tab. Click inside the console to log in. SSH - Log in to 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. Using the AMT When you first log in to 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. 49

50 Uninstall - Uninstalls VMware Tools from the VA. We recommend using 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 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 search on (for example, yourcompany.com, yourcompany.local). Domain names added manually require a space between, but no commas. If the DHCP server is properly configured, DNS names are added automatically. Note: The domain names you want to search on can be added using this option or through the Balance UI 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 affect until you commit them with this option. After committing your changes, you are given the option to abort. 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 directory, or use FTP to transfer it to another location. The file is encrypted with a static passphrase. Note: If you back up the file locally, you could use SCP to transfer the file to another location. 50

51 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 passphrase used during encryption. If you restore locally, you are prompted to specify the filename relative to the /home/selfmonitor directory. If you are retrieving a remote backup using FTP, specify the filename relative to the home FTP directory. Gather Interop Info and Offload - Packages information about discovered resources, including OS type, 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 - Displays determine 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 shut down 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 VA. Monitoring the VA in Balance is referred to as self-monitoring. Adding network adapters to Balance This section explains adding a network adapter to the Balance virtual appliance (VA) and configuring Balance to detect the network adapter. You might need an additional adapter to separate network traffic. Important! This procedure involves restarting Balance. To prevent gaps in data collection, you should perform this procedure before you start a Balance upgrade. To add a network adapter to the VA: 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 Advanced Management Tool (AMT). 3. Log in to the AMT. 4. Select IP Management Options > Change Management IP Address Settings. 5. Select the new network adapter. For example, eth1. 3/6/1251

52 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. 9. Type b (Back) to return to the Main Menu. 10.Select System Configuration > Reboot Operating System to restart Balance. Balance restarts to complete the configuration. 52

53 Copyright information Copyright NetApp, Inc. All rights reserved. Printed in the U.S.A. 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 system without 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.A. 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 (October 1988) and FAR (June 1987). 3/6/1253

54 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 {Conref} Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/or other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft Corporation in the U.S.A. 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 U.S.A. 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. 54

55 How to send your comments You can help us to improve the quality of our documentation by sending us your feedback. Your feedback is important in helping us to provide the most accurate and high-quality information. If you have suggestions for improving this document, send us your comments by to To help us direct your comments to the correct division, include in the subject line the product name, version, and operating system. You can also contact us in the following ways: NetApp, Inc., 495 East Java Drive, Sunnyvale, CA U.S. Telephone: +1 (408) Fax: +1 (408) Support telephone: +1 (888) /6/1255

56 56

57 Index Index A authentication configuring for Linux/UNIX 28 configuring for RSA 29 B Balance installing 10 interoperability 21 overview 6 upgrading 11 Brocade discovery requirements 42 C Cisco discovery requirements 43 configuring virtual appliance 14 Copyright 53 D data collection enabling for EMC Symmetrix 32 database enabling topology view 44 deploying virtual appliance 13 deployment requirements 12 discovery accessing NetApp systems with a user account 30 Brocade requirements 42 Cisco requirements 43 Dell EqualLogic requirements 31 EMC CLARiiON requirements 31 EMC Symmetrix requirements 32 enabling for IBM HMC VIO 39 E Engenio requirements 34 ESX/ESXi requirements 22 HDS requirements 36 HP EVA requirements 34 HP SVSP requirements 42 HP XP requirements 35 Hyper-V requirements 25 IBM HMC, VIO, LPAR requirements 39 IBM SVC requirements 41 IBM TotalStorage requirements 37 Linux requirements 25 NetApp requirements 30 Oracle requirements 43 SQL Server requirements 44 UNIX requirements 25 vcenter requirements 22 Windows requirements 23 EMC CLARiiON discovery requirements 31 multiprovider 31 EMC Symmetrix configuring the proxy 32 discovery requirements 32 enabling data collection 32 multiprovider 32 Engenio discovery requirements 34 multiprovider 34 ESX/ESXi discovery requirements 22 H HDS discovery requirements 36 enabling discovery collection 36 enabling statistics collection 37 multiprovider 36 HP EVA discovery requirements 34 multiprovider 34 HP SVSP discovery requirements 42 57

58 Index multiprovider 42 HP XP discovery requirements 35 enabling discovery collection 35 enabling statistics collection 36 multiprovider 35 Hyper-V discovery requirements 25 I IBM discovery requirements 37 enabling discovery collection 38 IBM DS and ESS multiprovider 37 IBM HMC VIO enabling discovery collection 39 IBM HMC, VIO, LPAR discovery requirements 39 IBM SVC discovery requirements 41 enabling statistics collection 41 multiprovider 41 IBM TotalStorage multiprovider 37 IBM XIV multiprovider 38 installation 11, 13 requirements 12 installing Balance 10 proxy 18 interoperability Balance 21 L limitations virtual appliance 13 Linux discovery requirements 25 password authentication 28 RSA authentication 29 M N EMC CLARiiON 31 EMC Symmetrix 32 Engenio 34 HDS 36 HP EVA 34 HP SVSP 42 HP XP 35 IBM DS and ESS 37 IBM SVC 41 IBM TotalStorage 37 IBM XIV 38 NetApp discovering with a user account 30 discovery requirements 30 O Oracle discovery requirements 43 enabling topology views 45 P ports used by the virtual appliance 47 proxy EMC Symmetrix configuration 32 host limitations 17 host requirements 16 in-band 32 installing 18 out-of-band 32 ports used 47 setting up 15 R RSA configuring authentication 29 multiprovider about 16 58

59 Index S SQL Server discovery requirements 44 enabling topology views 45 statistics collection supported storage arrays 29 T topology view enabling for databases 44 enabling for Oracle databases 45 enabling for SQL Server databases 45 U UNIX discovery requirements 25 password authentication 28 RSA authentication 29 upgrade 11, 13 requirements 12 upgrading Balance 11 V vcenter discovery requirements 22 virtual appliance configuring 14 deploying 13 limitations 13 ports used 47 requirements 12 W Windows discovery requirements 23 59

60 Index 60