Upgrade NetOps Portal

After you upgrade the data repository, upgrade the
NetOps Portal
.
Complete these steps after you upgrade the data repository.
If you enabled FIPS-compliant encryption, to avoid temporary FIPS-compatibility synchronization errors, upgrade the data aggregator before upgrading
NetOps Portal
. Otherwise, if you upgrade
NetOps Portal
before the data aggregator as recommended, this temporary condition is resolved after upgrade the data aggregator.
For more information about how to upgrade the data aggregator, see Upgrade the Data Aggregator and Upgrade Fault-Tolerant Data Aggregators.
Use the following process to host the
NetOps Portal
database on a separate node:
In this topic:
Verify the Prerequisites
The upgrade requires the zip and unzip packages. If these packages are not installed, issue one of the following commands to install them:
yum -y install zip unzip
SLES:
zypper install -y zip unzip
NetOps Portal
requires the wget package. If this package is not installed, use one of the following commands to install it:
yum -y install wget
SLES:
zypper install -y wget
MySQL Password Requirements
(3.7.3 and Higher Only)
As a step toward enhanced security, the
NetOps Portal
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 (")
  • (3.7.3 through 3.7.4 Only)
    Excludes the asterisk (*), or the dollar sign ($)
Verify the ulimit Value
Verify that the user account that is installing
NetOps Portal
(the
ulimit
) 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
    NetOps Portal
    host.
  2. Open a command prompt, and then verify the ulimit value by issuing the following command:
    ulimit -n
  3. If the value is not at least 65536, change the value:
    1. Issue the following command:
      ulimit -n 65536
    2. Open the
      /etc/security/limits.conf
      file, and then add the following lines:
      # Added by Performance Center
      * soft nofile 65536
      # Added by Performance Center
      * hard nofile 65536
Upgrade
NetOps Portal
The
NetOps Portal
installer supports product upgrades. To upgrade
NetOps Portal
, run the installation file for the new version that you received from Broadcom.
To determine which version you have installed, access the
/opt/CA/PerformanceCenter/InstallLogs/.history
file.
Follow these steps:
  1. Save the installation file to the
    /tmp
    directory on the
    NetOps Portal
    server.
    Verify that the
    /tmp
    location has at least 2 GB of space available.
  2. Change directories by issuing the following command:
    cd /tmp
  3. Change the directory permissions by issuing the following command:
    chmod +x CAPerfCenterSetup.bin
  4. Begin the installation in console mode by issuing the following command:
    ./CAPerfCenterSetup.bin -i console
    1. 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:
      /tmp/installer.properties
      Follow the prompts until you get to the summary, enter
      quit
      , and then press the
      Enter
      key on your keyboard.
    2. (Optional) On upgrade, the disaster recovery script is backed up. If a backup file already exists, you can overwrite it with the current file. To overwrite the disaster recovery script backup, add the following to the response file:
      -fileOverwrite_/opt/CA/PerformanceCenter/product_version_capc.sh=Yes
    3. To run the installation in silent mode, issue 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.
    If the current install owner is the
    root
    user, you are prompted to specify an install owner. You can specify a non-root user.
    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
    NetOps Portal
    .
    (3.7.3 and Higher Only)
    As a step toward enhanced security, the
    NetOps Portal
    installation prompts you to set a custom MySQL password.
    When you upgrade from
    DX NetOps Performance Management
    3.5 or lower 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 earlier than
DX NetOps Performance Management
3.0, the upgrade includes updates to MySQL. These updates require that you replace the
my.cnf
file. The upgrade backs up the existing
my.cnf
file as
my.cnf.bak
. If the
my.cnf.bak
file 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
file.
Follow these steps:
  1. Locate the
    my.cnf
    file and the
    my.cnf.bak
    file in the following directories:
    • /etc/my.cnf
    • /opt/CA/MySql/my.cnf
      This path reflects the default.
  2. Copy the relevant setting values from the
    my.cnf.bak
    file to the
    my.cnf
    file.
  3. Restart MySQL by issuing the following command:
    service mysql restart
Clear Browser Cache
Instruct
DX NetOps Performance Management
users to clear their browser cache before accessing the upgraded version.
(Optional) Restart the
Network Flow Analysis
Service
If you have
Network Flow Analysis
as a data source, you must restart the
Network Flow Analysis
OData service:
  1. Click
    Administration Services
    , and
    Services
    .
  2. Right-click the CA NFA OData Service.
  3. Click
    Restart
    .
(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 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.