Upgrade NetOps Portal
After you upgrade the data repository, upgrade the
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 Portalbefore the data aggregator as recommended, this temporary condition is resolved after upgrade the data aggregator.
Use the following process to host the
NetOps Portaldatabase on a separate node:
- Upgrade to this release.
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
zypper install -y zip unzip
NetOps Portalrequires the wget package. If this package is not installed, use one of the following commands to install it:
yum -y install wget
zypper install -y wget
MySQL Password Requirements
(3.7.3 and Higher Only)
As a step toward enhanced security, the
NetOps Portalinstallation 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 (!#&?)
- 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
ulimit) has a value of at least 65536 on the number of open files. Set this value permanently.
Follow these steps:
- As the root user or a sudo user, log in toNetOps Portalhost.
- Open a command prompt, and then verify the ulimit value by issuing the following command:ulimit -n
- If the value is not at least 65536, change the value:
- Issue the following command:ulimit -n 65536
- Open the/etc/security/limits.conffile, and then add the following lines:# Added by Performance Center* soft nofile 65536# Added by Performance Center* hard nofile 65536
NetOps Portalinstaller 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
Follow these steps:
- Save the installation file to the/tmpdirectory on theNetOps Portalserver.Verify that the/tmplocation has at least 2 GB of space available.
- Change directories by issuing the following command:cd /tmp
- Change the directory permissions by issuing the following command:chmod +x CAPerfCenterSetup.bin
- 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:-rresponse_fileresponse_filespecifies the directory the directory path and file name for the response file.Example:/tmp/installer.propertiesFollow the prompts until you get to the summary, enterquit, and then press theEnterkey 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:./installDA.bin -i silent -fresponse_fileresponse_fileis the directory path and file name of the previously generated response file.
- Follow the instructions in the console.If the current install owner is therootuser, 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 reinstallNetOps Portal.(3.7.3 and Higher Only)As a step toward enhanced security, theNetOps Portalinstallation prompts you to set a custom MySQL password.When you upgrade fromDX NetOps Performance Management3.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.
- (Optional) When prompted, specify the following parameters for fault tolerance:For more information, see Fault Tolerance.
The upgrade operation installs the software. The progress indicator may pause.When the upgrade is complete, the console displays a confirmation message.
- Configure with Fault Tolerant Data AggregatorIf fault tolerance was configured for the Data Aggregators, specify2for Yes.Default:1
- Data Aggregator Proxy HostSpecify the host name/IP address of the proxy server.
Reapply Custom MySQL Settings
For upgrades from earlier than
DX NetOps Performance Management3.0, the upgrade includes updates to MySQL. These updates require that you replace the
my.cnffile. The upgrade backs up the existing
my.cnf.bak. If the
my.cnf.bakfile already exists, the backup adds a number to the end of the file name. To retain custom MySQL settings, reapply the settings in the
Follow these steps:
- Locate themy.cnffile and themy.cnf.bakfile in the following directories:
- /opt/CA/MySql/my.cnfThis path reflects the default.
- Copy the relevant setting values from themy.cnf.bakfile to themy.cnffile.
- Restart MySQL by issuing the following command:service mysql restart
Clear Browser Cache
DX NetOps Performance Managementusers to clear their browser cache before accessing the upgraded version.
(Optional) Restart the
DX NetOps Network Flow AnalysisService
If you have
DX NetOps Network Flow Analysisas a data source, you must restart the
DX NetOps Network Flow AnalysisOData service:
- ClickAdministration Services, andServices.
- Right-click the CA NFA OData Service.
(Optional) Review Log Files
Review the log files in the following directory to track any issues with the upgrade:
Installation Errors and Configuration Events
Verify that the directory contains each log with the install date and time:
If logs are missing, the installation is incomplete. Review each log for any fatal errors. Verify that the
.historyfile is updated to the latest version.