![thebrain 9 manual thebrain 9 manual](https://d3i71xaburhd42.cloudfront.net/fe954e425cd9a9c6835de4eddf398953188345d2/2-Table1-1.png)
Cisco has its own special terminology for this (study Chapter 8 "Configuration and Image File Commands" of the CLI GUIDE for more information), but for now I will just give myself the actual command without going into the details:
![thebrain 9 manual thebrain 9 manual](https://images-na.ssl-images-amazon.com/images/I/71SeU-htxVL.jpg)
At this point, I should be able to log in via SSH.Next, make sure the SSH server is running: Security -> TCP/UDP Services -> SSH Service -> Enable -> Apply.actually, I prefer access via SSH key, but this is left as an exercise to me)
#Thebrain 9 manual password
![thebrain 9 manual thebrain 9 manual](https://images-na.ssl-images-amazon.com/images/I/71f0uNjn-hL.jpg)
Decide which VLAN will be default and which will be Management (in my case I have default VLAN 1 and management VLAN 15).This management VLAN must exist, and it must be assigned an IP address and netmask. The switch has a management interface, which is a VLAN. For this, it is important to understand what it means to assign an IP address to a switch like this. The first thing I wanted was to assign the switch an IP address so I could access the web UI.This topic alone is worth a separate article.
#Thebrain 9 manual serial
Using the provided serial cable, I got access to the management console.See also this blog post for useful SF300/SG300 CLI commands. Here are some notes on how I got started provisioning the switches. We recently got our hands on some Cisco SG300 52-port "top-of-rack" switches, and I have started taking some "baby steps" with them.