|
| 1 | +--- |
| 2 | +title: Azure Private 5G Core 2403 release notes |
| 3 | +description: Discover what's new in the Azure Private 5G Core 2403 release |
| 4 | +author: paulcarter |
| 5 | +ms.author: paulcarter |
| 6 | +ms.service: private-5g-core |
| 7 | +ms.topic: release-notes |
| 8 | +ms.date: 04/04/2023 |
| 9 | +--- |
| 10 | + |
| 11 | +# Azure Private 5G Core 2403 release notes |
| 12 | + |
| 13 | +The following release notes identify the new features, critical open issues, and resolved issues for the 2403 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. |
| 14 | + |
| 15 | +This article applies to the AP5GC 2403 release (2403.0-2). This release is compatible with the Azure Stack Edge Pro 1 GPU and Azure Stack Edge Pro 2 running the ASE 2403 release and supports the 2023-09-01, 2023-06-01 and 2022-11-01 [Microsoft.MobileNetwork](/rest/api/mobilenetwork) API versions. |
| 16 | + |
| 17 | +For more information about compatibility, see [Packet core and Azure Stack Edge compatibility](azure-stack-edge-packet-core-compatibility.md). |
| 18 | + |
| 19 | +For more information about new features in Azure Private 5G Core, see [What's New Guide](whats-new.md). |
| 20 | + |
| 21 | +## Support lifetime |
| 22 | + |
| 23 | +Packet core versions are supported until two subsequent versions are released (unless otherwise noted). You should plan to upgrade your packet core in this time frame to avoid losing support. |
| 24 | + |
| 25 | +### Currently supported packet core versions |
| 26 | +The following table shows the support status for different Packet Core releases and when they are expected to no longer be supported. |
| 27 | + |
| 28 | +| Release | Support Status | |
| 29 | +|---------|----------------| |
| 30 | +| AP5GC 2403 | Supported until AP5GC 2407 is released | |
| 31 | +| AP5GC 2310 | Supported until AP5GC 2404 is released | |
| 32 | +| AP5GC 2308 and earlier | Out of Support | |
| 33 | + |
| 34 | +## What's new |
| 35 | + |
| 36 | +### TCP Maximum Segment Size (MSS) Clamping |
| 37 | + |
| 38 | +TCP session initial setup messages that include a Maximum Segment Size (MSS) value, which controls the size limit of packets transmitted during the session. This feature involves setting this value where necessary to ensure packets are not too large for the core to transmit. This will reduce packet loss due to oversized packets arriving at the core's interfaces, and reduce the need for fragmentation and reassembly, which are costly procedures. |
| 39 | + |
| 40 | +## Issues fixed in the AP5GC 2403 release |
| 41 | + |
| 42 | +The following table provides a summary of issues fixed in this release. |
| 43 | + |
| 44 | + |No. |Feature | Issue | SKU Fixed In | |
| 45 | + |-----|-----|-----|-----|----| |
| 46 | + | 1 | Local distributed tracing | In Multi PDN session establishment/Release call flows with different DNs, the distributed tracing web GUI fails to display some of 4G NAS messages (Activate/deactivate Default EPS Bearer Context Request) and some S1AP messages (ERAB request, ERAB Release). | 2403.0-2 | |
| 47 | + | 2 | Packet Forwarding | A slight(0.01%) increase in packet drops is observed in latest AP5GC release installed on ASE Platform Pro2 with ASE-2309 for throughput higher than 3.0 Gbps. | 2403.0-2 | |
| 48 | + |
| 49 | +## Known issues in the AP5GC 2403 release |
| 50 | +<!--**TO BE UPDATED**> |
| 51 | + |No. |Feature | Issue | Workaround/comments | |
| 52 | + |-----|-----|-----|-----| |
| 53 | + | 1 | | | | |
| 54 | +<--> |
| 55 | + |
| 56 | +The following table provides a summary of known issues carried over from the previous releases. |
| 57 | + |
| 58 | + |No. |Feature | Issue | Workaround/comments | |
| 59 | + |-----|-----|-----|-----| |
| 60 | + | 1 | Local distributed tracing | 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. | |
| 61 | + |
| 62 | +## Next steps |
| 63 | + |
| 64 | +- [Upgrade the packet core instance in a site - Azure portal](upgrade-packet-core-azure-portal.md) |
| 65 | +- [Upgrade the packet core instance in a site - ARM template](upgrade-packet-core-arm-template.md) |
0 commit comments