So I'm trying to manage a growing fleet of Cisco RV325 routers, and I'd like to do more via the command-line interface. Things like regular backups, connectivity tests, even regular device reboots. Unfortunately, my initial foray into realizing this was frustrated... right at the beginning, since I get the error:
I know I have the correct username and password - I can login to the HTTPS console just fine, and my password is saved in a password manager. Both "SSH" and "Remote SSH" are enabled under "Firewall" > "General", and upon my initial connection to our router I got the usual SSH message (indicating that SSH is indeed running on the router):
$ ssh firstname.lastname@example.org
The authenticity of host 'routerurl.com (184.108.40.206)' can't be established.
ECDSA key fingerprint is SHA256:JGsaBbDgjKChWike6x28Ny50tumBFkEW8SWvfhO6AXk.
Are you sure you want to continue connecting (yes/no)?
This is frustrating guys. It's SSH. It shouldn't be this hard.
Cisco has disabled the console for this model. They say: “Maybe in the future we will do it”, “GUI is the future, the console is not” and so on. I also bought an RV model, because there promise a console access. Before i working with a catalysts series and work only via console. Buying an SMB series was my big mistake: "No support", "No documentation", "Tons of bugs".
Oh that's exciting! Classic Cisco, though. I'm sure artificially deactivating features that can be found for free in stable, freely downloadable operating systems has nothing to do with the fact that their market share in networking devices continues to decline. At my past gig, we used Fortinet devices, and they had some pretty bomb stuff!
Like basic SSH access, for example.
Oh well. This is what competitors are for, I suppose.