New in Avaya SBC Release 10.3

Last Updated : Oct 05, 2026 |
Prolog information

Support for Red Hat Enterprise Linux 9.6

Release 10.3 updates the underlying operating system to Red Hat Enterprise Linux 9.6 (RHEL 9.6), replacing the legacy RHEL 8.10 base. All fresh deployment installation packages (ISO, OVA, and QCOW2) ship with RHEL 9.6.

VMware ESXi Support

Avaya SBC 10.3 OVA/OVF images are fully qualified for deployment on VMware ESXi 8.x, and ESXi 9.x.
Note:
VMware ESXi 7.x and older hypervisor versions are discontinued and no longer supported for new installs or upgrades.

Kernel-based Virtual Machine (KVM) hypervisor support

With release 10.3, Avaya SBC enhanced KVM deployment using Avaya-supplied KVM on RHEL 9.6, optimized specifically for the Avaya Solutions Platform 130 Appliance R7.0 and Avaya Solutions Platform S8300 R7.0.

UEFI Boot Requirement

Release 10.3 exclusively supports UEFI boot mode (with optional UEFI secure boot enablement). Legacy boot systems cannot be directly upgraded.

FIPS 140-3 Compliance

With Release 10.3, Avaya SBC added support for FIPS 140-3 cryptographic standards.

Support for RADIUS over TLS

In release 10.3, RADIUS over TLS support is enhanced with the following capabilities:
  • Supports 4096-bit (4K) RSA keys for RADIUS server authentication while retaining 2048-bit (2K) key support for backward compatibility.
  • Increased maximum TLS fragment payload size to 8192 bytes to handle complex, multi-tiered certificate chains.

LVM-based disk architecture

  • Logical Volume Management (LVM)-based disk architecture replaces standard partitions with LVM layout on fresh installs, enabling fully supported dynamic disk resizing.
  • Increases default disk capacity for OVA, cloud, and KVM images from 64 GB to 80 GB to accommodate RHEL 9.6 root (/) directory expansion.
  • Introduces optional LUKS-based encryption for enhanced data-at-rest protection.
Important:
In-place upgrades preserve legacy partition layouts without LVM or encryption. Acquiring LVM layout or LUKS encryption requires an offline migration (backup, fresh install, restore).

Upgrade Simplification and Recommendations

Avaya SBC release 10.3 introduces updated guidelines and recommendations for managing the following base operating system upgrades:
  • All platform upgrades must be executed through the Command Line Interface (CLI) using sbc-upgrade. Upgrades using Web GUI are no longer supported.
  • For upgrading to release 10.3, an offline upgrade (migration) is strongly recommended to ensure system stability and data integrity.
    Upgrade packages must be staged in and executed directly from /archive/temp.

Updated Cloud Platform Support in R10.3

Starting with release R10.3 support for Microsoft Azure, Google Cloud Platform (GCP) and Nutanix will be discontinued.
Note:
If you are currently deployed on Microsoft Azure, GCP or Nutanix, please review Upgrading Avaya Session Border Controller guide or reach out to support to assist with your transition prior to upgrading to R10.3.