Merge pull request #295407 from sushantjrao/break-glass-setup

nnf features 8.0 update

Author: Stacyrch140

articles/operator-nexus/concepts-network-fabric-read-only-commands.md

@@ -16,7 +16,7 @@ Troubleshooting network devices is a critical aspect of effective network manage
 
 ## Understanding read-only commands 
 
-RO commands serve as essential tools for network administrators. Unlike read-write (RW) commands that modify device configurations, RO commands allow administrators to gather diagnostic information without altering the device's state. These commands provide valuable insights into the device's status, configuration, and operational data. 
+RO commands serve as essential tools for network administrators. Unlike read-write (RW) commands that modify device configurations, RO commands allow administrators to gather diagnostic information without altering the device's state. These commands provide valuable insights into the device's status, configuration, and operational data. The RO command also supports using a customer-provided storage account for storing output files.
 
 ## Read-only diagnostic API 
 
@@ -55,6 +55,8 @@ To use Network Fabric read-only commands, complete the following steps:
     > [!NOTE]
     > The Storage URL must be located in a different region from the Network Fabric. For instance, if the Fabric is hosted in East US, the storage URL should be outside of East US. 
 
+Alternatively, you can bring your own storage for storing output files by following the steps outlined in the [Bring Your Own Storage for Network Fabric](howto-configure-bring-your-own-storage-network-fabric.md) guide
+
  ## Command restrictions
 
 To ensure security and compliance, RO commands must adhere to the following specific rules:

articles/operator-nexus/concepts-network-fabric-read-write-commands.md

@@ -511,12 +511,17 @@ The RW command feature is open and there are no restrictions on it. However, pro
 
 ## Retreive runRW configuration
 
-To obtain the last successfully applied runRW configuration, refer to the rwDeviceConfig property. This property stores the last successfully applied RW configuration for the device. To access it, perform a GET request on the device resource.
+To obtain the last successfully applied runRW configuration, refer to the `rwDeviceConfig` property. This property stores the last successfully applied RW configuration for the device. To access it, perform a GET request on the device resource.
 
 ```rest
-az rest -m get -u /subscriptions/<example-subscription-id>/resourceGroups/<example-rg>/providers/Microsoft.ManagedNetworkFabric/NetworkDevices/<example-devicename>?api-version=2024-06-15-preview
+az networkfabric device show --resource-group "example-rg" --resource-name "example-device"
 ```
 
+| Parameter          | Alias | Description |
+|--------------------|-------|-------------|
+| `--resource-group` | `-g`  | Name of resource group. You can configure the default group using `az configure --defaults group=<name>`. |
+| `--resource-name`  |       | Name of the Network Device. |
+
 Expected output
 
 ```

articles/operator-nexus/howto-configure-bring-your-own-storage-network-fabric.md

@@ -31,27 +31,27 @@ Before proceeding, ensure you have:
 
 Create the UAMI(s) required for accessing the necessary resources.
 
-For more information on creating managed identities, refer to [Manage user-assigned managed](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities.md)
+For more information on creating managed identities, refer to [Manage user-assigned managed identities](https://learn.microsoft.com/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp)
 
 ## Configure the storage account
 
 ### Create or identify a storage account
 
-Create a new storage account or use an existing one. Refer to [Create an Azure storage account](/articles/storage/common/storage-account-create).
+Create a new storage account or use an existing one. Refer to [Create an Azure storage account](../storage/common/storage-account-create.md).
 
 ### Assign the required role
 
 Assign the **Storage Blob Data Contributor** role to the users and UAMI needing access to the **runRO** and **cable validation command output**.
 
-For role assignment details, see [Assign an Azure role for access to blob data](/articles/storage/blobs/assign-azure-role-data-access.md).
+For role assignment details, see [Assign an Azure role for access to blob data](../storage/blobs/assign-azure-role-data-access.md).
 
 ### 2.3 Restrict storage account access
 
 To limit access, configure Storage Firewalls and Virtual Networks:
 
 - Add all required users' IP addresses to the **Virtual Networks** and/or **Firewall** lists.
 
-- Follow instructions from [Configure Azure Storage firewalls and virtual networks](/articles/storage/common/storage-network-security.md).
+- Follow instructions from [Configure Azure Storage firewalls and virtual networks](../storage/common/storage-network-security.md).
 
 ### Enable Trusted Services
 

articles/operator-nexus/reference-supported-software-versions.md

@@ -14,17 +14,24 @@ This document provides the list of software versioning supported in Release 2407
 
 ## Supported software versions
 
-| **Software**                             | **Version(s)**                           | **Nexus Network Fabric run-time version** |
-|------------------------------------------|------------------------------------------|--------------------------|
-| **Arista Firmware**                      | 4.30.0F-30849330.bhimarel                | 1.0.0                    |
-|                                          | MD5 checksum: c52cff01ed950606d36f433470110dca |                          |
-|                                          | **4.30.3M**                              | 2.0.0                    |
-|                                          | MD5 checksum: 53899348f586d95effb8ab097837d32d |                          |
-|                                          | **4.31.2FX-NX**                          | 3.0.0                    |
-|                                          | MD5 Checksum: e5ee34d50149749c177bbeef3d10e363 |                          |
-| **Instance Cluster AKS** | 1.29.4                       |                          |
-| **Azure Linux**                          | 2.0.20240425                               |                          |
-| **Purity**                               | 6.1.x, 6.5.1, 6.5.4, 6.5.6                             |                          |
+| **Software**            | **Version(s)**                           | **Nexus Network Fabric Run-time Version** |
+|-------------------------|-----------------------------------------|------------------------------------------|
+| **Arista Firmware**     | 4.30.0F-30849330.bhimarel               | 1.0.0 *(NOTE: This runtime version is not supported for fresh deployments.)* |
+|                         | MD5 checksum: c52cff01ed950606d36f433470110dca |                                          |
+|                         | **4.30.3M**                              | 2.0.0                                    |
+|                         | MD5 checksum: 53899348f586d95effb8ab097837d32d |                                          |
+|                         | **4.31.2FX-NX**                          | 3.0.0                                    |
+|                         | MD5 checksum: e5ee34d50149749c177bbeef3d10e363 |                                          |
+|                         | **4.32.2FX-NX**                          | 4.0.0                                    |
+|                         | MD5 checksum: c02f7cd5429c9aa0e4109b542388eb31 |                                          |
+|                         | **EOS-4.33.1F**                          | 5.0.0                                    |
+|                         | MD5 checksum: 92bd63991108dbfb6f8ef3d2c15e9028 |                                          |
+| **Instance Cluster AKS** | NC4.1.4                                  | NC Runtime is 1.30.7                                  |
+| **Azure Linux (aka Mariner)** | NC4.1.4                          | NC Runtime is 3.0.20250102                             |
+| **Purity**              | 6.5.1, 6.5.4, 6.5.6, 6.5.8               |                                          |
+
+> [!Note]
+> Management Switches (Arista devices) support only 32bit OS images and all other devices support only 64 bits OS images.
 
 ### Supported K8S versions
 Versioning schema used for the Operator Nexus Kubernetes service, including the supported Kubernetes versions, are listed at [Supported Kubernetes versions in Azure Operator Nexus Kubernetes service](./reference-nexus-kubernetes-cluster-supported-versions.md).