The Oracle Communications Session Border Controller (OCSBC) supports High Availability (HA) deployments on public clouds using the redundancy mechanisms native to those clouds. You configure the cloud to recognize the OCSBC. The REST client on the OCSBC subsequently makes requests to the cloud's Software Defined Networking (SDN) controller for authentication and virtual IP address (VIP) management. While HA configuration across all OCSBC platforms is similar, public cloud HA configuration fundamentally does not require configuring virtual MAC addresses. This feature supports only IPv4 addressing. The OCSBC includes a REST client to configure the cloud's SDN controller. The local REST client supports both HTTP and HTTPS, using the former for metadata requests and the latter for other cloud management requests.

Vendors manage public clouds using SDN. The SDN controller owns all networking aspects including vNICs, IP addresses, MAC addresses, and so forth. Without the knowledge of the SDN controller, IP addresses cannot be assigned or moved. As a result, the network either drops or ignores GARP traffic. The absence of GARP invalidates the use of HA by the OCSBC in these networks, therefore requiring alternate HA functionality on the OCSBC.

The OCSBC recognizes when it is deployed on these clouds. When it needs to failover, instead of issuing GARP traffic to invoke the transfer of VIPs from one node to another, it uses the cloud's REST API to reconfigure virtual IP addressing.

Cloud configuration and the use of REST is equivalent across the range of public clouds, with vendors using different terminology for similar functions and objects.