Skip to content

Commit eb612e4

Browse files
committed
tidy up merge
1 parent 944a3ea commit eb612e4

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

articles/private-5g-core/commission-cluster.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,8 +123,6 @@ You can input all the settings on this page before selecting **Apply** at the bo
123123
- Control plane access interface
124124
- User plane access interface
125125
- User plane data interface(s)
126-
127-
<<<<<<< HEAD
128126
You can name these networks yourself, but the name **must** match what you configure in the Azure portal when deploying Azure Private 5G Core. For example, you can use the names **N2**, **N3** and **N6-DN1**, **N6-DN2**, **N6-DN3** (for a 5G deployment with multiple data networks (DNs); just **N6** for a single DN deployment). You can optionally configure each virtual network with a virtual local area network identifier (VLAN ID) to enable layer 2 traffic separation. The following example is for a 5G multi-DN deployment without VLANs.
129127
:::zone pivot="ase-pro-2"
130128
3. Carry out the following procedure three times, plus once for each of the supplementary data networks (so five times in total if you have three data networks):

0 commit comments

Comments
 (0)