ICX8000 SCP Backup Creates 0-Byte Files on QNAP Server

[ahmad_bahrami]

Hello Ruckus Support Team,

I am experiencing an issue when attempting to back up the running-configuration from ICX8200 switches to a QNAP server using SCP.

copy running-config scp 10.x.x.x /QNAP/S1-Core-MDF.cfg

The switch initiates the transfer, but the process takes an unusually long time and ultimately creates a backup file with a size of 0 bytes on the QNAP server instead of the expected configuration file.

To rule out issues with the SCP server configuration, I performed the same backup procedure on more than 200 switches from the ICX7000 series. In all cases, the SCP backup completed successfully and the configuration files were transferred correctly.

The issue appears to be specific to the ICX8000 series, as I have consistently observed the problem on ICX8200 switches while the identical SCP destination and procedure work properly on ICX7000 switches.

Could you please confirm whether this is a known issue, firmware bug, or SCP compatibility problem affecting the ICX8000 series? If so, are there any recommended workarounds or firmware versions that resolve this behavior?

Thank you for your assistance.

Best regards,

Ahmad Bahrami

[va10462]

Hi Ahmad,

• The same QNAP SCP server successfully accepts backups from 200+ ICX7000 switches.
• The issue is consistently reproducible only on ICX8200.
• The transfer starts but eventually creates a 0-byte file, suggesting that the SSH/SCP session is established but the data transfer never completes.

the problem is more likely related to either:

• an SCP protocol compatibility issue between the FastIron 10.x SCP client and the SSH implementation on the QNAP NAS,
• or a software issue specific to the FastIron version running on the ICX8200.

Recommended troubleshooting

Before concluding that this is a software defect, I would recommend collecting the following information:

1. FastIron version

   show version

   Verify the exact 10.0.x build (for example 10.0.10d/e/f/g).

2. Test with another SCP server

   • Linux OpenSSH
   • WinSCP SFTP/SCP service
   • SolarWinds SCP Server

   If the backup succeeds to another SCP server, it would strongly indicate a compatibility issue with the QNAP SSH/SCP implementation.

3. Test alternate transfer protocols

   • TFTP
   • SFTP (if supported by your FastIron release)
   • FTP

   This helps determine whether the issue is isolated to SCP.

4. Capture SSH debug logs
   If available in your software version:

   debug ssh

   or collect packet captures between the switch and the QNAP server to determine where the SCP session terminates.

5. Review QNAP SSH logs
   Check the NAS logs for:
   • authentication success
   • SCP session termination
   • protocol errors
   • permission errors

Thanks,

Vivek