Brocade Configupload Stopped Working after FOS Update to V9.2.0b

[Lekhpal]

Hello.  Have anybody faced this issue observed after the Brocade FOS Update to version:  v9.2.0b.

configUpload not permitted (ftp failed). Usage error.
Terminated

Note, that supportsave to same ftp works fine, and I guess supportsave and configupload works with same mechanism.   Tried two different FTP Servers,  of different vendors, still same observation:  configuload fails, supportsave works fine. Any clues, and solutions.

Best

[Cali · Accepted solution]

Hi,

Insecure protocols are now no longer supported, use SFTP or SCP.

Also: When performing supportSave with SCP as the selected transfer protocol, the command defaults to using SFTP internally. In environments where SFTP ports are blocked the supportSave upload will fail.

Cali

[Lekhpal]

Hi Cali.  Thanks for the pointer. We indeed tried using that path as well.  We first Enable secure switch mode (yes, y, no, n): [no] yes.  After that we tried doing a SFTP, and that also failed.  Do you have some tried/tested procedure to do that.  Please share.  Thanks

[Lekhpal]

Hi Cali.  

You mentioned:

In environments where SFTP ports are blocked the supportSave upload will fail.

And, on FTP/SFTP Host, I see this:

C:\Users\xyz>netstat -a -n | findstr 21
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING
TCP 10.8.34.177:21 10.8.34.177:51530 ESTABLISHED
TCP [::]:21 [::]:0 LISTENING
UDP 0.0.0.0:49321 *:*

C:\Users\xyz>netstat -a -n | findstr 22
TCP 10.8.1.74:51322 10.8.35.6:445 ESTABLISHED
UDP 0.0.0.0:52242 *:*
UDP [::]:52242 *:*

So 22 seems not listening.  

Now, how the port needs to be opened by FW Team.   Between each SAN Switch and the FTP/SFTP Server.  Correct.

Please advise.   Thanks

[NimaG]

Hello Lekhpal,
I understand that 'supportsave' works fine after FOS upgrade to v9.2.0b; however, 'configupload' does not work.
I see you have checked with two different FTP servers, with same outcome; with both FTP and SFTP.

Would you have any other switches that are working?
Regards,

[Lekhpal]

Hi.  The same behaviour observed in all 20 of them in both fabrics including the two director cores.  I suspect Port 22 is not open,  or there is some bug in new FOS, as supportsave works with ftp protocol though.  Configupload fails.   Thanks

[NimaG]

Hello Lekhpal,
I request you to raise an HPE support case as your entire environment is affected. Log analysis and expert diagnosis will be required to identify the issue and provide a solution.
Thanks,

[Lekhpal]

@NimaG @Cali Hi Cali and NimaG,

As you had suggested insecure protocols are no more supported. So, we used sftp after opening port 22 bi-directionally between each switch and the FTP/SFTP Server,  configupload works fine.

But now another strange behaviour seen.   Interactive command line works but via script doesn't work and both are same.

switch:admin> configupload
Protocol (scp, ftp, sftp, local) [ftp]: sftp
Do you want to continue with CRA (Y/N) [N]:
SCP/SFTP Server Port Number [22]:
Server Name or IP Address [host]: 10.X.XX.XX
User Name [user]: StorageUser
Path/Filename [<home dir>/config.txt]: /backup.cfg
Section (all|chassis|switch [all]):
StorageUser@10.X.XX.XX's password:

configUpload complete: All selected config parameters are uploaded

configupload -all -p sftp -P 22 10.X.XX.XX,StorageUser,/backup.cfg,somepassword
configupload -all -p sftp -P 22 "10.X.XX.XX","StorageUser","/backup.cfg","somepassword"

configUpload not permitted (sftp failed).
Terminated

Any clue or pointers.

Thanks