You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-nexus/how-to-validate-cables.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,21 +5,21 @@ author: HollyCl
5
5
ms.author: HollyCl
6
6
ms.service: azure-operator-nexus
7
7
ms.topic: how-to #Required; leave this attribute/value as-is
8
-
ms.date: 04/10/2024
8
+
ms.date: 04/15/2024
9
9
10
10
#CustomerIntent: As a < type of user >, I want < what? > so that < why? >.
11
11
---
12
-
# Validate Cables for Nexus Network Fabric
12
+
# Validate Cables for Nexus Network Fabric
13
13
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.
15
15
16
16
## Prerequisites
17
17
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.
20
20
21
21
> [!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.
23
23
24
24
## Validate cabling
25
25
@@ -28,20 +28,24 @@ This article explains the Fabric cable validation, where the primary function o
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.
|`deviceDestinationResourceId`| Azure Resource Manager ID of the connected Neighbor (destination device) |
174
176
|`roleName`| The role of the Network Fabric Device (CE or TOR) |
175
177
176
-
177
178
## Known issues and limitations in cable validation
178
179
179
-
- Post Validation Connections between TORs and Compute Servers isn't supported.
180
+
- Post Validation Connections between TORs and Compute Servers isn't supported.
180
181
- 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.
183
184
184
185
## Generate the storage URL
185
186
@@ -191,4 +192,4 @@ Refer to [Create a container](../storage/blobs/blob-containers-portal.md#create-
191
192
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.
192
193
193
194
> [!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