CA Infrastructure Management Data Aggregator

Transcription

1 CA Infrastructure Management Data Aggregator Installation Guide Release

2 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

3 CA Technologies Product References This document references the following CA Technologies products: CA Infrastructure Management Data Aggregator (Data Aggregator) CA Infrastructure Management Data Collector (Data Collector) CA Performance Center Contact CA Technologies Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following resources: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback About Product Documentation If you have comments or questions about CA Technologies product documentation, you can send a message to techpubs@ca.com. To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at

4

5 Contents Chapter 1: Prerequisites and Installation Considerations 7 Data Aggregator Deployment... 7 Required Ports... 9 Data Repository Prerequisites... 9 Set the Limit on the Number of Open Files on Data Repository Hosts (Single-Node and Cluster Installations) Enable Core Dump File Generation (Single-Node and Cluster Installations) Configure the Sudo User Account for Data Repository (Required if Using a Sudo User Account to Install Vertica) Set a Unique Hostname for Each Data Repository Host (Single-Node and Cluster Installations) Disable the Firewall Settings on Each Data Repository Host (Single-Node and Cluster Installations) Verify that the NTP Daemon is Running (Cluster Installations Only) Configure Hostname Resolution (Cluster Installations Only) Data Aggregator Prerequisites Set the Limit on the Number of Open Files on Data Aggregator Configure the Sudo User Account for Data Aggregator Configure UTF-8 Support Data Aggregator Considerations Data Collector Prerequisites Configure the Sudo User Account for Data Collector Configure UTF-8 Support Set a Unique Hostname for the Data Collector Host Data Collector Considerations Chapter 2: Installing CA Infrastructure Management 27 How to Install Data Repository, Data Aggregator, CA Performance Center, and Data Collector Install Data Repository Generate a Response File for the Data Repository Installation (Optional) Configure Log Rotation for Data Repository (Required) Set Up Autostart on Data Repository (Optional) Set Up Automatic Backups of Data Repository Data Aggregator and Data Collector Installation Install Data Aggregator with the Installation Wizard Install Data Collector with the Installation Wizard Install Data Aggregator from the Command Line Install Data Collector from the Command Line Install Data Aggregator in Silent Mode Contents 5

6 Install Data Collector in Silent Mode Make Data Aggregator Aware of Data Repository Hosts in a Cluster Environment (Cluster Installations Only) Configure the Automatic Recovery of the Data Aggregator Process (Recommended) Modify Maximum Memory Usage for Data Aggregator and Data Collector Components After Installation Change the Opened Port Number on the Data Aggregator Host Chapter 3: Upgrading CA Infrastructure Management 77 How to Upgrade Data Aggregator Stop Data Collector and Data Aggregator Upgrade Data Repository How to Upgrade the Data Aggregator Installation How to Upgrade the Data Collector Installation Chapter 4: Uninstalling CA Infrastructure Management 85 Uninstalling Data Aggregator and Data Collector Uninstall Data Aggregator with the Installation Wizard Uninstall Data Collector with the Installation Wizard Uninstall Data Aggregator from the Command Line Uninstall Data Collector from the Command Line Uninstall Data Aggregator in Silent Mode Uninstall Data Collector in Silent Mode Uninstall Data Repository Appendix A: Troubleshooting 93 Troubleshooting: Data Aggregator Synchronization Failure Troubleshooting: CA Performance Center Cannot Contact Data Aggregator Troubleshooting: Data Collector Installs But Does Not Appear in the Data Collector List Menu Installation Guide

7 Chapter 1: Prerequisites and Installation Considerations This section contains the following topics: Data Aggregator Deployment (see page 7) Required Ports (see page 9) Data Repository Prerequisites (see page 9) Data Aggregator Prerequisites (see page 18) Data Collector Prerequisites (see page 22) Data Aggregator Deployment You have three options for a Data Aggregator deployment, depending on the amount of monitoring that you need: A small deployment, capable of handling 15,000 metrics per second, for monitoring up to 100,000 items. A medium deployment, capable of handling 75,000 metrics per second, for monitoring up to 500,000 items. A large deployment, capable of handling 150,000 metrics per second, for monitoring up to 1,000,000 items. Note: We recommend a clustered Data Repository deployment (based on three nodes) for medium and large deployments. Chapter 1: Prerequisites and Installation Considerations 7

8 Data Aggregator Deployment The following diagram demonstrates how each component works together: Note: For Data Aggregator system requirements, see the Data Aggregator Release Notes. 8 Installation Guide

9 Required Ports Required Ports Open the following ports before you install Data Aggregator, Data Collector, and Data Repository. These ports are in addition to the ports you opened when you installed CA Performance Center. Note: For more information about installing CA Performance Center, see the CA Performance Center Installation Guide. Port Number Port Is Utilized On This System Remote Access to Port Required 5433 Data Repository Yes 8581 Data Aggregator Yes Note: You can change this port number after you install Data Aggregator. Data Aggregator Yes More information: Data Repository Prerequisites (see page 9) Data Aggregator Prerequisites (see page 18) Data Collector Prerequisites (see page 22) Data Repository Prerequisites Meet the following prerequisites before you install Data Repository for a single-node or in a cluster: 1. Open the necessary ports (see page 9). 2. (Single-node and cluster installations) Decide whether to install Data Repository on a single node or if you are going to install Data Repository in a cluster. When installing Data Repository in a cluster, decide which hosts you are going to install Data Repository nodes on. Important! Database software is deployed on each participating host in a cluster. This software represents a node in the cluster. A three node cluster represents the simplest configuration that can tolerate the loss of a single node. You can, however, include more than three hosts in the cluster. If more than one node fails or shuts down, Data Repository is no longer available for use and Data Aggregator shuts down automatically. Chapter 1: Prerequisites and Installation Considerations 9

10 Data Repository Prerequisites 3. (Single-node and cluster installations) Ensure that the user that is installing Data Repository has a ulimit value of at least (see page 11). 4. (Single-node and cluster installations) Enable core dump file generation. (see page 12) 5. (Optional for single-node and cluster installations) Configure the sudo user account for Data Repository (see page 13). 6. (Single-node and cluster installations) Set a unique hostname for each Data Repository host (see page 15). 7. (Single-node and cluster installations) Disable the firewall settings on each Data Repository host (see page 16). 8. (Single-node and cluster installations) If a release file appears in the etc directory, remove it, otherwise, the Data Repository installation will fail. 9. (Single-node and cluster installations) Verify that the root user or sudo user can create database administrator user accounts, or have an administrator create these accounts. 10. (Single-node and cluster installations) Verify that CPU frequency scaling is disabled. Disable CPU frequency scaling through the host system Basic Input/Output System (BIOS). 11. (Cluster installations only) Verify that the NTP daemon is running (see page 16). 12. (Cluster installations only) Configure hostname resolution (see page 17). 13. (Cluster installations only) Verify all of the hosts in the cluster have the same subnet mask. 14. (Cluster installations only) Verify that the root user can use Secure Shell (SSH) to log in (ssh) to all of the hosts in the cluster. More information: Generate a Response File for the Data Repository Installation (Optional) (see page 38) Install Data Repository (see page 28) 10 Installation Guide

11 Data Repository Prerequisites Set the Limit on the Number of Open Files on Data Repository Hosts (Single-Node and Cluster Installations) Ensure that the user that is installing Data Repository has a value of at least on the number of open files. Set this value permanently. Follow these steps: 1. As the root user or a sudo user, log in to each computer where you are going to install Data Repository. Open a command prompt and type the following command to change the ulimit for the open files limit to at least 65536: ulimit -n ulimit_number For example: ulimit -n Open the /etc/security/limits.conf file on each computer where you are going to install Data Repository and add the following lines: # Added by Vertica * soft nofile # Added by Vertica * hard nofile # Added by Vertica * soft fsize unlimited # Added by Vertica * hard fsize unlimited 3. Type the following command on each computer where you are going to install Data Repository: /etc/init.d/sshd restart Note: If you do not have restart as an argument, type the following commands to stop and start sshd: /etc/init.d/sshd stop /etc/init.d/sshd start 4. To verify that the number of open files is set properly on each computer where you are going to install Data Repository, type the following command: ulimit -n The command returns the ulimit number that you specified earlier. 5. (Cluster installations only) Log in as the root user or a sudo user. Ssh from one node to another node and confirm that the number of open files is set properly on each computer: ulimit -n The command returns the ulimit number that you specified earlier. Chapter 1: Prerequisites and Installation Considerations 11

12 Data Repository Prerequisites The user that is installing Data Repository must have a ulimit value of at least The ulimit value is set permanently. This value remains set, even if the computer where Data Repository is installed is rebooted. 6. If the ulimit value is not set to at least on any of the hosts, do the following step on that host: Open the /etc/security/limits.conf file and add the following lines: # Added by Vertica * soft nofile # Added by Vertica * hard nofile More information: Data Repository Prerequisites (see page 9) Enable Core Dump File Generation (Single-Node and Cluster Installations) Ensure that core dump file generation is enabled on each computer where you are going to install Data Repository. Ensure also that there are no restrictions on the size of the core file. Core files are necessary to troubleshoot unexpected termination of the application. Follow these steps: 1. As the root user or a sudo user, log in to each computer where you are going to install Data Repository. Open a command prompt and type the following command to see whether core dump file generation is enabled already: ulimit -c 2. Look at the output for the -c line to see what limit is set on the file size. A value of 0 means that core dump file generation is disabled. 3. If you see a value of 0, enable core dump file generation on each computer where you are going to install Data Repository by setting the limit on core file size to "unlimited". Type the following command: ulimit -c unlimited Note: This ulimit setting must be applied to all processes that the vertica Linux database administrator user account will launch and for all terminal sessions. Consult your system administrator to configure this setting appropriately for the vertica Linux database administrator user account. More information: Data Repository Prerequisites (see page 9) 12 Installation Guide

13 Data Repository Prerequisites Configure the Sudo User Account for Data Repository (Required if Using a Sudo User Account to Install Vertica) Before you install Data Repository, log in as the root user. However, in some environments, unrestricted root user access is not available. If root user access is not available, a sudo user with access to a limited set of commands can install and run the software. Follow these steps: 1. Log in to the computer where you want to install Data Repository as a root user. Copy the installdr.bin file locally. For example: cp /mnt/cdrom/ca/installdr.bin /directory 2. Create the sudo user by typing the following command: useradd username p userpassword -d /directory For example: useradd sudouser p password -d /home/sudouser Ensure that the directory that you chose for the sudo user exists and is accessible by the sudo user. Note: In a cluster installation, perform this step on each host in the cluster. 3. Determine whether the root user owns the installation file. If the root user owns the installation file, change its owner to sudo user by typing the following command: chown sudouser:sudouser installdr.bin Chapter 1: Prerequisites and Installation Considerations 13

14 Data Repository Prerequisites 4. Do one of the following: a. Add the following command alias to the command alias section of the /etc/sudoers file to grant the sudo user all root access: sudouser_name (ALL) ALL sudouser_name Indicates the name of the sudo user you created previously. b. Add the following command alias to the command alias section of the /etc/sudoers file to restrict access: # CA Vertica Cmnd_Alias CA_VERTICA = /etc/init.d/ntpd, /etc/init.d/sshd, /bin/cp, /bin/rpm, /bin/tar, /bin/mv, /bin/bash, /sbin/sysctl, /usr/sbin/ntpq, /opt/vertica/bin/validators.sh, /opt/vertica/sbin/, /opt/vertica/bin/admintools, /opt/vertica/bin/vsql, /opt/vertica/log/, /etc/init.d/spreadd, /usr/bin/, /bin/grep, /bin/echo, /bin/cat, /bin/sed, /bin/ls, /bin/uname, /bin/ps, /bin/sh, /bin/chown, /bin/rm, /bin/touch, /bin/chgrp, /bin/chmod, /bin/su, /usr/sbin/groupadd, /usr/sbin/usermod, /sbin/ifconfig, /sbin/route, /usr/sbin/useradd, /bin/chown, /bin/mkdir ## Allows the sudouser to perform database administration sudouser_name ALL = CA_VERTICA sudouser_name Indicates the name of the sudo user you created previously. This command alias details the commands that the sudo user must be able to run on. Note: In a cluster installation, perform this step on each host in the cluster. 5. (Cluster installations only) Create an ssh key for the root user: a. Using ssh-keygen t rsa, copy the public key to each host in the cluster. b. Append the public key to the authorized_keys file of the root user. c. Type the following command to restart the sshd service: service sshd restart The sudo user account is configured. More information: Install Data Repository (see page 28) Generate a Response File for the Data Repository Installation (Optional) (see page 38) Data Repository Prerequisites (see page 9) 14 Installation Guide

15 Data Repository Prerequisites Set a Unique Hostname for Each Data Repository Host (Single-Node and Cluster Installations) Set a unique hostname for each computer where you are going to install Data Repository. Three unique hostnames are required in a cluster installation. Follow these steps: 1. As the root user, log in to each computer where you are going to install Data Repository and type the following command: vi /etc/sysconfig/network 2. Modify the hostname line to what you want it to be and press Escape. 3. Type the following command: :wq! The file is saved and closed. 4. Type the following command: service network restart 5. Verify that the following lines appear in the /etc/hosts file: Do not remove the following line, or various programs # that require network functionality will fail localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 IP address of your host YourHostName YourHostName.domain The /etc/hosts file is configured correctly. The unique host name is set. More information: Install Data Repository (see page 28) Data Repository Prerequisites (see page 9) Chapter 1: Prerequisites and Installation Considerations 15

16 Data Repository Prerequisites Disable the Firewall Settings on Each Data Repository Host (Single-Node and Cluster Installations) Disable the firewall settings on each computer where you are going to install Data Repository. Disable the firewall settings so that the computer where Data Repository is installed can communicate with the computers where Data Aggregator and Data Collector are installed. Follow these steps: 1. Type the following command: chkconfig --list grep iptables 2. If runlevels 3 and 5 are on, type the following command: chkconfig --level 35 iptables off The firewall settings are turned off. More information: Install Data Repository (see page 28) Data Repository Prerequisites (see page 9) Verify that the NTP Daemon is Running (Cluster Installations Only) The network time protocol (NTP) daemon must be running on all of the hosts in the cluster. This daemon helps ensure that the clocks on the hosts are synchronized for timing purposes. If the nodes do not have NTP running, the installation can fail. Follow these steps: 1. Open a console and type the following command: $ chkconfig --list ntpd If the NTP daemon is installed, the output resembles the following example: ntp 0:off 1:off 2:on 3:on 4:off 5:on 6:off The output indicates the runlevels where the daemon runs. 2. Verify that the current runlevel of the system (usually 3 or 5) has the NTP daemon set to 'on'. If you do not know the current runlevel, type the following commands to find it: $ runlevel N 3 16 Installation Guide

17 Data Repository Prerequisites If the current runlevel does not have the NTP daemon enabled, enable it by typing the command: $ chkconfig ntpd on 3. Type the following command to start the NTP daemon manually by typing the following command: $ /etc/init.d/ntpd start The daemon is started. More information: Data Repository Prerequisites (see page 9) Configure Hostname Resolution (Cluster Installations Only) The hostnames of all hosts participating in the cluster must resolve correctly. If the hostname resolution is incorrect, the Data Repository cluster does not install or work properly. All participating hosts in the cluster must use static IP or permanently leased DHCP addresses. Follow these steps: 1. Set up the /etc/hosts file on each of the three hosts you chose to participate in the cluster. The hosts file must contain entries for all three hosts in the cluster. For example, if the hosts in the cluster are named host01, host02, and host03, the /etc/hosts file on each host looks like the following example: localhost.localdomain localhost host host host03 Note: Do not remove the loopback address ( ) line. Also, do not use the loopback address or localhost name when you are defining hosts in the cluster. 2. Verify that hostname resolution works for each host in the cluster. For example, on host01, the following syntax is correct: $ /bin/hostname -f host01 3. Edit the /etc/sysconfig/network file to set HOSTNAME to the desired hostname. For example: HOSTNAME=host01 4. Ping the host from the computer and verify that the reply output contains the hostname specified in the previous step (host01). Chapter 1: Prerequisites and Installation Considerations 17

18 Data Aggregator Prerequisites For example, type the following command to ping host01: $ ping host01 PING host01 ( ) 56(84) bytes of data. 64 bytes from host01 ( ): icmp_seq=0 ttl=64 time=0.086 ms 5. Verify that the HOSTNAME environment variable is set correctly and matches the value established in /etc/sysconfig/network by issuing the following command: # echo $HOSTNAME host01 Hostname resolution is configured. More information: Data Repository Prerequisites (see page 9) Data Aggregator Prerequisites Meet the following prerequisites before installing Data Aggregator: 1. Open the necessary ports (see page 9). 2. Verify that Data Repository is set up and running. 3. Verify that the directory where you are going to install has write privileges for your Data Aggregator user. 4. Ensure that the user that is installing Data Aggregator has a ulimit value of at least (see page 19) 5. (Optional) Configure the sudo user account (see page 19). 6. Configure UTF-8 support (see page 20). 7. Review the installation considerations (see page 21). More Information: Install Data Aggregator with the Installation Wizard (see page 50) Install Data Aggregator from the Command Line (see page 57) Install Data Aggregator in Silent Mode (see page 65) 18 Installation Guide

19 Data Aggregator Prerequisites Set the Limit on the Number of Open Files on Data Aggregator Ensure that the user that is installing Data Aggregator has a value of at least on the number of open files. Set this value permanently. Follow these steps: 1. As the root user or a sudo user, log in to the computer where you are going to install Data Aggregator. Open a command prompt and type the following command to change the ulimit for the open files limit to at least 65536: ulimit -n ulimit_number For example: ulimit -n Open the /etc/security/limits.conf file on the computer where you are going to install Data Aggregator and add the following lines: # Added by Data Aggregator * soft nofile # Added by Data Aggregator * hard nofile Note: Restart Data Aggregator for these changes to take affect. If you are upgrading, the upgrade process automatically restarts Data Aggregator. 3. To verify that the number of open files is set properly on the computer where you are going to install Data Aggregator, type the following command: ulimit -n The command returns the ulimit number that you specified earlier. More information: Data Aggregator Prerequisites (see page 18) How to Upgrade Data Aggregator (see page 77) Configure the Sudo User Account for Data Aggregator Before you install Data Aggregator, log in as the root user. However, in some environments, unrestricted root user access is not available. If root user access is not available, a sudo user with access to a limited set of commands can install and run the software. Follow these steps: 1. Log in to the computer where you want to install Data Aggregator as the root user. 2. Copy the installation package to the /tmp folder. Chapter 1: Prerequisites and Installation Considerations 19

20 Data Aggregator Prerequisites 3. Verify that the root user owns the installda.bin file. 4. If the root user does not own the Data Aggregator executable, download the executable and change its owner to the root user by typing the following command: chown root /tmp/installda.bin Note: The root user must own the executable for the sudo user to run the installer. 5. Add the following command alias to the command alias section of the /etc/sudoers file: Cmnd_Alias CA_DATAAGG = /tmp/installda.bin, /etc/init.d/dadaemon, /opt/imdataaggregator/uninstall ## Allows the Data Aggregator user to manage the Data Aggregator dasudouser_name ALL = CA_DATAAGG This command alias details the commands that the sudo user must be able to run. The sudo user account is configured. More Information: Install Data Aggregator with the Installation Wizard (see page 50) Install Data Aggregator from the Command Line (see page 57) Data Aggregator Prerequisites (see page 18) Install Data Aggregator in Silent Mode (see page 65) Uninstall Data Aggregator with the Installation Wizard (see page 85) Uninstall Data Aggregator from the Command Line (see page 86) Uninstall Data Aggregator in Silent Mode (see page 88) Configure UTF-8 Support Configure the computer where you will install the component to support UTF-8 encoding. If UTF-8 encoding is not enabled, characters may not display properly during the installation. The appropriate language packs are also required to support localized deployments. 20 Installation Guide

21 Data Aggregator Prerequisites Follow these steps: 1. Do one of the following steps: a. Type the following command from a Korn shell: export LANG=LANG_value ; export LC_ALL=$LANG LANG_value Indicates the value of the language you want the product to support. The following variables are supported: English: en_us.utf8 French: fr_fr.utf8 Japanese: ja_jp.utf8 Simplified Chinese: zh_cn.utf8 Traditional Chinese: zh_tw.utf8 For example: export LANG=zh_TW.utf8 ; export LC_ALL=$LANG b. Type the following command from a Bourne shell: LANG=LANG_value ; export LANG LC_ALL=LANG_value ; export LC_ALL For example: LANG=zh_CN ; export LANG LC_ALL=zh_CN ; export LC_ALL The language variable is set. More information: Data Aggregator Prerequisites (see page 18) Data Aggregator Considerations Consider the following information before you install Data Aggregator: Data Aggregator can communicate with only one Data Repository at a time. In a multi-tenant deployment, Data Aggregator can be shared between tenants. The information for each tenant is secure and other tenants cannot view this information. Chapter 1: Prerequisites and Installation Considerations 21

22 Data Collector Prerequisites More information: Data Aggregator Prerequisites (see page 18) Data Collector Prerequisites Meet the following prerequisites before you install Data Collector: 1. Open the necessary ports (see page 9). 2. (Optional) Configure the sudo user account (see page 22). 3. Ensure that your desired tenant and corresponding IP domain are provisioned in CA Performance Center. While a single IP domain can be associated with more than one Data Collector, each Data Collector can have only one IP domain assigned to it. Note: If you are not deploying multi-tenancy, use the Default Tenant and the Default Domain. For more information about creating tenants and IP domains, see the CA Performance Center Administrator Guide. 4. Set a unique hostname for each host (see page 24). 5. Review the installation considerations (see page 25). More information: Install Data Collector with the Installation Wizard (see page 54) Install Data Collector from the Command Line (see page 61) Install Data Collector in Silent Mode (see page 66) Configure the Sudo User Account for Data Collector Before you install Data Collector, log in as the root user. However, in some environments, unrestricted root user access is not available. If you cannot log in as the root user, a sudo user with access to a limited set of commands can install and run the software. Follow these steps: 1. Log in to the computer where you want to install Data Collector as the root user. 2. Copy the installation package to the /tmp folder. 3. Verify that the root user owns the install.bin file. 22 Installation Guide

23 Data Collector Prerequisites 4. If the root user does not own the Data Collector executable, download the executable and change its owner to the root user by typing the following command: chown root /tmp/install.bin Note: The root user must own the executable for the sudo user to run the installer. 5. Add the following command alias to the command alias section of the /etc/sudoers file: Cmnd_Alias CA_DATACOLL = /tmp/install.bin, /etc/init.d/dcmd, /opt/imdatacollector/, /opt/imdatacollector/uninstall/uninstall ## Allows the Data Collector user to manage the Data Collector sudouser_name ALL = CA_DATACOLL This command alias details the commands that the sudo user must be able to run. The sudo user account is configured. More information: Install Data Collector with the Installation Wizard (see page 54) Install Data Collector from the Command Line (see page 61) Data Collector Prerequisites (see page 22) Install Data Collector in Silent Mode (see page 66) Uninstall Data Collector with the Installation Wizard (see page 86) Uninstall Data Collector from the Command Line (see page 87) Uninstall Data Collector in Silent Mode (see page 89) Configure UTF-8 Support Configure the computer where you will install the component to support UTF-8 encoding. If UTF-8 encoding is not enabled, characters may not display properly during the installation. The appropriate language packs are also required to support localized deployments. Chapter 1: Prerequisites and Installation Considerations 23

24 Data Collector Prerequisites Follow these steps: 1. Do one of the following steps: a. Type the following command from a Korn shell: export LANG=LANG_value ; export LC_ALL=$LANG LANG_value Indicates the value of the language you want the product to support. The following variables are supported: English: en_us.utf8 French: fr_fr.utf8 Japanese: ja_jp.utf8 Simplified Chinese: zh_cn.utf8 Traditional Chinese: zh_tw.utf8 For example: export LANG=zh_TW.utf8 ; export LC_ALL=$LANG b. Type the following command from a Bourne shell: LANG=LANG_value ; export LANG LC_ALL=LANG_value ; export LC_ALL For example: LANG=zh_CN ; export LANG LC_ALL=zh_CN ; export LC_ALL The language variable is set. More information: Data Aggregator Prerequisites (see page 18) Set a Unique Hostname for the Data Collector Host Set a unique hostname for the computer where you are going to install Data Collector. Follow these steps: 1. As the root user, log in to the computer where you are going to install Data Collector and type the following command: vi /etc/sysconfig/network 2. Modify the hostname line to what you want it to be and press Escape. 24 Installation Guide

25 Data Collector Prerequisites 3. Type the following command: :wq! The file is saved and closed. 4. Type the following command: service network restart 5. Verify that the following lines appear in the /etc/hosts file: Do not remove the following line, or various programs # that require network functionality will fail localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 IP address of your host YourHostName YourHostName.ca.com The /etc/hosts file is configured correctly. The unique host name is set. More information: Install Data Repository (see page 28) Data Collector Prerequisites (see page 22) Install Data Collector with the Installation Wizard (see page 54) Install Data Collector from the Command Line (see page 61) Install Data Collector in Silent Mode (see page 66) Data Collector Considerations Consider the following information before you install Data Collector: Install Data Collector on a separate computer from the server where Data Aggregator is installed. You can install more than one Data Collector. However, each Data Collector must be installed on a separate computer. Data Collector can support only one Data Aggregator. In a multi-tenant deployment, Data Collector is not shared among tenants. However, a tenant can have more than one Data Collector. In a multi-tenant environment where a managed service provider is monitoring devices for multiple tenants, you can take the following steps: Install Data Collector at the MSP site. Note: This setup requires Data Collector to gain access through a tenant firewall to poll the devices that are being managed. Install Data Collector at each tenant site. Chapter 1: Prerequisites and Installation Considerations 25

26 Data Collector Prerequisites If Data Aggregator is IPv6 only, Data Collector must support the IPv6 protocol. To verify that Data Collector supports IPv6, take the following steps: On the Data Aggregator host, type the following command to find the IPv6 address of the computer: > ifconfig On the Data Collector host, type the following command to ensure that Data Collector can contact Data Aggregator using its IPv6 address: > ping6 ipv6_address_of_data Aggregator More information: Data Collector Prerequisites (see page 22) 26 Installation Guide

27 Chapter 2: Installing CA Infrastructure Management This section contains the following topics: How to Install Data Repository, Data Aggregator, CA Performance Center, and Data Collector (see page 27) Install Data Repository (see page 28) Data Aggregator and Data Collector Installation (see page 50) Make Data Aggregator Aware of Data Repository Hosts in a Cluster Environment (Cluster Installations Only) (see page 69) Configure the Automatic Recovery of the Data Aggregator Process (Recommended) (see page 70) Modify Maximum Memory Usage for Data Aggregator and Data Collector Components After Installation (see page 72) Change the Opened Port Number on the Data Aggregator Host (see page 74) How to Install Data Repository, Data Aggregator, CA Performance Center, and Data Collector Install one Data Repository, one Data Aggregator, CA Performance Center, and at least one Data Collector. One Data Aggregator can communicate with one or more Data Collector. Important! Complete the prerequisites before you install Data Repository, Data Aggregator, CA Performance Center, and Data Collector. For information on CA Performance Center prerequisites, see the CA Performance Center Installation Guide. To install Data Repository, Data Aggregator, CA Performance Center, and Data Collector, we recommend the following installation order. All steps are required unless otherwise indicated. 1. (Optional) Generate a response file for the Data Repository installation (see page 38). 2. Install Data Repository (see page 28). 3. Configure log rotation for Data Repository (see page 40). 4. (Optional) Set up autostart on Data Repository (see page 41). 5. Set up automatic backups of Data Repository (see page 44). 6. Install Data Aggregator using the installation wizard (see page 50), command line interface (see page 57), or install Data Aggregator in silent mode (see page 65). Chapter 2: Installing CA Infrastructure Management 27

28 Install Data Repository 7. Install CA Performance Center. Note: For information on installing CA Performance Center, see the CA Performance Center Installation Guide. 8. Register Data Aggregator as a data source in CA Performance Center. Note: For information about adding Data Aggregator as a data source, see the CA Performance Center Administrator Guide. 9. Set up the automatic recovery of the Data Aggregator process (see page 70). 10. (Cluster installations only) Make Data Aggregator aware of the Data Repository hosts in a cluster environment (see page 69). 11. Install Data Collector using the installation wizard (see page 54), command line interface (see page 61), or install Data Collector in silent mode (see page 66). 12. Configure the maximum memory usage on Data Aggregator and Data Collector for large-scale deployments (see page 72). 13. (Optional) Change the opened port number on the Data Aggregator host (see page 74). Install Data Repository Install Data Repository before you install Data Aggregator. Note: Before you install Data Repository, review the system requirements in the Release Notes. Follow these steps: 1. Review the Data Repository installation prerequisites (see page 9). 2. Open a console and log in to the computer where you plan to install Data Repository by doing one of the following tasks: Type the following command to log in as the root user: su - root Type the following command to log in as a sudo user with a limited set of commands: su - sudouser Important! In a cluster installation, you can initiate the Data Repository installation from any of the three hosts that is participating in the cluster. The required software components are pushed to the additional two nodes during installation. 3. Copy the installdr.bin file locally. 28 Installation Guide

29 Install Data Repository 4. Change permissions for the installation file by typing the following command: chmod u+x installdr.bin 5. Do one of the following actions: Type the following command to extract the installation file:./installdr.bin Important! The installdr.bin file does not install Data Repository. This file extracts the Data Repository rpm and license file. You install Data Repository later in this procedure. Type the following command to use a generated response file:./installdr.bin -i silent -f installer.properties Important! If you are using a generated response file, skip the next two steps. Note: The directory that was chosen during the installdr.bin installation should be accessible by all users. chmod can be used to enable read/write for directories within the user home directories (for example, chmod -R 755 ). The License Agreement opens. If you extract the Data Repository installation file from a secure shell or console and you are not running an X Window System on the computer where you want to install Data Repository, the License Agreement opens in console mode (command line). Otherwise, the agreement opens within a user interface. 6. Read the license agreement, accept the agreement, and click Next if you are in the user interface. Press Enter if you are in console mode. 7. When prompted, enter an installation directory to extract the Data Repository installation package and Vertica license file to, or accept the default installation directory of /opt/ca/imdatarepository_vertica6/. Click Install and click Done if you are in the user interface. Press Enter, twice, if you are in console mode. The Data Repository installation package and license file are extracted to the chosen directory. 8. Type the following command to run the Data Repository installation package: rpm -ivh installation_directory/vertica x86_64.rhel5.rpm installation directory Indicates the installation directory where the Data Repository installation package resides. You extracted the license file and the Data Repository installation package to this installation directory. Chapter 2: Installing CA Infrastructure Management 29

30 Install Data Repository Examples: As the root user: rpm -ivh /opt/ca/imdatarepository_vertica6/vertica x86_64.rhel5.rpm As the sudo user: sudo rpm -ivh /opt/ca/imdatarepository_vertica6/vertica x86_64.rhel5.rpm 9. (Optional) Review the CA_Infrastructure_Management_Data_Repository_install_installation_date.log file on the computer where Data Repository is installed. This log file is located in the /opt/ca/imdatarepository_vertica6/uninstall/logs directory. If the installation is successful, the log shows a return code of 0 Warnings, 0 NonFatalErrors, and 0 FatalErrors in the Summary section. 10. Create a Linux user to serve as the account for the Linux database administrator user. In a cluster installation, perform this step on each host in the cluster. Do the following steps: a. Type the following command to create the Linux user account for the database administrator user and set the home directory for this user: path to useradd Linux_user_account_for_database_administrator -d home directory -d home directory Indicates the Linux user home directory for the database administrator user. Note: Use the entire path for the UNIX useradd command. Example: /usr/sbin/useradd dradmin -d /export/dradmin For a sudo user, prefix the command with the word "sudo". Note: Be sure that the export directory exists on the host. b. Type the following command to set the Linux user account password for the database administrator user: passwd Linux_user_account_for_database_administrator Example: passwd dradmin Note: For a sudo user, prefix the command with the word "sudo". c. When prompted, reenter the password. 30 Installation Guide

31 Install Data Repository d. Verify that you see the following output. This output indicates that the password you supplied is valid and accepted: passwd: all authentication tokens updated successfully. e. Modify the /etc/security/access.conf file by adding the following entry for the database administrator user: -:ALL EXCEPT dradmin root:local 11. To set the dradmin user shell to bash, type the following command: chsh -s /bin/bash dradmin_username For example: chsh -s /bin/bash dradmin The following table describes the user that you created: New User Example Password Example Operating System User Account? Vertica Database User Account? Notes Permissions dradmin drpass Yes No This user can run the Data Repository processes and the Administration Tools utility. This user owns Data Repository catalog files, data files, and so on. Note: The operating system user account is independent from the database user account. 12. To put the Vertica license in the /tmp directory, type the following command: cp installation_directory/vlicense.dat /tmp/vlicense.dat chown dradmin_username:dradmin_username /tmp/vlicense.dat chmod 664 /tmp/vlicense.dat Chapter 2: Installing CA Infrastructure Management 31

32 Install Data Repository dradmin_username Indicates the username of the vertica Linux database administrator user account you created previously. installation directory Indicates the installation directory where the Data Repository installation package resides. You extracted the license file and the Data Repository installation package to this installation directory. For example: cp license file directory/vlicense.dat /tmp/vlicense.dat chown dradmin:dradmin /tmp/vlicense.dat chmod 664 /tmp/vlicense.dat Note: When running the chown and chmod commands as a sudo user, prefix these commands with the word "sudo". 13. Create the data directory by doing the following steps: a. To view diskspace availability, type the following command. This step helps you decide where to put the directory you will create: df -lk Note: Perform this step on each node in a cluster environment. b. To create the data directory and change the owner for the data directory, type the following command: mkdir -p data_directory chown dradmin_username:dr_username data_directory dradmin_username Indicates the username of the vertica Linux database administrator user account you created previously. -p data directory Indicates the location of the data directory that meets the Data Repository storage requirements and specifications. Note: For more information about Data Repository system requirements, see the Data Aggregator Release Notes. Example: mkdir -p /data chown dradmin:dradmin /data For a sudo user, prefix both commands with the word "sudo". Note: In a cluster environment, this directory will be created on each node during the installation process. 32 Installation Guide

33 Install Data Repository 14. To invoke the Data Repository installer, type the following command: /opt/vertica/sbin/install_vertica -s hostname[,hostname,hostname] -u dr_username -l home_directory -d data_directory -L /tmp/vlicense.dat [-r installation_directory] -s hostname[,hostname,hostname] Indicates the name of the hosts where you want to install Data Repository. For a single-node installation, specify one hostname. For a cluster installation, specify a comma-separated list of three hostnames without whitespace before or after the commas. Each host in the cluster is set up for the installation. Note: Do not use 'localhost' in the case of a single-node installation. Specify the actual hostname of the computer. -u dradmin_ username Indicates the username of the vertica Linux database administrator user account you created previously. -l home directory -d data directory Indicates the Linux user home directory. Indicates the location of the data directory that meets the Data Repository storage requirements and specifications. Note: For more information about Data Repository system requirements, see the Data Aggregator Release Notes. [-r installation_directory] (Cluster installation only) Indicates the installation directory where the Data Repository installation package resides. You extracted the license file and the Data Repository installation package to this installation directory. Note: For a sudo user, prefix the command with the word "sudo". Examples: A single-node installation: /opt/vertica/sbin/install_vertica -s `hostname` -u dradmin -l /export/dradmin -d /data -L /tmp/vlicense.dat A cluster installation: /opt/vertica/sbin/install_vertica -s host01,host02,host03 -u dradmin -l /export/dradmin -d /data -L /tmp/vlicense.dat -r /opt/ca/imdatarepository_vertica6/vertica x86_64.rhel5.rpm Note: Do not add spaces before or after the commas in the hostname list or the installation script will fail. Chapter 2: Installing CA Infrastructure Management 33

34 Install Data Repository 15. If the installation script fails with the following error: ERROR: Passwordless SSH access to other sites... FAILED Do the following steps: a. To become the Linux user account for the database administrator user, type the following command: su - dradmin_username b. To generate a public key, type the following command. In a cluster installation, type this command on each host that is participating in the cluster: ssh-keygen -N "" -t rsa -f ~/.ssh/id_rsa c. Copy the contents of the public key to the authorized_keys2 file on the same computer. In a cluster installation, copy the contents of the public key to the authorized_keys2 file on each host that is participating in the cluster: cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys2 d. (Cluster installation only) Copy the contents of the public key from each host to each of the other hosts: As the database administrator user on the first host, type the following command and copy the content of the file: vi ~/.ssh/id_rsa.pub As the database administrator user on the second host, type the following command: vi ~/.ssh/authorized_keys2 Paste the contents from the id_rsa.pub file on the first host to the end of the authorized_keys2 file on the second host. As the database administrator user on the third host, type the following command: vi ~/.ssh/authorized_keys2 Paste the contents from the id_rsa.pub file on the first host to the end of the authorized_keys2 file on the third host. To enable you to ssh from one host to another without being prompted for a password, repeat these steps for all hosts in the cluster. e. To set permissions for the authorized_keys2 file, type the following command. In a cluster environment, type these commands on each host in the cluster: chmod 644 ~/.ssh/authorized_keys2 f. As the root user, type the following commands to restart the ssh daemon. In a cluster environment, type this command on each host in the cluster: su - root /etc/init.d/sshd restart 34 Installation Guide

35 Install Data Repository g. (Single-node installation only) To confirm that you are not prompted for a password, type the following commands: su - dradmin ssh dradmin@hostname ls /tmp h. (Cluster installation only) To confirm that you are not prompted for a password, type the following commands on the first host in the cluster: su - dradmin ssh dradmin@host1 ls /tmp ssh dradmin@host2 ls /tmp ssh dradmin@host3 ls /tmp Repeat this step on each host in the cluster. i. To reinvoke the Data Repository installer, type the following command: /opt/vertica/sbin/install_vertica -s hostname[,hostname,hostname] -u dr_username -l home_directory -d data_directory -L /tmp/vlicense.dat [-r installation_path] Note: When the dradmin user is created, a verticadba group is also created. The dradmin user is added to this group. 16. If prompted, specify the password for the Linux user account for the database administrator user. Data Repository is installed. 17. To become the Linux user account for the database administrator user, type the following command: su - dradmin 18. Type the following command from a Bash shell: /opt/vertica/bin/admintools Note: Bash is required, or you can see the following warning: The admin tools depend on your login shell being /bin/bash. Your login shell is currently set to /usr/bin/ksh. If you continue to run the admin tools with this default shell, you can experience technical difficulties Proceed (Y/N). The Administration Tools dialog opens. 19. When the Administration Tools dialog opens for the first time, a license agreement opens. Hit Enter through various screens until you are asked to accept the terms. If you accept the terms, type ACCEPT and press Enter. 20. Select (6) Configuration Menu and select OK. Select (1) Create Database and select OK. The Create Database dialog opens. 21. Enter a database name and select OK. 22. Enter the database password and select OK. When prompted, reenter it to confirm. Chapter 2: Installing CA Infrastructure Management 35