Skip to content

Commit 98ecf8a

Browse files
committed
moved wording of port4 or 6 ip address to before per-DN stuff
1 parent 2a49a07 commit 98ecf8a

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

articles/private-5g-core/complete-private-mobile-network-prerequisites.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -102,14 +102,6 @@ Depending on your networking requirements (for example, if a limited set of subn
102102

103103
### Data networks
104104

105-
Allocate the following IP addresses for each data network in the site:
106-
107-
- Network address in CIDR notation.
108-
- Default gateway.
109-
- One IP address for the user plane interface.
110-
- For 5G, this is the N6 interface
111-
- For 4G, this is the SGi interface.
112-
- For combined 4G and 5G, this is the N6/SGi interface.
113105
:::zone pivot="ase-pro-2"
114106

115107
- One IP address for port 4 on the Azure Stack Edge Pro GPU device.
@@ -119,6 +111,15 @@ Allocate the following IP addresses for each data network in the site:
119111
- One IP address for port 6 on the Azure Stack Edge Pro GPU device.
120112
:::zone-end
121113

114+
Allocate the following IP addresses for each data network in the site:
115+
116+
- Network address in CIDR notation.
117+
- Default gateway.
118+
- One IP address for the user plane interface.
119+
- For 5G, this is the N6 interface
120+
- For 4G, this is the SGi interface.
121+
- For combined 4G and 5G, this is the N6/SGi interface.
122+
122123
### VLANs
123124

124125
You can optionally configure your Azure Stack Edge Pro device with virtual local area network (VLAN) tags. You can use this configuration to enable layer 2 traffic separation on the N2, N3 and N6 interfaces, or their 4G equivalents. For example, you might want to separate N2 and N3 traffic (which share a port on the ASE device) or separate traffic for each connected data network.

0 commit comments

Comments
 (0)