Skip to content

Commit 2a3b3aa

Browse files
vnikolinvnikolin
committed
Update JSON Code Blocks
1 parent 2aea2e9 commit 2a3b3aa

File tree

1 file changed

+36
-36
lines changed

1 file changed

+36
-36
lines changed

‎articles/operator-nexus/troubleshoot-hardware-validation-failure.md

Lines changed: 36 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Expanding `result_detail` for a given category shows detailed results.
5050
* Memory/RAM Related Failure (memory_capacity_GB) (measured in GiB)
5151
* Memory specs are defined in the SKU. Memory below threshold value indicates missing or failed Dual In-Line Memory Module (DIMM). A failed DIMM would also be reflected in the `health_info` category. The following example shows a failed memory check.
5252

53-
```json
53+
```yaml
5454
{
5555
"field_name": "memory_capacity_GB",
5656
"comparison_result": "Fail",
@@ -74,7 +74,7 @@ Expanding `result_detail` for a given category shows detailed results.
7474
* CPU Related Failure (cpu_sockets)
7575
* CPU specs are defined in the SKU. Failed `cpu_sockets` check indicates a failed CPU or CPU count mismatch. The following example shows a failed CPU check.
7676

77-
```json
77+
```yaml
7878
{
7979
"field_name": "cpu_sockets",
8080
"comparison_result": "Fail",
@@ -98,7 +98,7 @@ Expanding `result_detail` for a given category shows detailed results.
9898
* Model Check Failure (Model)
9999
* Failed `Model` check indicates that wrong server is racked in the slot or there's a cabling mismatch. The following example shows a failed model check.
100100

101-
```json
101+
```yaml
102102
{
103103
"field_name": "Model",
104104
"comparison_result": "Fail",
@@ -122,7 +122,7 @@ Expanding `result_detail` for a given category shows detailed results.
122122
* Serial Number Check Failure (Serial_Number)
123123
* The server's serial number, also referred as the service tag, is defined in the cluster. Failed `Serial_Number` check indicates a mismatch between the serial number in the cluster and the actual serial number of the machine. The following example shows a failed serial number check.
124124

125-
```json
125+
```yaml
126126
{
127127
"field_name": "Serial_Number",
128128
"comparison_result": "Fail",
@@ -146,7 +146,7 @@ Expanding `result_detail` for a given category shows detailed results.
146146
* iDRAC License Check Failure
147147
* All iDRACs require a perpetual/production iDRAC datacenter or enterprise license. Trial licenses are valid for only 30 days. A failed `iDRAC License Check` indicates that the required iDRAC license is missing. The following examples show a failed iDRAC license check for a trial license and missing license respectively.
148148

149-
```json
149+
```yaml
150150
{
151151
"field_name": "iDRAC License Check",
152152
"comparison_result": "Fail",
@@ -155,7 +155,7 @@ Expanding `result_detail` for a given category shows detailed results.
155155
}
156156
```
157157

158-
```json
158+
```yaml
159159
{
160160
"field_name": "iDRAC License Check",
161161
"comparison_result": "Fail",
@@ -171,7 +171,7 @@ Expanding `result_detail` for a given category shows detailed results.
171171
* Firmware Version Checks
172172
* Firmware version checks were introduced in release 3.9. The following example shows the expected log for release versions before 3.9.
173173

174-
```json
174+
```yaml
175175
{
176176
"system_info": {
177177
"system_info_result": "Pass",
@@ -184,7 +184,7 @@ Expanding `result_detail` for a given category shows detailed results.
184184

185185
* Firmware versions are determined based on the `cluster version` value in the cluster object. The following example shows a failed check due to indeterminate cluster version. If this problem is encountered, verify the version in the cluster object.
186186

187-
```json
187+
```yaml
188188
{
189189
"system_info": {
190190
"system_info_result": "Fail",
@@ -200,7 +200,7 @@ Expanding `result_detail` for a given category shows detailed results.
200200
* Disk Checks Failure
201201
* Drive specs are defined in the SKU. Mismatched capacity values indicate incorrect drives or drives inserted in to incorrect slots. Missing capacity and type fetched values indicate drives that are failed, missing, or inserted in to incorrect slots.
202202

203-
```json
203+
```yaml
204204
{
205205
"field_name": "Disk_0_Capacity_GB",
206206
"comparison_result": "Fail",
@@ -209,7 +209,7 @@ Expanding `result_detail` for a given category shows detailed results.
209209
}
210210
```
211211

212-
```json
212+
```yaml
213213
{
214214
"field_name": "Disk_0_Capacity_GB",
215215
"comparison_result": "Fail",
@@ -218,7 +218,7 @@ Expanding `result_detail` for a given category shows detailed results.
218218
}
219219
```
220220

221-
```json
221+
```yaml
222222
{
223223
"field_name": "Disk_0_Type",
224224
"comparison_result": "Fail",
@@ -244,7 +244,7 @@ Expanding `result_detail` for a given category shows detailed results.
244244
* Network Interface Cards (NIC) Check Failure
245245
* 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.
246246

247-
```json
247+
```yaml
248248
{
249249
"field_name": "NIC.Slot.3-1-1_LinkStatus",
250250
"comparison_result": "Fail",
@@ -253,7 +253,7 @@ Expanding `result_detail` for a given category shows detailed results.
253253
}
254254
```
255255

256-
```json
256+
```yaml
257257
{
258258
"field_name": "NIC.Embedded.2-1-1_LinkStatus",
259259
"comparison_result": "Fail",
@@ -262,7 +262,7 @@ Expanding `result_detail` for a given category shows detailed results.
262262
}
263263
```
264264

265-
```json
265+
```yaml
266266
{
267267
"field_name": "NIC.Slot.3-1-1_Model",
268268
"comparison_result": "Fail",
@@ -271,7 +271,7 @@ Expanding `result_detail` for a given category shows detailed results.
271271
}
272272
```
273273

274-
```json
274+
```yaml
275275
{
276276
"field_name": "NIC.Slot.3-1-1_LinkStatus",
277277
"comparison_result": "Fail",
@@ -280,7 +280,7 @@ Expanding `result_detail` for a given category shows detailed results.
280280
}
281281
```
282282

283-
```json
283+
```yaml
284284
{
285285
"field_name": "NIC.Slot.3-1-1_Model",
286286
"comparison_result": "Fail",
@@ -310,7 +310,7 @@ Expanding `result_detail` for a given category shows detailed results.
310310
* NIC Check L2 Switch Information
311311
* HWV reports L2 switch information for each of the server interfaces. The switch connection ID (switch interface MAC) and switch port connection ID (switch interface label) are informational.
312312

313-
```json
313+
```yaml
314314
{
315315
"field_name": "NIC.Slot.3-1-1_SwitchConnectionID",
316316
"comparison_result": "Info",
@@ -319,7 +319,7 @@ Expanding `result_detail` for a given category shows detailed results.
319319
}
320320
```
321321

322-
```json
322+
```yaml
323323
{
324324
"field_name": "NIC.Slot.3-1-1_SwitchPortConnectionID",
325325
"comparison_result": "Info",
@@ -331,7 +331,7 @@ Expanding `result_detail` for a given category shows detailed results.
331331
* Cabling Checks for Bonded Interfaces
332332
* Mismatched cabling is reported in the result_log. Cable check validates that that bonded NICs connect to switch ports with same Port ID. In the following example Peripheral Component Interconnect (PCI) 3/1 and 3/2 connect to "Ethernet1/1" and "Ethernet1/3" respectively on TOR, triggering a failure for HWV.
333333

334-
```json
334+
```yaml
335335
{
336336
"network_info": {
337337
"network_info_result": "Fail",
@@ -357,7 +357,7 @@ Expanding `result_detail` for a given category shows detailed results.
357357
* iDRAC (BMC) MAC Address Check Failure
358358
* The iDRAC MAC address is defined in the cluster for each BMM. A failed `iDRAC_MAC` check indicates a mismatch between the iDRAC/BMC MAC in the cluster and the actual MAC address retrieved from the machine.
359359

360-
```json
360+
```yaml
361361
{
362362
"field_name": "iDRAC_MAC",
363363
"comparison_result": "Fail",
@@ -371,7 +371,7 @@ Expanding `result_detail` for a given category shows detailed results.
371371
* Preboot execution environment (PXE) MAC Address Check Failure
372372
* 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.
373373

374-
```json
374+
```yaml
375375
{
376376
"field_name": "NIC.Embedded.1-1_PXE_MAC",
377377
"comparison_result": "Fail",
@@ -387,7 +387,7 @@ Expanding `result_detail` for a given category shows detailed results.
387387
* Health Check Sensor Failure
388388
* Server health checks cover various hardware component sensors. A failed health sensor indicates a problem with the corresponding hardware component. The following examples indicate fan, drive, and CPU failures respectively.
389389

390-
```json
390+
```yaml
391391
{
392392
"field_name": "System Board Fan1A",
393393
"comparison_result": "Fail",
@@ -396,7 +396,7 @@ Expanding `result_detail` for a given category shows detailed results.
396396
}
397397
```
398398

399-
```json
399+
```yaml
400400
{
401401
"field_name": "Solid State Disk 0:1:1",
402402
"comparison_result": "Fail",
@@ -405,7 +405,7 @@ Expanding `result_detail` for a given category shows detailed results.
405405
}
406406
```
407407

408-
```json
408+
```yaml
409409
{
410410
"field_name": "CPU.Socket.1",
411411
"comparison_result": "Fail",
@@ -429,7 +429,7 @@ Expanding `result_detail` for a given category shows detailed results.
429429
* Health Check LifeCycle (LC) Log Failures
430430
* 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's critical alarms indicate need for further investigation. The following example shows a failure for a critical backplane voltage alarm.
431431

432-
```json
432+
```yaml
433433
{
434434
"field_name": "LCLog_Critical_Alarms",
435435
"comparison_result": "Fail",
@@ -441,7 +441,7 @@ Expanding `result_detail` for a given category shows detailed results.
441441
* Virtual disk errors typically indicate a RAID cleanup false positive condition and are logged due to the timing of raid cleanup and system power off pre HWV. The following example shows an LC log critical error on virtual disk 238. If multiple errors are encountered blocking deployment, delete cluster, wait two hours, then reattempt cluster deployment. If the failures aren't deployment blocking, wait two hours then run BMM replace.
442442
* Virtual disk errors are allowlisted starting with release 3.13 and don't trigger a health check failure.
443443

444-
```json
444+
```yaml
445445
{
446446
"field_name": "LCLog_Critical_Alarms",
447447
"comparison_result": "Fail",
@@ -465,7 +465,7 @@ Expanding `result_detail` for a given category shows detailed results.
465465
* Health Check Server Power Control Action Failures
466466
* Dell server health checks fail for failed server power-up or failed iDRAC reset. A failed server control action indicates an underlying hardware issue. The following example shows failed power on attempt.
467467

468-
```json
468+
```yaml
469469
{
470470
"field_name": "Server Control Actions",
471471
"comparison_result": "Fail",
@@ -474,7 +474,7 @@ Expanding `result_detail` for a given category shows detailed results.
474474
}
475475
```
476476

477-
```json
477+
```yaml
478478
"result_log": [
479479
"Server power up failed with: server OS is powered off after successful power on attempt",
480480
]
@@ -495,7 +495,7 @@ Expanding `result_detail` for a given category shows detailed results.
495495
* RAID Cleanup Failures
496496
* RAID cleanup was added to HWV in release 3.13. As part of RAID cleanup the RAID controller configuration is reset. Dell server health check fails for RAID controller reset failure. A failed RAID cleanup action indicates an underlying hardware issue. The following example shows a failed RAID controller reset.
497497

498-
```json
498+
```yaml
499499
{
500500
"field_name": "Server Control Actions",
501501
"comparison_result": "Fail",
@@ -504,7 +504,7 @@ Expanding `result_detail` for a given category shows detailed results.
504504
}
505505
```
506506

507-
```json
507+
```yaml
508508
"result_log": [
509509
"RAID cleanup failed with: raid deletion failed after 2 attempts",
510510
]
@@ -527,7 +527,7 @@ Expanding `result_detail` for a given category shows detailed results.
527527
* Health Check Power Supply Failure and Redundancy Considerations
528528
* Dell server health checks warn when one power supply is missing or failed. Power supply "field_name" might be displayed as 0/PS0/Power Supply 0 and 1/PS1/Power Supply 1 for the first and second power supplies respectively. A failure of one power supply doesn't trigger an HWV device failure.
529529

530-
```json
530+
```yaml
531531
{
532532
"field_name": "Power Supply 1",
533533
"comparison_result": "Warning",
@@ -536,7 +536,7 @@ Expanding `result_detail` for a given category shows detailed results.
536536
}
537537
```
538538

539-
```json
539+
```yaml
540540
{
541541
"field_name": "System Board PS Redundancy",
542542
"comparison_result": "Warning",
@@ -563,7 +563,7 @@ Expanding `result_detail` for a given category shows detailed results.
563563
* The `boot_device_name` check is currently informational.
564564
* Mismatched boot device name shouldn't trigger a device failure.
565565

566-
```json
566+
```yaml
567567
{
568568
"field_name": "boot_device_name",
569569
"comparison_result": "Info",
@@ -578,7 +578,7 @@ Expanding `result_detail` for a given category shows detailed results.
578578
* Failed `pxe_device_1_name` or `pxe_device_1_state` checks indicate a problem with the PXE configuration.
579579
* Failed settings need to be fixed to enable system boot during deployment.
580580

581-
```json
581+
```yaml
582582
{
583583
"field_name": "pxe_device_1_name",
584584
"comparison_result": "Fail",
@@ -587,7 +587,7 @@ Expanding `result_detail` for a given category shows detailed results.
587587
}
588588
```
589589

590-
```json
590+
```yaml
591591
{
592592
"field_name": "pxe_device_1_state",
593593
"comparison_result": "Fail",
@@ -615,7 +615,7 @@ Expanding `result_detail` for a given category shows detailed results.
615615
* Device Login Check Considerations
616616
* The `device_login` check fails if the iDRAC isn't accessible or if the hardware validation plugin isn't able to sign-in.
617617

618-
```json
618+
```yaml
619619
{
620620
"device_login": "Fail"
621621
}

0 commit comments

Comments
 (0)