12
Software Upgrade
This section provides information about how to upgrade your Oracle Communications
Session Border Controller software image. Note that proprietary Acme Packet hardware is
normally delivered with an operational image ready to run. Your deployment, however, may
require a different version that what was delivered, making software upgrade a required step
in platform preparation.
The Check Upgrade Readiness Command
The OCSBC provides you with the ability to examine system components and status to
determine whether an upgrade can occur seamlessly. If not, the system provides you with
information that describes changes you should make prior to attempting an upgrade. Review
the output of this command three times during an upgrade cycle:
1.
Run the check-upgrade-readiness command before any software upgrade. Examine
the command output to identify and resolve any potential upgrade issues.
2.
Also note that the system runs the check-upgrade-readiness command automatically
upon the first reboot after a software upgrade. If the system finds significant issues after
running the command, it may revert back to booting with the previous software version.
3.
Run the check-upgrade-readiness after upgrade to check for any potential operational
issues.
Note that the verify-config command can also provide important system status information
that can assist you during an upgrade.
Upgrade Checklist
Before upgrading the Oracle Communications Session Border Controller software:
1.
Obtain the name and location of the target software image file from either Oracle
Software Delivery Cloud, https://edelivery.oracle.com/, or My Oracle Support, https://
support.oracle.com, as applicable.
2.
Provision platforms with the Oracle Communications Session Border Controller image file
in the boot parameters.
3.
Run the check-upgrade-readiness command and examine its output for any
recommendations or requirements prior to upgrade.
4.
Verify the integrity of your configuration using the ACLI verify-config command.
5.
Back up a well-working configuration. Name the file descriptively so you can fall back to
this configuration easily.
6.
Refer to the Oracle Communications Session Border Controller Release Notes for any
caveats involving software upgrades.
12-1
