Upgrade product to the current version.
If you are on Spectrum r9.2.x or older, you’ll need to upgrade to r9.3 or any of the versions listed below before upgrading to r10.2. For more information about upgrading from 9.2.x, to 9.3 or 9.4, see the 9.3 or 9.4.x documentation.
Integration Compatibility Matrix
To know more about version compatibility of other integrated products with Spectrum 10.3, see the compatibility matrix chart.
Q: In a distributed SS (DSS) environment, what is the supported and best practice for upgrading servers?
A:Upgrade the Primary MLS (main location server) SpectroSERVER first, followed by the Primary OneClick server, followed by the remaining Primary SpectroSERVERs. It is important that you start the primary MLS first, before starting the other primary SpectroSERVERs. This allows all of the cross landscape and "MOM" (manager of managers) functions to process and complete. Once the primary MLS is running and active, you can start the rest of the primaries. Upgrade the Secondary SpectroSERVERs last (including all SpectroSERVER and non primary OneClick servers). Once all SpectroSERVERs have been upgraded, be sure to stop and restart all CA Spectrum OneClick tomcat processes
againto update the tomcat cache with the updated SS info. Not doing this will cause OneClick issues, such as landscapes not showing in the client.
In a DSS setup, if you stop a primary SS to test your failover scenario without performing a successful database synchronization (via online backup) first, you may see the landscapes disappear in OneClick. To make sure this does not happen, manually start the online backup and allow the database synchronization to occur. Once complete, you can then test your failover scenario.
Upgrading from Earlier Versions
This Service Pack release supports direct upgrades only from CA Spectrum r10.2 and 10.2.1. If you are on any of the following versions (listed below) you need to upgrade to CA Spectrum r10.2, before you can upgrade to CA Spectrum r10.2.3
- 9.3 H01
- 9.3 H02
If you are on Spectrum r9.2.x, come to r9.3 or any of the above mentioned versions to directly upgrade to 10.2 first and then to 10.2.3. For more information about upgrading from 9.2.x, to 9.3 or 9.4 see the 9.3 or 9.4 documentation.
After upgrading to CA Spectrum 10.2.3, you must install CABI 4.1 SP3 for generating reports. CA Spectrum 10.0 is not compatible with earlier versions of CABI. CABI 4.1 SP3 is a fresh installation and it does not support upgrades from CABI 4.1 SP3.x. For more information, see Upgrade CABI section.
CA Spectrum 10.2.3 supports JasperReports Server for generating reports. For more information, see Install CABI JasperReports ServerInstall CABI JasperReports Server and CABI JasperReports Server Integration with CA Spectrum.
To see the CABI (BOXI), CABI (JasperReports Server) compatibility with CA Spectrum 10.2 and earlier versions of CA Spectrum, refer Integration Compatibility.
Upgrade to 10.2 from 9.4, 10.0 and 10.1.x to
To initiate loading your Spectrum r9.2 Ssdb to r10.2, refer to the Loading CA Spectrum r9.2 SSdb models to r10.2 section. All events and catalog customizations (watches, model type default changes, changes done in MTE) information will be lost. If you want to retain the custom configuration and data, upgrade to 9.4 first, and then proceed to install 10.2.
Before you upgrade to the latest version of CA Spectrum, ensure you:
- Are familiar with the best practices that are mentioned above.
- Stop all running applications other than CA Spectrum.
- Stop the following CA Spectrum applications:
- Shut down all OneClick clients by logging off all users from OneClick in the Client Details web page in the OneClick home page.
- Stop the SpectroSERVER and the Archive Manager by clicking Stop SpectroSERVER in the CA Spectrum Control Panel and then close the CA Spectrum Control Panel. Or you can stop the SpectroSERVER and Archive Manager from command line by running the "<$SPECROOT>/bin/stopSS.pl" as Spectrum Owner at the command prompt.
- Stop all VnmSh connections. For more information about stopping VnmSh connections, see command-line interface.
- Close all Bash shells.
- Ensure the 'Java' folder is not opened (under <$SPECROOT>) during the upgrade.
- If you have installed Spectrum Report Manager, verify that free disk space on the system is at least twice the size of the largest MYD file under$SPECROOT/mysql/data/reporting.
- Do not install third-party software that uses MySQL because the results can be unpredictable.
Upgrade Procedure from 9.4, 10.0 and 10.1.x
Upgrading from a previous version of Spectrum to the latest one, can be complex, because each release promises higher quality and latest technologies and services. Ensure that you go through the upgrade options that best suit your requirement.
- You can performeither:
- In Place Upgrade (With no fault-tolerant SpectroSERVERs configured in your deployment, a temporary fault-tolerant system is used during the upgrade. Once the temporary system is configured, the primary SpectroSERVER is disabled for an in-place upgrade. Meanwhile, the temporary, secondary SpectroSERVER system takes over core network management duties)
- Upgrade Models to ensure compatibility between SpectroSERVER database and a new version of CA Spectrum after upgrading
- Download CA Spectrum 10.2
- Go to the support.ca.com site and from the Menu bar, select Download Management.
- To select Spectrum as your product, type CA Spectrum – Core / SPECTROServer in the search bar.
- Now select, Spectrum Product> Release > Version for download. For example:
- You must download and install the ”Akamai Net Session Interface” before obtaining the product zip file. To download the zip file, change the settings from FTP to Enhanced Download Manager. This option is found on the top right corner of the page under Change Download Preference.
- For Windows, open the unzipped file setupnt.exe, downloaded the Spectrum file.
- Refer to the post-installation configurations
Post Upgrade tasks
- Migration Upgrade– (Best Practice - Preserve Customized Support Files)
- Upgrading Modelsto ensure compatibility between SpectroSERVER database and a new version of CA Spectrum after upgrading.
- 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 Spectrum\Install-Tools\PostInstall directory. For more information, see Troubleshooting the Post-Upgrade Installation Script.