Fibre Channel (SAN)

Reply
Contributor
Posts: 47
Registered: ‎07-21-2009

firmwaredown failure

Hi, I tried upgrading FOS on two 8510-18 switches from v7.2.1f to v7.3.0c. I successfully upgraded two 8510-8 switches without any issue. The 2nd upgrade on the two 8510-18 switces failed. Both with differnent error. Here is what I got for the two.

 

#firmwareshow
Slot Name       Appl     Primary/Secondary Versions               Status
--------------------------------------------------------------------------
  6  CP0        FOS      v7.2.1f                                  STANDBY
                         v7.2.1f                                 
  7  CP1        FOS      v7.2.1f                                  ACTIVE *
                         v7.2.1f                                 

                               
FID128:admin> firmwaredownload
Server Name or IP Address: 192.168.x.x
User Name: xxxxxx
File Name: /home/xxxxxx/v7.3.0c
Network Protocol(1-auto-select, 2-FTP, 3-SCP, 4-SFTP) [1]: 3
Verifying if the public key authentication is available.Please wait ...
The public key authentication is not available.
Password:
Server IP: 192.168.x,x, Protocol IPv4
Checking system settings for firmwaredownload...
System settings check passed.

This command will upgrade the firmware on both CP blades. If you want to
upgrade firmware on a single CP only, please use -s option.

You may run firmwaredownloadstatus to get the status of this
command.

This command will cause a warm/non-disruptive boot on the active CP,
but will require that existing telnet, secure telnet or SSH sessions
be restarted.


Do you want to continue (Y/N) [Y]: y
Firmware is being downloaded to standby CP. This step may take up to 30 minutes.
Firmware is being downloaded to Standby CP. Please wait...
Firmware download failed on standby CP - Failed to download firmware signature. (0x40)
Please use firmwaredownloadstatus and firmwareshow to see the firmware status.

 

2nd one took the firmware and ran for a little over half hour then timed out. Here is the error condition for the 2nd one.

 

fabos                       ##################################################
fabos-daemons               ##################################################
fabos-zoning                ##################################################
Firmwaredownload timed out..
2017/02/05-10:02:13, [SULB-1003], 9466, SLOT 7 | CHASSIS, INFO, xxxxxxx_DCX8518, Firmwarecommit has started.

 

The 2nd firmware installation was very slow. Is there any timeout value that can be set for firmwaredownload? As for the first failure, have anyone seen this or any ideas what's going on here.

Thanks

 

 

Brocade Moderator
Posts: 321
Registered: ‎08-31-2009

Re: firmwaredown failure

[ Edited ]

Hello,

 

The issue can come from the Ethernet connection. Can you check the configuration of Ethernet port of both Brocade switches and Ethernet switches where the units are connected?

Any and all information provided by me is not reviewed, approved or endorsed by Brocade and is provided solely as a convenience for Brocade customers. All systems and all networks are different and unique. If you have a service affecting network problem, please open a TAC service request for service through Brocade, or through your OEM equipment provider. If this provided you with a solution to this issue, please mark it with the button at the bottom "Accept as solution"
Valued Contributor
Posts: 555
Registered: ‎03-20-2011

Re: firmwaredown failure

For the first issue I agree with Thierry, your Standby CP can't connect to the FTP server where you keep the firmware.

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook