Skip to main content
NetApp Knowledge Base

Brocade firmware upgrade failed to download firmware signature. (0x40) to remote CP

Views:
2,197
Visibility:
Public
Votes:
6
Category:
ontap-9
Specialty:
brocade
Last Updated:

Applies to

  • Brocade DCX 85XX

Issue

  • Brocade Fabric OS download command fails with the message:

[SULB-1011],113,SLOT 6 CHASSIS,INFO,DCX8510,Firmwaredownload command failed. Failed to download firmware signature..

  • Command firmwaredownloadstatus provides the following failure:

firmwaredownloadstatus:
[1]: Sat Feb 13 20:06:46 2021 Slot 6 (CP0, active): Firmware is being downloaded to standby CP. This step may take up to 30 minutes.
[2]:  Sat Feb 13 20:06:49 2021 Slot 6 (CP0, active): Firmware download failed on standby CP - Failed to download firmware signature. (0x40)

  • Firewall or security system installed between switch and SCP/FTP server closing the TCP stream
  • Path used in the firmwaredownload command points to the firmware.gz file.
  • To check subnet for CP & Chassis use command ipaddrshow

ipaddrshow:
CHASSIS
Ethernet IP Address: XXX.XXX.XXX.49
Ethernet Subnetmask: 255.255.0.0
CP0
Ethernet IP Address: XXX.XXX.XXX.50
Ethernet Subnetmask: 255.255.255.0
Host Name: cp0
Gateway IP Address: none
CP1
Ethernet IP Address: XXX.XXX.XXX.51
Ethernet Subnetmask: 255.255.255.0

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.