Although the procedures in this document include steps that are used to support HA,
you use the same procedures without the HA steps to deploy the OCSBC in
standalone mode. Procedure documentation indicates when a step applies to HA
deployments.
Deploying the OCSBC on Cloud Infrastructures in HA Mode
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.
Note:
The OCSBC does not support High Availability (HA) when deployed over
Azure.
Key OCSBC Configuration and Operation Detail in HA Mode
When the OCSBC is deployed in an HA configuration in a public cloud, the system's
configuration and operation is predominantly the same as in an on-premise HA
configuration. The only operational difference is its behavior when going active.
Because the OCSBC knows it is deployed on a public cloud, it automatically replaces
its GARP procedures when it goes active with REST calls to fetch VIPs. Going active
includes first startup of the primary, as well as the standby taking over because of an
HA event.
HA Operation
When an OCSBC goes into active state on a public cloud, its REST client requests
VIPs. If it does not receive the addressing, it re-issues these requests after 5 seconds,
then 10, 20, 40, 80 and finally 160 seconds. If these request fail, it attempts to acquire
Chapter 7
Deploying the OCSBC on Cloud Infrastructures in HA Mode
7-2
Содержание netra X5-2
Страница 101: ...Chapter 7 Create and Deploy on Azure 7 35 ...
Страница 127: ...Figure 11 7 BMC Step 9 10 Click Next after the write operation is complete Chapter 11 Creating a Build Image 11 5 ...
Страница 151: ...Appendix A Acme Packet 6300 6350 Physical Interfaces A 12 ...
Страница 152: ...Note The Quad 10 GbE NIU must go in slot 0 Appendix A Acme Packet 6300 6350 Physical Interfaces A 13 ...
