Review Installation Requirements and Considerations

Review the following information before you install the product:
capm320
Review the following information before you install the product:
Operating System Requirements
This release introduces support for Red Hat Enterprise Linux (RHEL) 7.3 and deprecates support for Red Hat Enterprise Linux (RHEL) 5.x.
The following RHEL versions are supported:
Release
Kernel
RHEL 7.3
3.10.0-514
RHEL 6.9
2.6.32-696
RHEL 6.8
2.6.32-642
RHEL 6.7
2.6.32-573
RHEL 6.6
2.6.32-504
RHEL 6.8, 6.9, or 7.3 are recommended for all
CA Performance Management
components.
The following RHEL versions are not supported:
  • RHEL 5.x
  • RHEL 6.5 and lower
  • RHEL 7.0 - 7.2
Kernel versions before 2.6.32.504 are unsupported.
Root or Sudo User Access
Administrative privileges are required to install the software. Typically, the root users installs the software. In some environments, unrestricted root user access is not available.
If root user access is not available, configure a sudo user with access to a limited set of commands.
If you install the components with a sudo user account, add the 'sudo' prefix to commands that require the same user as the service owner, such as restart commands and SSL set up.
User Interface Access Requirements
Supported Browsers
The following browsers are supported:
  • Microsoft Internet Explorer version 10, 11
  • Google Chrome 48.x and later
  • Mozilla Firefox 42.x and later
Other Requirements
Virtual and SAN Environment Requirements
Review the the following document on CA Support Online:
The document discusses CA policies for installing and operating Infrastructure Management products on virtualized servers or Storage Array Networks (SAN). You must be logged in as a registered user to view documentation on CA Support Online.
Package Requirements
The installer for each component requires the following packages:
Components
Packages
All (RHEL 7.x)
  • dialog
  • mcelog
  • zip
  • unzip
  • chrony
All (RHEL 6.x)
  • dialog
  • mcelog
  • GLIBC++
Performance Center
(RHEL 6.x and RHEL 7.x)
  • libaio
  • libaio-devel
Data Repository (RHEL 6.x and RHEL 7.x)
  • bc
Common Considerations
  • Install each component on a separate system.
  • Verify that all your servers meet the minimum requirements and sizing guidelines.
    To provide high availability for your data, future scalability, and best end-user experience, deploy your Data Repository as a cluster.
    For information about the sizing requirements, see the capm Sizing Tool.
    If the sizing tool recommends a low-scale deployment, see Install a Low-Scale System.
  • Time synchronization using NTP is required. Start the NTP daemon on Linux if it is not running.
Except for anti-virus, system management, and time-synchronization software, do not install third-party software, especially third-party network monitoring software, on the same server as
CA Performance Management
components. Third-party software can interfere with the monitoring abilities of the CA system, and could void the warranty.
If you install third-party software on a CA system, CA Support might ask you to uninstall this software before troubleshooting an issue on the server.
Multi-tenant Deployment Considerations
In a multi-tenant deployment, note the following information:
  • The Data Aggregator is shared between tenants. The information for each tenant is secure and other tenants cannot view this information.
  • In a standard tenant deployment, each tenant has a dedicated Data Collector. A tenant can have more than one Data Collector. For multiple tenants that reside in the same IP routing space,
    CA Performance Management
     can be configured to use fewer Data Collectors. For more information, see Tenant-Agnostic Data Collectors.
  • Where a managed service provider is monitoring devices for multiple tenants, you can install Data Collector at the MSP site.
    This setup requires the Data Collector to gain access through a tenant firewall to poll the devices that are being managed.
Firewall and Connectivity Considerations
For 
CA Performance Management
 to work properly in a firewall-protected environment, certain ports must be open.
Open the following ports to allow
CA Performance Management
 communications to function properly. For more information, see Prepare to Install Performance Center.
Throughout the documentation 8182, 8382, and 61617 appear as suggested port numbers for secured communications. In the instances where these appear, you are free to use any value you want as long as no other processes are using it.
For more information about individual data sources, see the appropriate product documentation.
From
To
Port [Function]
Performance Center
services
Performance Center
  • TCP 3306
    Enables communications to the MySQL database (inbound) from the
    Performance Center
    services.
  • TCP/HTTP 8481
    Enables communications between the Device Manager and Console services.
User client computers
Performance Center
If you put the application behind a firewall, and you want customers to access only the user interface, open the following ports to the world:
  • TCP/HTTP 8181
    Enables communications between client computers and the
    Performance Center
    server.
  • TCP/HTTP 8381
    Enables communications between client computers and the
    Performance Center
    server. Also enables login using the single sign-on authentication component.
For secured communications, use the following ports instead of 8181 and 8381:
User client computers
Data Aggregator
  • TCP/HTTP 8581
    Allows for OpenAPI access.
    Note:
    Opening this port exposes the rest of the Data Aggregator services.
Data Aggregator
Performance Center
  • TCP/HTTP 8281
    Enables communications between the Event Manager, which is installed automatically with the
    Performance Center
    software, and the Data Aggregator. The Data Aggregator initiates communication and pushes data through this port.
  • TCP/HTTP 8381
    Enables communication between the Data Aggregator and
    Performance Center
    for direct authentication of OpenAPI queries.
  • TCP/HTTP 8581
    Enables synchronization with
    CA Performance Management
    for the Data Aggregator,
    Performance Center
    initiates communication and pulls data through this port.
For secured communications, use the following port instead of 8381:
Performance Center
CA Network Flow Analysis
  • TCP/HTTP 80 
    Enables synchronization with
    CA Network Flow Analysis
    to retrieve configuration data.
  • TCP/HTTP 8681
    Enables synchronization with
    CA Network Flow Analysis
    to retrieve device data.
Performance Center
CA Application Delivery Analysis
  • TCP/HTTP 80 
    Enables synchronization with
    CA Application Delivery Analysis
    to retrieve configuration data.
  • TCP/HTTP 8681
    Enables synchronization with
    CA Application Delivery Analysis
    to retrieve device data.
Performance Center
CA Business Intelligence
  • TCP/HTTP 8181
    Enables communications between
    CA Business Intelligence
    and the
    Performance Center
    server.
For secured communications, use the following port instead of 8181:
Data Collector
Data Aggregator
  • TCP/AMQ 61616
    Enables only ActiveMQ traffic between the Data Collector and Data Aggregator.
  • TCP/AMQ 61618
    Enables poll response delivery traffic between the Data Collector and Data Aggregator.
  • TCP/AMQ 61620
    Enables distributed IREP traffic between the Data Collector and Data Aggregator.
  • TCP/AMQ 61622
    Enables large data transfers between the Data Collector and Data Aggregator.
For secured communications, use the following ports instead of 61616, 61618, 61620, 61622:
Note:
The following ports are the default ports for Secure ActiveMQ communication if configured using the AMQ SSL documentation. For more information, see Authenticate and Encrypt ActiveMQ Communication.
  • TCP/AMQ SSL 61617
    Enables only ActiveMQ secured communications between the Data Collector and Data Aggregator.
  • TCP/AMQ SSL 61619
    Enables poll response delivery secured communications between the Data Collector and Data Aggregator.
  • TCP/AMQ SSL 61621
    Enables distributed IREP secured communications between the Data Collector and Data Aggregator.
  • TCP/AMQ SSL 61623
    Enables secured large data transfers between the Data Collector and Data Aggregator.
Data Collectors
Devices
  • UDP 161
    Enables SNMP connections to devices.
Data Aggregator
Data Repository
  • TCP/UDP 5433
    Enables communication between the Data Aggregator and the Data Repository for Java Database Connectivity.
Data Repository
Data Repository
  • TCP/SSH 22
    Enables Vertica administration tools and backup to run between nodes.
  • TCP/UDP 4803
    Enables spread communication between nodes.
  • TCP/UDP 5433
    Enables communication between the Data Aggregator and the Data Repository for Java Database Connectivity.
Open the following ports for the Vertica database:
  • UDP 4804
  • TCP 5434
  • UDP 6543
CA Spectrum
Performance Center
  • TCP 8281
    For event integration, enables the
    CA Spectrum
    OneClick server to communicate to the
    Performance Center
    host.
  • TCP 8481
    Enables the 
    CA Spectrum
    OneClick server to communicate to the Device Manager.
Performance Center
LDAP
  • TCP 389
    Enables Clear Text communication from the client to the LDAP server.
  • TCP 3268
    If you are using the global catalog for searches, enables communication from the client to the LDAP server.
Performance Center
LDAPS
  • TCP 636
    Enables encrypted and secure communication from the client to the Secure LDAP server.
  • TCP 3269
    If you are using the global catalog for searches, enables communication from the client to the Secure LDAP server.