Skip to content

Commit 4ba7fe8

Browse files
authored
Remove AP5GC 2211 router and RAN limitation
1 parent 11564b2 commit 4ba7fe8

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

articles/private-5g-core/azure-private-5g-core-release-notes-2211.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,6 @@ The following table provides a summary of known issues carried over from the pre
6868
|-----|-----|-----|
6969
| 1 | Policy configuration | Azure Private 5G Core may ignore non-default QoS and Policy configuration when handling 4G subscribers. |
7070
| 2 | Packet forwarding | Azure Private 5G Core may not forward buffered packets if NAT is enabled.  |
71-
| 3 | Packet forwarding | If Azure Private 5G Core is placed on the same subset as the RAN node (gNodeB / eNodeB) without an intervening/available router, there are two limitations. <br> - Only one RAN node can be used. It is not possible to connect multiple RAN nodes without an intervening router. <br> - The IP address of the RAN node must be supplied in the gateway field, for both N2/S1-MME and N3/S1-U when configuring the ASE Virtual Networks on AKS Hybrid. |
7271

7372

7473
## Next steps

0 commit comments

Comments
 (0)