Upgrade Process

To upgrade a software image for an HA node:

1. Confirm that Oracle® Enterprise Session Border Controller1 and Oracle® Enterprise Session Border Controller2 start up and are synchronized.

   You must also make sure that all of the running and current configurations on Oracle® Enterprise Session Border Controller1 and Oracle® Enterprise Session Border Controller2 have the same number. In the following examples, all of the configuration versions are 5.

   On Oracle® Enterprise Session Border Controller1 and Oracle® Enterprise Session Border Controller2, use the ACLI show health command to make sure that all processes are synchronized.

   On Oracle® Enterprise Session Border Controller1, show the current configuration version by using the ACLI display-current-cfg-version command. Then use the same command on Oracle® Enterprise Session Border Controller2 and be sure that its current configuration version is the same as the one on Oracle® Enterprise Session Border Controller1.

   ORACLE1# display-current-cfg-version
   Current configuration version is 5
    ORACLE1#
   ORACLE2# display-current-cfg-version
   Current configuration version is 5
   ORACLE2#

   On Oracle® Enterprise Session Border Controller1, show the running configuration version by using the ACLI display-running-cfg-version command. Then use the same command on Oracle® Enterprise Session Border Controller2 and be sure that its running configuration version is the same as the one on Oracle® Enterprise Session Border Controller1.

   ORACLE1# display-running-cfg-version
   Running configuration version is 5
   ORACLE1#
   ORACLE2# display-running-cfg-version
   Running configuration version is 5
   ORACLE2#

2. On Oracle® Enterprise Session Border Controller1, before loading the software image to the flash, check the remaining space in the /boot directory using the ACLI check-space-remaining code command.

   AORACLE1# check-space-remaining boot
   boot: 24759488/25760512 bytes (99%) remaining
   ORACLE1#

   If you see less than 50% of the memory remaining, delete older stored firmware images to make space.

   At a minimum, we recommend that you leave the diags.gz file and the currently running release on the flash memory (in the event that a rollback is required).

3. Upload the Oracle® Enterprise Session Border Controller software image file and stage three bootloader to the /boot directory using an SFTP client. See: Upgrade the Stage 3 Bootloader.
4. Change the boot configuration parameters on Oracle® Enterprise Session Border Controller1 to use the appropriate new release software image.

   Note:

   From the point that you upgrade the image file, do not make any configuration changes. Likewise, do not use the save-config or activate-config commands. Once you execute the save-config command, the configuration can not be guaranteed to be backward compatible should you have to back out of the upgrade.

   Access the boot parameters on Oracle® Enterprise Session Border Controller1:

   • In the ACLI configure terminal menu, type bootparam and press <Enter> to being displaying the list of boot parameters.

     Scroll through the boot parameters by pressing <Enter>. Stop when you reach the file name boot parameter.

     The following example uses the filenames /code/images/nnSCX640.gz and /boot/nnSCZ712.64.bz.

     ORACLE1# configure terminal
     ACMEPACKETSBC1(configure)# bootparam
     '.' = clear field;  '-' = go to previous field;  ^D = quit
     boot device          : eth0
     processor number     : 0
     host name            : boothost
     file name            : /code/images/nnSCX640.gz /boot/nnSCZ712.64.bz

     As shown above, type the new Release file name next to the previous one, including the path. Press <Enter> to continue scrolling through the boot parameters.

     Reboot Oracle® Enterprise Session Border Controller1.

5. After Oracle® Enterprise Session Border Controller1 has completed the boot process, use the verify-config command to confirm that the configuration has been upgraded properly.

   ORACLE1# verify-config

6. Confirm the Oracle® Enterprise Session Border Controller1 is running the new boot image using the show version command.

   ORACLE1# show version
   Acme Packet 4500 SCZ7.1.2 GA (Build 165)
   Build Date=07/17/13
   ORACLE1#

7. Use the ACLI show health command to confirm that Oracle® Enterprise Session Border Controller1 is the standby system.
8. As you did for Oracle® Enterprise Session Border Controller1, configure the boot parameters on Oracle® Enterprise Session Border Controller2 so to use the new Acme Packet Release S-CX6.4.0 software image. Then reboot Oracle® Enterprise Session Border Controller2.

   ORACLE2# reboot
   --------------------------------------------------------
   WARNING: you are about to reboot this SD!
   --------------------------------------------------------
   Reboot this SD [y/n]?: y

   Rebooting Oracle® Enterprise Session Border Controller2 causes Oracle® Enterprise Session Border Controller1 to become the active system in the HA node.

9. When Oracle® Enterprise Session Border Controller2 is finished rebooting, use the ACLI show health command to confirm that it is in the standby state.

   Note:

   If you need to revert to older image, use the HA Backout Procedure.