Dell PowerEdge XL 5133-4 Dell PowerEdge FTOS Command Line Reference Guide for - Page 249

diag stack-unit, hardware watchdog

Page 249 highlights

diag stack-unit Run offline diagnostics on a stack unit. Syntax diag stack-unit number {alllevels | level0 | level1 | level2 [verbose no-reboot] | terminate | interactive {test } number alllevels level0 level1 level2 verbose no-reboot terminate interactive Enter the stack-unit number. Range: 0 to 5 Enter the keyword alllevels to run the complete set of offline diagnostic tests. Enter the keyword level0 to run Level 0 diagnostics. Level 0 diagnostics check for the presence of various components and perform essential path verifications. In addition, they verify the identification registers of the components on the board. Enter the keyword Level1 to run Level 1 diagnostics. Level 1 diagnostics is a smaller set of diagnostic tests with support for automatic partitioning. They perform status/self test for all the components on the board and test their registers for appropriate values. In addition, they perform extensive tests on memory devices (e.g., SDRAM, flash, NVRAM, EEPROM, and CPLD) wherever possible. There are no tests on 10G links. At this level, stack ports are shut down automatically. Enter the keyword level2 to run Level 2 diagnostics. Level 2 diagnostics is a full set of diagnostic tests with no support for automatic partitioning. Level 2 diagnostics are used primarily for on-board loopback tests and more extensive component diagnostics. Various components on the board are put into loop back mode, and test packets are transmitted through those components. These diagnostics also perform snake tests using VLAN configurations. You must physically remove the unit from the stack to test 10G links. Enter the keyword verbose to run the diagnostic in verbose mode. Verbose mode gives more information in the output than standard mode. Enter the keyword no-reboot to avoid automatic rebooting of the chassis after completion of diagnostic execution. Generally, this option is never used because if you run the diagnostic once again without rebooting the chassis, it may cause an issue with the diagnostic results. Enter the keyword terminate to stop the execution of the level diag that is already started using the diag stack-unit command. Once this CLI is issued, syslogs indicating the termination of the diag test is displayed. The diag results for the executed tests are stored in the flash directory (TestReport-SU-X.txt). Enter the keyword interactive to run some individual diag tests such as POWERLEDTEST, STATUSLEDTEST and so on. The help option under the interactive command displays the list of tests that can be run. Defaults none Command Modes EXEC Privilege Command History Version 8.3.17.0 Supported on M I/O Aggregator hardware watchdog Set the watchdog timer to trigger a reboot and restart the system. Syntax hardware watchdog Defaults Enabled Debugging and Diagnostics | 247

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264

Debugging and Diagnostics
|
247
diag stack-unit
Run offline diagnostics on a stack unit.
Syntax
diag stack-unit
number
{
alllevels | level0 | level1 | level2
[verbose no-reboot] | terminate | interactive
{test <id>}
Defaults
none
Command Modes
EXEC Privilege
Command
History
hardware watchdog
Set the watchdog timer to trigger a reboot and restart the system.
Syntax
hardware watchdog
Defaults
Enabled
number
Enter the stack-unit number.
Range: 0 to 5
alllevels
Enter the keyword
alllevels
to run the complete set of offline diagnostic tests.
level0
Enter the keyword
level0
to run Level 0 diagnostics. Level 0 diagnostics check for the
presence of various components and perform essential path verifications. In addition, they
verify the identification registers of the components on the board.
level1
Enter the keyword
Level1
to run Level 1 diagnostics. Level 1 diagnostics is a smaller set of
diagnostic tests with support for automatic partitioning. They perform status/self test for all
the components on the board and test their registers for appropriate values. In addition, they
perform extensive tests on memory devices (e.g., SDRAM, flash, NVRAM, EEPROM, and
CPLD) wherever possible. There are no tests on 10G links. At this level, stack ports are shut
down automatically.
level2
Enter the keyword
level2
to run Level 2 diagnostics. Level 2 diagnostics is a full set of
diagnostic tests with no support for automatic partitioning. Level 2 diagnostics are used
primarily for on-board loopback tests and more extensive component diagnostics. Various
components on the board are put into loop back mode, and test packets are transmitted
through those components. These diagnostics also perform snake tests using VLAN
configurations. You must physically remove the unit from the stack to test 10G links.
verbose
Enter the keyword
verbose
to run the diagnostic in verbose mode. Verbose mode gives more
information in the output than standard mode.
no-reboot
Enter the keyword
no-reboot
to avoid automatic rebooting of the chassis after completion of
diagnostic execution. Generally, this option is never used because if you run the diagnostic
once again without rebooting the chassis, it may cause an issue with the diagnostic results.
terminate
Enter the keyword
terminate
to stop the execution of the level diag that is already started
using the diag stack-unit command. Once this CLI is issued, syslogs indicating the
termination of the diag test is displayed. The diag results for the executed tests are stored in
the flash directory (TestReport-SU-X.txt).
interactive
Enter the keyword
interactive
to run some individual diag tests such as POWERLEDTEST,
STATUSLEDTEST and so on. The help option under the interactive command displays the
list of tests that can be run.
Version 8.3.17.0
Supported on M I/O Aggregator