Removed isolation domain commands from quick-start and provided a link to how-to guide

Author: dramasamy

articles/operator-nexus/includes/l2-isolation-domain.md

@@ -32,34 +32,11 @@ You need to create various networks based on your workload needs. The following
 - Determine the BGP peering info for each network, and whether the networks need to talk to each other. You should group networks that need to talk to each other into the same L3 isolation domain, because each L3 isolation domain can support multiple L3 networks.
 - The platform provides a proxy to allow your VM to reach other external endpoints. Creating a `cloudservicesnetwork` instance requires the endpoints to be proxied, so gather the list of endpoints. You can modify the list of endpoints after the network creation.
 
-## Create networks for tenant workloads
-
-The following sections explain the steps to create networks for tenant workloads (VMs and Kubernetes clusters).
-
-### Create isolation domains
-
-Isolation domains enable creation of layer 2 (L2) and layer 3 (L3) connectivity between network functions running on Azure Operator Nexus. This connectivity enables inter-rack and intra-rack communication between the workloads.
-You can create as many L2 and L3 isolation domains as needed.
-
-You should have the following information already:
+## Create isolation domains
 
-- The network fabric resource ID to create isolation domains.
-- VLAN and subnet info for each L3 network.
-- Which networks need to talk to each other. (Remember to put VLANs and subnets that need to talk to each other into the same L3 isolation domain.)
-- BGP peering and network policy information for your L3 isolation domains.
-- VLANs for all your L2 networks.
-- VLANs for all your trunked networks.
-- MTU values for your networks.
+The isolation-domains enable communication between workloads hosted in the same rack (intra-rack communication) or different racks (inter-rack communication). You can find more details about creating isolation domains [here](./howto-configure-isolation-domain.md).
 
-#### L2 isolation domain
-
-[!INCLUDE [l2-isolation-domain](./includes/l2-isolation-domain.md)]
-
-#### L3 isolation domain
-
-[!INCLUDE [l3-isolation-domain](./includes/l3-isolation-domain.md)]
-
-### Create networks for tenant workloads
+## Create networks for tenant workloads
 
 The following sections describe how to create these networks:
 
@@ -68,13 +45,13 @@ The following sections describe how to create these networks:
 - Trunked network
 - Cloud services network
 
-#### Create an L2 network
+### Create an L2 network
 
 Create an L2 network, if necessary, for your workloads. You can repeat the instructions for each required L2 network.
 
 Gather the resource ID of the L2 isolation domain that you [created](#l2-isolation-domain) to configure the VLAN for this network.
 
-### [Azure CLI](#tab/azure-cli)
+#### [Azure CLI](#tab/azure-cli)
 
 ```azurecli-interactive
   az networkcloud l2network create --name "<YourL2NetworkName>" \
@@ -85,7 +62,7 @@ Gather the resource ID of the L2 isolation domain that you [created](#l2-isolati
     --l2-isolation-domain-id "<YourL2IsolationDomainId>"
 ```
 
-### [Azure PowerShell](#tab/azure-powershell)
+#### [Azure PowerShell](#tab/azure-powershell)
 
 ```azurepowershell-interactive
 New-AzNetworkCloudL2Network -Name "<YourL2NetworkName>" `
@@ -100,7 +77,7 @@ New-AzNetworkCloudL2Network -Name "<YourL2NetworkName>" `
 
 ---
 
-#### Create an L3 network
+### Create an L3 network
 
 Create an L3 network, if necessary, for your workloads. Repeat the instructions for each required L3 network.
 
@@ -112,7 +89,7 @@ You need:
 - The `ip-allocation-type` value, which can be `IPv4`, `IPv6`, or `DualStack` (default).
 - The `vlan` value, which must match what's in the L3 isolation domain.
 
-### [Azure CLI](#tab/azure-cli)
+#### [Azure CLI](#tab/azure-cli)
 
 ```azurecli-interactive
   az networkcloud l3network create --name "<YourL3NetworkName>" \
@@ -127,7 +104,7 @@ You need:
     --vlan <YourNetworkVlan>
 ```
 
-### [Azure PowerShell](#tab/azure-powershell)
+#### [Azure PowerShell](#tab/azure-powershell)
 
 ```azurepowershell-interactive
 New-AzNetworkCloudL3Network -Name "<YourL3NetworkName>" `
@@ -144,13 +121,13 @@ New-AzNetworkCloudL3Network -Name "<YourL3NetworkName>" `
 
 ---
 
-#### Create a trunked network
+### Create a trunked network
 
 Create a trunked network, if necessary, for your VM. Repeat the instructions for each required trunked network.
 
 Gather the `resourceId` values of the L2 and L3 isolation domains that you created earlier to configure the VLANs for this network. You can include as many L2 and L3 isolation domains as needed.
 
-### [Azure CLI](#tab/azure-cli)
+#### [Azure CLI](#tab/azure-cli)
 
 ```azurecli-interactive
   az networkcloud trunkednetwork create --name "<YourTrunkedNetworkName>" \
@@ -167,7 +144,8 @@ Gather the `resourceId` values of the L2 and L3 isolation domains that you creat
       "<YourL3IsolationDomainId3>" \
     --vlans <YourVlanList>
 ```
-### [Azure PowerShell](#tab/azure-powershell)
+
+#### [Azure PowerShell](#tab/azure-powershell)
 
 ```azurepowershell-interactive
 New-AzNetworkCloudTrunkedNetwork -Name "<YourTrunkedNetworkName>" `
@@ -183,7 +161,7 @@ New-AzNetworkCloudTrunkedNetwork -Name "<YourTrunkedNetworkName>" `
 
 ---
 
-#### Create a cloud services network
+### Create a cloud services network
 
 To create an Operator Nexus virtual machine (VM) or Operator Nexus Kubernetes cluster, you must have a cloud services network. Without this network, you can't create a VM or cluster.
 
@@ -197,7 +175,7 @@ The egress endpoints must comply with the domain name structures and hostname sp
 - `api.v1.contoso.com`: Incorporates two subdomains (`v1` and `api`) above the base domain contoso.com.
 - `.api.contoso.com`: A wildcard for any subdomain under `api.contoso.com`, covering multiple third-level domains.
 
-### [Azure CLI](#tab/azure-cli)
+#### [Azure CLI](#tab/azure-cli)
 
 ```azurecli-interactive
   az networkcloud cloudservicesnetwork create --name "<YourCloudServicesNetworkName>" \
@@ -208,7 +186,7 @@ The egress endpoints must comply with the domain name structures and hostname sp
     --additional-egress-endpoints "[{\"category\":\"<YourCategory >\",\"endpoints\":[{\"<domainName1 >\":\"< endpoint1 >\",\"port\":<portnumber1 >}]}]"
 ```
 
-### [Azure PowerShell](#tab/azure-powershell)
+#### [Azure PowerShell](#tab/azure-powershell)
 
 ```azurepowershell-interactive
 $endpointEgressList = @()