Merge pull request #246796 from PaulCarterMicrosoft/main

AP5GC 2307 Release

Author: v-regandowner

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

@@ -0,0 +1,58 @@
+---
+title: Azure Private 5G Core 2307 release notes
+description: Discover what's new in the Azure Private 5G Core 2307 release
+author: paulcarter
+ms.author: paulcarter
+ms.service: private-5g-core
+ms.topic: release-notes
+ms.date: 07/31/2023
+---
+
+# Azure Private 5G Core 2307 release notes
+
+The following release notes identify the new features, critical open issues, and resolved issues for the 2307 release of Azure Private 5G Core (AP5GC). The release notes are continuously updated, with critical issues requiring a workaround added as they’re discovered. Before deploying this new version, review the information contained in these release notes.
+
+This article applies to the AP5GC 2307 release (PMN-2307-0). This release is compatible with the ASE Pro 1 GPU and ASE Pro 2 running the ASE 2303 release, and supports the 2023-06-01, 2022-11-01-preview and 2022-04-01 [Microsoft.MobileNetwork](/rest/api/mobilenetwork) API versions.
+
+## Support lifetime
+
+Packet core versions are supported until two subsequent versions have been released (unless otherwise noted). This is typically two months after the release date. You should plan to upgrade your packet core in this time frame to avoid losing support.
+
+## What's new
+### UE usage tracking
+The UE usage tracking messages in Azure Event Hubs are now encoded in AVRO file container format, which enables you to consume these events via Power BI or Azure Stream Analytics (ASA). If you want to enable this feature for your deployment, contact your support representative.
+
+### Unknown User cause code mapping in 4G deployments
+In this release the 4G NAS EMM cause code for “unknown user” (subscriber not provisioned on AP5GC) changes to “no-suitable-cells-in-ta-15” by default. This provides better interworking in scenarios where a single PLMN is used for multiple, independent mobile networks.
+
+## Issues fixed in the AP5GC 2307 release
+
+The following table provides a summary of issues fixed in this release.
+
+  |No.  |Feature  | Issue |
+  |-----|-----|-----|
+  | 1 | Local distributed tracing | The distributed tracing web GUI fails to display & decode some fields of 4G NAS messages. Specifically, 'Initial Context Setup Request' and 'Attach Accept messages' information elements.
+  | 2 | 4G/5G Signaling | Removal of static or dynamic UE IP pool as part of attached data network modification on an existing AP5GC setup still requires reinstall of packet core.
+  | 3 | Install/Upgrade | In some cases, the packet core reports successful installation even when the underlying platform or networking is misconfigured. 
+  | 4 | 4G/5G Signaling | AP5GC may intermittently fail to recover after underlying platform is rebooted and may require another reboot to recover.
+  | 5 | Packet Forwarding | Azure Private 5G Core may not forward buffered packets if NAT is enabled | 
+
+## Known issues in the AP5GC 2307 release
+  |No.  |Feature  | Issue | Workaround/comments |
+  |-----|-----|-----|-----|
+  | 1 | Azure Active Directory | When a web proxy is enabled on the Azure Stack Edge appliance that the packet core is running on and Azure Active Directory is used to authenticate access to AP5GC Local Dashboards, the traffic to Azure Active Directory does not transmit via the web proxy. If there's a firewall blocking traffic that does not go via the web proxy then enabling Azure Active Directory causes the packet core install to fail. | Disable Azure Active Directory and use password based authentication to authenticate access to AP5GC Local Dashboards instead. |
+  | 2 | Install/Upgrade | Transient issues with the Arc Connected Kubernetes Cluster resource might trigger errors in packet core operations such as upgrade, rollback or reinstall.  | Check the availability of the Kubernetes cluster resource: navigate to the resource in the Portal and check the Resource Health. Ensure it's available and retry the operation. |  
+
+## Known issues from previous releases
+
+The following table provides a summary of known issues carried over from the previous releases.
+
+  |No.  |Feature  | Issue | Workaround/comments |
+  |-----|-----|-----|-----|
+  | 1 | Local Dashboards | When a web proxy is enabled on the Azure Stack Edge appliance that the packet core is running on and Azure Active Directory is used to authenticate access to AP5GC Local Dashboards, the traffic to Azure Active Directory doesn't transmit via the web proxy. If there's a firewall blocking traffic that doesn't go via the web proxy then enabling Azure Active Directory causes the packet core install to fail. | Disable Azure Active Directory and use password based authentication to authenticate access to AP5GC Local Dashboards instead. |
+  
+
+## 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,6 +10,8 @@ items:
     href: whats-new.md
   - name: Packet core release notes
     items:
+    - name: 2376 - Current
+      href: azure-private-5g-core-release-notes-2307.md  
     - name: 2306 - Current
       href: azure-private-5g-core-release-notes-2306.md  
     - name: 2305

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

@@ -23,14 +23,21 @@ To help you stay up to date with the latest developments, this article covers:
 This page is updated regularly with the latest developments in Azure Private 5G Core.
 
 ## July 2023
+### Packet core 2307
+
+**Type:** New release
+
+**Date available:** July 31, 2023
+
+The 2307 release for the Azure Private 5G Core packet core is now available. For more information, see [Azure Private 5G Core 2307 release notes](azure-private-5g-core-release-notes-2307.md).
 
 ### 2023-06-01 API
 
 **Type:** New release
 
 **Date available:** July 19, 2023
 
-The 2023-06-01 ARM API release introduces the ability to configure several upcoming Azure Private 5G Core features. From July 19th, 2023-06-01 is the default API version for Azure Private 5G Core deployments.
+The 2023-06-01 ARM API release introduces the ability to configure several upcoming Azure Private 5G Core features. From July 19, 2023-06-01 is the default API version for Azure Private 5G Core deployments.
 
 If you use the Azure portal to manage your deployment and all your resources were created using the 2022-04-01-preview API or 2022-11-01, you don't need to do anything. Your portal will use the new API.
 
@@ -89,9 +96,9 @@ The 2305 release for the Azure Private 5G Core packet core is now available. For
 
 **Date available:** May 31, 2023
 
-New-MobileNetworkSite now supports an additional parameter that makes it easier to create a site and its dependant resources.
+New-MobileNetworkSite now supports a parameter that makes it easier to create a site and its dependant resources.
 
-For details, see [Create additional Packet Core instances for a site using the Azure portal](create-additional-packet-core.md).
+For details, see [Create more Packet Core instances for a site using the Azure portal](create-additional-packet-core.md).
 
 ### Multiple Packet Cores under the same Site
 
@@ -167,7 +174,7 @@ The Azure Private 5G Core online service now reports the provisioning status of
 
 **Date available:** January 31, 2023
 
-You can now gather diagnostics for a site remotely using the Azure portal. Diagnostics packages will be collected from the edge site and uploaded to an Azure storage account, which can be shared with AP5GC support or others for assistance with issues. Follow [Gather diagnostics using the Azure portal](gather-diagnostics.md) to gather a remote diagnostics package for an Azure Private 5G Core site using the Azure portal.
+You can now gather diagnostics for a site remotely using the Azure portal. Diagnostics packages are collected from the edge site and uploaded to an Azure storage account, which can be shared with AP5GC support or others for assistance with issues. Follow [Gather diagnostics using the Azure portal](gather-diagnostics.md) to gather a remote diagnostics package for an Azure Private 5G Core site using the Azure portal.
 
 ### West Europe region
 
@@ -193,9 +200,9 @@ The **Diagnose and solve problems** option in the left content menu can now prov
 
 **Date available:** December 16, 2022
 
-If you're experiencing issues with your packet core deployment, you can now reinstall the packet core to return it to a known state. Reinstalling the packet core deletes the existing packet core deployment and attempts to deploy the packet core at the edge with the existing site configuration. Already created **Site**-dependent resources such as the **Packet Core Control Plane**, **Packet Core Data Plane** and **Attached Data Network** will continue to be used in the deployment.
+If you're experiencing issues with your packet core deployment, you can now reinstall the packet core to return it to a known state. Reinstalling the packet core deletes the existing packet core deployment and attempts to deploy the packet core at the edge with the existing site configuration. Already created **Site**-dependent resources such as the **Packet Core Control Plane**, **Packet Core Data Plane** and **Attached Data Network** continue to be used in the deployment.
 
-You can check the installation state on the **Packet Core Control Plane** resource's overview page. Upon successful redeployment, the installation state will change from **Reinstalling** to either **Installed** or **Failed**, depending on the outcome. You can reinstall the packet core if the installation state is **Installed** or **Failed**.
+You can check the installation state on the **Packet Core Control Plane** resource's overview page. Upon successful redeployment, the installation state changes from **Reinstalling** to either **Installed** or **Failed**, depending on the outcome. You can reinstall the packet core if the installation state is **Installed** or **Failed**.
 
 If you attempt a reinstall after an upgrade, redeployment will be attempted with the upgraded packet core version. The reinstall is done using the latest packet core version currently defined in the ARM API version.
 
@@ -227,7 +234,7 @@ You can add a custom certificate to secure access to your local monitoring tools
 
 The 2022-11-01 ARM API release introduces the ability to configure several upcoming Azure Private 5G Core features. From December 12, 2022-11-01 is the default API version for Azure Private 5G Core deployments.
 
-If you use the Azure portal to manage your deployment and all your resources were created using the 2022-04-01-preview API, you don't need to do anything. Your portal will use the new API and any differences between the APIs are handled automatically.
+If you use the Azure portal to manage your deployment and all your resources were created using the 2022-04-01-preview API, you don't need to do anything. Your portal uses the new API and any differences between the APIs are handled automatically.
 
 If you use ARM templates and want to keep using your existing templates, follow [Upgrade your ARM templates to the 2022-11-01 API](#upgrade-your-arm-templates-to-the-2022-11-01-api) to upgrade your 2022-04-01-preview API templates to the 2022-11-01 API.