Publish Route for Incoming Traffic in an Active-Standby Mode
The following sections describe the Control Plane and Data Plane call flows in an active/standby mode.
Control Plane Call Flow
This section describes the Control Plane call flow.

Step |
Description |
---|---|
1 |
The BGP speaker pod starts and fetches the service IP address, next-hop IP address (host IP or loopbackEth), and the Instance ID for the BGP speaker pod. The pod service is exposed through host IP or configured loopbackEth. The NF Instance ID is used to find the route priority or preference. |
2 |
The BGP speaker pod advertises routes by fetching vip-ip (service IP addresses) from the Ops Center. |
Data Plane Call Flow
This section describes the data plane call flow.

Step |
Description |
---|---|
1 |
AMF requests for service IP address. The request is sent to the nearest connected router through multiple external routers. Then, the router sends the request to the BGP speaker pod with highest priority. |
2 |
The BGP router sets the data plane flow based on the preference value. In the preceding call flow example, the router routes the service request through the host, 209.165.200.226 to pod 1 due to its higher preference value. From host 209.165.200.226, traffic is forwarded to the K8 service IP address, 209.165.201.10, which is then sent to either protocol pod 1 (209.165.200.226) or pod 2 (209.165.200.227). |