Upgrade NetOps Portal

Use the following process to upgrade
NetOps Portal
:
To host the
NetOps Portal
database on a separate node, see Migrate the
NetOps Portal
database to a separate node.
.
Verify the Prerequisites
Before upgrading
NetOps Portal
, ensure that you have completed the following:
Verify that the Packages are Installed
Ensure that the following packages are installed:
  • zip
    and
    unzip
    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
  • wget
    If this package is not installed, use one of the following commands to install it:
    yum -y install wget
    SLES:
    zypper install -y wget
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
<installation_directory>
/PerformanceCenter/InstallLogs/.history
file.
/opt/CA
is the default installation directory.
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
    • 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.
    • (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
    • To run the installation in silent mode, issue the following command:
      ./CAPerfCenterSetup.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
    • The installation prompts you to set a custom MySQL password. This 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 (")
  6. (Optional) When prompted, specify the following parameters for fault tolerance:
    For more information, see Fault Tolerance.
    • Configure Data Aggregator For Fault Tolerance
      Specify
      2
      for Yes to configure a fault-tolerant environment.
      Default:
      1 (configures a non-fault-tolerant environment).
    • Data Aggregator Proxy Host
      Specify the host name/IP address of the proxy server.
The upgrade operation installs the software. The progress indicator might pause.
When the upgrade is complete, the console displays a confirmation message.
Next Steps
Complete the following procedures after you have upgraded
NetOps Portal
.
Clear the 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
registered as a data source, restart the
Network Flow Analysis
OData service.
Follow these steps:
  1. Click
    Administration Services
    , and
    Services
    .
  2. Right-click the
    CA NFA OData Service
    , and then click
    Restart
    .
The
Network Flow Analysis
Service is restarted.
(Optional) Review the Log Files
A complete installation includes the following log files:
  • MySql_*
  • SSO_*
  • Device_Manager_*
  • Event_Manager_*
  • Console_*
  • Install_*
These log files are located in the
/opt/CA/PerformanceCenter/InstallLogs
directory. They include the install date and time. If a log file is missing, the upgrade is incomplete.
Use these log files to track possible issues with the upgrade. Review each file for any fatal errors. Verify that the
.history
file is updated to the latest version.