The Cisco Small Business Managed Switches can be remotely accessed and configured through the Command Line Interface (CLI). Accessing the CLI allows commands to be entered in a terminal-based window. If you prefer to configure using terminal commands on your switch through the CLI rather than the web-based utility, this would be an easier alternative. Certain tasks such as Layer 3 mode enabling can only be performed through the CLI.
In order to remotely access the CLI of your switch, you must use an SSH or Telnet client. You must also enable the Telnet and SSH service on your switch first before you can access it remotely.
Note: For instructions on how to configure the Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) settings on your switch, click here.
This article provides instructions on how to access the CLI of your switch through SSH or Telnet using the following clients:
PuTTY — A standard Telnet and SSH client. You can download an installer here and install in your Windows computer.
Terminal — An application that is pre-installed in every Mac OS X computer. It is also known as the shell or the console.
Important: Before you make an SSH or Telnet connection to the switch, you must set the IP address for the switch. For instructions, click here.
1.4.7.06 — Sx300, Sx500
2.2.8.04 — Sx350, SG350X, Sx550X
Access the CLI of the Switch through SSH
The SSH sessions disconnect automatically after the idle time configured in the switch has passed. The default idle session timeout for SSH is 10 minutes.
To make an SSH connection to the switch, choose your platform:
Note: The images may vary according to the version of the Windows operating system you are using. In this example, the Windows 7 Ultimate is used and the PuTTY version is 0.63.
Step 1. Launch the PuTTY client on your computer.
Step 2. Enter the hostname or IP address of the switch that you want to remotely access in the Host Name (or IP address) field.
Note: In this example, 192.168.100.105 IP address is used.
Step 3. Enter 22 as the port number to be used for the SSH session in the Port field.
Step 4. In the Connection type area, click the SSH radio button to choose SSH as your method of connection with the switch.
Step 5. (Optional) To save the session, enter the session name in the Saved Sessions field.
Note: In this example, SSH Sessions is used.
Step 6. (Optional) Click Save to save the session.
Step 7. (Optional) In the Close window on exit area, click the radio button to choose the behavior of the SSH window upon exit.
Note: In this example, Only on clean exit is chosen.
Step 8. Click Open to start the session.
Step 9. If this is your first time using SSH to connect to the switch, you may receive a Security Breach Warning. This warning lets you know that it is possible that you are connecting to another computer pretending to be the switch. Once you have ensured you entered the correct IP address in the Host Name field in Step 4, click Yes to update the Rivest Shamir Adleman 2 (RSA2) key to include the new switch.
Step 10. Enter the username and password of the switch in the login as, User Name and Password fields accordingly.
You should now have successfully remotely accessed the CLI of your switch through SSH using PuTTY.
I was setup SSL VPN. on my RV340 Mandatory Gateway SettingsGateway Interface: WAN1Gateway Port: 8443Certificate File: DefaulClient Address Pool: 10.11.12.0Client Netmask: 255.255.255.0 My LAN/DHCP Settings IP Version 4DHCP Mode: server...
I am trying to setup a site to site vpn to 2 remote sites where the remote sites have MIFI. if I use the RV160w at the remote sites, is there an issue to leverage the address from the wireless MIFI to bind the tunnel to back to the RV160 in the main...
Hi all. This is my first time setting up a home lab and I feel like the current typology I have is extremely inefficient. I have posted my current typology below and will offer a brief explanation of what I have done. Essentially what I have done is I use...
Yesterday I ended up checking for new RV340 firmware and discovered the CIsco Security Advisory on the Authenticated Remote Code Execution Vulnerabilities. I downloaded and installed the new firmware, version 1.0.03.21. However, with both p...
Dear Everyone who reads this, A company was going out of business and said all the ip phones inside were to go to another home or company, i went in and garbed two a 7940 and 7960, When i got home and pluged them into my netgear p...