Skip to main content
NetApp Knowledge Base

Brocade FOS firmwaredownload failed due to invalid firmware path

Views:
683
Visibility:
Public
Votes:
1
Category:
fabric-interconnect-and-management-switches
Specialty:
brocade
Last Updated:

Applies to

  • Brocade Switches
  • SCP

Issue

firmwaredownload failed with error "The server is inaccessible or firmware path is invalid"  while using SCP protocol
 

<switchname>:<switchadminuser>> firmwaredownload
Server Name or IP Address: w.x.y.z
User Name: <sftpuser>
File Name: /fw/v7.4.2g2
Network Protocol(1-auto-select, 2-FTP, 3-SCP, 4-SFTP) [1]: 3
Do you want to input SFTP options (Y/N) [N]:
Verifying if the public key authentication is available.Please wait ...
The public key authentication is not available.
Password:
Do you want to continue with CRA (Y/N)[N]:

Server IP: w.x.y.z, Protocol IPv4
Checking system settings for firmwaredownload...
Failed to access sftp://<sftpuser>:@w.x.y.z//fw/fos/v9.0.1e1_G6_MID
The server is inaccessible or firmware path is invalid. Please make sure the server name/IP address and the firmware path are valid, the protocol and authentication are supported. It is also possible that the RSA host key could have been changed and please contact the System Administrator for adding the correct hostkey.

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.