OnCommand
®Balance 4.2
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: [email protected] Part number: 215-08255_B0 August 2014
Contents
OnCommand Balance (OCB) ... 5
OnCommand Balance features ... 5
Balance licenses ... 6
Questions you can answer using OnCommand Balance ... 6
OnCommand Balance product documentation ... 7
Balance installation requirements ... 8
Virtual machine host requirements ... 8
Virtual machine resource guidelines ... 9
Balance Proxy host requirements for NetApp ... 9
Balance Proxy host resource limits ... 10
Balance web browser requirements ... 11
Downloading the latest Java version ... 11
Balance scalability limitations ... 12
Installing your OnCommand Balance software ... 14
Downloading the installation file ... 14
Installing Balance ... 14
Saving the installation file for OnCommand Balance ... 16
Configuring the virtual machine ... 16
Balance configuration ... 16
Installing the proxy for Windows ... 17
Applying the Controller license ... 18
Upgrading Balance ... 18
Upgrading the Balance Proxy ... 19
Configuring resources for data collection ... 20
VMware vCenter Server and ESXi Server requirements ... 20
VMware vCenter Server requirements ... 20
VMware ESXi Server requirements ... 20
Windows and Hyper-V Server requirements ... 21
Windows Server requirements ... 21
Hyper-V Server requirements ... 22
Linux and UNIX server requirements ... 22
Linux and UNIX requirements ... 23 Table of Contents | 3
Linux and UNIX configuration for volume monitoring ... 24
Linux and UNIX configuration for password authentication ... 26
Configuring RSA authentication for Linux and UNIX servers ... 27
NetApp storage system requirements ... 27
Enabling discovery of Data ONTAP operating in 7-Mode with a user account ... 27
NetApp system requirements for Balance ... 28
Storage virtualization software ... 29
HMC Virtual IO Servers (IBM LPAR) requirements ... 29
SAN device requirements ... 32
Database requirements ... 32
Enabling topology views of database applications ... 33
Preparing an Oracle database for discovery ... 33
Preparing a MS SQL Server for discovery ... 34
Self-monitoring requirements ... 34
NetApp communication ports for Balance ... 34
Configuring ports behind Windows firewalls ... 34
Advanced Balance configuration options ... 36
Accessing the Advanced Management Tool (AMT) ... 36
Advanced Management Tool configuration options for Balance ... 36
Adding network adapters ... 38
Copyright information ... 40
Trademark information ... 41
How to send your comments ... 42
OnCommand Balance (OCB)
OnCommand Balance (OCB) 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 the only analytics-based IT management software solution on the market designed to optimize performance and utilization of virtual machines, physical servers, and storage resources. IT organizations use Balance to isolate performance problems quickly, reduce
infrastructure costs, and ultimately enable a service-oriented infrastructure. Balance is agentless and available as a virtual machine. It provides support for VMware vSphere, Windows Hyper-V and other host operating systems, and NetApp storage systems running on clustered Data ONTAP and 7-Mode.
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 offer 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 machine (VM) that runs on an ESXi Server and on a Windows Hyper-V Server.
• Discovers and collects performance statistics from NetApp storage systems running on clustered Data ONTAP and 7-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.
Balance licenses
Two types of licenses are available for Balance: an evaluation license, and a Controller license for NetApp storage systems.
The software licenses have these characteristics:
• Evaluation: This is a Controller license that enables you to evaluate Balance for use in your environment. Please contact your NetApp Sales representative for a Balance evaluation license. • Controller: This license applies to NetApp storage systems only, and supports Data ONTAP 8.1
or later operating in 7-Mode and clustered Data ONTAP 8.1.1 or later. For storage systems running Data ONTAP 8.0 or earlier, such as 7.3, you must manually verify the license in Balance. A Capacity license, which applies to both NetApp and non-NetApp storage systems, is supported if you purchased the license before its end of availability. Capacity licenses are based on the storage capacity in terabytes (TB) that you plan to monitor in Balance. Each time you apply a storage system to the Capacity license, the storage system capacity is subtracted from the total capacity purchased. When the total license capacity has been used up, you can purchase more capacity for adding additional storage systems.
Note: NetApp V-Series systems running Data ONTAP software operating in 7-Mode are supported using Capacity licensing only.
To apply a new Capacity license key, you can open your license file in a text editor, copy the entire character string into the license key field on the Administration - License page, and click Continue. As of Release 4.1.1 the Capacity license was eliminated. If you purchased a Capacity license prior to that, see the Interoperability Matrix Tool (IMT) to check support for your storage system.
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?
Optimize
performance •• How much headroom do I have?Where can I put my VM or application for best performance?
• How can I better balance my workloads? • Are LUNs and VMDK partitions misaligned? • Which workloads are contending for resources?
Predict problems • How can I proactively avoid bottlenecks?
• How can I head off issues?
• Can I add VMs or workloads without impacting performance? • When will I run out of storage?
OnCommand Balance product documentation
OnCommand Balance (OCB) product user information is available as a Help system in the
Dashboard. To display the Help system, open the Dashboard and click the Help link at the top of the page.
The complete product documentation is available on the NetApp Support Site in these two guides: OnCommand
Balance Installation and Configuration Guide
Provides instructions for setting up OnCommand Balance in your data center. Also provides the system requirements and configuration
instructions for adding the servers, SAN devices, NetApp storage systems, and applications you want to monitor.
OnCommand Balance User Guide
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 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 ESXi Server and proxy host meet minimum requirements.
The minimum resource requirements for the 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.
Related references
Virtual machine host requirements on page 8
Virtual machine resource guidelines on page 9
Balance Proxy host requirements for NetApp on page 9
Balance scalability limitations on page 12
Virtual machine host requirements
The VMware ESXi server that will host the virtual machine (VM) must meet minimum resource requirements. Review these requirements before deploying the VA.
Resource Minimum Requirements
ESXi Server Hardware and software must be 64-bit.
Network 1 Gigabit Ethernet connection for fastest installation (optional). By default, the VM uses DHCP to communicate with the IP network. Virtual CPUs 2 @ 2.33 GHz
Virtual Memory 4 GB
With this amount of memory, you can add a maximum of 3 proxies to Balance. Increase the memory to twice this value or higher to add more proxies.
Disks At least 5 disk spindles in RAID-DP or other RAID array. During an upgrade, Balance requires a minimum of 50 percent free disk space. Balance uses the free portion of the disk to back up the original database (the used portion of the disk).
To view the percentage of Capacity Used, select Admin >
Resource Minimum Requirements
Storage Data store requires at least 205 GB of disk capacity, which includes an extra 5 GB for VM memory and additional files (for example, swap). Refer to the virtual machine resource recommendations for the minimum number of disks required.
Note: To optimize performance when installing Balance, there should be no memory limit set on vCenter OCB appliances. Virtual machines running Balance should be set to operate at their full RAM allocation. If performance becomes slow, reset the limit on VMs to use their maximum RAM allocation.
Virtual machine resource guidelines
The virtual machine (VM) resource guidelines listed here are based on the number of servers you plan to monitor. Additional virtual CPUs can be added through the vSphere Client.
The VM has a minimum memory reservation of 4,096 MB (default). If this amount of memory is not available on the ESXi Server, the VM might not power on. The VM offers support for 4, 8, 12 or 16 GB of RAM. The table below lists the tested configurations.
Monitored Windows servers vCPUs CPU reservation (MHz) Memory (MB) Memory reservation (MB) Minimum disks Network usage (KBps) 1,200 4 8000 8,192 8,192 12 140 800 4 5000 8,192 8,192 10 120 600 4 4000 4,096 4,096 8 100 400 4 3000 4,096 4,096 6 80 200 2 2000 4,096 4,096 4 60 100 or fewer 2 1500 4,096 4,096 3 60
Balance Proxy host requirements for NetApp
The host on which you install the Balance Proxy must meet minimum system requirements based on the number of servers the proxy will monitor. It must be installed on a separate server and cannot be installed on the same server as Unified Manager (UM).
Host requirements
The following table lists the minimum system and software requirements for the server on which you install the proxy.
Resource Requirement
Proxy Host 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 At least 20 GB of disk space assigned to the proxy, approximately 10 GB should be available after installation.
Java Runtime 32-bit version of Java is required for both 32-bit and 64-bit systems.
User Account A user account with local administrative privileges on the proxy host.
The account can be a domain or group user, but make sure that the account 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 bedisabled. 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.
Balance 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 Windows servers vCPUs CPU reservation (MHz) Memory (MB) Memory reservation (MB) Minimum disks Network usage (KBps) 600 2 4000 2,048 2,048 4 360 400 2 3400 2,048 2,048 4 340 300 2 2600 2,048 2,048 2 260
Monitored Windows servers vCPUs CPU reservation (MHz) Memory (MB) Memory reservation (MB) Minimum disks Network usage (KBps) 200 2 1800 2,048 2,048 2 180 100 2 1000 2,048 2,048 1 80 Less than 100 2 500 2,048 2,048 1 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.
Balance web browser requirements
Balance requires specific web browsers and plugins to properly display the web-based interface. Balance requires one of the following browsers and plugins. The Interoperability Matrix Tool (IMT) lists the latest version of supported browsers.
Note: For all browsers, ensure that pop-up windows are enabled for the Balance server. • Mozilla Firefox
• Microsoft Internet Explorer (IE)
Note: For IE 9 and IE 10, ensure that Compatibility Mode is enabled. See the Microsoft IE online help for information on enabling and disabling Compatibility Mode.
There is a bug with Windows 2003 that prevents IE from displaying the Balance login page. To resolve this problem, use Firefox or Chrome or apply the following hotfix to the server:
http://support.microsoft.com/kb/938397/
• Google Chrome
• Java Runtime Environment (JRE) and Adobe Flash Player plugins that are compatible with your browser. The latest versions of these plugins are recommended.
Downloading the latest Java version
If you are running Java 7 or earlier, you must download the latest Java version to run with Balance, and you must add Balance to the Java site.
Steps
1. Download the latest version of Java.
2. In the Java control panel Security tab, click Edit Site List.
If the Java version you are running does not include the Edit Site List option in the Java control panel, complete these steps:
a. Navigate to the option in the Windows Startup menu. b. Select All Programs, and then type Java.
c. Select Configure Java in the results list. d. In the Security tab, click Edit Site List.
3. Add the Balance IP address to the list as https://balance_ip_address.
4. Refresh the browser window displaying Balance.
Balance scalability limitations
Limiting the number of resources you discover ensures that Balance can operate efficiently, and accurately analyze collected statistics.
The following table lists the recommended limit for each resource type that Balance supports. If you exceed these limits, Balance may not perform at an optimal level during data collection and statistical analysis.
Resource Limit
Servers (VM, virtual host, and physical) 1,200 LUNs (server and storage) per Balance 6,000
Volumes per Balance 3,000
Storage arrays per Balance 20
Disk groups per Balance 512
Storage array disks 2,000 (across all monitored arrays) Applications per storage group Not tested
Applications per server Tested to 64, but no restrictions around additional applications.
Volumes per application Tested to 64, but no restrictions around additional applications.
LUNs per storage array Tested to 4,096
LUNs per server Tested to 64, but no restrictions around additional applications.
Resource Limit
LUNs per volume Tested to 64, but no restrictions around additional applications.
Note: Values in the Limit column are the recommended total limit for all monitored resources, not a limit for each individual resource. For Linux/UNIX servers, the limit is 800.
Installing your OnCommand Balance software
The installation process contains three steps: downloading the virtual appliance (VA) installation file, deploying the VA, and performing the initial configuration.
You download the VA as an OVA installation file from the NetApp Support Site. You need a customer account to access the site.
You also need to be familiar with the operations of the VMware vSphere Client to deploy the OVA installation file that creates the virtual machine (VM). After the initial configuration using the vSphere Client, you can copy the IP address for your new VM into a supported browser and then start using the software to monitor your NetApp storage systems.
Downloading the installation file
To set up the software installation, you need to download the virtual appliance (VA) installation file and then use a VMware vSphere Client to deploy the file to a VMware ESXi Server. The VA is available in an OVA file.
Steps
1. Download the OVA installation file from the NetApp Support Site.
You need to log into the Support website to access this file.
2. Save the OVA file to a local or network location that is accessible to your vSphere Client. 3. Verify the checksum on the Download page to ensure you have the correct installation file.
Installing Balance
To install Balance, you use a VMware vSphere Client to deploy the virtual appliance (VA) to a VMware ESXi Server. The vSphere Client converts the VA to a virtual machine (VM). Steps
1. In the vSphere Client, select File > Deploy OVF Template. 2. 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. For more information, see the vSphere online help.
Note: If your vCenter has multiple networks specified, check the VA configuration to confirm that the correct network is selected.
4. In the vSphere Client, install VMware Tools for the VM.
A 90 second timeout message is displayed on the Balance console enabling you to install VMware Tools. If you do not install VMware Tools during the 90 second timeout, Balance deployment continues without installing VMware Tools.
If you do not install VMware Tools during this initial deployment, or if VMware Tools fail to install, you must install VMware Tools manually as described in the substeps below.
Note: If VMware Tools continues failing to install, reboot the appliance a second time, then manually install VMware Tools from the console.
5. In the vSphere Client, click the Console tab to monitor the status as the VM powers up, Balance
starts, and Balance uses DHCP to assign an IP address to the VM.
If DHCP is not detected, you are prompted to specify the network settings for assigning an IP address to the VM. You enter this IP address in a web browser to access and use the Balance web client to configure the VM.
If you did not install VMware Tools in step 4 above, install the VMware Tools manually: a. In the vSphere Client, select the Balance VM and install VMware Tools.
b. Select the Console tab, and click inside the console to log in.
Note: The default username and password is netapp (all lowercase). You should change the default credentials when you log in for the first time.
c. Choose option 2 for Hypervisor Tools, then choose option 1 to install. d. When prompted, type y to continue.
e. When the installation has completed, exit the menu.
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.
After you finish Configure the VM. Related concepts
Balance installation requirements on page 8
Related tasks
Downloading the installation file on page 14
Configuring the virtual machine on page 16
Applying the Controller license on page 18
Installing the proxy for Windows on page 17
Saving the installation file for OnCommand Balance
When you upgrade OnCommand Balance, you might need to create a backup or clone of your OVA installation file. You use VMware Tools to save the virtual appliance (VA).
Steps
1. While you are working with the installation file, you need to back up the original OVA
installation file.
2. Use the VMware Tools to create a copy of the installation file that might be needed during an
upgrade process.
3. Save the backup file in a separate location.
Configuring the virtual machine
After deploying the virtual appliance (VA) and powering it on, you can open a web browser and use the fully-qualified domain name (FQDN) or IP address assigned to the Virtual Machine (VM) to access the software and begin configuring the VM.
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 VM when it was deployed. 3. Follow the on-screen instructions to configure the VM.
After you complete the configuration, the login page opens.
4. Enter your login credentials.
The default is the following (all lowercase): • User: admin
• Password: password
You should change the default credentials when you log in for the first time.
Balance configuration
After installing the virtual machine and opening it in a web browser, Balance requires some additional configuration.
OnCommand Balance must meet minimum product requirements for the appliance to start and function properly.
The first time you log in, the Dashboard page is inactive (empty) but displays this list of links to guide you through the configuration:
• Configure your storage arrays. • Configure your vCenter Server. • Configure physical servers. • Configure other resources. • Configure database applications. • Add email recipients.
The Dashboard is then populated after Balance has discovered the data center resources in its environment.
Installing the proxy for Windows
Balance requires the Balance proxy to discover and communicate with Windows Servers. 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. In addition, the proxy cannot be installed on the same server as Unified Manager (UM).
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. Select Discovery > 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 the proxy.
At 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 is incorrect, click Browse to locate the management software and update that path.
After you complete the installation wizard, the proxy becomes selectable when adding a resource in Balance.
Applying the Controller license
You need to add your Balance Controller license information to each NetApp node and add information for each node to Balance.
Before you begin
You have obtained a Controller license from your NetApp Sales Representative or authorized reseller.
Steps
1. In a text editor, open the license file and copy the entire license key string. 2. Log onto your NetApp Controller and enter one of the following commands:
For a clustered node, enter: Insight_balance license at the cluster level using license add -license <license_key>.
For a 7-Mode node, enter: Insight_balance license at each node using license add -license <-license_key>.
3. Open the Balance browser and select Discovery > Storage. Click Add storage system.
4. In the Add new storage system dialog box, enter the IP address for the cluster-management LIF
or the node IP for a 7-Mode node.
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.
Note: Before upgrading Balance, ensure a minimum of 50 percent free disk space. Balance uses the free portion of the disk to back up the original database (the used portion of the disk). To view the percentage of Capacity Used, select Admin > Configuration > Data growth.
Steps
1. To download the upgrade image, go to the NetApp Support Site 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 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: The default username and password is netapp (all lowercase). You should change the default credentials when you log in for the first time.
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 tasks
Upgrading the Balance Proxy on page 19
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.
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.
For the latest information on supported system models and required software versions, use the Interoperability Matrix.
Related concepts
VMware vCenter Server and ESXi Server requirements on page 20
Related references
Windows Server requirements on page 21
NetApp storage system requirements on page 27
VMware vCenter Server and ESXi Server requirements
Balance supports VMware vCenter servers and allows for the discovery of guests associated with ESXi Servers. It can also track vMotion activity.The user account for accessing the vCenter 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 ESXi Server requirements
Balance supports standalone VMware ESXi Server.
To discover ESXi Servers, Balance has the following discovery requirements: • FQDN, Hostname, or IP address of the server.
Note: VM guests must have VMware Tools installed before they can be monitored. ESXi servers have the following limitations:
• ESXi hosted 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
ESXi 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 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.
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.
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.
Hyper-V Server requirements
The supported versions of Windows Hyper-V Server and the fulfillment of software requirements associated with the server are required to enable server discovery.
Balance supports clustering for V. Balance does not support VM clusters running on a Hyper-V server. Balance discovers Hyper-Hyper-V virtual machines (Hyper-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)
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
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 Requirements
Red Hat Enterprise
Linux • Root access to the server or non-root access with sudo, which is a freedownload, to access restricted commands. • SSH installed. Balance uses an SSH login using a password or key
exchange to communicate with Linux servers.
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 Requirements
HP-UX • 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.
UNIX Type Requirements
IBM AIX • 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.
• 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.
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
Platform Installation Locations
Dynamic Link Manager
IBM AIX /usr/DynamicLinkManager/bin/dlnkmgr
Emulex HBAnyware
Solaris /usr/sbin/hbanyware/hbacmd Inq IBM AIX /usr/local/bin/inq
Red Hat Logical
Volume Manager
Red Hat /sbin/lvm Solaris SUSE Managed devices (Linux RAID Software)
Red Hat /sbin/mdadm
PowerPath IBM AIX /usr/sbin/powermt Red Hat /sbin/powermt SUSE Solaris /etc/powermt QLogic Host Bus Adapter Simple Command Line Interface (SCLI)
Red Hat /usr/local/bin/scli,/opt/QLogic_Corporation/SANsurferCLI/scsli SUSE
Solaris /usr/bin/ls/opt/QLogic_Corporation/SANsurferCLI/scli
Volume Manager
Platform Installation Locations
Veritas Volume Manager
HP-UX /usr/lib/vxvm/diag.d/vxdmpinq,/usr/lib/vxvm/diag.d/vxscsiinq IBM AIX /usr/lib/vxvm/diag.d/vxdmpinq,/usr/sbin/vxdisk,/usr/sbin/
vxdmpadm,/usr/lib/vxvm/diag.d/vxscsiinq
Red Hat /usr/lib/vxvm/diag.d/vxdmpinq,/usr/sbin/vxdisk,/usr/lib/vxvm/ diag.d/vxscsiinq
Solaris SUSE
ZFS Solaris /usr/sbin/zfs,/usr/sbin/zpool
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.
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.
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 machine (VM), you need to create RSA keys and RSA credentials in Balance. Steps
1. Create the following RSA keys:
• To monitor (self-monitor) the Balance VM, 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 VM,
copy or rename the id_rsa.pub key to .ssh/authorized_keys.
3. In Balance, create the RSA credentials.
4. On the Add Credentials page, for RSA File, upload the private side of the RSA keypair 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.
NetApp storage system requirements
The NetApp storage systems you want to add to Balance must meet minimum requirements. NetApp storage systems with these requirements:
• Clustered Data ONTAP software.
• Cluster administrator account with ONTAPI Application access and the read-only role. This account provides read-only administrator access to the cluster.
• Cluster Management IP (LIF) to discover all nodes in the cluster.
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 access to your storage systems. About this task
For storage systems with Data ONTAP operating in 7-Mode, you can use a command line interface 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 and use the command line interface.
2. Enter the following command to create the user role:
useradmin role add balance_user
-a login-http-admin,api-system-get-info,api-system-get-version,api- license-list-info,api-fcp-adapter-list-info,cli-fcp,api-cf-status,api- disk-list-info,api-aggr-list-info,api-volume-list-info,api-volume-list- info-iter-start,api-volume-list-info-iter-next,api-volume-list-info- iter-end,api-volume-get-root-name,api-lun-list-info,api-lun-get- geometry,api-lun-map-list-info,api-qtree-list,api-lun-get-serial- number,api-lun-stats-list-info,api-system-cli,cli-rdfile,cli- ifconfig,api-vfiler-list-info,security-api-vfiler,api-nfs-status,api- nfs-exportfs-list-rules,api-nfs-exportfs-list-rules-2,api-cifs- status,api-cifs-share-list-iter-start,api-cifs-share-list-iter-next,api- cifs-share-list-iter-end,api-perf-object-list-info,api-perf-object- counter-list-info,api-perf-object-get-instances,api-perf-object-get- instances-iter-start,api-perf-object-get-instances-iter-next,api-perf- object-get-instances-iter-end,api-useradmin-user-list,api-useradmin-group-list,api-useradmin-role-list
where balance_user is the name of your user role.
Note: If you previously added a balance_user, you only need to update the role. You 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 word wrap disabled, fix any missing hyphens, and then copy into the
Use Command Line field.
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.
NetApp system requirements for Balance
In order to discover and collect statistics, some systems have specific requirements. • Apply the controller license to V-Series systems.
• Discover V-Series systems.
When Balance discovers NetApp V-Series systems, it discovers the local disk groups on the systems. 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 NetApp 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.
Storage virtualization software
Balance supports virtualization software for HMC with specific software installed on each VIO server.
HMC Virtual IO Servers (IBM LPAR) requirements
To discover HMC servers, VIO servers, and the associated AIX logical partitions (LPAR), Balance requires specific software to be installed on each VIO server.
There are 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 want to discover. You then add the HMC and VIO servers to Balance to monitor the AIX LPARs.
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.
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 machine (VM). 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.
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 want 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)
• Latest ODM driver installed on each VIO server for the servers to communicate with each connected storage array.
• 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 !env_reset
username hostname=PASSWD: /tmp/aixhba or
Defaults !env_reset
username 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 machine (VM) 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.
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 configure Balance to discover the database as an application.
Note: Balance does not monitor applications hosted on Microsoft clusters. Balance supports Oracle and Microsoft SQL Server database applications.
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.
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.
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.
For Method, select Login.
Self-monitoring requirements
To monitor the Balance virtual machine (VM) in a process referred to as "self-monitoring," or to access the selfmonitor directory on the VM, you need to create a specific credential for accessing the VM.
The selfmonitor credential has the following requirements: • Username: selfmonitor
• Password: h1ghlys3cure
The username and password are case-sensitive. A Balance Proxy is not required for discovering the VM. To change the password, you can use the Advanced Management Tool.
NetApp communication ports for Balance
The Balance virtual machine (VM) and the Balance Proxy use different ports to communicate with each resource.
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.
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 machine 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.
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 machine (VM) upgrade.
Hypervisor Tools
Provides options for installing and uninstalling VMware Tools on the VM.
• Install - Installs VMware Tools on the VM if they are not already installed. Use the vSphere
Client to install the VMware Tools ISO on the VM. For information on installing VMware Tools manually, see the substeps in Installing OnCommand Balance on page 14.
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
You can use these options for any required backup and restore processes:
• Database Backup and Offload - Packages and encrypts the database as a .gpg file. You can back
up the file locally to the /home/selfmonitor/offloads directory 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 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 virtual
machine. Monitoring the virtual machine in Balance is referred to as self-monitoring.
Adding network adapters
You use the Advanced Management Tool (AMT) to add a network adapter to the virtual machine (VM) 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 VM.
Note: See the vSphere online help for instructions.
2. After adding the network adapter, select the VM 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).
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.
Copyright information
Copyright © 1994–2014 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 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. 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).
