Upgrade Performance Center

After you upgrade the Data Repository component, upgrade the npc component.
capm360
After you upgrade the Data Repository component, upgrade the
Performance Center
component.
If you enabled FIPS-compliant encryption, and you upgrade
Performance Center
before the Data Aggregator, temporary FIPS compatibility synchronization errors occur. These errors occur until the Data Aggregator is upgraded. To avoid this temporary condition, upgrade the Data Aggregator before upgrading
Performance Center
.
Before you upgrade, verify the zip and unzip packages are installed. If these packages are not installed, use the following command to install them:
yum -y install zip unzip
To upgrade
Performance Center
, complete the following procedures:
MySQL Password Requirements (3.6.9 and Higher Only)
As a step toward enhanced security, the Performance Center installation prompts you to set a custom MySQL password.
The MySQL password must meet the following requirements:
  • Excludes the user names "root" or "netqos"
  • Minimum length of 8 characters
  • Maximum length of 30 characters
  • Contains at least 3 of the following types of characters:
    • Special Characters (!#&?)
    • Uppercase
    • Lowercase
    • Numbers (0-9)
  • Excludes the percentage sign (%), apostrophe ('), or quotation mark ("), asterisk (*), or the dollar sign ($)
Verify the ulimit Value
Verify that the user account that is installing CA
Performance Center
has a value of at least 65536 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
    Performance Center
    host.
  2. Open a command prompt and type the following command to verify the ulimit value:
    ulimit -n
  3. If the value is not at lease 65536, change the value:
    1. Type the following command:
      ulimit -n 65536
    2. Open the /etc/security/limits.conf file, and add the following lines:
      # Added by Performance Center
      * soft nofile 65536
      # Added by Performance Center
      * hard nofile 65536
Upgrade
Performance Center
The CA
Performance Center
installer includes features to support product upgrades. To perform an upgrade of the software, run the installation file for the new version that you received from CA.
To determine which version you have installed, access the .history file in the /opt/CA/PerformanceCenter/InstallLogs directory.
Follow these steps:
  1. Save the installation file to /tmp on the CA
    Performance Center
    server.
    Verify that your /tmp location has at least 2 GB of space available.
  2. Run the following command:
    cd /tmp
  3. Change the directory permissions:
    chmod +x CAPerfCenterSetup.bin
  4. Run the following command:
    ./CAPerfCenterSetup.bin -i console
    The installation begins in Console mode.
    To generate a response file for silent installation, add the following argument:
    -r
    response_file
    response_file
    specifies the directory the directory path and file name for the response file.
    Example:
    /temp/installer.properties
    Follow the prompts until you get to the summary, type "quit", and press Enter.
    To run the installation in silent mode, use the following command:
    ./installDA.bin -i silent -f
    response_file
    response_file
    is the directory path and file name of the previously generated response file.
  5. Follow the instructions in the console.
    The installation checks to see whether the partition with the MySQL data directory has enough disk space to handle storage engine upgrades. If there does not appear to be enough disk space to complete the installation successfully, exit the installer, allocate more space for the data partition, and reinstall
    Performance Center
    .
    (3.6.9 and Higher Only)
    As a step toward enhanced security, the Performance Center installation prompts you to set a custom MySQL password.
    When you upgrade from a release before
    CA Performance Management
    3.6 to release 3.6 or higher, the storage engine is migrated. The upgrade might take longer than expected up to an hour. Do not cancel the installation while it runs.
  6. (Optional) When prompted, specify the following parameters for fault tolerance. For more information, see Fault Tolerance.
    • Configure with Fault Tolerant Data Aggregator
      If fault tolerance was configured for the Data Aggregators, specify 2 for Yes.
      Default:
      1
    • Data Aggregator Proxy Host
      Specify the host name/IP address of the proxy server.
    The upgrade operation installs the software. The progress indicator may pause.
    When the upgrade is complete, the console displays a confirmation message.
Reapply Custom MySQL Settings
For upgrades from releases before
CA Performance Management
3.0, this upgrade includes updates to MySQL. These updates require replacing my.cnf. The upgrade backs up the existing my.cnf files as my.cnf.bak. If my.cnf.bak already exists, the backup adds a number to the end of the file name. To retain custom MySQL settings, reapply the settings in the my.cnf files.
Follow these steps:
  1. Locate my.cnf and my.cnf.bak in the following directories:
    • /etc/my.cnf
    • /opt/CA/MySql/my.cnf
      This path reflects the default.
  2. Copy the relevant setting values from my.cnf.bak to my.cnf.
  3. Restart MySQL:
    service mysql restart
Clear Browser Cache
Instruct
CA Performance Management
users to clear their browser cache before accessing the upgraded version.
(Optional) Review Log Files
Review the log files in the following directory to track any issues with the upgrade:
Installation Errors and Configuration Events
/opt/CA/PerformanceCenter/InstallLogs
Verify that the directory contains each log with the install date and time:
  • MySql_*
  • SSO_*
  • Device_Manager_*
  • Event_Manager_*
  • Console_*
  • Install_*
If any logs are missing, the installation is incomplete. Review each log for any fatal errors. Verify that the
.history
file is updated to the latest version.