Skip to content

Commit f67e884

Browse files
committed
update router config info
1 parent 8b2dbe6 commit f67e884

File tree

2 files changed

+9
-2
lines changed

2 files changed

+9
-2
lines changed

articles/private-5g-core/configure-routers-high-availability.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,17 +12,24 @@ ms.custom: template-how-to
1212

1313
# Configure routers for a Highly Available (HA) deployment
1414

15-
In a Highly Available Azure Private 5G Core deployment, the Azure Kubernetes Service (AKS) cluster runs on a pair of ASE devices. The ASE devices are deployed in an active / standby configuration, with the backup ASE rapidly taking over service in the event of a failure. Incoming traffic uses a virtual IP address which is routed to the physical IP address of the active ASE. Bidirectional Forwarding Detection (BFD) is used to detect failures.
15+
In a Highly Available Azure Private 5G Core deployment, the Azure Kubernetes Service (AKS) cluster runs on a two-node cluster of ASE devices. The ASE devices are deployed in an active / standby configuration, with the backup ASE rapidly taking over service in the event of a failure. Incoming traffic uses a virtual IP address which is routed to the active ASE's virtual network interface card (vNIC). Bidirectional Forwarding Detection (BFD) is used to detect failures.
1616

1717
This requires you to deploy a gateway router between the ASE cluster and:
1818

1919
- the RAN equipment in the access network
2020
- the data networks.
2121

22-
The routers should rapidly detect the failure of an ASE device through a BFD session going down and immediately redirect all traffic to the other ASE. With the recommended settings, BFD should be able to detect failure in about one second, ensuring that traffic should be restored in less than 2.5 seconds.
22+
The routers should rapidly detect the failure of an ASE device through a BFD session going down and immediately redirect all traffic to the other ASE. With the recommended settings, BFD should be able to detect failure in about one second, ensuring that traffic should be restored in less than 2.5 seconds. User plane state is replicated across the two ASEs to ensure the backup can take over immediately.
23+
24+
:::image type="content" source="media/ha-summary.png" alt-text="Diagram showing the routing configuration in a highly available deployment.":::
2325

2426
This how-to guide describes the configuration required on your router or routers to support an HA deployment. The gateway router for the access network and the gateway router for the data networks may be the same device or separate devices.
2527

28+
## Prerequisites
29+
30+
- Complete all of the steps in [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md) and [Commission the AKS cluster](commission-cluster.md).
31+
- Ensure you can sign in to the Azure portal using an account with access to the active subscription you identified in [Complete the prerequisite tasks for deploying a private mobile network](complete-private-mobile-network-prerequisites.md). This account must have the built-in Contributor or Owner role at the subscription scope.
32+
2633
## Collect router configuration values
2734

2835
To determine how to configure the static routes on the gateway routers, navigate to your **Packet Core Control Plane** resource in the Azure portal. Under **Settings**, select **Router configuration**. This shows the N2S1 and N3 virtual IP addresses, the IP prefix for all UE pools for each data network and the next hops and relative priorities.
105 KB
Loading

0 commit comments

Comments
 (0)