Upgrade Best Practices DSS Deployments without Fault Tolerance

This section contains the following topics:
casp941
This section contains the following topics:
Upgrade Best Practices DSS Deployments without Fault Tolerance
The topic titled Upgrade Fault-Tolerant SpectroSERVERs and OneClick Web Servers provides the steps to upgrade 
 in a fault-tolerant environment. With no fault-tolerant 
SpectroSERVER
s 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.
Some 
 applications do not support automatic failover and are disabled during the upgrade. For example, TL1, Southbound Gateway, Modeling Gateway, Alarm Notifier, and Event Notifier are temporarily disabled during the upgrade.
Upgrading 
SpectroSERVER
s and OneClick Web Servers in a Non-Fault Tolerant Deployment
When you upgrade a 
 DSS environment that lacks a fault-tolerant configuration, deploy a temporary server to preserve network monitoring activities. This server is systematically configured as the Secondary, fault-tolerant server for each 
SpectroSERVER
 that is upgraded. Start the upgrade with the MLS, the main 
SpectroSERVER
.
The procedure to perform an in-place upgrade with no network management loss is described below.
Follow these steps:
  1. Designate a server to serve as the temporary Secondary 
    SpectroSERVER
    .
  2. Install a copy of your currently installed (that is, backlevel) 
     software on the temporary 
    SpectroSERVER
    . Be sure to install all required patches.
    Do not start the
    SpectroSERVER
    yet.
  3. Edit the Host Security configuration on the temporary 
    SpectroSERVER
    . The list of hostnames must be identical to that of the MLS in your current deployment.
  4. Perform an online backup of the 
    SpectroSERVER
     database on the MLS.
    Be sure to disable file compression and automatic backup features until the entire upgrade process has completed.
  5. Copy the backup database to the 
    $SPECROOT
    /SS directory on the temporary 
    SpectroSERVER
    .
  6. On the temporary 
    SpectroSERVER
     host, navigate to the SS directory.
  7. Load the database backup file by issuing the following command:
    ../SS-Tools/SSdbload -il -add precedence savefile
    • precedence
      A numeric value that is greater than the Primary 
      SpectroSERVER
       (the MLS) default value.
      Default
      : 10 (20 is recommended).
    • savefile
      The name of the database backup file that you created previously.
  8. Edit the .vnmrc file to increase the 'maximum event records' parameter on the temporary 
    SpectroSERVER
    . For example, change the following parameter:
    max_event_records=20000
    to the following value:
    max_event_records=200000
    The new value ensures that no events are lost during the upgrade.
  9. Disable the Archive Manager on the Secondary 
    SpectroSERVER
     from starting automatically to avoid losing event and statistical data. 
    Taking this step ensures that all data is cached and returned to the Primary 
    SpectroSERVER
     once the upgrade has completed and the Primary 
    SpectroSERVER
     has been restarted.
    1. On the temporary Secondary 
      SpectroSERVER
      , launch a Spectrum Control Panel.
    2. Click Control, and clear the box next to “Auto Start/Stop Archive Manager.”
    As a best practice, ensure that no events are lost during the upgrade. You can increase the maximum locally stored event record size. The default maximum locally stored log sizes for events and statistics are 20,000 and 5,000. In most cases, these default settings are sufficient.
  10. Start the 
    SpectroSERVER
     on the temporary 
    SpectroSERVER
     host. The temporary 
    SpectroSERVER
     is now the Secondary, fault-tolerant 
    SpectroSERVER
     for the MLS. 
    An orange alarm on the VNM indicates that the Archive Manager is not running. You can ignore it.
  11. Verify the setup of the Secondary fault tolerant 
    SpectroSERVER
     by checking the Landscape Configuration view on the MLS:
    1. In OneClick, double-click the VNM icon in the Universe Topology view. The landscape container is displayed.
    2. In the Contents panel highlight the “LocalLscpe” model.
    3. In the Component Detail panel, select the Information tab.
    4. Locate and expand the “Loaded Landscapes” subview.
    5. Verify that the list contains both the Primary MLS, with a precedence of 10, and the temporary Secondary 
      SpectroSERVER
      , with a precedence of 20 (or the precedence value that was specified with the “SSdbload” command).
  12. Shut down the Primary 
    SpectroSERVER
     (the MLS). 
    The Secondary 
    SpectroSERVER
     resumes management tasks while the MLS is upgraded.
  13. Follow the steps that are listed in How to Perform In-Place Upgrades to upgrade the MLS.
  14. Once the MLS has been successfully upgraded, manually start the Archive Manager on the Primary 
    SpectroSERVER
    :
    1. Launch a Spectrum Control Panel.
    2. Select Control, and click Start Archive Manager.
    Starting the Archive Manager ensures that the events that are being stored locally on the Secondary
    SpectroSERVER
    are sent over to the Primary Archive Manager.
  15. Start the 
    SpectroSERVER
    Primary management functions switch back to the MLS.
  16. Do not perform the step that instructs you to initiate an Online Backup.
    This upgrade configuration ensures that alarms that are synchronized from the secondary 
    SpectroSERVER
     and that were generated before the primary 
    SpectroSERVER
     was upgraded do not contain non-UTF-8 data.
  17. Configure the temporary 
    SpectroSERVER
     host as a Secondary 
    SpectroSERVER
     for the next 
    SpectroSERVER
     that you plan to upgrade.
  18. Repeat the above steps to back up, shut down, and upgrade each 
    SpectroSERVER
     in turn.
  19. Upgrade the OneClick Web Server last.
  20. Review the post-installation steps in Post-Installation Configurations.