VIPs every 300 seconds until it succeeds. Upon success, the OCSBC suspends these re-
requests and begins to send address verification requests every 300 seconds. These
requests verify that the SDN continues to associate this OCSBC with these VIPs.
When moving from Active to any other state, the OCSBC gracefully abandons any
outstanding REST client operations.
Configuration Considerations
Key OCSBC configuration considerations across all cloud environments include:
•
Do not configure virtual MAC addresses
•
Configure VIPs via the cloud's console as secondary private IPs on the media vNICs
•
Obtain wancom0 management address via DHCP
•
Obtain the wancom0 default gateway via DHCP
•
Obtain the cloud's name servers via DHCP, allowing the local DNS resolver to cache
cloud infrastructure addressing
Regarding the use of DHCP to obtain addressing, this means that those subnets must have
DHCP enabled and DNS name server IPs configured.
Authentication
The public cloud's API requires that the client authenticate with the cloud to successfully
invoke the API. Although each cloud has differences between their authentication
mechanisms, they are typically categorized as either Provisioning or Automatic. The OCSBC
uses Automatic authentication.
With Automatic authentication, the SDN assigns an OCSBC instance with an appropriate
role, providing credentials through its instance metadata. The instance does not need to be
provisioned with any credentials. These credentials may be temporary and change
periodically. As a result, the OCSBC instance does not cache its credentials, obtaining the
latest credentials when invoking the API.
DNS Resolver
Because the REST API resolves hostnames into IP addresses, OCSBC needs an active DNS
resolver. This ensures that it can forward properly. As part of this feature, the OCSBC
enables its DNS resolver when deployed on public clouds. The OCSBC then obtains the
name server IPs for the DNS resolution through DHCP. The DHCP client obtains the name
server IPs and populates them in the /etc/resolv.conf file. The OCSBC uses the
nameservers for DNS resolution when invoking REST API.
Note: The OCSBC must obtain the IP address for the wancom0 interface through DHCP
which will provide the name server IPs. Without DHCP, the OCSBC has no mechanism to
manually configure the name server IPs.
IP Addressing
The following diagram portrays an IP addressing example applicable to an HA deployment in
a public cloud. Note that the external endpoints are SIP peers reachable through internet/
public IPs.
Chapter 7
Deploying the OCSBC on Cloud Infrastructures in HA Mode
7-3
Содержание 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 ...
