Spectrum Upgrade Suggestions and Tips
Article ID: 205954
Updated On:
Products
Issue/Introduction
We're planning on upgrading in the next few weeks and we're looking for any "gotchas" or tips regarding upgrading to or using the current versions
Environment
Version: 22.2.x or lower
Component: SPCCSS - SpectroSERVER Core
Resolution
1. The latest version of DX NetOps Spectrum is 22.2.9
2. Currently available downloads can be seen and downloaded from the Download Management:
https://support.broadcom.com/download-center/product-download.html?subfamily=SPECTRUM
3. Announcements for the product updates are also made on the NetOps Communities:
4. Please review the Fixed Issues and Known Issues:
5. To provide the greatest protection from catastrophic failure, proper backups are highly advised prior to upgrading or migration:
SSdb database:
DDMdb database:
reporting database:
CA Spectrum Database Maintenance Guidelines and Suggestions
6. Check the System Requirements for Windows and Linux:
7. Check the Integration Compatibility
8. Ensure all required Firewall ports are open:
9. For Linux installation, enter a username with root access. Or, you can use a sudoers file for root permissions.
You can use a sudoers file to provide users with limited root permissions for remote clients. Root permissions apply only to the commands required to install DX NetOps Spectrum. This option is available for Linux operating systems.
Grant Limited Root Permissions (Linux)
Sudo (super user do) is a third-party application. Using this application, a system administrator can let users run certain commands as root or as another user. DX NetOps Spectrum is compatible with the sudoers file (which the Sudo application uses). Specifically, you can use the sudoers files to grant users root permissions that are needed for running the DX NetOps Spectrum installation on remote systems. This file eliminates the need for the installation program to have full root permissions on all of the remote systems where DX NetOps Spectrum is installed.
Note:
DX NetOps Spectrum does not use the actual Sudo application to change user permissions. Instead, it parses the applicable information in the sudoers file to provide installation permissions to the specified user. For information about the Sudo application, see http://www.courtesan.com/sudo/.
Change the Sudoers File Owner (Linux)
By default, root owns the sudoers file. However, to limit the number of users who can access the sudoers file, you can change its owner. Then, modify the sradmin.exe startup parameters so that the sradmin.exe application honors only the configuration found in the sudoers file that the specified user owns. Sudoers files that other users own are ignored.
To change the sudoers file owner, add the --sudoowners parameter to the command line in the S99sradmin file that is used for starting sradmin.exe.
Follow these steps:
a) Open the following file:
On Linux: /etc/rc2.d/K09sradmin
b) Locate the following line:
$SRADHOME/sradmin.exe --start
c) Add the following parameter to this line:
--sudoowners=<username>
username
Specifies the user who owns the sudoers file. For example, you can enter:
$SRADHOME/sradmin.exe --start --sudoowners=bsmith
d) Save and close the file.
The sudoers file owner is changed.
For further information, please review the following sections of Spectrum guide:
10. You will need to manually make a copy of the $SPECROOT/Notifier directory and the $SPECROOT/lib/SDPM/partslist/ directory. If you have customized any out of the box files in the partslist directory you will need to copy them back in after the upgrade as they will be lost.
11. If you are upgrading CA Spectrum from a post 9.0 release, you do not need to install SRAdmin. SRAdmin is automatically upgraded.
12. Upgrading SpectroSERVER gotchas:
If you are performing the migration to new hardware, ensure the database filenames have been renamed. Make sure the SSdb file is unzipped before renaming it. Leave the DDMdb file zipped.
Upgrade Best Practices Fault-Tolerant Deployments
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/10-4-3/installing-and-upgrading/upgrading/upgrade-best-practices-fault-tolerant-deployments.html
Installation Methods
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/10-4-3/installing-and-upgrading/fresh-install/sradmin-installation-methods.html
Ensure you are using an updated version of the Host Installation Information (HII - hostargs) file if you are performing the upgrade, in case you updated the Main and Backup Location Hostname.
Ensure all the Spectrum processes were shut down gracefully before starting the installation/upgrading.
a) Stop the SpectroSERVER and Archive Manager either via Spectrum Control Panel (SCP) or $SPECROOT/bin/stopSS.pl script.
b) Close the Spectrum Control Panel (SCP) in case it is opened.
c) Ensure the Archive Manage is successfully shut down prior to stopping the Spectrum Process Daemon. Check either the $SPECROOT/SS/DDM/ARCHMGR.OUT file or if the ArchMgr process is gone.
d) Ensure all processes managed by Spectrum Process Daemon were successfully stopped. Ensure the $SPECROOT/lib/SDPM/runtime/ directory is empty. If not, you will have to manually end the process that is listed in each .rtt file.
Also, review the following KB articles:
The "distinst" command line install on Linux is failing with no errors
Why does the SRAdmin silent install fail for Linux when following the documentation?
DX Netops Spectrum 22.2.2+ MySQL 8 Upgrade Considerations
How to prepare for a DX NetOps Spectrum Upgrade by running the preUpgradeBackup Script
Checklists for DX NetOps Installations or Upgrades
Spectrum 21.2.8 OneClick Performance is slow after upgrade
Upgrade to Spectrum 21.2.8 fails with mySQL error "Access denied for user 'root'@'localhost'"
Rest api call giving error for creating a model using the mtypeid parameter in Spectrum (21.2.8)
How to save and ensure an Spectrum SNMPv3 Profile prior to migration (export function)
After upgrading Spectrum, custom entries in the Rtr.txt file are missing
SpectroServer memory usage keeps increasing since 21.2.6 upgrade
Upgrade to 21.2.6 has broken failover
Unable to install Spectrum 10.4.3 on Linux using Sudo and receive error Insufficient Privileges
SpectroSERVER crash post-upgrade to 20.2.7 in Qualys security scan
Dx Spectrum: SpectroSERVERs crashing after upgrade to 10.4.2.1 or 10.4.2.2
Spectrum installer ./setuplin.exe not found no such file or directory
Non-MLS SpectroSERVER's are crashing after an upgrade to 10.3.2 and 10.4.x
Spectrum's "processd --start" no longer automatically starts upon reboot with RHEL 7.9
Spectrum Alarm Notifier is not starting after an upgrade
unable to log into Bash - bash: fork: retry: resource temporarily unavailable
Failed to install CA Spectrum 10.4 on Windows 2016
"undefined symbol" messages seen in the VNM.OUT file after upgrading Spectrum
Spectrum Distributed Installation Does Not Contain Installation Information
How to install Spectrum on Linux with no root password or sudo
Spectrum install missing charsets in String to FontSet conversion
Why does the SRAdmin silent install fail for Linux when following the documentation?
DX Netops Spectrum 21.2 upgrade using silent method
"Detected incompatible model mask configuration" error after upgrade from Spectrum 10.4 to 10.4.2
Error message "SPC-INT-20049: Insufficient privileges..." trying to install Spectrum on Windows
After installing fresh DX Netops Spectrum 20.2 / 10.4.2 the SpectroSERVER will not start
Unable to upgrade on Linux to 10.4.1 on Linux "Cannot connect to sradmin"
Archive Manager's backup related KB articles:
How to completely rebuild the Spectrum Archive Manager (DDMDB) from scratch
Spectrum install fails on Linux running mysql.cus and ddm.cus scripts
Archive Manager does not start after upgrade to 21.2.8 onwards - SPC-OCP-10067
Unable to start the Archive Manager after upgrading to Spectrum 21.2.8
Failure in the mysqlbackup during the execution of post_olb_script does not generate event and alarm
ddm_save.pl does not zip the save file enough (poor/low compression on DDMdb backup file)
Spectrum ddm_save.pl fails with errors
Analyzing custom post_olb_script script failure in CA Spectrum
SpectroSERVER lost contact with the Archive Manager during the OnLineBackup - post_olb_script
13. Upgrading OneClick gotchas:
We recommend that you back up the reporting data on the installation server before you upgrade from an earlier version of OneClick with Spectrum Report Manager.
Also, review the following KB articles:
Emailing Alarms from OneClick not working after upgrade to Spectrum 22.2.7 & 22.2.8
22.2.8 upgrade WebApp is not working
Spectrum 22.2.7, 22.2.8, 22.2.9: Administration menu missing
Spectrum 10.4.2.2 Upgrade to 22.2 fails with Script Install-Tools/CUS/mibtools.cus has FAILED
Report Manager does not start after Upgrade to 22.2
How to drop and rebuild the Spectrum Report Manager database without performing a re-installation?
22.2.8 upgrade WebApp is not working
Spectrum 22.2.7: Install owner does not have admin rights when logging into One Click
Spectrum 22.2.7 JNLP Does not launch with "No suitable JVM was found to start the application"
Unable to launch Spectrum OneClick WebApp after installing 21.2.12
Alarms tab is empty after upgrade to 22.2.3
OneClick Upgrade Fails On fediz_config.xml - "keyStore" must not contain the '<' character
Migrate Report Data from a Previous Report Manager Installation
mysql upgrade fails during Spectrum upgrade
MySQL error while upgrading to CA Spectrum 10.3
Mysql.cus script fails when upgrading to 10.3.2 on ReHat Linux 7.7
Spectrum upgrade failure with error message "slmWebOp.cus has failed"
REST API is no longer working after upgrade to CA Spectrum release
Spectrum Tomcat does not start if the port is set to 443 in Linux
14. Upgrading Secure Domain Connector (SDC) gotchas:
- Before upgrading to 10.4.2, if -loglevel debug is enabled in sdm.config, you must remove it. Once SpectroSERVER and the corresponding Secure Domain Connector (SDC) are upgraded, you can add it back.
- For 10.4.2, ensure that SDC and Secure Domain Manager (SDM) have the same version.
- During an upgrade scenario, when SpectroSERVER is getting upgraded, stop the SDC services. Once SpectroSERVER is upgraded, you can then upgrade SDC to 10.4.2.
- While performing modeling gateway operations from 10.2.0 or 10.2.1 to 10.4.2, remove all entries of SNMPv3 profiles and import on 10.4.2. After upgrade, create SNMPv3 profiles manually
Also, review the following KB articles:
20.2 Secure Domain Connector backwards compatibility
How to identify the version of the Spectrum Secure Domain Connector (SDC)?
How to create a silent install for Secure Domain Connector in Spectrum 10.4.2.1
Spectrum Secure Domain Connector (SDC) silent install support for TrapX
Command Line installation of the Spectrum Secure Domain Connector on Linux
15. Troubleshooting Upgrade Installation Problems
Spectrum top troubleshooting tips, One Click, Login, Memory, Performance, Online Backup, SRM, NCM
16. Post Upgrade Tasks
a) If any models display Minor (yellow) alarms with a probable cause of DIFFERENT TYPE MODEL, clear the alarms. To convert all eligible models, run the NewMM.pl script from the $SPECROOT/Install-Tools/PostInstall directory. For more information see:
b) Re-deploy the reports to repair the existing report or to update to a newer version. After upgrading to a new version of DX NetOps Spectrum, click the Re-deploy button to sync up the Jasper reports with DX NetOps Spectrum upgrade fixes, enhancements, and new reports.
c) If you have configured OneClick to launch from Report Manager using SSL, configure this modification again. For more information see:
d) Archive Manager Database (DDM Database) Tables Conversion: With the previous release, it is recommended that you convert your Archive Manager database from MyISAM to InnoDB for better performance.
DX Spectrum : Archive Manager Table Conversion issue
17. Troubleshooting DX NetOps Performance Management integration
Integration between PC and Spectrum OneClick via HTTPS / SSL
18. Troubleshooting DX Infrastructure Manager / Unified Infrastructure Manager (UIM) integration
19. Troubleshooting DX NetOps Virtual Network Assurance (VNA) integration
20. Troubleshooting CABI JasperReports Server integration
Also, review the following KB articles:
How to test the connection of Spectrum data sources in JasperReports
DX Netops Spectrum reports in CABI fail with error after upgrading CABI to 7.9.x
CABI Jaspersoft 7.1.1 install/upgrade fail due to unsupported OS
JasperReports 7.1.1 SP1 installation failure while configuring postgres
JasperReports setup.sh identified CA Business Intelligence is already installed
Spectrum CABI JasperSoft AD-Hoc reports cannot be run
Additional Information
DX NetOps 21.2 Upgrade Requirements for All Components
https://support.broadcom.com/external/content/product-advisories/DX-NetOps-21.2-Upgrade-Requirements-for-All-Components/17590
In Spectrum 10.0, the event table of reporting database has been enhanced (InnoDB engine).
- To improve the Events reports performance, the ‘events’ table in the MySQL Reporting database has been partitioned.
- 52 partitions – each partition containing 1 week’s data – are maintained for a period of 1 year.
- An additional 6 partitions are created to cater to the 45-day window which is the default Archive Manager data retention period.
- All partitioning related administration is handled internally no additional administration is required.
In Spectrum 10.3, the event table of DDM database has been enhanced (InnoDB engine).
- Each partition of the event table contains one day of data
- The number of partitions will be equal to Archive Manager event retention period + 1 (future date)
- In case of fresh install you will see two partitions – one partition for installation date and another for future date
- Each day depending upon retention period Archive Manager
o Creates a new partition
o Deletes the oldest partition during the events purge
Spectrum releases and its corresponding NetOps version:
- Spectrum 10.4.0 = DX NetOps Spectrum 19.1
- Spectrum 10.4.1 = DX NetOps Spectrum 19.4
- Spectrum 10.4.2.0 = DX NetOps Spectrum 20.2.0
- Spectrum 10.4.2.1 = DX NetOps Spectrum 20.2.3
- Spectrum 10.4.2.2 = DX NetOps Spectrum 20.2.5
- Spectrum 10.4.3.0 = DX NetOps Spectrum 20.2.7
- Spectrum 10.4.3.1 = DX NetOps Spectrum 20.2.10
Feedback
