Merge pull request #275648 from robswain/vlan-trunking

Add VLAN trunking for HA

Author: Stacyrch140

articles/private-5g-core/collect-required-information-for-a-site.md

@@ -40,11 +40,7 @@ In this step, you'll create the mobile network site resource representing the ph
 
     :::image type="content" source="media/create-a-site/create-site-basics-tab.png" alt-text="Screenshot of the Azure portal showing the Basics configuration tab for a site resource.":::
 
-1. You'll now see the **Packet core** configuration tab.
-
-    :::image type="content" source="media/create-a-site/create-site-packet-core-tab.png" alt-text="Screenshot of the Azure portal showing the Packet core configuration tab for a site resource.":::
-
-1. In the **Packet core** section, set the fields as follows:
+1. You'll now see the **Packet core** configuration tab. Set the fields as follows:
 
     - Use the information you collected in [Collect packet core configuration values](collect-required-information-for-a-site.md#collect-packet-core-configuration-values) to fill out the **Technology type**, **Azure Stack Edge device**, and **Custom location** fields.
     - For a Highly Available (HA) deployment, specify the ASE two node cluster as the Azure Stack Edge device.
@@ -67,8 +63,6 @@ In this step, you'll create the mobile network site resource representing the ph
     - If you decided not to configure a DNS server, clear the **Specify DNS addresses for UEs?** checkbox.
     - If you decided to keep NAPT disabled, ensure you configure your data network router with static routes to the UE IP pools via the appropriate user plane data IP address for the corresponding attached data network.
 
-    :::image type="content" source="media/create-a-site/create-site-attach-data-network.png" alt-text="Screenshot of the Azure portal showing the Attach data network screen.":::
-
     Once you've finished filling out the fields, select **Attach**.
 :::zone-end
 :::zone pivot="ase-pro-2"
@@ -84,8 +78,6 @@ In this step, you'll create the mobile network site resource representing the ph
     - If you decided not to configure a DNS server, clear the **Specify DNS addresses for UEs?** checkbox.
     - If you decided to keep NAPT disabled, ensure you configure your data network router with static routes to the UE IP pools via the appropriate user plane data IP address for the corresponding attached data network.
 
-    :::image type="content" source="media/create-a-site/create-site-attach-data-network.png" alt-text="Screenshot of the Azure portal showing the Attach data network screen.":::
-
     Once you've finished filling out the fields, select **Attach**.
 :::zone-end
 

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

@@ -62,7 +62,7 @@ To perform packet capture using the command line, you must:
 
 1. Once the packet capture has completed, the AP5GC online service will save the output at the provided storage account URL.
 
-    In HA deployments, two packet capture files will be uploaded, one for each node. The files will be labelled with a `0` or a `1`, corresponding to the `core-mec-dp-0` or `core-mec-dp-1` pod. If one packet capture fails, the status page will show an error, but the successful capture results will upload as normal.
+    In HA deployments, two packet capture files will be uploaded, one for each node. The files will be labeled with a `0` or a `1`, corresponding to the `core-mec-dp-0` or `core-mec-dp-1` pod. If one packet capture fails, the status page will show an error, but the successful capture results will upload as normal.
 
 1. To download the packet capture output, you can use the **Copy to clipboard** button in the **Storage** or **File name** columns to copy those details and then paste them into the **Search** box in the portal. To download the output, right-click the file and select **Download**.
 
@@ -83,19 +83,17 @@ To perform packet capture using the command line, you must:
     mect list
     ```
 
-    This should report a single interface on the control plane network (N2), a single interface on the access network (N3) and an interface for each attached data network (N6). For example:
+    This should report a single interface on the control plane network (N2), a single interface on the access network (N3) and a single interface for the core network (N6).
 
     ```azurecli
     n2trace
     n3trace
-    n6trace0 (Data Network: internet)
-    n6trace1 (Data Network: enterprise)
-    n6trace2 (Data Network: test)
+    n6trace
     ```
-
 1. Run `mectdump` with any parameters that you would usually pass to tcpdump. In particular, `-i` to specify the interface, and `-w` to specify where to write to. Close the tool when finished by pressing <kbd>Ctrl + C</kbd>. The following examples are common use cases:
-    - To run capture packets on all interfaces, run `mectdump -i any -w any.pcap`
-    - To run capture packets for the N3 interface and the N6 interface for a single data network, enter the MEC-DP troubleshooter pod in two separate windows. In one window run `mectdump -i n3trace -w n3.pcap` and in the other window run `mectdump -i <N6 interface> -w n6.pcap` (use the N6 interface for the data network as identified in step 2).
+    - To capture packets on all interfaces, run `mectdump -i any -w any.pcap`
+    - To capture packets for the N3 interface and the N6 interface for a single data network, enter the MEC-DP troubleshooter pod in two separate windows. In one window run `mectdump -i n3trace -w n3.pcap` and in the other window run `mectdump -i n6trace -w n6.pcap`. To select an individual data network, filter by VLAN ID.
+
 
     > [!IMPORTANT]
     > Packet capture files might be large, particularly when running packet capture on all interfaces. Specify filters when running packet capture to reduce the file size - see the tcpdump documentation for the available filters.