Skip to content

Commit 15c7f38

Browse files
v-dirichardsv-dirichards
authored
Merge pull request #229950 from robswain/2202-release-notes
2302 release notes
2 parents ec60f68 + 3c40cb2 commit 15c7f38

File tree

5 files changed

+88
-7
lines changed

5 files changed

+88
-7
lines changed

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

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -42,12 +42,13 @@ The following table provides a summary of issues fixed in this release.
4242

4343
The following table provides a summary of known issues carried over from the previous releases.
4444

45-
|No. |Feature | Issue |
46-
|-----|-----|-----|
47-
| 1 | Policy configuration | Azure Private 5G Core may ignore non-default QoS and Policy configuration when handling 4G subscribers. |
48-
| 2 | Packet forwarding | Azure Private 5G Core may not forward buffered packets if NAT is enabled.  |
49-
| 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).  |
50-
| 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. |
45+
|No. |Feature | Issue | Workaround/comments |
46+
|-----|-----|-----|-----|
47+
| 1 | Policy configuration | Azure Private 5G Core may ignore non-default QoS and Policy configuration when handling 4G subscribers. | Not applicable. |
48+
| 2 | Packet forwarding | Azure Private 5G Core may not forward buffered packets if NAT is enabled. | Not applicable. |
49+
| 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). | Not applicable. |
50+
| 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. | Not applicable. |
51+
| 5 | Install/upgrade | Changing the technology type of a deployment from 4G (EPC) to 5G using upgrade or site delete and add is not supported. | Please contact support for the required steps to change the technology type. |
5152

5253
## Next steps
5354

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

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
title: Azure Private 5G Core 2302 release notes
3+
description: Discover what's new in the Azure Private 5G Core 2302 release
4+
author: b-branco
5+
ms.author: biancabranco
6+
ms.service: private-5g-core
7+
ms.topic: release-notes
8+
ms.date: 01/31/2023
9+
---
10+
11+
# Azure Private 5G Core 2302 release notes
12+
13+
The following release notes identify the new features, critical open issues, and resolved issues for the 2302 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, please review the information contained in these release notes.
14+
15+
This article applies to the AP5GC 2302 release (PMN-2302-0). This release is compatible with the ASE Pro GPU running the ASE 2301 release, and is supported by the 2022-04-01-preview and 2022-11-01 [Microsoft.MobileNetwork](/rest/api/mobilenetwork) API versions.
16+
17+
## Support
18+
19+
The default support lifetime for a packet core version is roughly two calendar months from release.
20+
21+
The support lifetime for version 2302 will end on April 30, 2023. Please be prepared to plan your packet core upgrade to a future version before 2302 goes out of support on this date.
22+
23+
## What's new
24+
25+
- **Rollback** - This feature allows you to easily revert to a previous packet core version if you encounter issues after upgrading the packet core. For details, see [Rollback (portal)](upgrade-packet-core-azure-portal.md#rollback) or [Rollback (ARM)](upgrade-packet-core-arm-template.md#rollback).
26+
27+
## Issues fixed in the AP5GC 2302 release
28+
29+
The following table provides a summary of issues fixed in this release.
30+
31+
|No. |Feature | Issue |
32+
|-----|-----|-----|
33+
| 1 | 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 them to be dropped. This issue has been fixed in this release. |
34+
35+
## Known issues in the AP5GC 2302 release
36+
37+
|No. |Feature | Issue | Workaround/comments |
38+
|-----|-----|-----|-----|
39+
| 1 | 4G/5G signaling | Modifications to the Attached Data Network resource in an existing deployment may cause service disruption unless the packet core is reinstalled. | Reinstall the packet core. |
40+
| 2 | Packet forwarding | In scenarios of sustained high load (for example, continuous setup of 100s of TCP flows per second) combined with NAT pinhole exhaustion, AP5GC can encounter a memory leak, leading to a short period of service disruption resulting in some call failures. | In most cases, the system will recover automatically and be ready to handle new requests after a few seconds' disruption. UEs will need to re-establish any dropped connections. |
41+
| 3 | 4G/5G signaling | In some cases the Azure Private 5G Core reports successful installation even when the underlying platform or networking is misconfigured. | Not applicable. |
42+
43+
## Known issues from previous releases
44+
45+
The following table provides a summary of known issues carried over from the previous releases.
46+
47+
|No. |Feature | Issue | Workaround/comments |
48+
|-----|-----|-----|-----|
49+
| 1 | Packet forwarding | Azure Private 5G Core may not forward buffered packets if NAT is enabled. | Not applicable. |
50+
| 2 | 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). | Not applicable. |
51+
| 3 | 4G/5G signaling | In rare scenarios of continuous high load over several days on a 4G multi-data network setup, the packet core may experience slight disruption resulting in some call failures. | The packet core will resume operations within a few seconds. |
52+
| 4 | Install/upgrade | Changing the technology type of a deployment from 4G (EPC) to 5G using upgrade or site delete and add is not supported. | Please contact support for the required steps to change the technology type. |
53+
54+
## Next steps
55+
56+
- [Upgrade the packet core instance in a site - Azure portal](upgrade-packet-core-azure-portal.md)
57+
- [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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@ The following table provides information on which versions of the ASE device are
1818

1919
| Packet core version | Compatible ASE versions |
2020
|-----|-----|
21+
| 2302 | 2301 |
2122
| 2301 | 2210, 2301 |
2223
| 2211 | 2210 |
2324
| 2210 | 2209, 2210 |

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,9 @@ items:
1010
href: whats-new.md
1111
- name: Packet core release notes
1212
items:
13-
- name: 2301 - Current
13+
- name: 2302 - Current
14+
href: azure-private-5g-core-release-notes-2302.md
15+
- name: 2301
1416
href: azure-private-5g-core-release-notes-2301.md
1517
- name: 2211
1618
href: azure-private-5g-core-release-notes-2211.md

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

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,26 @@ To help you stay up to date with the latest developments, this article covers:
2222

2323
This page is updated regularly with the latest developments in Azure Private 5G Core.
2424

25+
## February 2023
26+
27+
### Packet core 2302
28+
29+
**Type:** New release
30+
31+
**Date available:** March 6, 2023
32+
33+
The 2302 release for the Azure Private 5G Core packet core is now available. For more information, see [Azure Private 5G Core 2302 release notes](azure-private-5g-core-release-notes-2302.md).
34+
35+
### Rollback
36+
37+
**Type:** New feature
38+
39+
**Date available:** February 16, 2023
40+
41+
This feature allows you to easily revert to a previous packet core version if you encounter issues after upgrading the packet core.
42+
43+
For details, see [Rollback (portal)](upgrade-packet-core-azure-portal.md#rollback) or [Rollback (ARM)](upgrade-packet-core-arm-template.md#rollback).
44+
2545
## January 2023
2646

2747
### Packet core 2301

0 commit comments

Comments
 (0)