1. DSR Cloud Software Upgrade Guide
  2. Upgrade Multiple Servers – Upgrade Administration

Upgrade Multiple Servers – Upgrade Administration

The procedures in this section upgrade multiple servers in parallel.

Note:

This procedure is executed multiple times during the overall upgrade, depending on the number of servers in your DSR. Make multiple copies of Appendix D to mark up or keep another form of written record of the steps performed.

Active NOAM VIP: View Pre-Upgrade Status of the Servers

  1. Repeat the steps listed in Active NOAM VIP: View Pre-Upgrade Status of the Servers.

Active NOAM VIP: Verify Status of Servers to be Upgraded

  1. Repeat the steps listed in Active NOAM VIP: Verify Status of Servers to be Upgraded.

Active NOAM VIP: Verify Upgrade Status is Ready

  1. The Upgrade Administration form refreshes and the server to upgrade displays Upgrade Status = Ready. This may take a minute. Depending on the server being upgraded, new alarms may occur.

    The Upgrade Administration form refreshes and the server to upgrade displays Upgrade Status = Ready. This may take a minute. Depending on the server being upgraded, new alarms may occur.

    Alarm ID = 10008 (Provisioning Manually Disabled)

    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 = 32515 (Server HA Failover Inhibited)

    Alarm ID = 31101 (DB Replication to slave DB has failed)

    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 = 31114 (DB Replication over SOAP has failed)

    Alarm ID = 31225 (HA Service Start Failure)

Determine Upgrade Method

  1. To upgrade multiple servers in parallel using the manual option, execute Active NOAM VIP: Initiate upgrade (part 1) and Active NOAM VIP: Initiate upgrade (part 2).
  2. To upgrade a server group using the Automated Server Group Upgrade option, proceed to Active NOAM VIP: Initiate (part 1) – Automated Server Group Upgrade option.

Active NOAM VIP: Initiate Upgrade (Part 1)

  1. From the Upgrade Administration screen, select the servers to upgrade.
  2. Click Upgrade Server.

    The Initiate Upgrade form displays on the Administration, then Software Management, and then Upgrade Initiate screen.

Active NOAM VIP: Initiate Upgrade (Part 2) – Select ISO Form

  1. From the Upgrade Settings – Upgrade ISO options, select the ISO to use in the server upgrade.
  2. Click OK.

    The upgrade begins and control returns to the Upgrade Administration screen.

  3. Proceed to Active NOAM VIP: Initiate (part 2) – Automated Server Group Upgrade procedure to complete this procedure.

Active NOAM VIP: Initiate (Part 1) – Automated Server Group Upgrade Option

  1. To utilize the Automated Server Group upgrade option, verify no servers in the server group are selected.
  2. Click Auto Upgrade.

Active NOAM VIP: Initiate (Part 2) – Automated Server Group Upgrade

The settings to be used in this step are specified in the calling procedure.
  1. The Upgrade Settings section of the Initiate screen controls the behavior of the automated upgrade. Select the settings that apply to the server type being upgraded.

    Bulk: Select this option for active/standby and multi-active server groups. For servers in an active/standby configuration, the standby server is upgraded first, followed by the active. Servers in a multi-active configuration are upgraded in parallel to the extent allowed by the Availability setting.

    Serial: Select this option to upgrade multiple servers one at a time.

    Grouped Bulk: Select this option for SBR server groups. Grouped bulk always upgrades the spare(s), followed by the standby, followed by the active.

    Availability: This setting determines how many servers remain in service while servers in the server group are upgraded. For example, a setting of 50% ensures at least half of the servers in the server group remain in service.

    Note:

    The Serial upgrade mode is available as an alternative to Bulk and Grouped Bulk for a more conservative upgrade scenario. Serial mode upgrades each server in the server group one at a time, and can be used on any server group type.
  2. Select the appropriate ISO from the Upgrade ISO options.
  3. Click OK to start the upgrade.

Active NOAM VIP: View the Upgrade Administration Form to Monitor Upgrade Progress

  1. Repeat the steps mentioned in Active NOAM VIP: View the Upgrade Administration Form to Monitor Upgrade Progress

    Note:

    See Server CLI: (Optional) View in-progress status from command line procedure for an optional method of monitoring upgrade progress.

    See Server CLI: If upgrade fails procedure for instructions if the Upgrade fails, or if execution time exceeds 60 minutes.

Server CLI: View In-Progress Status from Command Line

  1. Repeat the Server CLI: View In-Progress Status from Command Line procedure.

Server CLI: If Upgrade Fails

  1. Repeat the Server CLI: If Upgrade Fails procedure.

Active NOAM VIP: Verify Post-Upgrade Status

  1. Repeat the Active NOAM VIP: Verify Post-Upgrade Status procedure.

Verify the Upgrade

  1. Repeat the Verify the Upgrade procedure.