Stand-alone Upgrade
This process incurs system downtime; your Oracle Communications Session Border Controller stops passing traffic for a period of time. Please plan for your standalone upgrade accordingly.
Upload the Stage 3 Boot Loader and System Image
While the boot loader is generally backward compatible with previous releases, Oracle recommends that you install a boot loader from the same Major.Minor release as the system image. Installing a maintenance or patch release within a Major.Minor release does not normally require updating the boot loader. Perform this procedure for stand-alone and HA deployments, ensuring you are bootingall applicable machines using the correct bootlaoder.
System upgrades typically consist of transferring the new system image and
Stage3 boot loader to the system and setting boot parameters to the new system
software. To ensure compatibility, copy the Stage 3 boot loader to /code/images/
before
you update the boot parameters to use the new software image file. The boot loader
file must be renamed using the set-boot-loader command on the
target system. When upgrading an HA pair, you must perform the upgrade procedure on
each HA node. This includes rebooting the systems after setting the bootloader and
image. When performing this task, make sure to upgrade and reboot the standby system
first.
Follow the steps below to upload the Stage3 boot loader and system image.
Software Upgrade Procedure
The following procedure describes how to upgrade a
Oracle Communications Session Border Controller with a new software image. In this procedure, the image file is located on the
Oracle Communications Session Border Controller’s local file system in
/boot
.
To upgrade a software image on a stand-alone system: