Dell PowerEdge VRTX Chassis Management Controller Version 1.0 for Dell PowerEd - Page 178

Recovering Firmware Image, Troubleshooting Network Problems

Get Dell PowerEdge VRTX PDF manuals and user guides View all Dell PowerEdge VRTX manuals
Add to My Manuals
Save this manual to your list of manuals

Page 178 highlights

To obtain recovery information: 1. Install a NULL modem cable between a CMC system and a client system. 2. Open a terminal emulator of your choice (such as HyperTerminal or Minicom). Enter the following specification when prompted: 8 bits, no parity, no flow control, baud rate 115200. A core memory failure displays an error message every 5 seconds. 3. Press the key. If a recovery prompt appears, additional information is available. The prompt indicates the CMC slot number and failure type. To display failure reason and syntax for a few commands, type recover, and then press . Sample prompts: recover1[self test] CMC 1 self test failure recover2[Bad FW images] CMC2 has corrupted images - If the prompt indicates a self test failure, there are no serviceable components on CMC. CMC is bad and must be returned to Dell. - If the prompt indicates Bad FW Images, complete tasks in Recovering Firmware Image. Recovering Firmware Image CMC enters recover mode when a normal CMC operating boot is not possible. In recover mode, a small subset of commands are available that allow you to reprogram the flash devices by uploading the firmware update file, firmimg.cmc. This is the same firmware image file used for normal firmware updates. The recovery process displays its current activity and boots to the CMC OS upon completion. When you type recover and then press at the recovery prompt, the recover reason and available subcommands display. An example recover sequence may be: recover getniccfg recover setniccfg 192.168.0.120 255.255.255.0 192.168.0.1 recover ping 192.168.0.100 recover fwupdate -g -a 192.168.0.100 NOTE: Connect the network cable to the left most RJ45. NOTE: In recover mode, you cannot ping CMC normally because there is no active network stack. The recover ping command allows you to ping to the TFTP server to verify the LAN connection. You may need to use the recover reset command after setniccfg on some systems. Troubleshooting Network Problems The internal CMC trace log allows you to debug CMC alerts and networking. You can access the trace log using the CMC Web interface or RACADM. See the gettracelog command section in the RACADM Command Line Reference Guide for iDRAC7 and CMC. The trace log tracks the following information: • DHCP - Traces packets sent to and received from a DHCP server. • DDNS - Traces dynamic DNS update requests and responses. • Configuration changes to the network interfaces. 178

  • 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
To obtain recovery information:
1.
Install a NULL modem cable between a CMC system and a client system.
2.
Open a terminal emulator of your choice (such as HyperTerminal or Minicom). Enter the following specification
when prompted: 8 bits, no parity, no flow control, baud rate 115200.
A core memory failure displays an error message every 5 seconds.
3.
Press the <Enter> key.
If a recovery prompt appears, additional information is available. The prompt indicates the CMC slot number and
failure type.
To display failure reason and syntax for a few commands, type
recover
, and then press <Enter>.
Sample prompts:
recover1[self test] CMC 1 self test failure
recover2[Bad FW images] CMC2 has corrupted images
–
If the prompt indicates a self test failure, there are no serviceable components on CMC. CMC is bad and
must be returned to Dell.
–
If the prompt indicates
Bad FW Images
, complete tasks in
Recovering Firmware Image
.
Recovering Firmware Image
CMC enters recover mode when a normal CMC operating boot is not possible. In recover mode, a small subset of
commands are available that allow you to reprogram the flash devices by uploading the firmware update file,
firmimg.cmc
. This is the same firmware image file used for normal firmware updates. The recovery process displays its
current activity and boots to the CMC OS upon completion.
When you type recover and then press <Enter> at the recovery prompt, the recover reason and available sub-
commands display. An example recover sequence may be:
recover getniccfg
recover setniccfg 192.168.0.120 255.255.255.0
192.168.0.1
recover ping 192.168.0.100
recover fwupdate -g -a 192.168.0.100
NOTE:
Connect the network cable to the left most RJ45.
NOTE:
In recover mode, you cannot ping CMC normally because there is no active network stack. The
recover
ping <TFTP server IP>
command allows you to ping to the TFTP server to verify the LAN connection. You
may need to use the
recover reset
command after
setniccfg
on some systems.
Troubleshooting Network Problems
The internal CMC trace log allows you to debug CMC alerts and networking. You can access the trace log using the
CMC Web interface or RACADM. See the
gettracelog
command section in the
RACADM Command Line Reference
Guide for iDRAC7 and CMC
.
The trace log tracks the following information:
•
DHCP — Traces packets sent to and received from a DHCP server.
•
DDNS — Traces dynamic DNS update requests and responses.
•
Configuration changes to the network interfaces.
178