Merge pull request #273757 from sushantjrao/deletel3isolationdomain

Deletel3isolationdomain

Author: v-dirichards

articles/operator-nexus/TOC.yml

@@ -154,6 +154,8 @@
               href: howto-delete-access-control-list-network-to-network-interconnect.md
             - name: How to Configure Diagnostic Settings and Monitor Configuration Differences in Nexus Network Fabric
               href: howto-configure-diagnostic-settings-monitor-configuration-differences.md
+            - name: How to Delete L3 Isolation Domains in Azure Nexus Network Fabric
+              href: howto-delete-layer-3-isolation-domains.md
     - name: Nexus Kubernetes cluster
       expanded: false
       items:

articles/operator-nexus/howto-configure-diagnostic-settings-monitor-configuration-differences.md

@@ -11,39 +11,39 @@ ms.custom: template-how-to
 
 # How to configure diagnostic settings and monitor configuration differences in Nexus Network Fabric
 
-In this guide, we'll walk you through the process of setting up diagnostic settings and monitoring configuration differences in Nexus Network Fabric.
+In this guide, we walk you through the process of setting up diagnostic settings and monitoring configuration differences in Nexus Network Fabric.
 
-## Step 1: Accessing device settings in Azure Portal
+## Step 1: Accessing device settings in Azure portal
 
 - Sign in to the Azure portal.
 
 - In **Search resources, service, and docs (G+/)** at the top of the portal page, enter **Network Device**.
 
-- :::image type="content" source="media/search-network-device.png" alt-text="Screenshot of search box for Network Device in portal.":::
+    :::image type="content" source="media/search-network-device.png" alt-text="Screenshot of search box for Network Device in portal.":::
 
 - Select the appropriate network device from the search results. Ensure that you choose the device for which you need to configure diagnostic settings.
 
 ## Step 2: Adding diagnostic setting
 
 - After selecting the appropriate network device, navigate to the monitoring and select diagnostic settings.
 
-- Within the diagnostic settings section, select "Add diagnostic setting".
+- After accessing the diagnostic settings section, select "Add diagnostic setting".
 
-- :::image type="content" source="media/network-device-dignostics-settings.png" alt-text="Screenshot of diagnostics settings page for network device.":::
+    :::image type="content" source="media/network-device-diagnostics-settings.png" alt-text="Screenshot of diagnostics settings page for network device.":::
 
-- In the diagnostic settings, provide a descriptive name for the diagnostic setting to easily identify its purpose.
+- Within the diagnostic settings, provide a descriptive name for the diagnostic setting to easily identify its purpose.
 
-- Select the desired categories of data that you want to collect for this diagnostic setting. In this case, select "System Session History Updates" from the list of available categories.
+- In the diagnostic settings, select the desired categories of data that you want to collect for this diagnostic setting.
 
-:::image type="content" source="media/network-device-system-session-history-updates.png" alt-text="Showcases specific categories of data to collect in portal.":::
+    :::image type="content" source="media/network-device-system-session-history-updates.png" alt-text="Showcases specific categories of data to collect in portal.":::
 
 ## Step 3: Choosing log destination
 
 - Once the diagnostic setting is added, locate the section where the log destination can be specified.
 
 - Select the log destination from several choices, including Log Analytics Workspace, Storage account, and Event Hubs.
 
-- :::image type="content" source="media/network-device-log-analytics-workspace.png" alt-text="Screenshot of configuration page for selecting Log Analytics Workspace as the log destination for a network device.":::
+    :::image type="content" source="media/network-device-log-analytics-workspace.png" alt-text="Screenshot of configuration page for selecting Log Analytics Workspace as the log destination for a network device.":::
 
 > [!Note]
 > In our example, we'll push the logs to the Log Analytics Workspace.<br>
@@ -55,8 +55,8 @@ In this guide, we'll walk you through the process of setting up diagnostic setti
 
 - Navigate to the Log Analytics Workspace where the logs from the network device are being stored.
 
-- Within the Log Analytics Workspace, access the query interface or log search functionality. 
+- Within the Log Analytics Workspace, access the query interface or log search functionality.
 
-- :::image type="content" source="media/network-device-config-difference.png" alt-text="Screenshot of comparison of configuration differences for a network device in a visual format.":::
+    :::image type="content" source="media/network-device-configuration-difference.png" alt-text="Screenshot of comparison of configuration differences for a network device in a visual format.":::
 
 - In the query interface, specify the event category as "MNFSystemSessionHistoryUpdates". This will filter the logs to specifically show configuration updates and changes comprehensively.

articles/operator-nexus/howto-create-access-control-list-for-network-to-network-interconnects.md

@@ -23,20 +23,20 @@ To create an ACL and define its properties, you can utilize the `az networkfabri
 
 If you have multiple subscriptions and need to set one as the default, you can do so with:
 
-```bash
+```Azure CLI
 az account set --subscription <subscription-id>
 ```
 
 2. **Create ACL:**
 
-```bash
+```Azure CLI
     az networkfabric acl create --resource-group "<resource-group>" --location "<location>" --resource-name "<acl-name>" --annotation "<annotation>" --configuration-type "<configuration-type>" --default-action "<default-action>" --match-configurations "[{matchConfigurationName:<match-config-name>,sequenceNumber:<sequence-number>,ipAddressType:<IPv4/IPv6>,matchConditions:[{ipCondition:{type:<SourceIP/DestinationIP>,prefixType:<Prefix/Exact>,ipPrefixValues:['<ip-prefix1>', '<ip-prefix2>', ...]}}],actions:[{type:<Action>}]}]"
 ```
 
 | Parameter            | Description                                                          |
 |----------------------|----------------------------------------------------------------------|
 | Resource Group       | Specify the resource group of your network fabric.                   |
-| Location             | Define the location where the ACL will be created.                   |
+| Location             | Define the location where the ACL is created.                   |
 | Resource Name        | Provide a name for the ACL.                                          |
 | Annotation           | Optionally, add a description or annotation for the ACL.            |
 | Configuration Type   | Specify whether the configuration is inline or by using a file.     |

articles/operator-nexus/howto-delete-layer-3-isolation-domains.md

@@ -0,0 +1,62 @@
+---
+title: How to Delete L3 Isolation Domains in Azure Nexus Network Fabric
+description: Learn how to effectively delete L3 Isolation Domains in the Azure Nexus Network Fabric.
+ms.service: azure-operator-nexus
+ms.custom: template-how-to, devx-track-azurecli
+ms.topic: how-to
+ms.date: 02/07/2024
+author: sushantjrao
+ms.author: sushrao
+---
+
+# How to delete L3 isolation domains in Azure Nexus Network Fabric
+
+In managing network infrastructure, deleting Layer 3 (L3) Isolation Domains (ISDs) needs careful consideration and precise execution to maintain the network's integrity and functionality. This step-by-step guide outlines the process of safely deleting L3 ISDs.
+
+Below are the steps involved:
+
+ [!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment.md)]
+
+1. **Set subscription (if necessary):**
+ 
+If you have multiple subscriptions and need to set one as the default, you can do so with:
+ 
+```Azure CLI
+az account set --subscription <subscription-id>
+```
+
+2. **Disable L3 isolation domains**
+
+Before deleting an L3 ISD, it's crucial to disable it to prevent any disruption to the network using the following command.
+
+```Azure CLI
+az nf l3domain update-admin-state --resource-group "ResourceGroupName" --resource-name "example-l3domain" --state Disable
+```
+
+| Parameter            | Description                                                                                     |
+|----------------------|-------------------------------------------------------------------------------------------------|
+| --resource-group     | The name of the resource group containing the L3 isolation domain to update.                   |
+| --resource-name      | The name of the L3 isolation domain to update.                                                 |
+| --state              | The desired state of the L3 isolation domain. Possible values: "Enable" or "Disable".         |
+
+>!**Note:**
+>Disabling the L3 isolation domain will disassociate all attached resources, including route policies, IP prefixes, IP communities, and both internal and external networks.
+
+3. **Delete L3 isolation domains**
+
+After disabling the L3 isolation domain and disassociating its associated resources, you can safely delete it using the following command. 
+
+```Azure CLI
+az nf l3domain delete --resource-group "ResourceGroupName" --resource-name "example-l3domain"
+```
+
+| Parameter            | Description                                                                                     |
+|----------------------|-------------------------------------------------------------------------------------------------|
+| --resource-group     | The name of the resource group containing the L3 isolation domain to delete.                   |
+| --resource-name      | The name of the L3 isolation domain to delete.                                                 |
+
+This table outlines the parameters required for executing the `az nf l3domain delete` command, facilitating users in understanding the necessary inputs for deleting an L3 isolation domain.
+
+3. Validation:
+
+After executing the deletion command, use either the `show` or `list` commands to validate that the isolation domain has been successfully deleted.