Skip to content

Commit ca5d491

Browse files
Merge pull request #272177 from HollyCl/nexus0404
Nexus0404 - Validate Cables Updates
2 parents 7d77236 + 54c7d2c commit ca5d491

File tree

1 file changed

+21
-20
lines changed

1 file changed

+21
-20
lines changed

articles/operator-nexus/how-to-validate-cables.md

Lines changed: 21 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -5,21 +5,21 @@ author: HollyCl
55
ms.author: HollyCl
66
ms.service: azure-operator-nexus
77
ms.topic: how-to #Required; leave this attribute/value as-is
8-
ms.date: 04/10/2024
8+
ms.date: 04/15/2024
99

1010
#CustomerIntent: As a < type of user >, I want < what? > so that < why? >.
1111
---
12-
# Validate Cables for Nexus Network Fabric
12+
# Validate Cables for Nexus Network Fabric
1313

14-
This article explains the Fabric cable validation, where the primary function of the diagnostic API is to check all fabric devices for potential cabling issues. The Diagnostic API assesses whether the interconnected devices adhere to the Bill of Materials (BOM), classifying them as compliant or non-compliant. The results are presented in a JSON format, encompassing details such as validation status, errors, identifier type, and neighbor device ID. These results are stored in a customer-provided Storage account. It is vital to the overall deployment that errors identified in this report are resolved before moving onto the Cluster deployment step.
14+
This article explains the Fabric cable validation, where the primary function of the diagnostic API is to check all fabric devices for potential cabling issues. The Diagnostic API assesses whether the interconnected devices adhere to the Bill of Materials (BOM), classifying them as compliant or noncompliant. The results are presented in a JSON format, encompassing details such as validation status, errors, identifier type, and neighbor device ID. These results are stored in a customer-provided Storage account. It's vital to the overall deployment that errors identified in this report are resolved before moving onto the Cluster deployment step.
1515

1616
## Prerequisites
1717

18-
- Ensure the Nexus Network Fabric is successfully provisioned.
19-
- Provide the Network Fabric ID and storage URL with WRITE access via a support ticket.
18+
- Ensure the Nexus Network Fabric is successfully provisioned.
19+
- Provide the Network Fabric ID and storage URL with WRITE access via a support ticket.
2020

2121
> [!NOTE]
22-
> The Storage URL (SAS) is short-lived. By default, it is set to expire in eight hours. If the SAS URL expires, then the fabric must be re-patched.
22+
> The Storage URL (SAS) is short-lived. By default, it is set to expire in eight hours. If the SAS URL expires, then the fabric must be re-patched.
2323
2424
## Validate cabling
2525

@@ -28,20 +28,24 @@ This article explains the Fabric cable validation, where the primary function o
2828
```azurecli
2929
az networkfabric fabric validate-configuration –resource-group "<NFResourceGroupName>" --resource-name "<NFResourceName>" --validate-action "Cabling" --no-wait --debug
3030
```
31-
The following (truncated) output should appear. Locate the operation status URL within the output. This URL is used to check the status of the operation, as described in the following step.
31+
32+
The following (truncated) output appears. Copy the URL through **private preview**. This portion of the URL is used in the following step to check the status of the operation.
3233
3334
```azurecli
34-
https://management.azure.com/subscriptions/xxxxxxxxxxx/providers/Microsoft.ManagedNetworkFabric/locations/EASTUS/operationStatuses/xxxxxxxxxxx?api-version=20XX-0X-xx-xx
35-
```
35+
https://management.azure.com/subscriptions/9531faa8-8c39-4165-b033-48697fe943db/providers/Microsoft.ManagedNetworkFabric/locations/EASTUS2EUAP/operationStatuses/59fdc0c8-eeb1-4258-9163-3cf096490148*A9E6DB3DF5C58D67BD395F7A608C056BC8219C392CC1CE0AD22E4C36D70CEE5C?api-version=2022-01-15-privatepreview&t=638485032018035520&c=MIIHHjCCBgagAwIBAgITfwKWMg6goKCq4WwU2AAEApYyDjANBgkqhkiG9w0BAQsFADBEMRMwEQYKCZImiZPyLGQBGRYDR0JMMRMwEQYKCZImiZPyLGQBGRYDQU1FMRgwFgYDVQQDEw9BTUUgSW5mcmEgQ0EgMDIwHhcNMjQwMTMwMTAzMDI3WhcNMjUwMTI0MTAzMDI3WjBAMT4wPAYDVQQDEzVhc3luY29wZXJhdGlvbnNpZ25pbmdjZXJ0aWZpY2F0ZS5tYW5hZ2VtZW50LmF6dXJlLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALMk1pBZQQoNY8tos8XBaEjHjcdWubRHrQk5CqKcX3tpFfukMI0_PVZK-Kr7xkZFQTYp_ItaM2RPRDXx-0W9-mmrUBKvdcQ0rdjcSXDek7GvWS29F5sDHojD1v3e9k2jJa4cVSWwdIguvXmdUa57t1EHxqtDzTL4WmjXitzY8QOIHLMRLyXUNg3Gqfxch40cmQeBoN4rVMlP31LizDfdwRyT1qghK7vgvworA3D9rE00aM0n7TcBH9I0mu-96JE0gSX1FWXctlEcmdwQmXj_U0sZCu11_Yr6Oa34bmUQHGc3hDvO226L1Au-QsLuRWFLbKJ-0wmSV5b3CbU1kweD5LUCAwEAAaOCBAswggQHMCcGCSsGAQQBgjcVCgQaMBgwCgYIKwYBBQUHAwEwCgYIKwYBBQUHAwIwPQYJKwYBBAGCNxUHBDAwLgYmKwYBBAGCNxUIhpDjDYTVtHiE8Ys-
36+
37+
```
3638
3739
1. You can programmatically check the status of the operation by running the following command:
40+
3841
```azurecli
39-
az rest -m get -u "<Azure-operationsstatus-endpoint url>"
42+
az rest -m get -u "<Azure-AsyncOperation-endpoint url>"
4043
```
41-
The operation status indicates if the API succeeded or failed.
4244
43-
> [!NOTE]
44-
> The operation takes roughly 20~40 minutes to complete based on the number of racks.
45+
The operation status indicates if the API succeeded or failed.
46+
47+
> [!NOTE]
48+
> The operation takes roughly 20~40 minutes to complete based on the number of racks.
4549
4650
1. Download and read the validated results from the storage URL.
4751
@@ -108,10 +112,8 @@ networkFabricInfoSkuId": "M8-A400-A100-C16-ab",
108112
                },
109113
```
110114

111-
112115
### Customer Edge to Top of the Rack switch validation
113116

114-
115117
```azurecli
116118
{
117119
                      "name": "Ethernet11/1",
@@ -173,13 +175,12 @@ networkFabricInfoSkuId": "M8-A400-A100-C16-ab",
173175
|`deviceDestinationResourceId` | Azure Resource Manager ID of the connected Neighbor (destination device) |
174176
|`roleName` | The role of the Network Fabric Device (CE or TOR) |
175177

176-
177178
## Known issues and limitations in cable validation
178179

179-
- Post Validation Connections between TORs and Compute Servers isn't supported.
180+
- Post Validation Connections between TORs and Compute Servers isn't supported.
180181
- Cable Validation for NPB isn't supported because there's no support for "show lldp neighbors" from Arista.
181-
- The Storage URL must be 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.
182-
- Cable validation supports both 4 rack and 8 rack BOMs.
182+
- The Storage URL must be 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.
183+
- Cable validation supports both four rack and eight rack BOMs.
183184

184185
## Generate the storage URL
185186

@@ -191,4 +192,4 @@ Refer to [Create a container](../storage/blobs/blob-containers-portal.md#create-
191192
Refer to [Generate a shared access signature](../storage/blobs/blob-containers-portal.md#generate-a-shared-access-signature) to create the SAS URL of the container. Provide Write permission for SAS.
192193

193194
> [!NOTE]
194-
> ESAS URLs are short lived. By default, it is set to expire in eight hours. If the SAS URL expires, then you must open a Microsoft support ticket to add a new URL.
195+
> ESAS URLs are short lived. By default, it is set to expire in eight hours. If the SAS URL expires, then you must open a Microsoft support ticket to add a new URL.

0 commit comments

Comments
 (0)