A.6.5 Manual SBR Upgrade Procedure

The following procedure is used to upgrade the SBR server group manually. This procedure is an alternative to the normal SBR upgrade procedures.

Note:

Note: Before upgrading the active SBR, it is imperative that the database audit of the spare and standby servers complete successfully. Failure to comply could result in a loss of session/binding data.

A.6.5 Active NOAM VIP: Upgrade Spare SBR Server

Follow this procedure to upgrade spare SBR server if it needs to be upgraded in this upgrade iteration.

1. Execute Appendix C Upgrade Single Server – DSR 8.x.
2. After successfully completing the procedure in Upgrade Single Server – DSR 8.x, return to this point to monitor server status.
3. Navigate to SBR, then Maintenance, and then SBR Status. Open the tab of the server group being upgraded.

   Note:

   After executing Appendix C, the spare SBR temporarily disappears from the SBR Status screen. When the server comes back online, it reappears on the screen with a status of Out of Service.
4. Monitor the Resource HA Role status of the spare server. Wait for the status to transition from Out of Service to Spare.
5. If the system is equipped with a second spare SBR server, repeat sub-steps 1 through 3 for the other spare.

   Note:

   Do not proceed to the next procedure until the Resource HA Role of the spare SBR server returns to Spare.

   Note:

   Repeat this procedure for all remaining binding and session server groups to be upgraded.

A.6.5 Upgrade Standby SBR Server

Follow these steps to upgrade standby SBR server.

1. Execute Upgrade Single Server - DSR.x procedure.
2. After successfully completing the procedure, return and continue with the next step.

   Note:

   Repeat this procedure for all remaining binding and session server groups to be upgraded.

A.6.5 Active NOAM VIP: Verify Standby SBR Server Status

1. 1. Navigate to SBR, then Maintenance, and then SBR Status.
2. 2. Open the tab of the server group being upgraded.

   Note:

   After executing Appendix C, the standby SBR temporarily disappears from the SBR Status screen, and the spare server assumes the standby role. When the upgraded server comes back online, it reappears on the screen with a status of Out of Service.
3. 3. Monitor the Resource HA Role status of the upgraded server. Wait for the status to transition from Out of Service to Standby.

   Caution:

   Do not proceed to the next procedure until the Resource HA Role of the upgraded server transitions to Standby.

   Note:

   Repeat this procedure for all remaining binding and session server groups to be upgraded.

A.6.5 Active NOAM VIP: Verify Bulk Download from the Active SBR to the Standby and Spare SBRs Completes

1. Navigate to Alarm & Event, then View History.
2. Export the Event log using the following filter:

   Server Group: Choose the SBR group that is in upgrade

   Display Filter: Event ID = 31127 – DB Replication Audit Complete

   Collection Interval: X hours ending in current time

   where X is the time from upgrade completion of the standby and spare servers to the current time.

3. Wait for all instances of Event 31127:

   1 for the Standby binding SBR

   1 for the Standby session SBR

   1 for the Spare binding SBR

   1 for the Spare session SBR

   1 for the 3rd site Spare binding SBR (if equipped)

   1 for the 3rd site Spare session SBR (if equipped)

   Note:

   There is an expected loss of traffic depending on size of the bulk download. This must be noted along with events captured.

   Note:

   Repeat this procedure for all remaining binding and session server groups to be upgraded.

A.6.5 Active SBR (CLI): Verify the Replication Status for DB Replication and pSbrBindingPolicy

Follow this procedure to verify the replication status for DB Replication and pSbrBindingPolicy (Binding SBR) Or pSbrSessionPolicy (Session SBR).

1. Use the SSH command (on UNIX systems – or putty if running on windows) to log into the active SBR of the first non-upgraded site:

   ssh admusr@<SBR_XMI_IP>

   password: <enter password>

   Answer yes if you are asked to confirm the identity of the server.

2. Execute command

   irepstat -w

   Verify replication is showing as Active for ActStb [DbReplication] policy, pSbrSessionPolicy (for Session SBR), and pSbrBindingPolicy (for Binding SBR).

   Do not proceed if replication is not Active for all of the resource.

   Note:

   Repeat this procedure for all remaining binding and session server groups to be upgraded.

A.6.5 Upgrade Active SBR Server as Identified in Step 1 of This Procedure

1. Execute Upgrade Single Server - DSR 8.x procedure.
2. After successfully completing step 1, return and continue with the next step.