Skip to content

Commit 3c40cb2

Browse files
committed
add column header
1 parent a56782f commit 3c40cb2

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -42,12 +42,12 @@ 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. |
5151
| 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. |
5252

5353
## Next steps

0 commit comments

Comments
 (0)