NFA Upgrade Tips
Article ID: 213747
Updated On:
Products
Issue/Introduction
We're planning on upgrading DX NetOps Performance Management in the next few weeks and were looking for any "gotcha's" or tips regarding upgrading to or using the current versions.
Environment
NFA : Current as of 22.2.6
Resolution
1. The latest version of NFA is 22.2.6.
See the following HIGHLY IMPORTANT note about upgrading to 22.2.6:
NFA 22.2.6 Upgrade Path Requirement (broadcom.com)
The ONLY supported upgrade path from NFA 9.x and up is to FIRST upgrade to NFA 22.2.5. Once you are on 22.2.5, you can upgrade to 22.2.6.
- Upgrade to 22.2.5.
- Check if the "backup" database exists on the NFA Console reporter database. From an open command prompt, issue the following commands as administrator:
mysql -uroot -p<mysql root password>
show databases;
exit
- If the "backup" database is not listed on the console, issue the following commands as administrator:
mysql -uroot -p<mysql root password>
create database backup;
exit
- Run the Pre-Upgrade commands for each Harvester: NFA 22.2.6 Pre-Upgrade Script
- At this point you can safely upgrade to NFA 22.2.6. If there are any issue, please contact Broadcom Support.
2. Currently available downloads can be seen and downloaded from the Download Center:
3. Announcements for the product updates are also made on the NetOps Communities:
4. Please review the fixed issues list:
5. To provide the greatest protection from catastrophic failure, proper backups are highly advised prior to upgrading or migration:
Backup Instructions for NFA Components:
Backing Up and Restoring Data (broadcom.com)
6. How do I migrate the NFA Console or Harvester to a new server?
https://knowledge.broadcom.com/external/article?articleId=137926
7. Check the x:/CA/NFA/ folder on each NFA server to ensure that there are no "console_movie.xml or collector_movie.xml" files. If so, rename them from *.xml to *.backup and move the file to the /migrator folder. This will prevent upgrade issues.
8. Check whether there are any scripts, utilities, or Scheduled Tasks in place to monitor and automatically restart any of the NFA or MySQL services. If so, please disable these scripts for the duration of the upgrades. The upgrade procedure involves stopping and restarting services multiple times, and any scripts that interfere with this will cause problems with the upgrade.
9. When upgrading ensure to run the .exe file by right clicking and selecting "Run As Administrator" as this can prevent File Permissions errors during the mysql version upgrade.
10. Do *NOT* Delete the existing Data Source in CAPC as part of the NFA upgrade procedure. This is very likely to cause "Bind" issues when attempting to re-bind NFA to CAPC after the upgrade is complete!
11. All the servers in PM must be upgraded, like DC, DA DR and CAPC. Any data sources are considered separate upgrades.
12. Make sure to complete all Harvester upgrades before starting the NFA Console upgrade. Otherwise, the Pump service on the NFA Console may fail to start if it attempts to pump files generated on Harvesters running older versions of NFA.
13. NFA 22.2.3+ Requires .NET Framework 4.8.
This component must be manually installed, the PreCheck Script and the Install utility won't install it for you.
Please download the Microsoft offline installer for .NET Framework 4.8.0:
https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net48-offline-installer
This only needs to be installed on the NFA Console Server.
See the following KB:
NFA 22.2.3+ Requires .NET Framework 4.8 (broadcom.com)
Considerations for Linux Harvesters
Some special considerations for Linux Harvesters:
1) The init script (or systemd unit) must be on the root (/) file system.
RHEL 7.3 Service Scripts not executing on reboot (broadcom.com)
2) The /$installdir/CA/NFA/DBUsers/ReporterAnalyzer.ini is in Windows format. Needs to be fixed with the "dos2unix" utility:
Linux NFA Reaper Service won't stay running (broadcom.com)
Post Upgrade Tips
Verify the Revision History version in the Database
After the upgrade is complete, we can run the following mysql commands to doublecheck that the NFA version shows correctly in the database.
NFA Console:
mysql reporter -unetqos -pnetqos -t -e "select * from revision_history;"
Harvesters:
mysql harvester -unetqos -pnetqos -t -e "select * from revision_history;"
The output of the last line of the above commands should match the new version that we upgraded to.
HTTPS
If you previously had HTTPS configured for access to the NFA Web Page, you may to update your configuration as per the link below:
To make HTTPS configuration easier, the "APPLYHTTPS" script can be used to automatically configure HTTPS for you in various scenarios:
NFA: ApplyHTTPS Tool (broadcom.com)
System Status Issues
If "System Status" messages appear in CAPC after the upgrade, make sure that port 8981 is open betweern CAPC and the NFA Console, and that the "CA NFA Odata" service is running on NFA.
Please see the following KB articles:
Errors in System Status page in NetOps portal for NFA datasources
NetOps CAPM Shows Blank NFA Admin Views
Mandatory Patches
-Please note that NFA 21.2.10 has a patch that is considered mandatory. Please review this here:
NFA 21.2.10 Drive filling after upgrade Patch
-Please also install the appropriate Harvester Buffer patch for the version of NFA installed for NFA versions under 22.2.5:
NFA Harvester Buffer Patch (broadcom.com)
Additional Information
Older "Communities" post documenting Upgrade Path procedure as of NFA 9.5:
Performance Management Upgrade Suggestions and Tips:
Performance Management Upgrade Suggestions and Tips (broadcom.com)
Feedback
