Merge pull request #225548 from b-branco/release-notes-2301

2301 release notes

Author: v-regandowner

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

@@ -50,6 +50,7 @@ The following table provides a summary of known issues in this release.
   | 10 | 4G/5G signaling  | In rare scenarios, Azure Private 5G Core may corrupt the internal state of a packet data session, resulting in subsequent changes to that packet data session failing.  | Reinstall the Packet Core.  |
   | 11 | 4G/5G signaling  | In scenarios when the establishment of a PDU session has failed, Azure Private 5G Core may not automatically release the session, and the UE may need to re-register.  | The UE should re-register.  |
   | 12 | 4G/5G signaling  | 4G UEs that require both circuit switched (CS) and packet switched (PS) network availability to successfully attach to Azure Private 5G Core may disconnect after a successful attach.  | Update/enhance the UEs to support PS only networks if possible, as CS isn't supported by Azure Private 5G Core. If it isn't possible to reconfigure the UEs, customer support can apply a low-level configuration tweak to Azure Private 5G Core to let these UEs believe there's a CS network available.  |
+  | 13 | Packet forwarding  | When Azure Private 5G Core has NAT enabled on a data network, approximately one in every 65,536 downlink packets sent to a UE will be emitted with an incorrect IP checksum, which will likely cause it to be dropped.  | 
 
 ## Next steps
 

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

@@ -53,6 +53,7 @@ The following table provides a summary of known issues carried over from the pre
   | 13 | 4G/5G Signaling  | In rare scenarios, due to a race condition triggered during a RAN disconnect/re-connect sequence, Azure Private 5G Core may fail to process incoming requests from the eNodeB or gNodeB.   | Reinstall the packet core.  |
   | 14 | Local dashboards  | On the packet core dashboards, the 4G interface panel doesn’t display the data.  | Select each panel’s edit button and select Data source again as Prometheus and select refresh to see the data. |
   | 15 | 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. | If sessions are released, UEs may need to re-connect with the system to use data services.  |
+  | 16 | Packet forwarding  | When Azure Private 5G Core has NAT enabled on a data network, approximately one in every 65,536 downlink packets sent to a UE will be emitted with an incorrect IP checksum, which will likely cause it to be dropped.  | 
 
 ## Next steps
 

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

@@ -40,6 +40,7 @@ The following table provides a summary of known issues carried over from the pre
   | 5 | Local dashboards  | Azure Private 5G Core local dashboards may show incorrect values in some graphs (for example, session counts) after a power cycle of the Azure Stack Edge server.  | Not applicable. |
   | 6 | Local dashboards  | The distributed tracing web GUI fails to display and decode some fields of 4G/5G NAS messages. Specifically, the *Request Type* and *DNN* information elements.  | Messages will have to be viewed from separate packet capture if needed.  |
   | 7 | Performance  | It has been observed very rarely that CPU allocation on an Azure Private 5G Packet Core deployment can result in some signaling processing workloads sharing a logical CPU core with data plane processing workloads, resulting in session creation failures or packet processing latency/failures at a moderate load.  | Redeploying the Azure Private 5G Packet Core may resolve the problematic CPU allocation.  |
+  | 8 | Packet forwarding  | When Azure Private 5G Core has NAT enabled on a data network, approximately one in every 65,536 downlink packets sent to a UE will be emitted with an incorrect IP checksum, which will likely cause it to be dropped.  | 
 
 ## Next steps
 

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

@@ -68,6 +68,7 @@ The following table provides a summary of known issues carried over from the pre
   |-----|-----|-----|
   | 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 may not forward buffered packets if NAT is enabled.   | 
+  | 3 | Packet forwarding  | When Azure Private 5G Core has NAT enabled on a data network, approximately one in every 65,536 downlink packets sent to a UE will be emitted with an incorrect IP checksum, which will likely cause it to be dropped.  | 
 
 
 ## Next steps

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

@@ -0,0 +1,55 @@
+---
+title: Azure Private 5G Core 2301 release notes 
+description: Discover what's new in the Azure Private 5G Core 2301 release
+author: b-branco
+ms.author: biancabranco
+ms.service: private-5g-core
+ms.topic: release-notes
+ms.date: 01/31/2023
+---
+
+# Azure Private 5G Core 2301 release notes
+
+The following release notes identify the new features, critical open issues, and resolved issues for the 2301 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 2301 release (PMN-2301-0). This release is compatible with the ASE Pro GPU running the ASE 2210 and ASE 2301 releases, 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 2301 will end on March 31, 2023. Please be prepared to plan your packet core upgrade to a future version before 2301 goes out of support on this date. 
+
+## What's new
+
+- **Azure Active Directory based login to SAS and Grafana** - Azure Private 5G Core provides the distributed tracing and packet core dashboards tools for monitoring your deployment at the edge. With this new feature available as part of this AP5GC release, you can access these tools using Azure Active Directory (Azure AD) authentication. We recommend setting up Azure AD authentication to improve security in your deployment, although the existing local username and password mechanism is also available. 
+
+  For details on configuring Azure AD based login after creating a site, see [Enable Azure Active Directory (Azure AD) for local monitoring tools](enable-azure-active-directory.md). You can also change the authentication type for existing sites by following [Modify the local access configuration in a site](modify-local-access-configuration.md).
+
+- **Multiple attached data networks improvements** – These improvements remove the need for additional manual steps when deploying or editing configuration for multiple data networks for your packet core. Additional guidance for configuring multiple data networks is also provided. All other support for multiple data network functionality remains as per the 2211 release. 
+
+- **User plane packet capture** - This feature delivers a new debugging tool for use during system turn-up. The tool allows you to capture packet trace on N3 and N6 interfaces in order to debug network connectivity. For more details, see [Perform data plane packet capture for a packet core instance](data-plane-packet-capture.md).
+
+## Issues fixed in the AP5GC 2301 release
+
+The following table provides a summary of issues fixed in this release.
+
+  |No.  |Feature  | Issue |
+  |-----|-----|-----|
+  | 1 | 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. This issue has been fixed in this release.   |
+
+## 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 may not forward buffered packets if NAT is enabled.   | 
+  | 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).   | 
+  | 4 | Packet forwarding  | When Azure Private 5G Core has NAT enabled on a data network, approximately one in every 65,536 downlink packets sent to a UE will be emitted with an incorrect IP checksum, which will likely cause it to be dropped.  | 
+
+## 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/azure-stack-edge-packet-core-compatibility.md

@@ -18,6 +18,7 @@ The following table provides information on which versions of the ASE device are
 
 | Packet core version  | Compatible ASE versions  |
 |-----|-----|
+| 2301 | 2210, 2301  |
 | 2211 | 2210  |
 | 2210 | 2209, 2210  |
 | 2209 | 2209  |

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

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