Skip to content

Commit cae9dc3

Browse files
sushantjraosushantjrao
committed
updated the content
1 parent 3da1ff7 commit cae9dc3

4 files changed

+26
-17
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Troubleshooting network devices is a critical aspect of effective network manage
1616

1717
## Understanding read-only commands
1818

19-
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.
19+
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.
2020

2121
## Read-only diagnostic API
2222

@@ -55,6 +55,8 @@ To use Network Fabric read-only commands, complete the following steps:
5555
> [!NOTE]
5656
> 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.
5757
58+
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
59+
5860
## Command restrictions
5961

6062
To ensure security and compliance, RO commands must adhere to the following specific rules:

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -511,7 +511,7 @@ The RW command feature is open and there are no restrictions on it. However, pro
511511

512512
## Retreive runRW configuration
513513

514-
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.
514+
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.
515515

516516
```rest
517517
az rest -m get -u /subscriptions/<example-subscription-id>/resourceGroups/<example-rg>/providers/Microsoft.ManagedNetworkFabric/NetworkDevices/<example-devicename>?api-version=2024-06-15-preview

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,27 +31,27 @@ Before proceeding, ensure you have:
3131

3232
Create the UAMI(s) required for accessing the necessary resources.
3333

34-
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)
34+
For more information on creating managed identities, refer to [Manage user-assigned managed identities](https://learn.microsoft.com/en-us/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-azp)
3535

3636
## Configure the storage account
3737

3838
### Create or identify a storage account
3939

40-
Create a new storage account or use an existing one. Refer to [Create an Azure storage account](/articles/storage/common/storage-account-create).
40+
Create a new storage account or use an existing one. Refer to [Create an Azure storage account](../storage/common/storage-account-create.md).
4141

4242
### Assign the required role
4343

4444
Assign the **Storage Blob Data Contributor** role to the users and UAMI needing access to the **runRO** and **cable validation command output**.
4545

46-
For role assignment details, see [Assign an Azure role for access to blob data](/articles/storage/blobs/assign-azure-role-data-access.md).
46+
For role assignment details, see [Assign an Azure role for access to blob data](../storage/blobs/assign-azure-role-data-access.md).
4747

4848
### 2.3 Restrict storage account access
4949

5050
To limit access, configure Storage Firewalls and Virtual Networks:
5151

5252
- Add all required users' IP addresses to the **Virtual Networks** and/or **Firewall** lists.
5353

54-
- Follow instructions from [Configure Azure Storage firewalls and virtual networks](/articles/storage/common/storage-network-security.md).
54+
- Follow instructions from [Configure Azure Storage firewalls and virtual networks](../storage/common/storage-network-security.md).
5555

5656
### Enable Trusted Services
5757

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

Lines changed: 18 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -14,17 +14,24 @@ This document provides the list of software versioning supported in Release 2407
1414

1515
## Supported software versions
1616

17-
| **Software** | **Version(s)** | **Nexus Network Fabric run-time version** |
18-
|------------------------------------------|------------------------------------------|--------------------------|
19-
| **Arista Firmware** | 4.30.0F-30849330.bhimarel | 1.0.0 |
20-
| | MD5 checksum: c52cff01ed950606d36f433470110dca | |
21-
| | **4.30.3M** | 2.0.0 |
22-
| | MD5 checksum: 53899348f586d95effb8ab097837d32d | |
23-
| | **4.31.2FX-NX** | 3.0.0 |
24-
| | MD5 Checksum: e5ee34d50149749c177bbeef3d10e363 | |
25-
| **Instance Cluster AKS** | 1.29.4 | |
26-
| **Azure Linux** | 2.0.20240425 | |
27-
| **Purity** | 6.1.x, 6.5.1, 6.5.4, 6.5.6 | |
17+
| **Software** | **Version(s)** | **Nexus Network Fabric Run-time Version** |
18+
|-------------------------|-----------------------------------------|------------------------------------------|
19+
| **Arista Firmware** | 4.30.0F-30849330.bhimarel | 1.0.0 *(NOTE: This runtime version is not supported for fresh deployments.)* |
20+
| | MD5 checksum: c52cff01ed950606d36f433470110dca | |
21+
| | **4.30.3M** | 2.0.0 |
22+
| | MD5 checksum: 53899348f586d95effb8ab097837d32d | |
23+
| | **4.31.2FX-NX** | 3.0.0 |
24+
| | MD5 checksum: e5ee34d50149749c177bbeef3d10e363 | |
25+
| | **4.32.2FX-NX** | 4.0.0 |
26+
| | MD5 checksum: c02f7cd5429c9aa0e4109b542388eb31 | |
27+
| | **EOS-4.33.1F** | 5.0.0 |
28+
| | MD5 checksum: 92bd63991108dbfb6f8ef3d2c15e9028 | |
29+
| **Instance Cluster AKS** | NC4.1.4 | NC Runtime is 1.30.7 |
30+
| **Azure Linux (aka Mariner)** | NC4.1.4 | NC Runtime is 3.0.20250102 |
31+
| **Purity** | 6.5.1, 6.5.4, 6.5.6, 6.5.8 | |
32+
33+
> [!Note]
34+
> Management Switches (Arista devices) support only 32bit OS images and all other devices support only 64 bits OS images.
2835
2936
### Supported K8S versions
3037
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).

0 commit comments

Comments
 (0)