Dell PowerEdge R830 Integrated Remote Access Controller 8 Version 2.70.70.70 U - Page 295

Use case scenarios, Troubleshooting an inaccessible managed system

Page 295 highlights

25 Use case scenarios This section helps you in navigating to specific sections in the guide to perform typical use case scenarios. Topics: • Troubleshooting an inaccessible managed system • Obtaining system information and assess system health • Setting up alerts and configuring email alerts • Viewing and exporting Lifecycle log and System Event Log • Interfaces to update iDRAC firmware • Performing graceful shutdown • Creating new administrator user account • Launching server remote console and mounting a USB drive • Installing bare metal OS using attached virtual media and remote file share • Managing rack density • Installing new electronic license • Applying IO Identity configuration settings for multiple network cards in single host system reboot Troubleshooting an inaccessible managed system After receiving alerts from OpenManage Essentials, Dell Management Console, or a local trap collector, five servers in a data center are not accessible with issues such as hanging operating system or server. Need to identify the cause to troubleshoot and bring up the server using iDRAC. Before troubleshooting the inaccessible system, make sure that the following prerequisites are met: • Enable last crash screen • Alerts are enabled on iDRAC To identify the cause, check the following in the iDRAC web interface and re-establish the connection to the system: NOTE: If you cannot access the iDRAC web interface, go to the server, access the LCD panel, write down the IP address or the host name, and then perform the following operations using iDRAC web interface from your management station: • Server's LED status - Blinking amber or Solid amber. • Front Panel LCD status or error message - Amber LCD or error message. • Operating system image is seen in the Virtual Console. If you can see the image, reset the system (warm boot) and log in again. If you are able to log in, the issue is fixed. • Last crash screen. • Boot capture video. • Crash capture video. • Server Health status - Red x icons for the system components with issues. • Storage array status - Possible array offline or failed • Lifecycle log for critical events related to system hardware and firmware and the log entries that were logged at the time of system crash. • Generate Tech Support report and view the collected data. • Use the monitoring features provided by iDRAC Service Module Related tasks Previewing virtual console Viewing boot and crash capture videos Viewing system health Viewing logs Generating SupportAssist Collection Use case scenarios 295

  • 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
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298

Use case scenarios
This section helps you in navigating to specific sections in the guide to perform typical use case scenarios.
Topics:
Troubleshooting an inaccessible managed system
Obtaining system information and assess system health
Setting up alerts and configuring email alerts
Viewing and exporting Lifecycle log and System Event Log
Interfaces to update iDRAC firmware
Performing graceful shutdown
Creating new administrator user account
Launching server remote console and mounting a USB drive
Installing bare metal OS using attached virtual media and remote file share
Managing rack density
Installing new electronic license
Applying IO Identity configuration settings for multiple network cards in single host system reboot
Troubleshooting an inaccessible managed system
After receiving alerts from OpenManage Essentials, Dell Management Console, or a local trap collector, five servers in a data center are
not accessible with issues such as hanging operating system or server. Need to identify the cause to troubleshoot and bring up the server
using iDRAC.
Before troubleshooting the inaccessible system, make sure that the following prerequisites are met:
Enable last crash screen
Alerts are enabled on iDRAC
To identify the cause, check the following in the iDRAC web interface and re-establish the connection to the system:
NOTE:
If you cannot access the iDRAC web interface, go to the server, access the LCD panel, write down the IP address
or the host name, and then perform the following operations using iDRAC web interface from your management station:
Server’s LED status — Blinking amber or Solid amber.
Front Panel LCD status or error message — Amber LCD or error message.
Operating system image is seen in the Virtual Console. If you can see the image, reset the system (warm boot) and log in again. If you
are able to log in, the issue is fixed.
Last crash screen.
Boot capture video.
Crash capture video.
Server Health status — Red
x
icons for the system components with issues.
Storage array status — Possible array offline or failed
Lifecycle log for critical events related to system hardware and firmware and the log entries that were logged at the time of system
crash.
Generate Tech Support report and view the collected data.
Use the monitoring features provided by iDRAC Service Module
Related tasks
Previewing virtual console
Viewing boot and crash capture videos
Viewing system health
Viewing logs
Generating SupportAssist Collection
25
Use case scenarios
295