Upgrading

Upgrade product to the current version.
casp1041
See, the
DX NetOps Spectrum
Patch General Information
page for detailed steps on
DX NetOps Spectrum
patch installation.
Get Started and Upgrade to 10.4.1!
Considerations
  • Before upgrading to 10.4.1, if
    -loglevel debug
    is enabled in sdm.config, you must remove it. And, once SpectroSERVER and corresponding Secure Domain Connector (SDC) are upgraded, you can add it back.
  • For 10.4.1, 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. And, once SpectroSERVER is upgraded, you can then upgrade SDC to 10.4.1.
  • While performing modeling gateway operations from 10.2.0 or 10.2.1 to 10.4.1, remove all entries of SNMPv3 profiles and import on 10.4.1. After upgrade, create SNMPv3 profiles manually.
Integration Compatibility Matrix
To know more about version compatibility of other integrated products with
DX NetOps Spectrum
10.4.1, see the Integration Compatibility chart.
Upgrade Path
10.4.1 is a full release. You can directly upgrade to 10.4.1 from 10.2.x, 10.3.x, and 10.4 releases (for example, 10.2, 10.2.1, 10.2.2, 10.2.3, 10.3, 10.3.1, 10.3.2, 10.4). You do not need to install any other releases or patches.
FAQs
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
DX NetOps Spectrum
OneClick Tomcat processes
again
to 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.
Features and Enhancements in Current Release
For more information about the new feature in the current release, see the Features and Enhancements page.
Platform Updates
For third-party software updates in this release, see the third-party software page.
Upgrade to 10.4.1
This section provides information about how you can upgrade to this release.
Prerequisites
Before you upgrade to the latest version of
CA Spectrum
, perform the following tasks:
  1. Review the best practices for upgrading in a fault-tolerant and non-fault tolerant environments. Also, preserve the customized support files.
  2. Stop all running applications other than
    CA Spectrum
    .
  3. Stop the following
    CA Spectrum
    applications:
    • Shut down all OneClick clients by logging off all users from OneClick on the Client Details web page in the OneClick home page.
      For more information about shutting down OneClick clients, see OneClick Administration.
    • Stop the SpectroSERVER and the Archive Manager by clicking Stop SpectroSERVER in the Spectrum Control Panel and then close the Spectrum Control Panel. Or you can stop the SpectroSERVER and Archive Manager from the command line by running the "<$SPECROOT>/bin/stopSS.pl" as
      CA 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.
  4. If you have installed
    CA 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.
  5. Do not install third-party software that uses MySQL because the results can be unpredictable.
Upgrade Procedure
Upgrading from a previous version of
CA Spectrum
to the latest one can be complex, because each release promises higher quality with the latest technologies and services. Ensure that you go through the upgrade options that best suit your requirements.
  1. You can perform either:
    • 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 the SpectroSERVER database and a new version of
      CA Spectrum
      after upgrading.
  2. Download the release.
    1. Sign in to the support portal.
    2. Click Enterprise Software.
    3. Click Product Downloads.
    4. Enter the product name in the search bar and click the search icon.
    5. Click the link that is displayed after the search is completed.
    6. Select the release to download.
Post Upgrade Tasks
  • Archive Manager Database (DDM Database) Tables Conversion: With the previous release, it is recommended that you convert your Archive Manager database tables from MyISAM to InnoDB for better performance. Refer to this section at the end of this page, for more information.
  • Migration Upgrade (Best Practice - Preserve Customized Support Files)
  • Upgrading Models to ensure compatibility between the SpectroSERVER database and a new version of
    DX NetOps Spectrum
    after upgrading.
Other Upgrade Tasks
  • If you have configured OneClick to launch from Report Manager using SSL, configure this modification again.  For more information about this modification, see
  • 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
    CA Spectrum
    \Install-Tools\PostInstall directory. For more information, see Troubleshooting the Post-Upgrade Installation Script.