Performance Management Upgrade Suggestions and Tips
Article ID: 201642
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
Current as of 21.2.8
Resolution
- The latest versions of DX NetOps Performance Management is 21.2.8, please note that the maintenance releases are roughly monthly and it is recommended to go to the latest maintenance release.
- Currently available downloads can be seen and downloaded from the Download Center:
- Announcements for the product updates are also made on the NetOps Communities:
- Please review the Fixed Issues list:
- To provide the greatest protection from catastrophic failure, proper backups are highly advised prior to upgrading or migration:
Backup instructions for all components:
NetOps Portal:
DA:
DR:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/dx-netops/21-2/Performance-Monitoring-with-DX-Performance-Management/administrating/data-repository-administration/back-up-the-data-repository.html
VNA:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-netops/21-2/Modern-Network-Monitoring-with-DX-Virtual-Network-Assurance/administrating/back-up-and-restore.html
- Follow the required package instructions.
Before starting an upgrade for any system component, run the "rpm -qa <packageName>" command for each required package. If it's installed, great, move on to the next one.
If ANY are found missing ensure they're installed.
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-netops/21-2/Performance-Monitoring-with-DX-Performance-Management/upgrading/upgrade-requirements-and-considerations.html#concept.dita_b2aa9703ab037cf3947eb0bb6f2777d530bdd53f_PackageRequirements
The libaio is an important required MySql package. Ensure it’s installed to avoid the following issue with MySql start failure post upgrade. Discussed further in the following KB article: https://knowledge.broadcom.com/external/article/142976
- Ensure all required Firewall ports and protocols are open:
- Ensure the dr_validate.sh (manually run etlHealth.sh as well if upgrading to 20.2.3 or earlier) script is run well before the upgrade. If the etlHealth check within it is unsuccessful, follow the instructions listed to look into the cause and remedy of the failure. If this fails, DO NOT UPGRADE until given the go-ahead from engineering.
See the section on dr_validate.sh
- Common issues hit during install on the various systems:
A bad space calculation that might halt the install.
https://knowledge.broadcom.com/external/article/121288
When /tmp is set with noexec or doesn't have enough space and we need to use a different location.
https://knowledge.broadcom.com/external/article/6223
Make sure the DISPLAY environmental variable is not set if using console mode:
https://knowledge.broadcom.com/external/article?articleId=198807
- If your mail server advertises STARTTLS you need to import the mail server certificate as noted here if updating/upgrading from a revision < 3.7.7 to a version higher than 3.7.7:
As mail will try to use a TLS connection if so.
Related KB:
https://knowledge.broadcom.com/external/article?articleId=187195
- Upgrading Data Collector gotcha’s
If a Data Collector install fails for some reason, it’s often easier and swifter to simply uninstall and reinstall it. When doing so it’s critical to re-use the DCM_ID the install is assigned so that the devices that DC manages are properly tied back to the ‘new’ reinstalled DC. In case that’s necessary the simple thing to do is gather a set of the DCM_ID values and setting them aside prior to the start of the upgrade.
How to list the unique Data Collector id DCM_ID in Performance Management
https://knowledge.broadcom.com/external/article?articleId=13251
How to move or replace a DC
https://knowledge.broadcom.com/external/article?articleId=48474
How to pass the DCM_ID when installing the Data Collector using sudo
https://knowledge.broadcom.com/external/article?articleId=138990
Data Collector UI launched upgrade when not using root user does not complete
https://knowledge.broadcom.com/external/article?articleId=136090
Data collector stays in upgrading status
https://knowledge.broadcom.com/external/article?articleId=132474
When upgrading from a version of DX Netops Performance Management 20.2.x before 20.2.6 to 20.2.6 or later, you must upgrade the Dcs as soon as possible to minimise data loss:
https://knowledge.broadcom.com/external/article/210214/data-missing-for-devices-after-upgrade-t.html
- Upgrading Data Repository gotcha’s
Ensure the dradmin or equivalent OS users password is valid. If it’s expired or locked out the dr_validate.sh script will fail when it prompts for that users password. Reference article for customers with further details/impacts re: dradmin user password changes.
https://knowledge.broadcom.com/external/article/37746
13. Upgrading VNA gotchas:
Make sure you know the current WildFly admin/WildFly JMS/MySQL root user password before upgrading
Do NOT shut down wildfly/mysql before upgrading.
14. When upgrading a Fault Tolerant Data Aggregator environment, you must upgrade the Data Aggregator proxy BEFORE either of the Fault Tolerant Data Aggregators as in the order outlined in the documentation:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/performance-management/21-2/upgrading/upgrade-the-data-aggregator/upgrade-fault-tolerant-data-aggregators.html
15. If you are upgrading to DX Netops Performance Management 20.2.9 or DX Netops Performance Management 20.2.10, if you have any SNMPv3 profiles with no authentication, this can cause SNMP profiles to fail to load, see:
https://knowledge.broadcom.com/external/article?articleId=219137
Feedback
