Upgrade Requirements and Considerations

Before you upgrade, review the following information to ensure that you have met all the requirements:
capm370
Before you upgrade, review the following information to ensure that you have met all the requirements:
For cloud environments, see Rehydrating Data in a Cloud Environment.
Verify System Requirements
To ensure that you successfully upgrade
CA Performance Management
, verify that your environment meets the system requirements. To verify the sizing requirements, use the
CA Performance Management
Sizing Tool
.
The following operating systems were verified:
  • SUSE Linux Enterprise Server (SLES) 12 SP2
  • Oracle Linux (OL) 7.3 (Red Hat compatible kernel only)
The following RHEL versions were verified:
A RHEL installation offers packages and add-ons.
CA Performance Management
supports a Minimal Install environment for RHEL.
  • RHEL 6.6 - 6.9
  • RHEL 6.10
  • RHEL 7.3 - 7.5
RHEL 6.8, 6.9, 7.3, or 7.4 are recommended.
The following RHEL versions are not supported:
  • RHEL 5.x
  • RHEL 6.5 and lower
  • RHEL 7.0 - 7.2
CA Performance Management
components that are installed on unsupported RHEL versions require an OS upgrade before upgrading the
CA Performance Management
components. You might also need to move the
CA Performance Management
components, including configurations, customizations, and data, from one system to another system. For more information, see Plan the Upgrade or Migration.
Package Requirements
The installer for each component requires the following packages:
Components
Packages
All (SLES)
  • dialog
  • mcelog
  • zip
  • unzip
All (RHEL 7.x, OL)
  • dialog
  • mcelog
  • zip
  • unzip
  • chrony
All (RHEL 6.x)
  • dialog
  • mcelog
  • zip
  • unzip
  • glibc
CA Performance Center
(SLES)
  • fontconfig
  • libaio1
  • libnuma1
  • wget
CA Performance Center
(RHEL 6.x)
  • fontconfig
  • libaio
  • libaio-devel
  • numactl
  • wget
CA Performance Center
(RHEL 7.x, OL)
  • fontconfig
  • libaio
  • libaio-devel
  • numactl-libs
  • wget
Data Repository (RHEL 6.x, RHEL 7.x, SLES, OL)
  • bc
  • pstack
  • gstack
For RHEL 7.x, the
pstack
and
gstack
packages are included in the
gdb
package.
Data Collectors (RHEL 6.x, RHEL 7.x, SLES, OL)
  • at
Direct Upgrade Paths
Since releases 3.7 and higher upgrade the Data Repository to Vertica release 9.1, we support Data Repository upgrades directly from the following releases to 3.7:
  • Release 3.6
For other
CA Performance Management
components, we support upgrades directly from the following releases to 3.7:
  • Release 3.1
  • Release 3.2
  • Release 3.5
  • Release 3.6
For more information, see Plan the Upgrade or Migration.
Sudo User Installations
For systems without root access, sudo user accounts are used to install and run the software. Add the sudo prefix to commands to upgrade the components. Verify that your sudo accounts contain the correct permissions for each component.
For more information, see the sudo user configuration details for each component:
Back Up
CA Performance Management
Before you begin the upgrade process, back up all aspects of the product:
Low-Scale Systems
For a low-scale system where the Data Collector shares a host with the Data Aggregator, complete the configuration to enable the components to run on the same host. For more information, see Install a Low-Scale System.
CA Business Intelligence
Integrations
If you have an existing
CA Business Intelligence
(CABI) integration, this version of
CA Performance Management
supports CABI 6.4.2 and higher.
After you upgrade to a supported CABI version, you must re-install your CABI content. For more information, see Install CA Business Intelligence Reports and Dashboards.
ActiveMQ Versions
To minimize data loss when you upgrade your Data Collectors, ActiveMQ continues to run unless you upgrade its version with the release.
This release supports ActiveMQ 5.15.8.
Apache Karaf Update
Release 2.7 introduced an update to Apache Karaf that changes the name of the Karaf directory. Karaf now uses the following directory:
installation_directory
/apache-karaf-2.4.3
NetOps Upgrade Considerations
The
CA Performance Management
user interface now supports supports the co-existence of retired and replacement devices coming from CA Network Flow Analysis. If your system is integrated with CA Network Flow Analysis, you must upgrade CA Virtual Network Assurance along with
CA Performance Management
to ensure that Items monitored by both the Data Aggregator and Virtual Network Assurance are properly reconciled when Lifecycle changes occur.
Review the Known Limitations
To ensure that your system runs successfully after the upgrade, review the limitations of
CA Performance Management
3.7. For more information, see Known Limitations.