note VLAN trunking mandatory for HA

Author: robswain

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

@@ -77,19 +77,19 @@ You can input all the settings on this page before selecting **Apply** at the bo
     - User plane access interface
     - User plane data interface(s)  
 
-    You can name these networks yourself, but the name **must** match what you configure in the Azure portal when deploying Azure Private 5G Core. Under the recommended setup of vlan-trunking mode, you have **one single** N6 virtual network with no IP information. VLAN and IP information is done when configuring the mobile network. With this setup, you could use the names **N2**, **N3** and **N6**. 
+    You can name these networks yourself, but the name **must** match what you configure in the Azure portal when deploying Azure Private 5G Core. If you are using VLAN trunking (required for HA deployments), you have **one single** N6 virtual network with no IP information. VLAN and IP information is done when configuring the mobile network. With this setup, you could use the names **N2**, **N3** and **N6**.
 
     Under Access VLAN or non-VLAN mode, there is an N6 virtual network for each attached data network. You could use the names **N2**, **N3** and up to ten **N6-DNX** (where **X** is the DN number 1-10 in a multiple DN deployment; or 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.
 :::zone pivot="ase-pro-2"
-3. If using the recommended setup of VLAN-trunking mode, carry out the following procedure 3 times:
+3. If you are using VLAN trunking (required for HA deployments), carry out the following procedure 3 times:
     1. Select **Add virtual network** and fill in the side panel:
         - **Virtual switch**: select **vswitch-port3** for N2 and N3. Select **vswitch-port4** for N6.
         - **Name**: *N2*, *N3*, or *N6*.
         - **VLAN type**: Trunk VLAN
         - **Allowed VLAN ID Range**: Fill in the set of VLAN-IDs you want to configure.
     2. Select **Modify** to save the configuration for this virtual network.
     3. Select **Apply** at the bottom of the page and wait for the notification (a bell icon) to confirm that the settings have been applied. Applying the settings will take approximately 8 minutes. 
-4. If using Access VLAN or non-VLAN mode, carry out the following procedure three times, plus once for each of the supplementary data networks (twelve times in total if you have the maximum ten data networks):
+4. If you are using Access VLAN or non-VLAN mode, carry out the following procedure three times, plus once for each of the supplementary data networks (twelve times in total if you have the maximum ten data networks):
     > [!IMPORTANT]
     > If you are using port 3 for data networks, we recommend that it is used for the lowest expected load.
     1. Select **Add virtual network** and fill in the side panel:
@@ -107,15 +107,15 @@ You can input all the settings on this page before selecting **Apply** at the bo
   :::image type="content" source="media/commission-cluster/commission-cluster-advanced-networking-ase-2.png" alt-text="Screenshot showing Advanced networking, with a table of virtual switch information and a table of virtual network information.":::
 :::zone-end
 :::zone pivot="ase-pro-gpu"
-3. If using the recommended setup of VLAN-trunking mode, carry out the following procedure 3 times:
+3. If you are using VLAN trunking (required for HA deployments), carry out the following procedure 3 times:
     1. Select **Add virtual network** and fill in the side panel:
         - **Virtual switch**: select **vswitch-port5** for N2 and N3. Select **vswitch-port6** for N6.
         - **Name**: *N2*, *N3*, or *N6*.
         - **VLAN type**: Trunk VLAN
         - **Allowed VLAN ID Range**: Fill in the set of VLAN-IDs you want to configure.
     2. Select **Modify** to save the configuration for this virtual network.
     3. Select **Apply** at the bottom of the page and wait for the notification (a bell icon) to confirm that the settings have been applied. Applying the settings will take approximately 8 minutes. 
-4. If using Access VLAN or non-VLAN mode, carry out the following procedure three times, plus once for each of the supplementary data networks (twelve times in total if you have the maximum ten data networks):
+4. If you are using Access VLAN or non-VLAN mode, carry out the following procedure three times, plus once for each of the supplementary data networks (twelve times in total if you have the maximum ten data networks):
     > [!IMPORTANT]
     > If you are using port 5 for data networks, we recommend that it is used for the lowest expected load.
     1. Select **Add virtual network** and fill in the side panel:
@@ -145,16 +145,16 @@ In the local Azure Stack Edge UI, go to the **Kubernetes (Preview)** page. You'l
       1. Enter one IP address in a range for the service IP address, also on the management network. This will be used for accessing local monitoring tools for the packet core instance.
       1. Select **Modify** at the bottom of the panel to save the configuration.
     > [!IMPORTANT]
-    > In VLAN-trunking mode, no IP configuration is done for the virtual networks at this point. IP configuration is done when configuring the mobile network.
-1. Under **Virtual network**, select a virtual network. In VLAN-trunking mode, this will be either **N2**, **N3** and **N6**. Otherwise, choose from **N2**, **N3**, **N6-DNX** (where *X* is the DN number 1-10). In the side panel:
-      1. Enable the virtual network for Kubernetes and add a pool of IP addresses. If **NOT** in VLAN-trunking mode, also add a pool of IP addresses: 
+    > If you are using VLAN trunking (required for HA deployments), no IP configuration is done for the virtual networks at this point. IP configuration is done when configuring the mobile network.
+1. Under **Virtual network**, select a virtual network. In VLAN trunking mode, this will be either **N2**, **N3** and **N6**. Otherwise, choose from **N2**, **N3**, **N6-DNX** (where *X* is the DN number 1-10). In the side panel:
+      1. Enable the virtual network for Kubernetes and add a pool of IP addresses. If **NOT** in VLAN trunking mode, also add a pool of IP addresses: 
         1. For a standard deployment, add a range of one IP address for the appropriate address (N2, N3, or N6-DNX as collected earlier). For example, *10.10.10.20-10.10.10.20*.
         1. For an HA deployment, add a range of two IP addresses for each virtual network, where the N2 and N3 pod IP addresses are in the local access subnet and the N6 pod IP addresses are in the appropriate local data subnet.
       1. Repeat for each of the N2, N3, and N6-DNX virtual networks.
       1. Select **Modify** at the bottom of the panel to save the configuration.
 1. Select **Apply** at the bottom of the page and wait for the settings to be applied. Applying the settings will take approximately 5 minutes.
 
-The page should now look like the following image (in VLAN-trunking mode):
+The page should now look like the following image (in VLAN trunking mode):
 
 :::image type="content" source="media/commission-cluster/commission-cluster-kubernetes-preview-enabled.png" alt-text="Screenshot showing Kubernetes (Preview) with two tables. The first table is called Compute virtual switch and the second is called Virtual network. A green tick shows that the virtual networks are enabled for Kubernetes.":::
 

articles/private-5g-core/private-mobile-network-design-requirements.md

@@ -48,7 +48,7 @@ This section outlines some decisions you should consider when designing your net
 :::zone pivot="ase-pro-gpu"
 When deployed on Azure Stack Edge Pro GPU (ASE), AP5GC uses physical port 5 for access signaling and data (5G N2 and N3 reference points/4G S1 and S1-U reference points) and port 6 for core data (5G N6/4G SGi reference points).
 
-The recommended setup for your deployment is VLAN-trunking mode, where data networks are separated by VLANs. In this setup, all core data uses port 6. If not in VLAN-trunking mode and more than six data networks are configured, port 5 is used for core data for the remaining data networks.
+For HA deployments, you must use VLAN trunking, where data networks are separated by VLANs. In this setup, all core data uses port 6. If you are not using VLAN trunking and more than six data networks are configured, port 5 is used for core data for the remaining data networks.
 
 AP5GC supports deployments with or without layer 3 routers on ports 5 and 6. This is useful for avoiding extra hardware at smaller edge sites.
 
@@ -59,7 +59,7 @@ AP5GC supports deployments with or without layer 3 routers on ports 5 and 6. Thi
 :::zone pivot="ase-pro-2"
 When deployed on Azure Stack Edge 2 (ASE 2), AP5GC uses physical port 3 for access signaling and data (5G N2 and N3 reference points/4G S1 and S1-U reference points) and port 4 for core data (5G N6/4G SGi reference points). 
 
-The recommended setup for your deployment is in VLAN-trunking mode, where data networks are separated by VLANs. In this setup, all core data uses port 4. If not in VLAN-trunking mode and more than six data networks are configured, port 3 is used for core data for the remaining data networks.
+For HA deployments, you must use VLAN trunking, where data networks are separated by VLANs. In this setup, all core data uses port 6. If you are not using VLAN trunking and more than six data networks are configured, port 3 is used for core data for the remaining data networks.
 
 AP5GC supports deployments with or without layer 3 routers on ports 3 and 4. This is useful for avoiding extra hardware at smaller edge sites.
 
@@ -88,7 +88,7 @@ There are multiple ways to set up your network for use with AP5GC. The exact set
   :::image type="content" source="media/private-mobile-network-design-requirements/layer-2-network.png" alt-text="Diagram of a layer 2 network." lightbox="media/private-mobile-network-design-requirements/layer-2-network.png":::
 
 - Layer 3 network with multiple data networks
-  - The recommended setup for deployments with multiple data networks is to use VLAN trunking. In this setup, AP5GC can support up to ten attached data newtorks, each with its own configuration for Domain Name System (DNS), UE IP address pools, N6 IP configuration, and NAT. You can provision UEs as subscribed in one or more data networks and apply data network-specific policy and quality of service (QoS) configuration.
+  - The recommended setup for deployments with multiple data networks is to use VLAN trunking. In this setup, AP5GC can support up to ten attached data networks, each with its own configuration for Domain Name System (DNS), UE IP address pools, N6 IP configuration, and NAT. You can provision UEs as subscribed in one or more data networks and apply data network-specific policy and quality of service (QoS) configuration. VLAN trunking is required for HA deployments.
   - In this topology, there is a single N6 virtual network on the ASE with no IP information. All VLAN and IP configuration is done when configuring each attached data network.
   :::image type="content" source="media/private-mobile-network-design-requirements/layer-3-network-with-vlan-trunking.png" alt-text="Diagram of a layer 3 network with VLAN trunking." lightbox="media/private-mobile-network-design-requirements/layer-3-network-with-vlan-trunking.png":::
 
@@ -104,8 +104,8 @@ There are multiple ways to set up your network for use with AP5GC. The exact set
   :::image type="content" source="media/private-mobile-network-design-requirements/layer-3-network-with-vlans.png" alt-text="Diagram of layer 3 network topology with V L A N s." lightbox="media/private-mobile-network-design-requirements/layer-3-network-with-vlans.png":::
 
 - Layer 3 network with 7-10 data networks without VLAN trunking.
-  - With VLAN trunking, all DNs are routed through port 6. 
-  - Without VLAN trunking, If you want to deploy more than six VLAN-separated data networks, the additional (up to four) data networks must be deployed on ASE port 5. This requires one shared switch or router that carries both access and core traffic. VLAN tags can be assigned as required to N2, N3 and each of the N6 data networks.
+  - With VLAN trunking, all DNs are routed through port 6. VLAN trunking is required for HA deployments.
+  - Without VLAN trunking, if you want to deploy more than six VLAN-separated data networks, the additional (up to four) data networks must be deployed on ASE port 5. This requires one shared switch or router that carries both access and core traffic. VLAN tags can be assigned as required to N2, N3 and each of the N6 data networks.
   - No more than six data networks can be configured on the same port.
   - For optimal performance, the data networks with the highest expected load should be configured on port 6.
   :::image type="content" source="media/private-mobile-network-design-requirements/layer-3-network-with-additional-dns.png" alt-text="Diagram of layer 3 network topology with 10 data networks." lightbox="media/private-mobile-network-design-requirements/layer-3-network-with-vlans.png":::
@@ -126,7 +126,7 @@ There are multiple ways to set up your network for use with AP5GC. The exact set
   :::image type="content" source="media/private-mobile-network-design-requirements/layer-2-network.png" alt-text="Diagram of a layer 2 network." lightbox="media/private-mobile-network-design-requirements/layer-2-network.png":::
 
 - Layer 3 network with multiple data networks
-  - The recommended setup for deployments with multiple data networks is to use VLAN trunking. In this setup, AP5GC can support up to ten attached data newtorks, each with its own configuration for Domain Name System (DNS), UE IP address pools, N6 IP configuration, and NAT. You can provision UEs as subscribed in one or more data networks and apply data network-specific policy and quality of service (QoS) configuration.
+  - The recommended setup for deployments with multiple data networks is to use VLAN trunking. In this setup, AP5GC can support up to ten attached data networks, each with its own configuration for Domain Name System (DNS), UE IP address pools, N6 IP configuration, and NAT. You can provision UEs as subscribed in one or more data networks and apply data network-specific policy and quality of service (QoS) configuration. VLAN trunking is required for HA deployments.
   - In this topology, there is a single N6 virtual network on the ASE with no IP information. All VLAN and IP configuration is done when configuring each attached data network.
   :::image type="content" source="media/private-mobile-network-design-requirements/layer-3-network-with-vlan-trunking.png" alt-text="Diagram of a layer 3 network with VLAN trunking." lightbox="media/private-mobile-network-design-requirements/layer-3-network-with-vlan-trunking.png":::
 
@@ -144,7 +144,7 @@ There are multiple ways to set up your network for use with AP5GC. The exact set
   :::image type="content" source="media/private-mobile-network-design-requirements/layer-3-network-with-vlans-azure-stack-edge-2.png" alt-text="Diagram of layer 3 network topology with V L A N s." lightbox="media/private-mobile-network-design-requirements/layer-3-network-with-vlans-azure-stack-edge-2.png":::
 
 - Layer 3 network with 7-10 data networks without VLAN trunking.
-  - Without VLAN trunking, If you want to deploy more than six VLAN-separated data networks, the additional (up to four) data networks must be deployed on ASE port 3. This requires one shared switch or router that carries both access and core traffic. VLAN tags can be assigned as required to N2, N3 and each of the N6 data networks.
+  - Without VLAN trunking, if you want to deploy more than six VLAN-separated data networks, the additional (up to four) data networks must be deployed on ASE port 3. This requires one shared switch or router that carries both access and core traffic. VLAN tags can be assigned as required to N2, N3 and each of the N6 data networks. VLAN trunking is required for HA deployments.
   - No more than six data networks can be configured on the same port.
   - For optimal performance, the data networks with the highest expected load should be configured on port 4.