OnCommand Performance Manager 1.1

Transcription

1 OnCommand Performance Manager 1.1 Installation and Setup Guide For Red Hat Enterprise Linux NetApp, Inc. 495 East Java Drive Sunnyvale, CA U.S. Telephone: +1 (408) Fax: +1 (408) Support telephone: +1 (888) Web: Feedback: Part number: _B0 August 2015

2

3 Table of Contents 3 Contents Introduction to Performance Manager installation and setup on Red Hat Enterprise Linux... 5 How Performance Manager works with Red Hat Enterprise Linux... 5 Contents of the Performance Manager installation package for Red Hat Enterprise Linux... 5 What the umadmin users do... 6 What AutoSupport does... 7 Requirements for Performance Manager on Red Hat Enterprise Linux... 8 Browser and platform requirements... 9 Protocol and port requirements Installing Performance Manager on Red Hat Enterprise Linux Downloading and installing Performance Manager on a blank Red Hat Enterprise Linux system Downloading and installing Performance Manager on a fully configured Red Hat Enterprise Linux system Downloading and installing Performance Manager on a partially configured Red Hat Enterprise Linux system Configuring after installation Completing the setup wizard Configuring Performance Manager to send alert notifications Configuring settings Enabling remote authentication Adding authentication servers Configuring alerts Adding users Adding clusters Requirements for adding a cluster to Performance Manager Changing the umadmin password Setting up a connection between Performance Manager and Unified Manager Creating a user with Event Publisher role privileges Configuring a connection between a Performance Manager server and Unified Manager Deleting a connection between a Performance Manager server and Unified Manager Setting up a connection between a Performance Manager server and an external data provider Performance data that can be sent to an external server Prerequisites for sending performance data to Graphite... 35

4 4 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL Configuring a connection from a Performance Manager server to an external data provider Performance Manager stop, restart, remove, upgrade, or host rename operations in Red Hat Enterprise Linux Stopping and starting Performance Manager in Red Hat Enterprise Linux Removing Performance Manager from Red Hat Enterprise Linux Performance Manager 1.1 on Red Hat Enterprise Linux upgrade overview Changing the Performance Manager host name in Red Hat Enterprise Linux Generating and sending a support bundle if Performance Manager is installed on Red Hat Enterprise Linux Troubleshooting Performance Manager Installation on Red Hat Enterprise Linux Notification of nonsigned software packages during installation on Red Hat Enterprise Linux Performance Manager installation terminates due to MySQL packages upgrade fail notification of initial cron job failure at the end of the Performance Manager Red Hat Enterprise Linux installation operation can be disregarded Adding disk space to the /data directory of the Performance Manager Red Hat Enterprise Linux host Copyright information Trademark information How to send your comments Index... 49

5 5 Introduction to Performance Manager installation and setup on Red Hat Enterprise Linux You can install Performance Manager on both physical servers or virtual servers running Red Hat Enterprise Linux. Performance Manager provides performance monitoring and incident root-cause analysis of systems running clustered Data ONTAP 8.3 and 8.2.x. Performance Manager helps you identify workloads that are over-using cluster components and decreasing the performance of other workloads on the cluster. It alerts you to these performance issues so that you can take corrective action and return performance back to normal operation. You can view and analyze incidents in the Performance Manager GUI or view them in the Unified Manager Dashboard. Performance Manager is the performance management part of Unified Manager. Performance Manager can also be downloaded and installed as a virtual appliance on a VMware ESXi Server. For more information on this type of deployment, see the OnCommand Performance Manager Installation and Administration Guide for VMware Virtual Appliances. For the most current compatibility information, see the Interoperability Matrix. Related concepts Installing Performance Manager on Red Hat Enterprise Linux on page 11 Related references Requirements for Performance Manager on Red Hat Enterprise Linux on page 8 How Performance Manager works with Red Hat Enterprise Linux Red Hat Enterprise Linux is a commercial-grade operating system. It is one of the supported systems on which you can install and run Performance Manager to monitor and manage your clustered Data ONTAP storage domain. The Red Hat Enterprise Linux server on which you install Performance Manager can be running either on a physical machine or on a virtual machine running on VMware ESXi Server or Microsoft Hyper-V. To install Performance Manager on Red Hat Enterprise Linux, you must first download and run Red Hat package manager modules (RPMs), which are the package formats most often used for installing software applications on the Red Hat OS. Contents of the Performance Manager installation package for Red Hat Enterprise Linux The Performance Manager download web page enables you to download two zipped bundles to install Performance Manager on Red Hat Enterprise Linux: an optional third-party-dependencies bundle, and the main Performance Manager bundle. Contents of the Performance Manager bundle The Performance Manager bundle includes all the modules necessary to install the Performance Manager software on top of the required vendor software not made by NetApp. The contents of this zipped bundle includes the following RPM modules:

6 6 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL ocie-serverbase rpm ocie-server rpm ocie-au rpm ocf-server rpm netapp-opm rpm Contents of the third-party-dependencies bundle The third-party-dependencies bundle is a zipped file that contains packages for installing Java, MySQL, and other vendor utilities. These utilities are not made by NetApp, but they are necessary to support Performance Manager. If your Red Hat Enterprise Linux system is not already installed with the required utilities and the versions of Java and MySQL necessary to support a Performance Manager installation, you can download and install the contents of this bundle to ensure a successful installation. The contents of this bundle includes RPM packages for the following products: JRE 1.7 MySQL 5.6 Enterprise Edition p7zip rrdtool Related tasks Downloading and installing Performance Manager on a blank Red Hat Enterprise Linux system on page 11 Downloading and installing Performance Manager on a fully configured Red Hat Enterprise Linux system on page 14 Downloading and installing Performance Manager on a partially configured Red Hat Enterprise Linux system on page 17 Related references Requirements for Performance Manager on Red Hat Enterprise Linux on page 8 What the umadmin users do For each instance in which Performance Manager or Unified Manager is installed on Red Hat Enterprise Linux, an initial user, always named "umadmin," is automatically created. The umadmin users are the initial users used to access the Performance Manager web UI or the Unified Manager web UI after installation and from there perform configuration and management functions. umadmin users and customized passwords The name umadmin, whether created for Performance Manager or for Unified Manager, can never be changed; however, the password assigned to each umadmin user can and should be customized immediately after installation. For example, in a storage management infrastructure consisting of a Unified Manager server and two Performance Manager servers, access to the three objects might be configured as follows: The umadmin user for Unified Manager can log in as umadmin but authenticate with a customized password like "UMx9x947." The umadmin user for Performance Manager server 1 will log in as umadmin authenticate with a customized password like "PMz8z831."

7 Introduction to Performance Manager installation and setup on Red Hat Enterprise Linux 7 The umadmin user for Performance Manager server 2 will log in as umadmin authenticate with a customized password like "PMz468RT." The umadmin user OnCommand Administrator role and maintenance user type During an installation of Unified Manager or Performance Manager on a Red Hat Enterprise Linux machine, the associated umadmin user is assigned an OnCommand Administrator user role and configured as the maintenance user type. As such, each umadmin user can perform functions reserved for that role and that type. Performance Manager umadmin user abilities The umadmin user created during Performance Manager installation can perform the following functions: In the OnCommand Administrator role in Performance Manager allows the umadmin user to log in to the Performance Manager web UI and perform all the performance monitoring and troubleshooting operations supported through that interface. As the maintenance user type, the umadmin user can perform the following operations. Start the initial configuration of the Performance Manager web UI. Access the Performance Manager maintenance console and perform all menu operations displayed through that interface, including configuring a connection between Performance Manager and Unified Manager. Unified Manager umadmin user abilities The umadmin user created during Unified Manager installation can perform the following functions: As the OnCommand Administrator, log in to the Unified Manager web UI and perform all the monitoring and configuration operations supported through that interface. As the sole user assigned the maintenance user type, the umadmin user alone is authorized to start the initial configuration of Unified Manager. Related tasks Changing the umadmin password on page 29 What AutoSupport does With the help of the AutoSupport feature, Performance Manager sends information to technical support to help with troubleshooting. AutoSupport messages are scanned for potential problems and are available to technical support when they assist you in resolving issues. Related tasks Completing the setup wizard on page 21

8 8 Requirements for Performance Manager on Red Hat Enterprise Linux To ensure successful installation of Performance Manager on Red Hat Enterprise Linux, you must confirm that the system on which Performance Manager is being installed meets certain system and software requirements. System requirements The Red Hat Enterprise Linux system on which you install Performance Manager requires that the following additional capabilities and capacities be reserved to support Performance Manager: Note: These requirements must be met whether the target machine is a virtual machine, running on VMware ESXi Server or Microsoft Hyper-V, or a physical machine. Reserved CPU cycle capacity: 9572 MHz Reserved RAM: 12 GB Reserved free hard disk space: 300 GB, where the capacity is allotted as follows: 50 GB allotted to the root partition of the target system 250 GB of free disk space allotted to the /data directory, which is mounted on an LVM drive or on a separate local disk attached to the target system Important: Mounting the /data directory on an NFS or CIFS share is not supported. This configuration enables you to use a Red Hat Enterprise Linux machine with a smaller root partition and also enables you to expand /data directory storage if required at a later time. If the Red Hat Enterprise Linux target machine has a pre-existing configuration in which the /opt directory and /var/log directory are mounted on a separate partition, you must follow these sizing guidelines: Allocate at least 15 GB for /var/log Allocate at least 5 GB for /opt With this configuration, you can allocate space for root partition as per the best practice guidelines for Red Hat Enterprise Linux. Host connectivity requirement The Red Hat Enterprise Linux physical or virtual system on which you install Performance Manager must be FQDN-configured in such a way that you can successfully ping the host name from the host itself. You can use the host name (or the host IP address) to access the product web UI. If you configured a static IP address for your network during deployment, then you would have designated a name for the network host. If you configured the network using DHCP, the host name should be taken from the DNS. Software requirements The Red Hat Enterprise Linux system on which you install Performance Manager requires the following versions of the operating system and supporting software installed: Red Hat Enterprise Linux version 6.5 (64-bit)

9 Requirements for Performance Manager on Red Hat Enterprise Linux 9 Oracle JRE 1.7.0_79 MySQL Enterprise Edition This version must be supplied by Oracle Corporation or by the downloaded Performance Manager third-party-dependencies bundle. p7zip rrd tool and libraries If you do not have the listed software installed, downloading, unzipping, and installing the thirdparty-dependencies bundle automatically installs these packages. User authorization requirements To perform Performance Manager installation on Red Hat Enterprise Linux, you must be logged in as the root user on the target Red Hat Enterprise Linux system. Restriction: Installation by non-root users using the sudo command is not supported. License requirements No special licenses are required to install Performance Manager on Red Hat Enterprise Linux. Dedicated use requirement The Red Hat Enterprise Linux physical or virtual system on which you install Performance Manager must be used exclusively for Performance Manager and not shared with other applications. Important: This restriction includes Unified Manager. Unified Manager cannot be installed on the same Red Hat Enterprise Linux server on which you are installing Performance Manager. Related concepts What the umadmin users do on page 6 Browser and platform requirements To use the Performance Manager GUI, you must use a supported browser that runs on a supported client platform. Performance Manager has been tested with the following browsers and client platforms; other browsers might work but have not been qualified. See the Interoperability Matrix at mysupport.netapp.com/matrix for the complete list of supported browser versions. Supported browsers Mozilla Firefox versions 24 and 31 Microsoft Internet Explorer (IE) versions 10 and 11 Google Chrome version 36 Apple Safari version 7 For IE, ensure that Compatibility View is disabled and Document Mode is set to the default. See the Microsoft IE documentation for information on these settings. For all browsers, disabling any popup blockers allows software features to display properly.

10 10 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL Supported browser client platforms Windows 7 and Windows XP Macintosh OS X 10.8 and 10.9 Protocol and port requirements Using a browser, API client, or SSH, the required ports must be accessible to the Performance Manager UI and APIs. The required ports and protocols enable communication between the Performance Manager server and the managed storage systems, servers, and other components. Connections to the Performance Manager server You do not have to specify port numbers when connecting to the Performance Manager web UI, because default ports are always used. For example, because Performance Manager always runs on its default port, you can enter instead of The default port numbers cannot be changed. The Performance Manager server uses specific protocols to access the following interfaces: Interface Protocol Port Description Performance Manager GUI Performance Manager GUI and programs using APIs Red Hat Enterprise Linux command line HTTP 80 Used to access the Performance Manager GUI; automatically redirects to the secure port 443. HTTPS 443 Used to securely access the Performance Manager GUI or to make API calls. API calls can only be made using HTTPS. SSH/ SFTP 22 Used to access the Red Hat Enterprise Linux command line and retrieve support bundles. Connections from the Performance Manager server You must configure your firewall to open ports that enable communication between the Performance Manager server and managed storage systems, servers, and other components. If a port is not open, communication fails. Depending on your environment, you can choose to modify the ports and protocols used by the Performance Manager server to connect to specific destinations. The Performance Manager server connects using the following protocols and ports to the managed storage systems, servers, and other components: Destination Protocol Port Description Storage system HTTPS 443/TCP Used to monitor and manage storage systems. AutoSupport server Authentication server HTTPS 443 Used to send AutoSupport information. Requires internet access to perform this function. LDAP 389 Used to make authentication requests, and user and group lookup requests. Mail server SMTP 25 Used to send alert notification . Graphite server TCP 2003 Used to send performance data to a server.

11 11 Installing Performance Manager on Red Hat Enterprise Linux It is important that you understand that the sequence of steps to download and install Performance Manager on Red Hat Enterprise Linux varies according to your download scenario. Downloading and installing Performance Manager on a blank Red Hat Enterprise Linux system If you want to install Performance Manager on a Red Hat Enterprise Linux platform that is not yet installed with the Java packages, MySQL packages, or utilities necessary to support the installation, you can download zipped bundles that enable you to automatically install Performance Manager and all the additional modules and utilities necessary to support it. Before you begin The system on which you want to install Performance Manager is running Red Hat Enterprise Linux 6.5 or a later supported version (see the NetApp Interoperability Matrix Tool). The system on which you want to install Performance Manager is configured with a Fully- Qualified Domain Name ( FQDN) such that ping responses to the host name and FQDN are successful. The system on which you want to install Performance Manager is dedicated exclusively to running Performance Manager, not shared with any other application. You can log in as the root user to the Red Hat Enterprise Linux system upon which you want to install Performance Manager. Restriction: Installation by non-root users using the sudo command is not supported. You have a supported Internet browser. Your terminal emulation software is scrollback enabled. Steps 1. Use your web browser to navigate to the NetApp Support Site at mysupport.netapp.com, and locate the Download pages for installing Performance Manager on the Red Hat Enterprise Linux platform. 2. Download the Performance Manager bundle (OnCommandPerformanceManager zip) to a target directory on the target Red Hat Enterprise Linux system. 3. Download the third-party-dependencies bundle (ThirdPartyDependencies zip) to the same target directory on the target Red Hat Enterprise Linux system. 4. Log in as the root user to the target Red Hat Enterprise Linux system. 5. Navigate to the target directory and enter the following command to expand the third-partydependencies bundle: unzip ThirdPartyDependencies zip The required RPM modules for Java, MySQL, and supporting utilities are unzipped to the target directory.

12 12 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL 6. Still in the target directory, enter the following command to expand the Performance Manager bundle: unzip OnCommandPerformanceManager zip The required RPM modules for Performance Manager are unzipped to the target directory. 7. Confirm the presence of the listed modules by entering the following command: ls *.rpm The following rpm modules are listed: JRE 1.7.0_79 rpm: jre-7u79-linux-x64.rpm Enterprise Edition MySQL rpms: MySQL-client-advanced el6.x86_64.rpm MySQL-server-advanced el6.x86_64.rpm MySQL-shared-compat-advanced el6.x86_64.rpm p7zip rpm: p7zip x86_64.rpm rrdtool rpms: rrdtool-perl fc13.wrl.x86_64.rpm rrdtool fc13.wrl.x86_64.rpm ocie-serverbase rpm: ocie-serverbase-<version>.x86_64.rpm ocie-server rpm: ocie-server-<version>.x86_64.rpm ocie-au rpm: ocie-au-<version>.x86_64.rpm ocf-server rpm ocf-server-<version>.x86_64.rpm netapp-opm rpm netapp-opm-<version>.x86_64.rpm 8. Enter the following command: yum install *.rpm This command automatically executes the RPM modules, installing the necessary supporting software and the Performance Manager modules that run on top of them. Caution: Do not attempt installation by use of alternative commands (such as rpm -ivh...). Successful installation of Performance Manager on Red Hat Enterprise Linux requires that all Performance Manager files and related files be installed in a specific order into a specific directory structure that are executed and configured automatically by the "yum install *.rpm" command. 9. After the installation messages are complete, disregard the notification that is displayed immediately following. The notifies the root user of an initial cron job failure that has no adverse effect on the installation.

13 Installing Performance Manager on Red Hat Enterprise Linux After the installation messages are complete, scroll back the messages until you see the message in which the system displays an IP address or URL for the Performance Manager web UI, the maintenance user name (umadmin), and a default password. The message is similar to the following: OnCommand Performance Manager is successfully installed on the computer. Log in to OnCommand Performance Manager in a web browser by using following username and password: username: umadmin password: admin You should change the password before you perform any operation. or Enter the passwd umadmin command to change the umadmin user password from the default "admin" string to a personalized string. 12. Record the IP address or URL, the assigned user name (umadmin), and current password. 13. Optional: If necessary, block access to non-essential open ports. After installation, the following ports, opened during the installation process, are no longer necessary. They are opened during JBoss startup associated with the start of OCIE service. For security purposes they can be blocked from user access by firewall or other means with no impairment to Performance Manager functions Used as the RMI/JRMP socket for connecting to the JMX MBeanServer 1091 Used as the RMI server socket 1098 Used by the Socket Naming service to receive RMI requests from client proxies 1099 Used as the listening socket for the Naming service 4446 Used as JBoss Remoting Connector by UnifiedInvoker 5500 Used for clear/non-ssl Remoting connections After you finish After installation is complete, enter the specified IP address or URL into a supported web browser to start the Performance Manager web UI and begin initial configuration. Related tasks Changing the umadmin password on page 29 Related references Contents of the Performance Manager installation package for Red Hat Enterprise Linux on page 5 Requirements for Performance Manager on Red Hat Enterprise Linux on page 8

14 14 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL Downloading and installing Performance Manager on a fully configured Red Hat Enterprise Linux system If you want to install Performance Manager on a physical or virtual Red Hat Enterprise Linux platform that is already fully configured with the necessary Java packages, MySQL packages, and utilities, you can download a single zipped bundle that enables you to automatically install Performance Manager on that platform. Before you begin The system on which you want to install Performance Manager is running Red Hat Enterprise Linux 6.5 or a later supported version (see the NetApp Interoperability Matrix Tool). The system on which you want to install Performance Manager is configured with a fully qualified domain name (FQDN) such that ping responses to the host name and FQDN are successful. The system on which you want to install Performance Manager is dedicated exclusively to running Performance Manager, not shared with any other application. You can log in as the root user to the Red Hat Enterprise Linux system upon which you want to install Performance Manager. Restriction: Installation by non-root users using the sudo command is not supported. You have a supported web browser. Your installation of Red Hat Enterprise Linux has the following additional software installed: Oracle JRE 1.7.0_79 MySQL Enterprise Edition (supplied by Oracle Corporation or with the downloaded Performance Manager third-party-dependencies bundle) p7zip rrd tool and libraries Your terminal emulation software is scrollback enabled. About this task In this context, a Red Hat Enterprise Linux system is fully configured if it has Red Hat Enterprise Linux 6.5 or later installed and has all the required versions of the required additional software already installed. Steps 1. Log in as the root user to the Red Hat Enterprise Linux server on which you want to install Performance Manager and enter the appropriate commands to verify that the target system has the Java and MySQL versions and utilities required to support installation of Performance Manager. To verify these required software and versions... Oracle JRE 1.7.0_79 Enter this command... java -version

15 Installing Performance Manager on Red Hat Enterprise Linux 15 To verify these required software and versions... MySQL Enterprise Edition (supplied by Oracle Corporation or with the Performance Manager third-partydependencies bundle) p7zip rrdtool wrl.x86_64 rrdtool-perl wrl.x86_64 Enter this command... rpm -qa grep -i mysql rpm -qa grep p7zip or p7zip x86_64 rpm -qa grep rrd Note: If the required versions of the required software are not installed, see the task titled Downloading and installing Performance Manager on a partially configured Red Hat Enterprise Linux system. 2. Use your web browser to navigate to the NetApp Support Site at mysupport.netapp.com, and locate the Download pages for installing Performance Manager on the Red Hat Enterprise Linux platform. 3. Download the Performance Manager bundle (OnCommandPerformanceManager zip) to a target directory on the target Red Hat Enterprise Linux system. 4. Navigate to the target directory and enter the following command to expand the Performance Manager bundle: unzip OnCommandPerformanceManager zip The required RPM modules for Performance Manager are unzipped to the target directory. 5. Confirm the presence of the listed modules by entering the following command: ls *.rpm The following RPM modules are listed: ocie-serverbase rpm: ocie-serverbase-<version>.x86_64.rpm ocie-server rpm: ocie-server-<version>.x86_64.rpm ocie-au rpm: ocie-au-<version>.x86_64.rpm ocf-server rpm ocf-server-<version>.x86_64.rpm netapp-opm rpm netapp-opm-<version>.x86_64.rpm 6. Enter the following command: yum install *.rpm This command automatically executes the RPM modules, installing the Performance Manager modules. Caution: Do not attempt installation by use of alternative commands (such as rpm -ivh...). Successful installation of Performance Manager on Red Hat Enterprise Linux requires that all Performance Manager files and related files be installed in a specific order into a specific

16 16 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL directory structure that are executed and configured automatically by the "yum install *.rpm" command. 7. After the installation messages are complete, disregard the notification that is displayed immediately following. The notifies the root user of an initial cron job failure that has no adverse effect on the installation. 8. After the installation messages are complete, scroll back the messages until you see the message in which the system displays an IP address or URL for the Performance Manager web UI, the maintenance user name (umadmin), and a default password. The message is similar to the following: OnCommand Performance Manager is successfully installed on the computer. Log in to OnCommand Performance Manager in a web browser by using following username and password: username: umadmin password: admin You should change the password before you perform any operation. or 9. Enter the passwd umadmin command to change the umadmin user password from the default "admin" string to a personalized string. 10. Record the IP address or URL, the assigned user name (umadmin), and current password. 11. Optional: If necessary, block non-root user access to non-essential open ports. After installation, the following ports, opened during the installation process, are no longer necessary. They are opened during JBoss startup associated with the start of OCIE service. For security purposes they can be blocked from user access by firewall or other means with no impairment to Performance Manager functions Used as the RMI/JRMP socket for connecting to the JMX MBeanServer 1091 Used as the RMI server socket 1098 Used by the Socket Naming service to receive RMI requests from client proxies 1099 Used as the listening socket for the Naming service 4446 Used as JBoss Remoting Connector by UnifiedInvoker 5500 Used for clear/non-ssl Remoting connections After you finish After installation is complete, enter the specified URL into a supported web browser to start the Performance Manager web UI and begin initial configuration. Related tasks Changing the umadmin password on page 29

17 Installing Performance Manager on Red Hat Enterprise Linux 17 Related references Contents of the Performance Manager installation package for Red Hat Enterprise Linux on page 5 Requirements for Performance Manager on Red Hat Enterprise Linux on page 8 Downloading and installing Performance Manager on a partially configured Red Hat Enterprise Linux system If you want to install Performance Manager on a physical or virtual Red Hat Enterprise Linux platform that is only partially configured with the necessary Java packages, MySQL packages, and utilities, you can download zipped bundles that enable you to automatically install Performance Manager and upgrade all the third-party modules and utilities necessary to support it. Before you begin The system on which you want to install Performance Manager is running Red Hat Enterprise Linux 6.5 or a later supported version (see the NetApp Interoperability Matrix Tool). The system on which you want to install Performance Manager is configured with a fully qualified domain name (FQDN) such that ping responses to the host name and FQDN are successful. The system on which you want to install Performance Manager is dedicated exclusively to running Performance Manager, not shared with any other application. You can log in as the root user to the Red Hat Enterprise Linux system upon which you want to install Performance Manager. Restriction: Installation by non-root users using the sudo command is not supported. You have a supported web browser Your installation of Red Hat Enterprise Linux has some version of the following additional software packages installed: Oracle JRE MySQL p7zip rrd tool and libraries Your terminal emulation software is scrollback enabled. About this task In this context, a Red Hat Enterprise Linux system is partially configured if it has Red Hat Enterprise Linux 6.5 or later installed but does not have all required versions of the required supporting software (Java, MySQL, additional utilities) installed. Steps 1. Log in as the root user to the Red Hat Enterprise Linux server on which you want to install Performance Manager and enter the appropriate commands to assess what software might require installation or upgrade on the target system to support: Required software and version Oracle JRE 1.7.0_79 Command to verify software and version java -version

18 18 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL Required software and version MySQL Enterprise Edition p7zip rrdtool wrl.x86_64 rrdtool-perl wrl.x86_64 Command to verify software and version rpm -qa grep -i mysql rpm -qa grep p7zip rpm -qa grep rrd 2. If any version of the listed software is earlier than the required version, enter the appropriate command to uninstall that module: Software to uninstall MySQL (Uninstall any version that is not MySQL Enterprise Edition and not supplied by Oracle Corporation or with the Performance Manager third-partydependencies bundle) All other modules Command to uninstall rpm -e mysql_package_name yum remove module_name 3. Use your web browser to navigate to the NetApp Support Site at mysupport.netapp.com, and locate the Download pages for installing Performance Manager on the Red Hat Enterprise Linux platform. 4. Download the Performance Manager bundle (OnCommandPerformanceManager zip) to a target directory on the target Red Hat Enterprise Linux system. 5. Download the third-party-dependencies bundle (ThirdPartyDependencies zip) to the same target directory on the target Red Hat Enterprise Linux system. 6. Navigate to the target directory and enter the following command to expand the third-partydependencies bundle. unzip ThirdPartyDependencies zip The required RPM modules for Java, MySQL, and supporting utilities are unzipped to the target directory. 7. Still in the target directory, enter the following command to expand the Performance Manager bundle: unzip OnCommandPerformanceManager zip The required RPM modules for Performance Manager are unzipped to the target directory. 8. Confirm the presence of the listed modules: ls *.rpm The following RPM modules are listed: JRE 1.7 rpm: jre-7u79-linux-x64.rpm Enterprise Edition MySQL rpms: MySQL-client-advanced el6.x86_64.rpm MySQL-server-advanced el6.x86_64.rpm MySQL-shared-compat-advanced el6.x86_64.rpm p7zip rpm: p7zip x86_64.rpm

19 Installing Performance Manager on Red Hat Enterprise Linux 19 rrdtool rpms: rrdtool-perl fc13.wrl.x86_64.rpm rrdtool fc13.wrl.x86_64.rpm ocie-serverbase rpm: ocie-serverbase-<version>.x86_64.rpm ocie-server rpm: ocie-server-<version>.x86_64.rpm ocie-au rpm: ocie-au-<version>.x86_64.rpm ocf-server rpm ocf-server-<version>.x86_64.rpm netapp-opm rpm netapp-opm-<version>.x86_64.rpm 9. Enter the following command: yum install *.rpm This command automatically executes the RPM modules, installing the necessary third-party systems and the Performance Manager modules that run on top of them. Caution: Do not attempt installation by use of alternative commands (such as rpm -ivh...). Successful installation of Performance Manager on Red Hat Enterprise Linux requires that all Performance Manager files and related files be installed in a specific order into a specific directory structure that are executed and configured automatically by the "yum install *.rpm" command. 10. After the installation messages are complete, disregard the notification that is displayed immediately following. The notifies the root user of an initial cron job failure that has no adverse effect on the installation. 11. After the installation messages are complete, scroll back the messages until you see the message in which the system displays an IP address or URL for the Performance Manager web UI, the maintenance user name (umadmin), and a default password. The message is similar to the following: OnCommand Performance Manager is successfully installed on the computer. Log in to OnCommand Performance Manager in a web browser by using following username and password: username: umadmin password: admin You should change the password before you perform any operation. or Enter the passwd umadmin command to change the umadmin user password from the default admin string to a personalized string. 13. Record the IP address or URL, the assigned user name (umadmin), and current password. 14. Optional: If necessary, block access to non-essential open ports. After installation, the following ports, opened during the installation process, are no longer necessary. They are opened during JBoss startup associated with the start of OCIE service. For

20 20 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL security purposes they can be blocked from user access by firewall or other means with no impairment to Performance Manager functions Used as the RMI/JRMP socket for connecting to the JMX MBeanServer 1091 Used as the RMI server socket 1098 Used by the Socket Naming service to receive RMI requests from client proxies 1099 Used as the listening socket for the Naming service 4446 Used as JBoss Remoting Connector by UnifiedInvoker 5500 Used for clear/non-ssl Remoting connections After you finish After installation is complete, enter the specified URL into a supported web browser to start the Performance Manager web UI and begin initial configuration. Related tasks Changing the umadmin password on page 29 Related references Contents of the Performance Manager installation package for Red Hat Enterprise Linux on page 5 Requirements for Performance Manager on Red Hat Enterprise Linux on page 8

21 21 Configuring after installation After installation of the software is complete, you can log in to the web UI as the default user umadmin, complete an initial setup to configure a minimum software configuration. You can then configure additional options, such as adding alerts, adding users, changing the passwords, and adding clusters you want to monitor. Because the default user umadmin is assigned the OnCommand Administrator user role, that user has authorization to perform any configuration task that is possible through the web UI. Related concepts Setting up a connection between a Performance Manager server and an external data provider on page 34 Related tasks Setting up a connection between Performance Manager and Unified Manager on page 30 Completing the setup wizard After the installation of Performance Manager is completed, you can access the GUI to complete the setup wizard. You use the setup wizard to configure alerts, enable AutoSupport, change the password for the default user, and add clusters you want to monitor. After completing the setup wizard, you can access the other areas of the GUI. Before you begin You are prepared to provide the setup wizard with the following information: An IP address or URL at which to access the login window to the Performance Manager web UI An assigned username for the maintenance user A password for the maintenance user You can specify the following maintenance user information: An address at which the user can receive AutoSupport messages The IP address of the associated SMTP mail server Clusters you want to add to Performance Manager meet configuration requirements. Steps 1. Use an Internet browser to log in to the Performance Manager web UI, using the IP address or URL, the username for the maintenance user, and password that you were assigned at the end of installation. The setup wizard is displayed, with four initial settings for you to configure. 2. Configure the following settings to complete the wizard: Set Up Specifies where alerts are to be sent. You can identify an initial recipient and an SMTP server to handle communication. When Performance Manager is installed

22 22 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL on Red Hat Enterprise Linux system, you can also specify a Network Time Protocol (NTP) server to synchronize Performance Manager server time with the time of the NTP server. After configuring the settings, you can click Test to confirm whether recipients can receive alerts. Set Up AutoSupport Specifies whether AutoSupport is enabled to send information about your installation of Performance Manager to technical support. Support personnel can use this information to stay current with the configuration and operation of your installation of Performance Manager, and to help you troubleshoot or manage the product. Change Admin Credentials Provides options for changing the password for the Administrator account. This is the password you assigned to the maintenance user account when you installed Performance Manager. You cannot change the Administrator account name. When Performance Manager is installed on Red Hat Enterprise Linux system, you can change the password at a later time by logging into the Red Hat Enterprise Linux system as root and running the appropriate command. Add Clusters Enables you to add one or more clusters to monitor. You can enter the fully qualified name (FQDN) or IP address and access credentials for each system running clustered Data ONTAP. Each cluster must meet minimum configuration requirements. Note: The first time you add a cluster, it can take up to 15 minutes for Performance Manager to fully discover it. Until the discovery process has completed, you cannot search for objects, such as volumes, on the cluster. After you finish If you choose not to immediately add clusters, you can configure additional options, such as alerts, and then add clusters for monitoring. Related concepts What AutoSupport does on page 7 What the umadmin users do on page 6 Browser and platform requirements on page 9 Related tasks Changing the umadmin password on page 29 Related references Protocol and port requirements on page 10 Requirements for adding a cluster to Performance Manager on page 28 Protocol and port requirements on page 10

23 Configuring after installation 23 Configuring Performance Manager to send alert notifications You can configure Performance Manager to send notifications that alert you about events in your environment. Before notifications can be sent, you must first configure several other Performance Manager options. Before you begin You must have the OnCommand Administrator role or the Storage Administrator role. About this task After deploying the virtual appliance and completing the initial configuration of Performance Manager, you should consider configuring your environment to trigger alerts and generate notification or SNMP traps. You can complete the following tasks to properly configure your environment to send alert notifications. Steps 1. Configure settings on page 23 If you want alert notifications sent when certain events occur in your environment, you must supply an address from which the alert notification can be sent. If your configuration uses an SMTP server for authentication, then you must provide the user name and password for the server. 2. Enable remote authentication on page 24 If you want remote LDAP or Active Directory users to access the Performance Manager GUI and receive alert notifications, then you must enable remote authentication. 3. Add authentication servers on page 25 If you enable remote authentication, then you must identify authentication servers. 4. Add users on page 27 You can add several different types of local or remote users and assign specific roles. When you create an alert, you assign a user to receive the alert notifications. 5. Configure alerts on page 27 After you have added the address for sending notifications, added users to receive the notifications, configured your network settings, and configured SMTP options needed for your environment, then you specify the incident alerts to send. Configuring settings You can configure SMTP settings for the Performance Manager server to send notifications when an event is generated. You can specify the corresponding mail server to be used. Before you begin The following information must be available: address from which the alert notification is sent

24 24 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL Host name (or IP address), user name, password, and default port to configure the SMTP server You must have the OnCommand Administrator role or the Storage Administrator role. Steps 1. Click Administration > Configure Settings. 2. In the Configure Settings dialog box, click Management Server > In the dialog box, configure the appropriate settings. The address appears in the From field in sent alert notifications. If the cannot be delivered for any reason, this address is also used as the recipient for undeliverable mail. If the host name of the SMTP server cannot be resolved, you can specify the IP address of the SMTP server instead. The user name and password are only required if SMTP authorization is enabled. 4. Click Test to confirm whether recipients receive alerts using the SMTP settings. Enabling remote authentication You can enable remote authentication using OPEN LDAP or Active Directory so that the management server can communicate with your authentication servers, and so users of the authentication servers can use Performance Manager and manage the storage objects and data. Before you begin You must have the OnCommand Administrator role or the Storage Administrator role. About this task If remote authentication is disabled, remote users or groups cannot access Performance Manager. The only two supported remote authentication methods are Active Directory and Open LDAP. LDAPS is not supported. Steps 1. Click Administration > Configure Settings. 2. In the Configure Settings dialog box, click Management Server > Authentication. 3. In the Authentication dialog box, select Enable Remote Authentication. 4. In the Authentication Service field, select either Active Directory or Open LDAP, and then enter the applicable information: If you are using... Active Directory Enter the following information... Authentication server administrator name Administrator password Base distinguished name (using the appropriate Active Directory notation)

25 Configuring after installation 25 If you are using... Open LDAP Enter the following information... Bind distinguished name (using appropriate LDAP notation) Bind password Base distinguished name If authentication of an Active Directory user takes a long time or times out, the authentication server is probably taking a long time to respond. Disabling support for nested groups in Performance Manager might reduce the authentication time. 5. Optional: Add authentication servers and test the authentication. 6. Click Save and Close. Disabling nested groups from remote authentication If you have remote authentication enabled, you can disable nested group authentication so that only individual users and not group members can remotely authenticate to Performance Manager. You might disable nested groups when you want to improve Active Directory authentication response time. Before you begin You must be logged in as an Active Directory domain user to perform this task. Logging in as an Active Directory administrator is not required. About this task Disabling support for nested groups in Performance Manager might reduce the authentication time. If nested group support is disabled and if a remote group is added to Performance Manager, individual users must be members of the remote group to authenticate to Performance Manager. Steps 1. Click Administration > Setup Options. 2. In the Setup Options dialog box, click Management Server > Authentication. 3. In the Authentication Service field, select Others. 4. In the Member field, change the member information from member: : to member. 5. Click Save and Close. Adding authentication servers You can add authentication servers and enable remote authentication on the management server to enable remote users within the authentication server to access Performance Manager. Before you begin The following information must be available: Host name or IP address of the authentication server Port number of the authentication server You must have enabled remote authentication and configured your authentication service so that the management server can authenticate remote users or groups in the authentication server.

26 26 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL You must have the OnCommand Administrator role or the Storage Administrator role. About this task If the authentication server that you are adding is part of a high-availability pair (using the same database), you can also add the partner authentication server. This enables the management server to communicate with the partner when one of the authentication servers is unreachable. Steps 1. Click Administration > Configure Settings. 2. In the Configure Settings dialog box, click Management Server > Authentication. 3. In the Authentication dialog box, in the Servers area, click Add. 4. In the Add Authentication Server dialog box, specify either the host name or IP address of the server, and the port details. 5. Click Save and Close. Result The authentication server that you added is displayed in the Servers area. After you finish Perform a test authentication to confirm that you are able to authenticate users in the authentication server that you added. Testing the configuration of authentication servers You can validate the configuration of your authentication servers to ensure that the management server is able to communicate with the authentication servers. You can test the configuration by searching for a remote user or group from your authentication servers and authenticate the user or group using the configured settings. Before you begin You must have enabled remote authentication and configured your authentication service so that Performance Manager can authenticate the remote user or group. You must have added your authentication servers so that the management server can search for the remote user or group from these servers and authenticate them. You must have the OnCommand Administrator role or the Storage Administrator role. About this task If the authentication service is set to Active Directory and if you are testing the authentication of remote users who belong to the primary group of the authentication server, information about the primary group is not displayed in the authentication results. Steps 1. Click Administration > Configure Settings. 2. In the Configure Settings dialog box, click Management Server > Authentication. 3. In the Authentication dialog box, click Test.