Overview

SBC SWe Edge is optionally deployable in a High Availability (HA) configuration with mid-call failover. HA functionality on the SBC SWe Edge enhances resiliency by offering Active and Standby SBC instances, among which the Standby instance takes over call management if the Active instance fails. The HA configuration uses the System Health Monitor (SHM) to check SIP call states, assuring failover. The Active and Standby SBC function with the same license under one License Manager (LM). At the time of deployment, licensing data must be configured and accepted by the Active instance, and then that information is replicated to the Standby instance. For the 12.1 release, the HA feature is supported exclusively for on-premise deployments and only available on VMware and KVM hypervisors. Additional limitations apply; see Limitations for more information.

HA Architecture Diagram

Limitations 

Below is a list of the limitations of the HA feature in release 12.1:

  • Deployment
    • HA functionality is not supported in Microsoft Azure and AWS deployments.
    • HA links must be IPv4.
    • HA functionality is not supported on SBC 1000/2000.
    • HA ports for an HA pair are only allowed on the same subnet.
    • DHCP on HA Interface is not supported.
    • Geo Redundancy is not supported.
    • Floating IPs are supported only on the packet interfaces, not the HA or Management interfaces.

  • Data Replication

    • The Standby instance does not replicate Alarms, Counters, and CDR details. 
    • The Standby instance does not replicate caches.
    • The Active and the Standby instances do not store backup CDR and VQ files in the database.
    • The Active and the Standby instances do not share a Debug Facility, Monitor View, or Logging details. Each instance only shows its details.

  • Call Features

    • SIP recording, Video calls, and Music On Hold do not support switchover scenarios.

    • The new Active instance (the instance that was the Standby instance before you upgraded the SBC Edge software) does not support Socket Reuse and TLS Session resumption.

  • Others

    • SNMP Proxy from the Standby instance to the Active instance, so that SNMP requests always get a response regardless of which instance receives the request, is not supported.

    • Using Service Discovery to find a RAMP instance when RAMP is configured for HA is not supported.