Unable to collect configupload or supportsave via SCP and SFTP on Brocade Switch
Applies to
Brocade SAN Switches
Issue
Unable to collect 'supportsaves' or 'configupload' by Secure Copy (SCP) and Secure File Transfer Protocol (SFTP) even it meets the following requirements.
- Switch is able to ping the SCP/SFTP server.
- SCP/SFTP server is also able to ping switch.
- No firewall blocking SCP or SFTP ports.
- Works with FTP.
SCP Example:
switch:admin> configupload
Protocol (scp, ftp, sftp, local) [ftp]: scp
Do you want to continue with CRA (Y/N) [N]: y
Server Name or IP Address [host]: 192.168.1.2
User Name [user]: admin
Path/Filename [
/config.txt]: /configupload.scp
Section (all|chassis|switch [all]): switch
lost connection
configUpload not permitted (scp failed).
Terminated
SFTP Example:
switch:admin> supportsave
This command collects RASLOG, TRACE, supportShow, core file, FFDC data
and then transfer them to a FTP/SCP/SFTP server or a USB device.
This operation can take several minutes.
NOTE: supportSave will transfer existing trace dump file first, then
automatically generate and transfer latest one. There will be two trace dump
files transferred after this command.
OK to proceed? (yes, y, no, n): [no] y
Host IP or Host Name: 192.168.1.2
User Name: admin
Password:
Protocol (ftp | scp | sftp): sftp
Remote Directory: /
Do you want to continue with CRA (Y/N) [N]: y
Saving support information for switch:switch, module:RAS...
....................................................................................
Remote Host:Could not connect to remote host.
SupportSave failed.