HP StorageWorks 1606 Brocade Fabric OS Troubleshooting and Diagnostics Guide v - Page 58

Troubleshooting firmwareDownload

Page 58 highlights

5 Troubleshooting firmwareDownload Perform a firmwareDownload -o command. The operand bypasses the checking of Coordinated HotCode Load (HCL). On single CP systems in interop fabrics, the HCL protocol is used to ensure data traffic is not disrupted during firmware upgrades. This option will allow a firmware download to continue even if HCL is not supported in the fabric or the protocol fails. Using this option may cause traffic disruption for some switches in the fabric. Symptom You receive a firmwaredownload is already in progress message. Probable cause and recommended action The firmware download process has already been started and it is in progress. Wait till it completes. You can use the firmwareDownloadStatus and firmwareShow commands to monitor its progress. If the problem persists, contact your switch support provider. Example of a firmwaredownload already in progress switch:admin> firmwaredownload Server Name or IP Address: 192.126.168.115 User Name: userFoo File Name: /users/home/userFoo/firmware/v6.2.0 Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]: 2 Password: Server IP: 192.126.168.115, Protocol IPv4 Checking system settings for firmwaredownload... Sanity check failed because firmwaredownload is already in progress. Troubleshooting firmwareDownload A network diagnostic script and preinstallation check is a part of the firmwareDownload procedure. The script and preinstallation check performs troubleshooting and automatically checks for any blocking conditions. If the firmware download fails, see the Fabric OS Message Reference for details about error messages. Also see, "Considerations for downgrading firmware" on page 45. If a firmware download fails in a director, the firmwareDownload command synchronizes the firmware on the two partitions of each CP by starting a firmware commit operation. Wait at least 15 minutes for this commit operation to complete before attempting another firmware download. If the firmware download fails in a director or enterprise-class platform, the CPs may end up with different versions of firmware and are unable to achieve HA synchronization. In such cases, issue the firmwareDownload -s command on the standby CP; the single mode (-s) option allows you to upgrade the firmware on the standby CP to match the firmware version running on the active CP. Then re-issue the firmwareDownload command to download the desired firmware version to both CPs. For example, if CP0 is running v6.1.0 on the primary and secondary partitions, and CP1 is running v6.0.0 on the primary and secondary partitions, then synchronize them by issuing the firmwareDownload command. NOTE Some of the messages include error codes (as shown in the example below). These error codes are for internal use only and you can disregard them. Example: Port configuration with EX ports enabled along with trunking for port(s) 63, use the portCfgEXPort, portCfgVEXPort, and portCfgTrunkPort commands to remedy this. Verify blade is ENABLED. (error 3) 44 Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-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

44
Fabric OS Troubleshoot and Diagnostics Guide
53-1001340-01
Troubleshooting firmwareDownload
5
Perform a
firmwareDownload -o
command. The operand bypasses the checking of Coordinated
HotCode Load (HCL). On single CP systems in interop fabrics, the HCL protocol is used to ensure
data traffic is not disrupted during firmware upgrades. This option will allow a firmware download
to continue even if HCL is not supported in the fabric or the protocol fails. Using this option may
cause traffic disruption for some switches in the fabric.
Symptom
You receive a firmwaredownload is already in progress message.
Probable cause and recommended action
The firmware download process has already been started and it is in progress. Wait till it
completes. You can use the
firmwareDownloadStatus
and
firmwareShow
commands to monitor its
progress. If the problem persists, contact your switch support provider.
Example of a firmwaredownload already in progress
switch:admin>
firmwaredownload
Server Name or IP Address:
192.126.168.115
User Name:
userFoo
File Name:
/users/home/userFoo/firmware/v6.2.0
Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]:
2
Password:
<hidden>
Server IP: 192.126.168.115, Protocol IPv4
Checking system settings for firmwaredownload...
Sanity check failed because firmwaredownload is already in progress
.
Troubleshooting firmwareDownload
A network diagnostic script and preinstallation check is a part of the
firmwareDownload
procedure.
The script and preinstallation check performs troubleshooting and automatically checks for any
blocking conditions. If the firmware download fails, see the
Fabric OS Message Reference
for
details about error messages. Also see,
“Considerations for downgrading firmware”
on page 45.
If a firmware download fails in a director, the
firmwareDownload
command synchronizes the
firmware on the two partitions of each CP by starting a firmware commit operation. Wait
at least
15
minutes for this commit operation to complete before attempting another firmware download.
If the firmware download fails in a director or enterprise-class platform, the CPs may end up with
different versions of firmware and are unable to achieve HA synchronization. In such cases, issue
the
firmwareDownload -s
command on the standby CP; the single mode (
-s
) option allows you to
upgrade the firmware on the standby CP to match the firmware version running on the active CP.
Then re-issue the
firmwareDownload
command to download the desired firmware version to both
CPs. For example, if CP0 is running v6.1.0 on the primary and secondary partitions, and CP1 is
running v6.0.0 on the primary and secondary partitions, then synchronize them by issuing the
firmwareDownload
command.
NOTE
Some of the messages include error codes (as shown in the example below). These error codes are
for internal use only and you can disregard them.
Example:
Port configuration with EX ports enabled along with trunking for port(s) 63, use the
portCfgEXPort
,
portCfgVEXPort
, and
portCfgTrunkPort
commands to remedy this. Verify blade is
ENABLED. (error 3)