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.

Check /boot for free space

  1. On the SBC, check for adequate space in the /boot volume to upload the new boot image and bootloader. Use the show space boot command.
    SBC# show space boot
    boot: 24759488/25760512 bytes (99%) remaining

    You may delete files from an SFTP client if you need to free space.

    The command check-space-remaining boot performs the same function as show space boot.

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.

  1. SFTP the software image (*.bz) and Stage3 boot loader (*.boot) to /code/images/.
    [Downloads]$ ls -l
    total 163380
    -rw-r--r-- 1 bob src  15591728 Dec  9 14:45 nnSCZ900p1.boot
    -rw-r--r-- 1 bob src 151705904 Dec  9 14:45 nnSCZ900p1.bz
    [Downloads]$ sftp admin@10.1.1.3
    Connected to admin@10.1.1.3.
    sftp> cd /code/images/
    sftp> put *
    Uploading nnSCZ900p1.boot to /code/images/nnSCZ900p1.boot
    nnSCZ840p3.boot                 100%   15MB  30.8MB/s   00:00
    Uploading nnSCZ840p3.bz to /code/images/nnSCZ900p1.bz
    nnSCZ900p1.bz                   100%  145MB  48.3MB/s   00:02 
    sftp> bye
    [Downloads]$
  2. SSH to your target machine.
  3. Run set-boot-loader with the path to the new bootloader.
    ORACLE# set-boot-loader /code/images/nnSCZ900p1.boot
    Verifying signature of /code/images/nnSCZ840p3.boot
    Version: Acme Packet SCZ9.0.0 Patch 3 (Build 188) 202010201742
    
    Image integrity verification passed
    
    Successfully copied /code/images/nnSCZ900p1.boot to /boot/bootloader
    ORACLE#
  4. Run set-boot-file with the path to the new software image.
    ORACLE# set-boot-file /code/images/nnSCZ900p1.bz
    Verifying signature of /code/images/nnSCZ840p3.bz
    Version: Acme Packet SCZ9.0.0 Patch 3 (Build 188) 202010201720
    
    Image integrity verification passed
    old boot file /boot/bzImage being replaced with /code/images/nnSCZ900p1.bz
    ORACLE#
  5. Reboot.

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:

  1. Change the boot configuration parameters to use the new image.

    In the ACLI configure terminal menu, type bootparam and press <Enter> to display the list of boot parameters. Scroll through the boot parameters by pressing Enter. Stop when you reach the file name boot parameter and type the appropriate file name next to the previous file name. Press <Enter> to continue scrolling through the boot parameters.

    The following example uses the filenames /boot/nnSCZ720m5.64.bz and /boot/nnSCZ730.64.bz.

    SBC1# configure terminal
    SBC1(configure)# bootparam
    '.' = clear field;  '-' = go to previous field;  ^D = quit
    boot device          : eth0
    processor number     : 0
    host name            : boothost
    file name            : /boot/nnSCZ720m5.64.bz /boot/nnSCZ730.64.bz
  2. Reboot the Oracle Communications Session Border Controller using the reboot command.

    The Oracle Communications Session Border Controller should now be successfully running the new release.