HA Upgrade
In the descriptions and processes outlined below, ORACLE-1 is initially the active system and ORACLE-2 is initially the standby system. Please read the following procedures carefully before beginning the upgrade. If necessary, you can back out of the upgrade once during the upgrade procedure and once after you have completed the upgrade procedure.
Note:
See the diagram below, which addresses how the HA Upgrade procedures' sequence includes rebooting the standby system first to avoid service interruption.Figure 11-1 Configure and Reboot Standby First for HA Procedures
Note:
Do not upgrade a non-LI HA deployment with an LI image or vice-versa if you wish to perform a hitless upgrade. This procedure results in a non-hitless upgrade, requiring that you reboot devices per your upgrade procedure, and then reboot all upgraded devices again to establish the new deployment type.HA Upgrade Procedure
Note:
In the procedure below, ORACLE-1 is the active system and ORACLE-2 is the standby system. The standby system should be rebooted first.HA Backout Procedure
If you reach the point in your upgrade procedure where you have upgraded both Oracle Communications Session Border Controllers in the HA pair to a later release that you decide you no longer want to use, you can fall back to a previous release. This section shows you how to fall back to an older image with both systems in your HA node upgraded.
Note:
In the procedure below, ORACLE-2 is the active system and ORACLE-1 is the standby system. The procedure uses these designations because the prior procedure results in ORACLE-2 as the active system. The standby system should be rebooted first.To backout to a previous (older) release with the both SBCs in the HA node upgraded: