Skip to content

Commit 10b594a

Browse files
v-regandownerv-regandowner
authored
Merge pull request #274867 from PaulCarterMicrosoft/main
Release Note updates for AP5GC2404 release.
2 parents 3da84c8 + d2e0765 commit 10b594a

File tree

5 files changed

+132
-11
lines changed

5 files changed

+132
-11
lines changed

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

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
---
2+
title: Azure Private 5G Core 2404 release notes
3+
description: Discover what's new in the Azure Private 5G Core 2404 release.
4+
author: paulcarter
5+
ms.author: paulcarter
6+
ms.service: private-5g-core
7+
ms.topic: release-notes
8+
ms.date: 05/09/2023
9+
---
10+
11+
# Azure Private 5G Core 2404 release notes
12+
13+
The following release notes identify the new features, critical open issues, and resolved issues for the 2404 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 2404 release (2404.0-3). This release is compatible with the Azure Stack Edge (ASE) Pro 1 GPU and Azure Stack Edge Pro 2 running the ASE 2403 release and supports the 2024-04-01, 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+
This release has been produced in accordance with Microsoft’s Secure Development Lifecycle, including processes for authorizing software changes, antimalware scanning, and scanning and mitigating security bugs and vulnerabilities.
22+
23+
## Support lifetime
24+
25+
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.
26+
27+
### Currently supported packet core versions
28+
The following table shows the support status for different Packet Core releases and when they're expected to no longer be supported.
29+
30+
| Release | Support Status |
31+
|---------|----------------|
32+
| AP5GC 2404 | Supported until AP5GC 2410 is released |
33+
| AP5GC 2403 | Supported until AP5GC 2408 is released |
34+
| AP5GC 2310 and earlier | Out of Support |
35+
36+
## What's new
37+
38+
### High Availability
39+
40+
We're excited to announce that AP5GC is now resilient to system failures when run on a two-node ASE cluster. Userplane traffic, sessions, and registrations are unaffected on failure of any single pod, physical interface, or ASE device.
41+
42+
### In Service Software Upgrade
43+
44+
In our commitment to continuous improvement and minimizing service impact we’re excited to announce that, upgrading from this version to a future release will include the capability for In-Service Software Upgrades (ISSU).
45+
46+
ISSU is supported for deployments on a 2-node cluster, software upgrades can be performed seamlessly, ensuring minimal disruption to your services. The upgrade completes with no loss of sessions or registrations and minimal packet loss and packet reordering. Should the upgrade fail, the software will automatically roll back to the previous version, also with minimal service disruption.
47+
48+
### Azure Resource Health
49+
50+
This feature allows you to monitor the health of your control plane resource using Azure Resource Health. Azure Resource Health is a service that processes and displays health signals from your resource and displays the health in the Azure portal. This service gives you a personalized dashboard showing all the times your resource was unavailable or in a degraded state, along with recommended actions to take to restore health.
51+
52+
For more information, on using Azure Resource Health to monitor the health of your deployment, see [Resource Health overview](../service-health/resource-health-overview.md).
53+
54+
### NAS Encryption
55+
56+
NAS (Non-Access-Stratum) encryption configuration determines the encryption algorithm applied to the management traffic between the UEs and the AMF(5G) or MME(4G). By default, for security reasons, Packet Core deployments are configured to preferentially use NEA2/EEA2 encryption.
57+
58+
You can change the preferred encryption level after deployment by [modifying the packet core configuration](modify-packet-core.md).
59+
60+
<!--## Issues fixed in the AP5GC 2404 release
61+
# NO FIXED ISSUES IN AP5GC2404
62+
63+
The following table provides a summary of issues fixed in this release.
64+
65+
|No. |Feature | Issue | SKU Fixed In |
66+
|-----|---------|-------|---------------|
67+
| 1 | | | |
68+
-->
69+
70+
## Known issues in the AP5GC 2404 release
71+
<!-- All known issues need a [customer facing summary](https://eng.ms/docs/strategic-missions-and-technologies/strategic-missions-and-technologies-organization/azure-for-operators/packet-core/private-mobile-network/azure-private-5g-core/cross-team/developmentprocesses/customer-facing-bug-summary)-->
72+
73+
|No. |Feature | Issue | Workaround/comments |
74+
|-----|---------|-------|---------------------|
75+
| 1 | Local distributed tracing | Local Dashboard Unavailable for 5-10 minutes after device failure | After the failure of a device in a two-node cluster, Azure Private 5G Core local dashboards won't be available for five to ten minutes. Once they recover, information for the time that they weren't available isn't shown. |
76+
| 2 | Local distributed tracing | When deployed on a two-node cluster, Azure Private 5G Core local dashboards can show an incorrect count for the number of PDU Sessions. | |
77+
78+
The following table provides a summary of known issues carried over from the previous releases.
79+
80+
|No. |Feature | Issue | Workaround/comments |
81+
|-----|-----|-----|-----|
82+
| 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. |
83+
84+
## Next steps
85+
86+
- [Upgrade the packet core instance in a site - Azure portal](upgrade-packet-core-azure-portal.md)
87+
- [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: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,8 @@ The following table provides information on which versions of the ASE device are
3030

3131
| Packet core version | ASE Pro GPU compatible versions | ASE Pro 2 compatible versions |
3232
|-----|-----|-----|
33-
| 2403 | 2403, 2405 | 2403, 2405 |
33+
| 2404 | 2403 | 2403 |
34+
| 2403 | 2403 | 2403 |
3435
| 2310 | 2309, 2312, 2403 | 2309, 2312, 2403 |
3536
| 2308 | 2303, 2309 | 2303, 2309 |
3637
| 2307 | 2303 | 2303 |

‎articles/private-5g-core/support-lifetime.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,6 @@ The following table shows the support status for different Packet Core releases
1919

2020
| Release | Support Status |
2121
|---------|----------------|
22-
| AP5GC 2403 | Supported until AP5GC 2407 is released |
23-
| AP5GC 2310 | Supported until AP5GC 2404 is released |
24-
| AP5GC 2308 and earlier | Out of Support |
22+
| AP5GC 2404 | Supported until AP5GC 2411 is released |
23+
| AP5GC 2403 | Supported until AP5GC 2408 is released |
24+
| AP5GC 2310 and earlier | Out of Support |

‎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: '2403 - Current'
13+
- name: '2404 - Current'
14+
href: azure-private-5g-core-release-notes-2404.md
15+
- name: '2403'
1416
href: azure-private-5g-core-release-notes-2403.md
1517
- name: '2310'
1618
href: azure-private-5g-core-release-notes-2310.md

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

Lines changed: 37 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: What's new in Azure Private 5G Core?
3-
description: Discover what's new in Azure Private 5G Core
3+
description: Discover what's new in Azure Private 5G Core.
44
author: paulcarter
55
ms.author: paulcarter
66
ms.service: private-5g-core
@@ -22,6 +22,37 @@ 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+
## May 2024
26+
### Packet core 2404
27+
28+
**Type:** New release
29+
30+
**Date available:** May 13, 2024
31+
32+
The 2404 release for the Azure Private 5G Core packet core is now available. For more information, see [Azure Private 5G Core 2404 release notes](azure-private-5g-core-release-notes-2404.md).
33+
34+
### High Availability
35+
36+
We're excited to announce that AP5GC is now resilient to system failures when run on a two-node ASE cluster. Userplane traffic, sessions, and registrations are unaffected on failure of any single pod, physical interface, or ASE device.
37+
38+
### In Service Software Upgrade
39+
40+
In our commitment to continuous improvement and minimizing service impact we’re excited to announce that when upgrading from this version to a future release, updates will include the capability for In-Service Software Upgrades (ISSU).
41+
42+
ISSU is supported for deployments on a 2-node cluster, software upgrades can be performed seamlessly, ensuring minimal disruption to your services. The upgrade completes with no loss of sessions or registrations and minimal packet loss and packet reordering. Should the upgrade fail, the software will automatically roll back to the previous version, also with minimal service disruption.
43+
44+
### Azure Resource Health
45+
46+
This feature allows you to monitor the health of your control plane resource using Azure Resource Health. Azure Resource Health is a service that processes and displays health signals from your resource and displays the health in the Azure portal. This service gives you a personalized dashboard showing all the times your resource was unavailable or in a degraded state, along with recommended actions to take to restore health.
47+
48+
For more information, on using Azure Resource Health to monitor the health of your deployment, see [Resource Health overview](../service-health/resource-health-overview.md).
49+
50+
### NAS Encryption
51+
52+
NAS (Non-Access-Stratum) encryption configuration determines the encryption algorithm applied to the management traffic between the UEs and the AMF(5G) or MME(4G). By default, for security reasons, Packet Core deployments will be configured to preferentially use NEA2/EEA2 encryption.
53+
54+
You can change the preferred encryption level after deployment by [modifying the packet core configuration](modify-packet-core.md).
55+
2556
## April 2024
2657
### Packet core 2403
2758

@@ -67,13 +98,13 @@ The SUPI (subscription permanent identifier) secret needs to be encrypted before
6798
For more information, see [Enable SUPI concealment](supi-concealment.md).
6899

69100
## February 2024
70-
### New Entra ID user role needed for distributed tracing tool
101+
### New Microsoft Entra ID user role needed for distributed tracing tool
71102

72103
**Type:** New feature
73104

74105
**Date available:** February 21, 2024
75106

76-
Access to the [distributed tracing](distributed-tracing.md) tool now requires a dedicated sas.user role in Microsoft Entra ID. This user is available from AP5GC version 4.2310.0-8, and required from AP5GC version 2402 onwards. If you are using Microsoft Entra ID authentication, you should create this user prior to upgrading to version 2402 to avoid losing access to the tracing tool. Entra ID access to the packet core dashboards is unchanged.
107+
Access to the [distributed tracing](distributed-tracing.md) tool now requires a dedicated sas.user role in Microsoft Entra ID. This user is available from AP5GC version 4.2310.0-8, and required from AP5GC version 2402 onwards. If you are using Microsoft Entra ID authentication, you should create this user prior to upgrading to version 2402 to avoid losing access to the tracing tool. Microsoft Entra ID access to the packet core dashboards is unchanged.
77108

78109
See [Enable Microsoft Entra ID for local monitoring tools](enable-azure-active-directory.md) for details.
79110

@@ -227,10 +258,10 @@ The 2306 release for the Azure Private 5G Core packet core is now available. For
227258
**Date available:** July 10, 2023
228259

229260
It's now possible to:
230-
- attach a new or existing data network
231-
- modify an attached data network's configuration
261+
- attach a new or existing data network.
262+
- modify an attached data network's configuration.
232263

233-
followed by a few minutes of downtime, but not a packet core reinstall.
264+
This is followed by a few minutes of downtime, but not a packet core reinstall.
234265

235266
For details, see [Modify a packet core instance](modify-packet-core.md).
236267

0 commit comments

Comments
 (0)