1. Diameter Signaling Router Diameter SDS Software Upgrade Guide
  2. Site Upgrade Execution
  3. Automated Site Upgrade
  4. Upgrade SOAM

9.1.2 Upgrade SOAM

The following procedure details how to upgrade SDS SOAM sites.

Note:

When upgrading an SDS topology, it is permissible to upgrade multiple SOAM sites in parallel. However, every attempt should be made to avoid upgrading mated SOAM sites in the same maintenance window.
  1. This step verifies the servers and server groups to be upgraded are in the proper state. Review site upgrade plan and site readiness.
    1. Log into the NOAM GUI using the VIP.
    2. Expand Administration select Software Management click Upgrade.
    3. Select the SOAM tab of the site to be upgraded.
    4. Verify the Entire Site link is selected.

    The Entire Site screen provides a summary of the server states and upgrade readiness. More detailed server status is available by selecting a specific server group link.

    Figure 9-1 Upgrade


    Upgrade

    Note:

    The Site Upgrade option can be used to upgrade an entire site, or a subset of site elements. The servers within the site may be in various states of readiness, including Accept or Reject, Ready, Backup Needed, Failed, or Not Ready. Only the servers in the Ready state or Failed state are upgrade eligible.
  2. In the Active NOAM VIP, initiate the site upgrade. Verify no Server Groups are selected on the upgrade administration screen. The Site Upgrade button is not available if a Server Group is selected. Click Site Upgrade.
    Review the upgrade plan as presented on the Site Initiate screen. This plan represents an approximation of how the servers will be upgraded. Due to the dynamic nature of upgrade, some servers (typically only C-level) may be upgraded in a different cycle than displayed here.

    Figure 9-2 Upgrade


    Upgrade

    Note:

    If you need to rearrange the upgrade cycle, see section Rearrange Automate Site Upgrade Cycles.
  3. In the Upgrade Settings section of the form, use the Upgrade ISO option to select the target ISO. Click OK to start the upgrade sequence. Control returns to the Upgrade Administration screen.
  4. In the Active NOAM VIP, view In-Progress Status. In View the Upgrade Administration form Monitor the upgrade progress. See step 5 of this procedure for instructions if the upgrade fails or if execution time exceeds 60 minutes.

    Note:

    If the upgrade processing encounters a problem, it may attempt to ROLL BACK to the original software release. In this case, the upgrade shows as Failed.

    The execution time may be shorter or longer, depending on the point in the upgrade where there was a problem.

    With the Entire Site link selected, a summary of the upgrade status for the selected site displays. This summary identifies the server group(s) currently upgrading, the number of servers within each server group that are upgrading, and the number of servers that are pending upgrade. This view can be used to monitor the upgrade status of the overall site.

    Figure 9-3 Monitor Progress


    Monitor Progress

    More detailed status is available by selecting the individual server group links. The server group view shows the status of each individual server within the selected server group. During the upgrade, the servers may have some or all of the following expected alarms.

    Note:

    Not all servers have all alarms:Alarm ID = 10073 (Server Group Max Allowed HA Role Warning)
    • Alarm ID = 10075 (The server is no longer providing services because application processes have been manually stopped)
    • Alarm ID = 31101 (DB Replication To Slave Failure)
    • Alarm ID = 31106 (DB Merge To Parent Failure)
    • Alarm ID = 31107 (DB Merge From Child Failure)
    • Alarm ID = 31228 (HA Highly available server failed to receive mate heartbeats) or (Lost Communication with Mate Server)
    • Alarm ID = 31233 (HA Secondary Path Down)
    • Alarm ID = 31283 (Highly available server failed to receive mate heartbeats)
    • Alarm ID = 32515 (Server HA Fail over Inhibited)
    • Alarm ID = 31114 (DB Replication over SOAP has failed)
    • Alarm ID = 31225 (HA Service Start Failure)

    Do not accept any upgrades at this time.

    Contact My Oracle Support for any assistance. Refer Recover from a Failed Upgrade for failed server recovery procedures.
  5. Upon completion of a successful upgrade, every server in the site is in the Accept or Reject state.

    Figure 9-4 Server State


    Server State

  6. In the Server CLI, if the upgrade of a server fails, access the server command line (using SSH or a console), and collect the following files:
    • /var/TKLC/log/upgrade/upgrade.log
    • /var/TKLC/log/upgrade/ugwrap.log
    • /var/TKLC/log/upgrade/earlyChecks.log
    • /var/TKLC/log/platcfg/platcfg.log
    Contact My Oracle Support for assistance. Refer to Upgrade Server Administration on SDS 9.0 for failed server recovery procedures.
  7. Update the tuned profile, after successful upgrade has been verified above, access each of the servers on command line (using SSH or console), and update the tuned profile:
    $ sudo /usr/TKLC/sds/bin/sdsSharedMemTuned.sh
    Verify whether tuned profile has been successfully set to comcol_app:
    $ sudo tuned-adm active
    Sample Output:
    [admusr@SOAM1 ~]$ sudo tuned-adm active
Current active profile: comcol_app
Service tuned: enabled, running
Service ktune: enabled, running
[admusr@SOAM1 ~]$