Note that the SCP server is NOT hosted on port 22, it's on 52398.
If I try to archive the config with FTP, it works fine, and sends the file in about 2 seconds. if I try to archive using SCP it sits there for an eternity - 120 seconds? -then just returns to the command shell, and meanwhile on the SCP server there is no activity, not even a log in attempt. I am able to send files to the SCP server from a separate (also external) Linux box, so I know the SCP server is working and the firewalls with the custom port are correct.
Am I doing something wrong? Or can the Cisco SCP implementation not handle ports other than 22?
Listen: https://smarturl.it/CCRS9E25 Follow us: twitter.com/ciscochampions
With applications and users everywhere, the networks are now, more than ever, being tasked with delivering consistent protection while providing an exceptional user exper...
Listen: https://smarturl.it/CCRS9E24 Follow us: https://twitter.com/CiscoChampion
Cisco Radio Aware Routing addresses several of the challenges faced when merging IP routing and radio communications in mobile networks, especially those exhibiti...
Listen: https://smarturl.it/CCRS9E23 Follow us: https://twitter.com/CiscoChampion The Wi-Fi 6E Catalyst 9136 access point takes advantage of the 6-GHz band to produce a network that is more reliable and secure, with higher throughput, more ...
When moving from OSPFv2 to OSPFv3, there are many changes in the format of the LSAs Type, but the most known changes are: IP prefix informations are no longer carried in Type-1 LSA and Type-2 LSA, new LSAs Type 8 and 9 are added to carry these prefixes.