Skip to main content
NetApp Knowledge Base

Broadcom BES-53248 RCF File Upload Fails with "File transfer failed"

  1. Last updated
  2. Save as PDF
Views:
7
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
HW
Last Updated:

Applies to

  • Broadcom BES-53248 Cluster Network Switch

  • EFOS 3.12.x

  • Reference Configuration File (RCF) upgrade / staging via SCP / SFTP

Issue

  • Staging or uploading an RCF script file (e.g., RCF-v1.14a-BES-53248-CL1.txt) to switch NVRAM (nvram:reference-config) fails immediately.

  • Switch CLI displays:

(switch)# copy scp://<username>@<server_ip>/<file_path> nvram:reference-config
Mode........................................... SCP
Set Server IP.................................. <server_ip>
Path........................................... ./
Filename....................................... <file_name>
Data Type...................................... unknown
Are you sure you want to start? (y/n) y
SCP Unknown file type transfer starting...

File transfer failed

  • Attempting to paste the configuration directly into the CLI results in:

    • Waiting for the pending transfer to complete...

    • Network error: Software caused connection abort

  • ICMP ping between the switch management interface and the server succeeds.

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.