Dell PowerEdge M1000e Fabric OS Troubleshooting and Diagnostics Guide - Page 69

Configuration Issues

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

Page 69 highlights

Firmware download issues 5 Symptom Symptom Symptom Firmwaredownload times out. Probable cause and recommended action This can be caused by an excessively slow network. If it takes more than 30 minutes to download firmware on a switch, or on each CP in a director, the firmware download process times out. If a timeout occurs on a switch, the firmware download process synchronizes the two partitions on the switch by starting a firmware commit operation. If a timeout occurs in a director, the firmware download process synchronizes the firmware on the two partitions on the CP blades by starting a firmware commit operation on each CP. Wait at least 15 minutes for the commit operation to complete then use the firmwareShow command to verify the partitions are synchronized. In some older versions of firmware, the firmware commit operation may not be started automatically on the switch (or on the standby CP in director). In this case, you can enter the firmwareCommit command manually on the switch (or on the standby CP in director) to synchronize the partitions. After the firmware commit operation completes, reissue the firmwareDownload command to upgrade the system. Cannot upgrade directly to v6.3.0. Upgrade your switch to v6.2.0 first before upgrading to the requested version. Probable cause and recommended action If the switch is running Fabric OS v6.1.0 or earlier, you will not be allowed to upgrade directly to v6.3.0 because of the "one-version" rule. Upgrade your switch to Fabric OS version v6.2.0 before upgrading to v6.3.0. The "one-version" rule also applies to downgrading. Server is inaccessible or firmware path is invalid. Probable cause and recommended action • The FTP or SCP server's host name is not known to the switch. Verify with your network administrator that the switch has access to the FTP server. Verify the path to the FTP or SCP server is accessible from the switch. For more information on checking your FTP or SCP server, see Chapter 4, "Configuration Issues". • The USB path is not correct. If your platform supports a USB memory device, verify that it is connected and running. Verify that the path name is correct by using the usbStorage -l command. Example of usbStorage -l command switch:admin> usbstorage -l firmwarekey\ 0B 2010 Mar 15 15:13 support\ 106MB 2007 Mar 24 05:36 support1034\ 105MB 2010 Mar 23 06:11 config\ 0B 2010 Mar 15 15:13 firmware\ 380MB 2010 Mar 15 15:13 FW_v6.4.0\ 380MB 2010 Mar 15 15:13 Available space on usbstorage 74% Example of error message switch:admin> firmwaredownload Server Name or IP Address: 192.126.168.115 User Name: userFoo File Name: /users/home/userFoo/firmware/v6.4.0 Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]: 2 Fabric OS Troubleshooting and Diagnostics Guide 55 53-1001769-01

  • 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
Fabric OS Troubleshooting and Diagnostics Guide
55
53-1001769-01
Firmware download issues
5
Symptom
Firmwaredownload times out.
Probable cause and recommended action
This can be caused by an excessively slow network. If it takes more than 30 minutes to download
firmware on a switch, or on each CP in a director, the firmware download process times out. If a
timeout occurs on a switch, the firmware download process synchronizes the two partitions on the
switch by starting a firmware commit operation. If a timeout occurs in a director, the firmware
download process synchronizes the firmware on the two partitions on the CP blades by starting a
firmware commit operation on each CP.
Wait at least 15 minutes for the commit operation to complete then use the
firmwareShow
command to verify the partitions are synchronized. In some older versions of firmware, the
firmware commit operation may not be started automatically on the switch (or on the standby CP in
director). In this case, you can enter the
firmwareCommit
command manually on the switch (or on
the standby CP in director) to synchronize the partitions. After the firmware commit operation
completes, reissue the
firmwareDownload
command to upgrade the system.
Symptom
Cannot upgrade directly to v6.3.0. Upgrade your switch to v6.2.0 first before upgrading to the
requested version.
Probable cause and recommended action
If the switch is running Fabric OS v6.1.0 or earlier, you will not be allowed to upgrade directly to
v6.3.0 because of the “one-version” rule. Upgrade your switch to Fabric OS version v6.2.0 before
upgrading to v6.3.0. The “one-version” rule also applies to downgrading.
Symptom
Server is inaccessible or firmware path is invalid.
Probable cause and recommended action
•
The FTP or SCP server’s host name is not known to the switch.
Verify with your network administrator that the switch has access to the FTP server.
Verify the path to the FTP or SCP server is accessible from the switch. For more information on
checking your FTP or SCP server, see
Chapter 4, “Configuration Issues”
.
•
The USB path is not correct.
If your platform supports a USB memory device, verify that it is connected and running. Verify
that the path name is correct by using the
usbStorage -l
command.
Example of usbStorage -l command
switch:admin>
usbstorage -l
firmwarekey\ 0B 2010 Mar 15 15:13
support\ 106MB 2007 Mar 24 05:36
support1034\ 105MB 2010 Mar 23 06:11
config\ 0B 2010 Mar 15 15:13
firmware\ 380MB 2010 Mar 15 15:13
FW_v6.4.0\ 380MB 2010 Mar 15 15:13
Available space on usbstorage 74%
Example of error message
switch:admin>
firmwaredownload
Server Name or IP Address:
192.126.168.115
User Name:
userFoo
File Name:
/users/home/userFoo/firmware/v6.4.0
Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]:
2