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.

27 Configuring after installation In the Test User dialog box, specify the user name and password of the remote user or group, and then click Test. If you are authenticating a remote group, you must not enter the password. Configuring alerts You can specify which incidents from Performance Manager to alert on and the recipients for those alerts. You can receive alerts for all new incidents, disable all alerts, or exclude alerts caused by a QoS policy group limit. By default, alerts are sent for all new incidents. Before you begin You must have the OnCommand Administrator role or the Storage Administrator role. Steps 1. Click Administration > Manage Alerts. 2. In the Configure Alerts dialog box, configure the appropriate settings. Note: For Recipients, use a comma or semicolon, with or without spaces, to separate the addresses. If you enter several addresses, such as by copying and pasting from an client, the addresses are automatically separated with commas after you click Save. Adding users You can create local users or database users from the Manage Users page. You can also add remote users or groups belonging to an authentication server. You can assign roles to these users, and based on the privileges of the roles, users can effectively manage the storage objects and data using Performance Manager, or view data in a database. Before you begin You must have the OnCommand Administrator role or the Storage Administrator role. To add a remote user or group, you must have enabled remote authentication and configured your authentication server. About this task If you add a group from active directory, then all direct members and nested subgroups can authenticate to Performance Manager. If you add a group from OpenLDAP or other authentication services, then only direct members of that group can authenticate to Performance Manager. Note: To ensure that you have at least one local user for accessing Performance Manager, you cannot delete the last local user administrator account. Steps 1. Click Administration > Manage Users. 2. In the Manage Users page, click Add. 3. In the Add User dialog box, select the type of user that you want to create and enter the required information. Note: The specified address must be unique to the instance of Performance Manager. 4. Click Save and Close.

28 28 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL Adding clusters You can add a cluster to Performance Manager to monitor the cluster and obtain information about its status and configuration. Before you begin The clusters you want to add meet the configuration requirements and you have the required privilege for adding them. You must have the OnCommand Administrator role or the Storage Administrator role. About this task You cannot add the same cluster to more than one instance of Performance Manager. When you attempt to add a cluster that a Performance Manager instance is already monitoring, a warning message is displayed in the GUI. Each cluster in a MetroCluster configuration must be added separately. A single instance of Performance Manager supports a specific number of clusters and volumes. If Performance Manager is monitoring an environment that exceeds the supported configuration, you might have difficulty collecting and analyzing configuration and performance data from the cluster. See the OnCommand Performance Manager Release Notes for the number of clusters, nodes, and volumes that Performance Manager can reliably support. Steps 1. Click Administration > Manage Data Sources. 2. On the Manage Data Sources page, click Add. 3. In the Add Cluster dialog box, specify the values as required and then click Save and Close. Result The cluster is added to the Performance Manager database after the default monitoring interval of approximately 15 minutes. If you destroy a Performance Manager virtual machine (VM) and then install a new instance using the same IP address assigned to the previous VM, adding the clusters from the previous VM to the new VM displays an error message that the clusters are already monitored. You can ignore this error message. Note: If the UUID of a monitored cluster changes, due to a cluster rebuild, for example, Performance Manager does not associate the new UUID with the cluster and the cluster is no longer monitored. To associate the cluster to the new UUID, you must remove the cluster from Performance Manager and then re-add it. Related references Protocol and port requirements on page 10 Requirements for adding a cluster to Performance Manager You must have all necessary configuration information available before adding a cluster. Required information Host name or cluster management IP address

29 Configuring after installation 29 The host name is the FQDN or short name that Performance Manager uses to connect to the cluster. This host name must resolve to the cluster management IP address. The cluster management IP address must be the cluster management LIF. If you use a node management LIF, the operation fails. User name and password to access the cluster If the version of Data ONTAP is earlier than 8.3, this account must have the Admin role with Application access set to ontapi. Type of protocol (HTTP or HTTPS) that is to be configured on the cluster and the port number of the cluster Changing the umadmin password For security purposes you are expected to change the default password for the umadmin user immediately after completing installation. If necessary you can change the password again anytime thereafter. On Red Hat Enterprise Linux, you change the Performance Manager umadmin password with a Linux command. Before you begin Performance Manager must be installed on a Red Hat Enterprise Linux system. You can log in as the root user to the Red Hat Enterprise Linux system upon which Performance Manager is running. Steps 1. Log in as the root user to the target Red Hat Enterprise Linux system on which Performance Manager is running. 2. Change the umadmin password: passwd umadmin The system prompts you to enter a new password string for the umadmin user. Related concepts What the umadmin users do on page 6

30 30 Setting up a connection between Performance Manager and Unified Manager This workflow shows you how to set up your connection between Performance Manager and Unified Manager. This enables you to monitor the performance issues that are detected by the Performance Manager server through the Unified Manager web UI. Before you begin Unified Manager is installed. Performance Manager is installed. You must have the OnCommand Administrator role in Unified Manager. If Unified Manager is installed on Red Hat Enterprise Linux, this role is automatically assigned to the user, "umadmin." You must have maintenance user log in access to Performance Manager. If Performance Manager is installed on Red Hat Enterprise Linux, the maintenance user automatically named "umadmin." About this task You can configure connections between one Unified Manager and multiple Performance Manager servers. Note: A connection configured between a Performance Manager server and a Unified Manager server requires either that both servers be deployed and running as virtual machines on VMware virtual infrastructure or that both servers be installed and running on Red Hat Enterprise Linux. Connections across installation types are not supported. Steps 1. Create a user with the event publisher role on page 30 You must first create a user with the event publisher role to begin connecting the Unified Manager server to an OnCommand Performance Manager server. 2. Set up a connection between Performance Manager and Unified Manager on page 31 You can connect an OnCommand Performance Manager server with the Unified Manager server to display performance issues in the Unified Manager web UI. 3. Delete a connection between Performance Manager and Unified Manager on page 32 You can delete a connection between an OnCommand Performance Manager server and the Unified Manager server if you no longer want to display performance issues discovered by a specific Performance Manager server in the Unified Manager web UI. Creating a user with Event Publisher role privileges To support a connection between a Performance Manager server and Unified Manager and the display of Performance Manager performance information in the Unified Manager web UI, you must create a local user for Unified Manager and assign to it the Event Publisher role. Before you begin You must have the OnCommand Administrator role in Unified Manager.

31 Setting up a connection between Performance Manager and Unified Manager 31 About this task When you configure a connection between a Performance Manager server and Unified Manager, the local user assigned the Event Publisher role is specified as the user under which performance incident notification is posted in the Unified Manager web UI. Steps 1. Click Administration > Manage Users. 2. In the Manage Users page, click Add. 3. In the Add User dialog box, select Local User for type and Event Publisher for role, and then enter the other required information. 4. Click Add. After you finish You can now configure a connection between one or more Performance Manager servers and Unified Manager. Configuring a connection between a Performance Manager server and Unified Manager To enable display in the Unified Manager web UI of performance issues discovered by a Performance Manager server, you must configure a connection between that server and Unified Manager in the Performance Manager maintenance console. Before you begin You must have created a local user with Event Publisher privileges on the Unified Manager in the connection you want to create. You must have an authorized login ID. Performance Manager, if installed on Red Hat Enterprise Linux, requires you have the Performance Manager umadmin user ID and password. You must be prepared to specify the following information about Unified Manager: Unified Manager server name or IP address Unified Manager server port (must always be 443) Event Publisher user name (the name of the local Unified Manager user assigned Event Publisher privileges) Event Publisher password (the password of the local Unified Manager user assigned Event Publisher privileges) Your Unified Manager and Performance Manager installation platforms must match. Unified Manager, if installed on Red Hat Enterprise Linux, can only connect with Performance Manager servers also installed on Red Hat Enterprise Linux. The clusters that are to be managed by Performance Manager and Unified Manager must be added to both Performance Manager and Unified Manager.

32 32 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL About this task You can configure connections between one Unified Manager and multiple Performance Manager servers. Steps 1. Log in via SSH as the maintenance user to the Performance Manager host to set up the Performance Manager and Unified Manager connection. If Performance Manager is installed on Red Hat Enterprise Linux, log in as umadmin (the maintenance user's automatically assigned name) to the Red Hat Enterprise Linux machine that hosts the Performance Manager server for which you want to create the Unified Manager connection. The Performance Manager maintenance console prompts are displayed. 2. In the maintenance console, type the number of the menu option labeled Unified Manager Connection and then type the number of the menu option labeled Add/Modify Unified Manager Server Connection. 3. When prompted, supply the requested Unified Manager server name or IP address and Unified Manager server port information. The maintenance console checks the validity of the specified Unified Manager server name or IP address and Unified Manager server port, and, if necessary, prompts you to accept the Unified Manager server trust certificate to support the connection. The default Unified Manager server port 443 must be used. 4. When prompted, supply the requested Event Publisher user name and Event Publisher password and then confirm that the settings are correct. 5. If you want to configure an additional connection between the Unified Manager and another Performance Manager server, log in as the maintenance user to that Performance Manager server and repeat this sequence. You can configure connections between a single Unified Manager server and up to five Performance Manager servers. Result After the connection is complete, all new performance incidents discovered by Performance Manager are reflected on the Unified Manager Dashboard page and Events page. Note: Until an initial performance incident is discovered the Unified Manager Dashboard page remains unchanged. Deleting a connection between a Performance Manager server and Unified Manager If you no longer want to display performance issues discovered by a specific Performance Manager server in the Unified Manager web UI, you can delete the connection between that server and Unified Manager. Additionally, if you are planning to delete a Performance Manager virtual machine that has an existing connection to Unified Manager, you must delete the connection before deleting the VM. Before you begin You must have the umadmin user ID, which is authorized to log in to the Red Hat Enterprise Linux machine on which sits the Performance Manager server.

33 Setting up a connection between Performance Manager and Unified Manager 33 Steps 1. Log in as the maintenance user (umadmin) to the Red Hat Enterprise Linux machine on which Performance Manager is installed. The Performance Manager maintenance console prompts are displayed. 2. In the maintenance console, type the number of the menu option labeled Unified Manager Connection. 3. Type the number of the menu option labeled Delete Unified Manager Server Connection. 4. When prompted whether you want to delete the connection, type y to delete the connection or type n to cancel. Result Performance incidents discovered by the specific Performance Manager server are no longer displayed in the Unified Manager web UI.

34 34 Setting up a connection between a Performance Manager server and an external data provider A connection between a Performance Manager server and an external data provider enables you to send cluster performance data to an external server so that storage managers can chart the performance metrics using third-party software. A connection between a Performance Manager server and an external data provider is established through the menu option labeled External Data Provider in the Performance Manager maintenance console. Performance data that can be sent to an external server Performance Manager collects a variety of performance data from all the clusters that it is monitoring. You can send specific groups of data to an external server. Depending on the performance data that you want to chart, you can choose to send one of the following groups of statistics: Statistics group Data included Details Performance Monitor Resource Utilization Drill Down High-level performance statistics for the following objects: LUNs Volumes Resource utilization statistics for the following objects: Nodes Aggregates Low-level read/write and perprotocol statistics for all tracked objects: Nodes Aggregates LUNs Volumes Disks LIFs Ports/NICs This group provides total IOPS or latency for all LUNs and volumes in all monitored clusters. This group provides the smallest number of statistics. This group provides utilization statistics for the node and aggregate physical resources in all monitored clusters. It also provides the statistics collected in the Performance Monitor group. This group provides read/write and perprotocol breakdowns for all seven tracked object types in all monitored clusters. It also provides the statistics collected in the Performance Monitor group and in the Resource Utilization group. This group provides the largest number of statistics. See knowledgebase article at for the list of all performance counters that can be sent to an external server.

35 Setting up a connection between a Performance Manager server and an external data provider 35 Prerequisites for sending performance data to Graphite Graphite is an open software tool for gathering and graphing performance data from computer systems. Your Graphite server and software must be configured correctly to receive statistical data from Performance Manager. After you have installed Graphite according to the installation instructions, you need to make the following changes to support statistical data transfer from Performance Manager: In the /opt/graphite/conf/carbon.conf file, set the maximum number of files that can be created on the Graphite server per minute to 200: MAX_CREATES_PER_MINUTE = 200 Depending on the number of clusters in your configuration, and the statistics objects you have selected to send, there may be thousands of new files that need to be created initially. At 200 files per minute it may take 15 or more minutes before all metric files are initially created. After all the unique metric files have been created, this parameter is no longer relevant. In the /opt/graphite/conf/storage-schemas.conf file, use the retentions parameter to set the frequency to 5 minutes and the retention period to the number of days that is relevant for your environment. The retention period can be as long as what your environment allows, but the frequency value must be set to 5 minutes for at least one retention setting. In the following example, a section is defined for Performance Manager using the pattern parameter, and the values set the initial frequency to 5 minutes and the retention period to 100 days: [OPM] pattern = ^netapp-performance\..* retentions = 5m:100d Note: If you change the default vendor tag from netapp-performance to something different, you will need to reflect that change in the pattern parameter as well. Important: If the Graphite server is unavailable when the Performance Manager server is attempting to send performance data, the data is not sent and there will be a gap in collected data. Configuring a connection from a Performance Manager server to an external data provider Performance Manager can send cluster performance data to an external server. You can specify the type of statistical data that is sent, and the interval at which data is sent. Before you begin You must have the Performance Manager umadmin user ID. You must have the following information about the external data provider: Server name or IP address Server default port (if not using default port 2003) You must have configured the remote server and third-party software so that it can receive statistical data from the Performance Manager server. You must know which group of statistics you want to send:

36 36 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL PERFORMANCE_INDICATOR: Performance monitor statistics RESOURCE_UTILIZATION: Resource utilization and Performance monitor statistics DRILL_DOWN: All statistics You must know the time interval at which you want to transmit statistics: 5, 10, or 15 minutes Performance Manager collects statistics at 5-minute intervals. If you set the transmit interval to 10 (or 15) minutes, the amount of data that is sent during each transmission is two (or three) times larger than when using the default 5-minute interval. About this task You can configure a connection between one Performance Manager server and one external data provider server. Steps 1. Log in via SSH as the maintenance user (umadmin) to the Red Hat Enterprise Linux machine on which Performance Manager is installed. The Performance Manager maintenance console prompts are displayed. 2. In the maintenance console, type the number of the External Data Provider menu option. The External Server Connection menu is displayed. 3. Type the number of the Add/Modify Server Connection menu option. The current server connection information is displayed. 4. When prompted, type y to continue. 5. When prompted, enter the IP address, or name, of the destination server and the server port information (if different from the default port 2003). 6. When prompted, type y if the information you entered is correct. 7. Press any key to return to the External Server Connection menu. 8. Type the number of the Modify Server Configuration menu option. The current server configuration information is displayed. 9. When prompted, type y to continue. 10. When prompted, enter the type of statistics to send, the time interval at which the statistics are sent, and whether you want to enable the transmission of statistics now: For.. Statistics group ID Vendor tag Enter PERFORMANCE_INDICATOR (default) 1 - RESOURCE_UTILIZATION 2 - DRILL_DOWN A descriptive name for the folder where the statistics will be stored on the external server. netapp-performance is the default name, but you can enter another value. By using dotted notation you can define a hierarchical folder structure. For example, by entering stats.performance.netapp the statistics will be located in stats > performance > netapp.

37 Setting up a connection between a Performance Manager server and an external data provider 37 For.. Transmit interval Enable/disable Enter... 5 (default), 10, or 15 minutes 0 - Disable 1 - Enable (default) 11. When prompted, type y if the information you entered is correct. 12. Press any key to return to the External Server Connection menu. 13. Type x to exit the maintenance console. Result After you have configured the connection, the selected performance data is sent to the destination server at the time interval you specified. It will take a few minutes before the metrics start to appear in Graphite. You may need to refresh your browser to see the new metrics in the metric hierarchy.

38 38 Performance Manager stop, restart, remove, upgrade, or host rename operations in Red Hat Enterprise Linux If Performance Manager is installed on Red Hat Enterprise Linux, operations such as stopping and restarting the service, removing the software, upgrading the software, or changing the hostname are performed using Linux commands. Stopping and starting Performance Manager in Red Hat Enterprise Linux You might occasionally need to stop Performance Manager prior to performing maintenance operations, such as backup and restore or changing the hostname, and then restart Performance Manager after those operations are completed. Before you begin You have root user access to the Red Hat Enterprise Linux machine on which Performance Manager is installed. Steps 1. Log in as root user to the Red Hat Enterprise Linux machine on which you want to stop the Performance Manager service. 2. Stop the Performance Manager service and the associated MySQL software by entering the following commands in the order shown: service ocieau stop service ocie stop service mysql stop 3. After the shutdown is complete, perform the maintenance operation that you stopped Performance Manager to perform. 4. After you complete your maintenance operation, restart Performance Manager by entering the following commands in the order shown: service mysql start service ocie start service ocieau start

39 Performance Manager stop, restart, remove, upgrade, or host rename operations in Red Hat Enterprise Linux 39 Removing Performance Manager from Red Hat Enterprise Linux If you need to remove Performance Manager from your Red Hat Enterprise Linux machine, you can stop and uninstall Performance Manager with a single command. Before you begin You must have root user access to the Red Hat Enterprise Linux machine from which want to remove Performance Manager. The Performance Manager server must not have an active connection to a Unified Manager server. If it does, you must delete the connection using the Performance Manager maintenance console. Steps 1. Log in as root user to the Red Hat Enterprise Linux machine on which you want to remove Performance Manager. 2. Stop and remove Performance Manager from the Red Hat Enterprise Linux machine: rpm -e netapp-opm ocf-server ocie-au ocie-server ocie-serverbase This step removes all the associated NetApp RPM packages. It does not remove the prerequisite software modules, such as Java, MySQL, and p7zip. 3. Optional: If appropriate, remove the supporting software modules, such as Java, MySQL, rrdtools, and p7zip. rpm -e p7zip rrdtool rrdtool-perl MySQL-client-advanced MySQL-serveradvanced jre Result After this operation is complete, the software is removed; however, MySQL data remains undeleted. Related tasks Deleting a connection between a Performance Manager server and Unified Manager on page 32 You can delete a connection between an OnCommand Performance Manager server and the Unified Manager server if you no longer want to display performance issues discovered by a specific Performance Manager server in the Unified Manager web UI. Performance Manager 1.1 on Red Hat Enterprise Linux upgrade overview Because Performance Manager installed on Red Hat Enterprise Linux was not supported in Performance Manager 1.0, there is no upgrade path from Performance Manager 1.0 (which is always installed as a virtual appliance) to Performance Manager 1.1 installed on Red Hat Enterprise Linux. Note: You can upgrade from Performance Manager 1.0 to Performance Manager 1.1 installed as a virtual appliance. To transition from Performance Manager 1.0 to Performance Manager 1.1 on Red Hat Enterprise Linux, follow the general process below: Download the OnCommandPerformanceManager zip bundle and install it on a Red Hat Enterprise Linux physical or virtual machine.

40 40 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL Configure the newly installed Performance Manager 1.1 instance to monitor the same clusters that were being monitored by the Performance Manager 1.0 instance. Because Performance Manager 1.1 cannot manage clusters that are being managed by another instance of Performance Manager, you must remove the clusters from the Performance Manager 1.0 instance before adding them to the Performance Manager 1.1 instance. Configure any additional settings, and, if required, connections to a Unified Manager server. Warning: All historical data will be lost when you move to Performance Manager 1.1 on Red Hat Enterprise Linux from Performance Manager 1.0 on a virtual appliance. Changing the Performance Manager host name in Red Hat Enterprise Linux At some point, you might want to change the host name of the Red Hat Enterprise Linux machine on which you have installed Performance Manager. For example, you might want to rename the host to more easily identify your Performance Manager servers by type, workgroup, or monitored cluster group when you list your Red Hat Enterprise Linux machines. Before you begin You have root user access to the Red Hat Enterprise Linux machine on which Performance Manager is installed. About this task You can use the host name (or the host IP address) to access the Performance Manager 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. Regardless of how the host name was assigned, if you change the host name and intend to use the new host name to access the Performance Manager web UI, you must generate a new security certificate. If you access the web UI by using the server's IP address instead of the host name, you do not have to generate a new certificate if you change the host name. However, it is the best practice to update the certificate, so that the host name in the certificate matches the actual host name. The new certificate does not take effect until the Red Hat Enterprise Linux machine is restarted. Steps 1. Log in as root user to the Performance Manager Red Hat Enterprise Linux machine whose host name you want to change. 2. Stop the Performance Manager software and the associated MySQL software by entering the following commands in the order shown: service ocieau stop service ocie stop service mysql stop 3. Edit the HOSTNAME parameter in the /etc/sysconfig/network file to specify the new fully qualified domain name and save it: HOSTNAME=new_FQDN Example HOSTNAME=nuhost.corp.widget.com

41 Performance Manager stop, restart, remove, upgrade, or host rename operations in Red Hat Enterprise Linux If there is an entry in the /etc/hosts file listing your IP address with the old host name, change it to the new name: ip-address new_fqdn new_hostname Example nuhost.corp.widget.com nuhost 5. Change the host name with the Linux hostname command: hostname new_fqdn Example hostname nuhost.corp.widget.com 6. Regenerate the HTTPS certificate: /opt/netapp/essentials/bin/cert.sh create 7. Restart the network service: service network restart 8. After the service is restarted, verify that the new host name is able to ping itself: ping new_hostname Example ping nuhost This command should return the same IP address that was set earlier for the original host name. 9. After you complete and verify your host name change, restart Performance Manager by entering the following commands in the order shown: service mysql start service ocie start service ocieau start Generating and sending a support bundle if Performance Manager is installed on Red Hat Enterprise Linux For the purpose of generating a package of data that can be used for storage domain troubleshooting, Performance Manager enables you to generate a zipped support bundle. If you install Performance Manager on Red Hat Enterprise Linux, you generate this bundle through a command line. Before you begin You must be able to log in to the Red Hat Enterprise Linux host with root user privilege. About this task You usually perform this task at the request of technical support. Steps 1. Log in with root user privilege to the Red Hat Enterprise Linux host on which you installed Performance Manager.

42 42 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL 2. At the command line, invoke the support bundle generation process: asup The AutoSupport component compiles support data into files and bundles those files into a zipped package. When the process is finished, the AutoSupport component displays a message similar to the following: Support bundle saved to /support/support_bundle_ _004711_467.7z 3. You can retrieve the zipped support bundle from the location indicated and send it to technical support or whoever requested it.

43 43 Troubleshooting Performance Manager Installation on Red Hat Enterprise Linux During or shortly after installation of Performance Manager on Red Hat Enterprise Linux, you might encounter some issues that require further attention. Notification of nonsigned software packages during installation on Red Hat Enterprise Linux If you are installing Performance Manager on a Red Hat Enterprise Linux system on which a signed software package requirement is enabled, your attempt to install Performance Manager with the normal yum install *.rpm command might fail. In such circumstances, at the point of failure, the yum install program displays a message similar to the following: Package ocie-au-xyz.rpm is not signed Workaround If you encounter this situation, you can run the yum install *.rpm command again but insert the --nogpgcheck option to suspend the signing requirement during installation: yum install --nogpgcheck *.rpm Performance Manager installation terminates due to MySQL packages upgrade fail The presence of any version of MySQL other than MySQL Enterprise Edition, supplied by Oracle, on the target Red Hat Enterprise Linux system causes the automated Performance Manager installation to terminate with a MySQL-related error. If you attempt to install Performance Manager on a Red Hat Enterprise Linux system by downloading and unzipping the Performance Manager package and convenience package and then invoking the yum install *rpm command, and if that system has a preexisting version of MySQL other than MySQL Enterprise Edition, the installation terminates and displays a message similar to the following: Error in PREIN scriptlet in rpm package MySQL-serveradvanced-5.x.xx-1.e16.86_64 Actions If you encounter this problem, perform the following steps: 1. Remove the existing MySQL packages from the target system. 2. Restart the Performance Manager installation by using the yum install *.rpm command. The automated installation process automatically installs MySQL Enterprise Edition as supplied in the convenience bundle.

44 44 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL notification of initial cron job failure at the end of the Performance Manager Red Hat Enterprise Linux installation operation can be disregarded At the end of the automated installation of Performance Manager in Red Hat Enterprise Linux (invoked by the yum install *.rpm command), the root user receives notification with messages, which can be disregarded, indicating failure of the initial cron job associated with Performance Manager installation. The contents of the message contain a log of an automated cron job associated with the installation and display messages that imply a failure of the installation process: cat: /proc//statm: No such file or directory cat: /proc//io: No such file or directory cat: /proc//io: No such file or directory These messages mean nothing. You can safely ignore them. Adding disk space to the /data directory of the Performance Manager Red Hat Enterprise Linux host If you allotted insufficient disk space to the /data directory to support Performance Manager when you originally set up the Red Hat Enterprise Linux host and then installed Performance Manager, you can add disk space post installation by increasing disk space on the /data directory. Before you begin You have root user access to the Red Hat Enterprise Linux machine on which Performance Manager is installed. About this task Performance Manager requires at least 250 GB of disk space allocated to the /data directory of the Red Hat Enterprise host on which it is installed. Steps 1. Log in as root user to the Red Hat Enterprise Linux machine on which you want to add disk space. 2. Stop the Performance Manager service and the associated MySQL software by entering the following commands in the order shown: service ocieau stop service ocie stop service mysql stop 3. Create a temporary backup folder (for example, /backup-data) with sufficient disk space to contain the data in the current /data directory. 4. Copy the content and privilege configuration of the existing /data directory to the backup data directory. cp -rp /data/* /backup-data

45 Troubleshooting Performance Manager Installation on Red Hat Enterprise Linux If SE Linux is enabled, perform the following substeps: a. Get the SE Linux type for folders on existing /data folder with the following command: se_type=`ls -Z /data awk '{print $4}' awk -F: '{print $3}' head -1` The system returns a confirmation similar to the following: echo $se_type mysqld_db_t b. Run the chcon command to set the SE Linux type for the backup directory. chcon -R --type=mysqld_db_t /backup-data 6. Remove the contents of the /data directory. cd /data rm -rf * 7. Expand the size of the /data directory to 100 GB through LVM commands or by adding extra disks. Important: Mounting the /data directory on an NFS export or CIFS share is not supported. 8. Confirm that the /data directory owner (mysql) and group (root) are unchanged with the following command: ls -ltr / grep data The system returns a confirmation similar to the following: drwxr-xr-x. 17 mysql root 4096 Aug 28 13:08 data 9. If SE Linux is enabled, confirm that the context for the /data directory is still set to mysqld_db_t with the following commands: touch /data/abc ls -Z /data/abc The system returns a confirmation similar to the following: -rw-r--r--. root root unconfined_u:object_r:mysqld_db_t:s0 /data/abc 10. Copy the contents from backup-data, back to the expanded /data directory. cp -rp /backup-data/* /data/ 11. Start the MySQL service: service mysql start 12. After the MySQL service is started, start the ocie and ocieau services by entering the following commands in the order shown: service ocie start service ocieau start 13. After all of the services are started, delete the backup folder /backup-data: rm -rf /backup-data

46 46 Copyright information Copyright 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 (October 1988) and FAR (June 1987).

47 47 Trademark information NetApp, the NetApp logo, Go Further, Faster, ASUP, AutoSupport, Campaign Express, Cloud ONTAP, clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, SANtricity, SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, and WAFL are trademarks or registered trademarks of NetApp, Inc., in the United States, and/or other countries. A current list of NetApp trademarks is available on the web at Cisco and the Cisco logo are trademarks of Cisco in the U.S. and other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.

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

49 Index 49 Index /data directory adding extra disk space 44 A Active Directory using to enable remote authentication 24 adding authentication servers 25 clusters 28 remote groups 27 remote users 27 adding clusters requirements for 28 alerts configuring 27 configuring your environment to send 23 assigning user roles 27 authentication adding servers 25 enabling remote 24 testing for remote users and groups 26 authentication, remote disabling nested groups 25 AutoSupport options offered by the Performance Manager setup wizard 21 what it does 7 B browsers requirements 9 C Chrome browser requirements 9 client software supported versions 9 clusters adding 28 options to add offered by the Performance Manager setup wizard 21 requirements for adding 28 comments how to send feedback about documentation 48 configuration options after installing Performance Manager 21 configuring alerts 27 notification settings 23 initial settings after installation 21 connection setting up between Performance Manager and Unified Manager 30 connections configuring from a Performance Manager server to an external data provider 35 introduction to setting up between Performance Manager and external data provider 34 creating database users 27 local users 27 D data Performance Manager performance, prerequisites for sending to Graphite servers 35 data providers configuring a connection from a Performance Manager server to external 35 database users creating 27 deleting connection between Performance Manager and Unified Manager 32 disk space adding to /data directory 44 documentation how to send feedback about 48 download process for Performance Manager on Red Hat Enterprise Linux fully configured systems 14 for Performance Manager on Red Hat Enterprise Linux partially configured systems 17 for Performance Manger on Red Hat Enterprise Linux blank systems 11 E notification settings configuring 23 notifications configuring 27 disabling 27 postponing 27 events configuring your environment to send notifications about 23 external data providers configuring a connection from a Performance Manager server to 35 F failure notification, false when installing Red Hat Enterprise Linux 44 feedback how to send comments about documentation 48 Firefox browser requirements 9

50 50 OnCommand Performance Manager 1.1 Installation and Setup Guide for RHEL G Graphite performance data available from Performance Manager 34 prerequisites for configuring to accept performance data from Performance Manager 35 groups testing remote authentication 26 groups, nested disabling remote authentication of 25 H host name changing for Performance Manager in Red Hat Enterprise Linux 40 I information how to send feedback about improving documentation 48 installation package for Red Hat Enterprise Linux contents 5 installation process for Performance Manager on Red Hat Enterprise Linux fully configured systems 14 for Performance Manager on Red Hat Enterprise Linux partially configured systems 17 for Performance Manger on Red Hat Enterprise Linux blank systems 11 installation, Performance Manager on Red Hat Enterprise Linux 5 Internet Explorer browser requirements 9 issue resolution what AutoSupport does 7 L license requirements to install Performance Manager on Red Hat Enterprise for Linux 8 local users creating 27 M Macintosh supported versions 9 messages, AutoSupport how used for troubleshooting 7 N nested groups disabling remote authentication of 25 notification configuring settings 23 notifications, alert O configuring your environment to send 23 OnCommand Administrator user role enabling configuration 21 Open LDAP using to enable remote authentication 24 P password, umadmin changing 29 performance data prerequisites for sending Performance Manager performance data to Graphite servers 35 statistics available for third-party software 34 Performance Manager configuring a connection to a Unified Manager server 31 configuring a connection to an external data provider 35 contents of installation package for Red Hat Enterprise Linux 5 deleting a connection to a Unified Manager server 32 introduction to setting up connection with external data provider 34 overview of upgrade on Red Hat Enterprise Linux 39 setting up a connection to Unified Manager 30 stopping and restarting in Red Hat Enterprise Linux 38 uninstalling 39 Performance Manager bundle, installation package for Red Hat Enterprise Linux contents 5 Performance Manager installation failure due to incorrect MySQL version or vendor 43 Performance Manager installation in Red Hat Enterprise Linux false failure notification 44 performance monitoring configuring a connection from a Performance Manager server to an external data provider 35 configuring connections between Performance Manager and Unified Manager 31 deleting connections between Performance Manager and Unified Manager 32 enabling 31 physical storage adding clusters 28 ports requirements 10 privileges creating a user with the Event Publisher role 30 R Red Hat Enterprise Linux and running Performance Manager on 5 content of installation package 5 installation and setup on 5 Red Hat program modules

51 Index 51 and installing Performance Manager on Linux 5 remote authentication disabling nested groups 25 enabling 24 remote groups adding 27 testing authentication 26 remote users adding 27 testing authentication 26 removing Performance Manager from Red Hat Enterprise Linux 39 requirements browser 9 restarting Performance Manager In Red Hat Enterprise Linux 38 role, Event Publisher creating a user having 30 roles assigning to users 27 purpose of umadmin 6 RPMs See Red Hat program modules S servers required ports 10 setting up notification settings 23 SMTP server notifications 23 setting up a connection between Performance Manager and Unified Manager 30 setting up connections between Performance Manager and external data provider, introduction to 34 setup, connection between Performance Manager and Unified Manager 30 setup, Performance Manager on Red Hat Enterprise Linux 5 signed package requirement stopping installation 43 software requirements to install Performance Manager on Red Hat Enterprise for Linux 8 stopping Performance Manager in Red Hat Enterprise Linux 38 suggestions how to send feedback about documentation 48 support bundles generating in Red Hat Enterprise Linux 41 system requirements to install Performance Manager on Red Hat Enterprise for Linux 8 system running clustered Data ONTAP adding 28 T testing authentication for remote users and groups 26 third-party-dependencies bundle, installation package for Red Hat Enterprise Linux contents 5 troubleshooting installation failure notification 44 what AutoSupport does 7 U umadmin password changing 29 umadmin user necessity of password 6 purpose 6 uninstalling Performance Manager from Red Hat Enterprise Linux 39 upgrade process for Performance Manager on Red Hat Enterprise Linux 39 user roles assigning 27 users adding 27 creating 27 creating having the Event Publisher role 30 purpose of umadmin 6 testing remote authentication 26 W Windows supported versions 9