●
●
●
●
●
Access the CLI via PuTTY using a Console
Connection on 300 and 500 Series Managed
Switches
Objective
Switches can be accessed and configured through the Command Line Interface (CLI). Accessing
the CLI allows commands to be entered in a terminal based window. For a user who has had more
experience with terminal commands, this may be an easier alternative to navigating the web
configuration utility. Certain tasks such as recovering an administrator password can only be
performed through the CLI. In order to access the CLI you must use an SSH client. PuTTY is a
standard SSH client and can be found here. This document assumes you are connecting to the
switch using PuTTY.
The objective of this document is to show you how to access the Command Line Interface (CLI) of
a switch and a Secure Shell (SSH) client.
Note: Cisco 200 Series Small Business Managed Switches do not support the CLI.
Applicable Devices | Software Version
Sx300 Series | 1.2.7.76 (Download latest)
Sx350 Series | 1.2.7.76 (Download latest)
SG350X Series | 1.2.7.76 (Download latest)
Sx500 Series | 1.2.7.76 (Download latest)
Sx550X Series | 1.2.7.76 (Download latest)
Accessing the CLI via PuTTY with a Console Connection
Step 1. Connect the switch to the computer using a standard 9-pin serial cable.
The Cisco DB9 to RJ45 Console Cable also supports console connections, but only if the switch
has an RJ45 Console port. An RJ45 Console port resembles an Ethernet port and is labeled
CONSOLE on the back of the switch.
Newer laptops don’t have Serial ports on them, so in this case you have to use a USB to Serial
adapter. When plugging that into a computer it assigns a COM port number to it that is not COM1.
If this is the case for you, you need to know where to look to find the correct COM port number
when setting up the connection with PuTTY. Right-click on the Windows logo/Start menu and click
on Device Manager to open it.
