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/troubleshoot-hardware-validation-failure.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -215,7 +215,7 @@ Expanding `result_detail` for a given category shows detailed results.
215
215
216
216
### Network info category
217
217
218
-
* Network Interface Card (NIC) Check Failure
218
+
* Network Interface Cards (NIC) Check Failure
219
219
* Dell server NIC specs are defined in the SKU. A mismatched link status indicates loose or faulty cabling or crossed cables. A mismatched model indicates incorrect NIC card is inserted in to slot. Missing link/model fetched values indicate NICs that are failed, missing, or inserted in to incorrect slots.
220
220
221
221
```json
@@ -340,7 +340,7 @@ Expanding `result_detail` for a given category shows detailed results.
340
340
}
341
341
```
342
342
343
-
* To troubleshoot this problem, ensure that correct MAC address is defined in the cluster. If MAC is correct attempt a flea drain. If problem persists ensure that server is racked in the correct location, cabled accordingly, and that the correct IP is assigned.
343
+
* To troubleshoot this problem, ensure that correct MAC address is defined in the cluster. If MAC is correct in the cluster object, attempt a flea drain. If problem persists ensure that server is racked in the correct location, cabled accordingly, and that the correct IP is assigned.
344
344
345
345
* Preboot execution environment (PXE) MAC Address Check Failure
346
346
* The PXE MAC address is defined in the cluster for each BMM. A failed `PXE_MAC` check indicates a mismatch between the PXE MAC in the cluster and the actual MAC address retrieved from the machine.
@@ -354,7 +354,7 @@ Expanding `result_detail` for a given category shows detailed results.
354
354
}
355
355
```
356
356
357
-
* To troubleshoot this problem, ensure that correct MAC address is defined in the cluster. If MAC is correct attempt a flea drain. If problem persists ensure that server is racked in the correct location, cabled accordingly, and that the correct IP is assigned.
357
+
* To troubleshoot this problem, ensure that correct MAC address is defined in the cluster. If MAC is correct in the cluster object, attempt a flea drain. If problem persists ensure that server is racked in the correct location, cabled accordingly, and that the correct IP is assigned.
358
358
359
359
### Health info category
360
360
@@ -400,7 +400,7 @@ Expanding `result_detail` for a given category shows detailed results.
400
400
401
401
* To troubleshoot a server health failure engage vendor.
402
402
403
-
* Health Check Lifecycle (LC) Log Failures
403
+
* Health Check LifeCycle (LC) Log Failures
404
404
* Dell server health checks fail for recent Critical LC Log Alarms. The hardware validation plugin logs the alarm ID, name, and timestamp. Recent LC Log critical alarms indicate need for further investigation. The following example shows a failure for a critical backplane voltage alarm.
0 commit comments