Merge pull request #221469 from robswain/2211releasenotes

AP5GC 2211 release notes

Author: PMEds28

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

@@ -0,0 +1,80 @@
+---
+title: Azure Private 5G Core 2211 release notes 
+description: Discover what's new in the Azure Private 5G Core 2211 release
+author: robswain
+ms.author: robswain
+ms.service: private-5g-core
+ms.topic: release-notes
+ms.date: 12/12/2022
+---
+
+# Azure Private 5G Core 2211 release notes
+
+The following release notes identify the new features, critical open issues, and resolved issues for the 2211 release of Azure Private 5G Core (AP5GC). The release notes are continuously updated, and as critical issues requiring a workaround are discovered, they’re added. Before deploying this new version, please review the information contained in these release notes.  
+
+This article applies to the AP5GC 2211 release (PMN-2211-0). This release is compatible with the ASE Pro GPU running the ASE 2210 release and is supported by the 2022-04-01-preview and 2022-11-01 [Microsoft.MobileNetwork](/rest/api/mobilenetwork) API versions.
+
+## Support
+
+The default support lifetime for a Packet Core version is roughly two calendar months from release. 
+
+The support lifetime for version 2211 is extended – due to the December holiday period – to three calendar months and will end on February 28, 2023. Please be prepared to plan your Packet Core upgrade to a future version before 2211 goes out of support on this date. 
+
+## What's new
+
+**Multiple data networks** - This release extends AP5GC to support connectivity to up to three Attached Data Networks for each Packet Core instead of one. 
+
+The operator can provision UEs as subscribed in one or more Data Networks and apply Data Network-specific policy and QoS, allowing UEs to use multiple Layer 3 uplink networks selected based on policy or UE preference. 
+
+Each Data Network can have its own configuration for DNS, UE IP address pools, N6 IP, and NAT. This concept also maps directly to 4G APNs. 
+
+This feature has the following limitations: 
+
+- Once more than a single Data Network is configured, further configuration changes require the packet core to be reinstalled. To ensure this reinstall happens only after you have made all your changes, you must follow the process for installing and modifying as described in the documentation.
+
+- VLAN separation of Data Networks is not supported. Only Layer 3 separation is supported (meaning overlapping IP address spaces across the Data Networks are not possible). 
+
+- Metrics are not yet reported on a per-Data Network basis.
+
+To add data networks to an existing site, see [Modify the packet core instance in a site](modify-packet-core.md). To create a new site, see [Create a site](create-a-site.md).
+
+## Issues fixed in the AP5GC 2211 release
+
+The following table provides a summary of issues fixed in this release.
+
+  |No.  |Feature  | Issue |
+  |-----|-----|-----|
+  | 1 | 4G/5G Signaling  | In rare scenarios when a significant number of UEs are bulk-registered and send continuous data, the core may incorrectly release data sessions. This issue has been fixed in this release.  |
+  | 2 | 4G/5G Signaling  | Azure Private 5G Core may perform an unnecessary PDU Session Resource Setup Transaction following a UE-initiated service request. This issue has been fixed in this release.  |
+  | 3 | Local distributed tracing  | The distributed tracing web GUI fails to display and decode 'Request Type' and 'DNN' information elements in 4G/5G NAS messages. This issue has been fixed in this release.  |
+  | 4 | Performance | Very rarely, CPU allocation can result in some signaling processing workloads sharing a logical CPU core with data plane processing workloads. This results in session creation failures and packet processing latency or failures at a moderate load. This issue has been fixed in this release.  |
+  | 5 | Local dashboards | Azure Private 5G Core local dashboards may show incorrect values in some graphs (e.g. session counts) after a power cycle of the server. This issue has been fixed in this release.  |
+
+## Known issues in the AP5GC 2211 release
+
+The following table provides a summary of known issues in this release.
+
+  |No.  |Feature  | Issue |
+  |-----|-----|-----|
+  | 1 | Packet forwarding | If Azure Private 5G Core is deployed into a network where the gNodeB is on the same subnet as the Packet Core's N3 interface address (that is, there is no gateway router between them) then all downstream traffic is broken.   | 
+  | 2 | Local dashboards | In deployments with multiple Data Networks, **UPF Downstream CPU Utilization** is incorrectly reported on the local dashboards when running calls using single Data Network.  | 
+  | 3 | Local dashboards  | In some scenarios, the local dashboards don't show session rejection under the **Device and Session Statistics** panel if Session Establishment requests are rejected due to invalid PDU type (e.g. IPv6 when only IPv4 supported).   | 
+
+
+## Known issues from previous releases
+
+The following table provides a summary of known issues carried over from the previous releases. 
+
+  |No.  |Feature  | Issue |
+  |-----|-----|-----|
+  | 1 | Policy configuration  | Azure Private 5G Core may ignore non-default QoS and Policy configuration when handling 4G subscribers.  | 
+  | 2 | Packet forwarding  | Azure Private 5G Core local dashboards may show incorrect values in some graphs (e.g. session counts) after a power cycle of the server.   | 
+  | 3 | Local dashboards  | Azure Private 5G Core local dashboards may show incorrect values in some graphs (e.g. session counts) after a power cycle of the server.   | 
+
+
+
+
+## Next steps
+
+- [Upgrade the packet core instance in a site - Azure portal](upgrade-packet-core-azure-portal.md)
+- [Upgrade the packet core instance in a site - ARM template](upgrade-packet-core-arm-template.md)

articles/private-5g-core/toc.yml

@@ -10,7 +10,9 @@ items:
     href: whats-new.md
   - name: Packet core release notes
     items:
-    - name: 2210 - Current
+    - name: 2211 - Current
+      href: azure-private-5g-core-release-notes-2211.md
+    - name: 2210
       href: azure-private-5g-core-release-notes-2210.md
     - name: 2209
       href: azure-private-5g-core-release-notes-2209.md

articles/private-5g-core/whats-new.md

@@ -156,6 +156,14 @@ The following is a comparison of templates using the 2022-04-01-preview and the
 
 ---
 
+### Packet core 2211
+
+**Type:** New release
+
+**Date available:** December 5, 2022
+
+The 2211 release for the Azure Private 5G Core packet core is now available. For more information, see [Azure Private 5G Core 2211 release notes](azure-private-5g-core-release-notes-2211.md).
+
 ### Multiple data networks
 
 **Type:** Feature
@@ -166,11 +174,11 @@ You can now configure up to three Attached Data Networks for each Packet Core in
 
 The operator can provision UEs as subscribed in one or more Data Networks and apply Data Network-specific policy and QoS, allowing UEs to use multiple Layer 3 uplink networks selected based on policy or UE preference. 
 
-Each Data Network can have its own configuration for DNS, UE IP address pools, N6 IP configuration, and NAT. This concept also maps directly to 4G APNs. 
+Each Data Network can have its own configuration for DNS, UE IP address pools, N6 IP, and NAT. This concept also maps directly to 4G APNs. 
 
 This feature has the following limitations: 
 
-- Once more than a single Data Network is configured, further configuration changes require the packet core to be reinstalled.
+- Once more than a single Data Network is configured, further configuration changes require the packet core to be reinstalled. To ensure this reinstall happens only after you have made all your changes, you must follow the process for installing and modifying as described in the documentation.
 
 - VLAN separation of Data Networks is not supported. Only Layer 3 separation is supported (meaning you can't have overlapping IP address spaces across the Data Networks).