Context Navigation

CLISetup

Timestamp:: Jan 24, 2010, 5:35:47 PM (14 years ago)
Author:: akoshibe
Comment:: —

Legend:

: Unmodified
: Added
: Removed
: Modified

Internal/OpenFlow/CLISetup

-              v24
+              v25
 If you are unfamiliar with "smart" switches or how to configure them, this is the place to start. This section covers the following:
  * Logging in for the first time (serial connection)
   * troubleshooting the connection
+ * Using the serial connection to log in
+  * troubleshooting
  * User modes and contexts
+  * available commands / help pages
+  * switching contexts and autocompletion (a remark)
  * Creating and configuring VLANs and VLAN interfaces
  * Setting up Telnet
+  * Using it
+  * troubleshooting
 ----
 == Logging into the switch for the first time. ==
 Out of the box, the switches are not configured for Telnet. In this case, you need to make configuration changes by logging into the switch via the console port, which uses a standard RS-232 cable. You'll also need to have software installed on your PC to be able to establish a serial connection. Kermit is the recommended choice - it's default settings allow you to connect without changing anything.
+Out of the box, the switches are not configured for Telnet. In this case, you need to log into the switch using the serial port, which uses a standard RS-232 cable. You'll also need to have software installed on your PC to be able to establish a serial connection. Kermit is the recommended choice - it's default settings allow you to connect without changing anything.
 . '''Name your switch.''' People names are easier to remember than IP addresses or machine-like names i.e. as01-hh-alex, and are easier to use in discussion if everyone agrees on names. Note, the names Bob, Nancy, and Andy are already taken.
 …
  * Make sure you are root when you start up kermit.
  *Kermit will balk if you try to log in while there is a session going on. Make sure that no one else is logged in via serial, and that you haven't forgotten to log out during a previous session.
+ * Kermit will balk if you try to log in while there is a session going on. Make sure that no one else is logged in via serial, and that you haven't forgotten to log out during a previous session.
  * If you get a message like this with the one-liner of `kermit -l /dev/ttyS0`. :
 …
  * If, for some reason, you can't use kermit or have to configure the settings for your serial connection, use the following settings:
+{{{
   * speed: 9600
   * data bits: 8
 …
   * Flow control: none
   * Parity: none
+}}}
  Note, we have found that minicom doesn't seem to work too well with the switches. If you get it to work, please note it!
 …
 Here, typing different sets of commands bring you to different configuration modes specific to the feature you are trying to modify. the commands that bring you to the specialized modes are called "contexts," and typing them are called "entering a context." Some contexts we want to focus on are:
  * `vlan n` - create/configure standard VLANs, n being the VLAN ID (some number)
  * `interface vlan n` - create/ configure a virtual interface with both Layer 2 and 3 characteristics
  * `interface gigabitethernet 0/n` - configure specific port, n being number between 1 and 48
  * `line <vty|console>` - configure telnet or console parameters, respectively
+{{{
+ - `vlan n` - create/configure standard VLANs, n being the VLAN ID (some number)
+ - `interface vlan n` - create/ configure a virtual interface with both Layer 2 and 3 characteristics
+ - `interface gigabitethernet 0/n` - configure specific port, n being number between 1 and 48
+ - `line <vty|console> vtyrange<0-b>` - configure telnet or console parameters, respectively
+}}}
 Don't worry even if these don't make sense now - The meanings of the contexts will be explained as we introduce each context.
 As you can see, when you enter a context, the prompt becomes "(config-if)#." However, this prompt doesn't indicate what context you are using; you just have to remember what you are doing.
+As you can see, when you enter a context, the prompt becomes "(config-if)#." However, this prompt doesn't indicate what context you are using; you just have to remember what you are doing. If you forget where you were, typing "show" will display all of the configurations saved for that specific context (hopefully giving you enough information to let you recall what you were trying to do).
 {{{
 (config)# interface vlan 8              <<---start by entering the 'interface vlan' context
+(config-if)#
+(config-if)# interface gi 0/3           <<---switch to 'interface gigabitethernet' context
+(config-if)#                            <<---note how prompt still shows up as "config-if"
+}}}
+!(config-if)#
+!(config-if)# interface gi 0/3           <<---switch to 'interface gigabitethernet' context
+!(config-if)#                            <<---note how prompt still shows up as "config-if"
+}}}
+As you can see above, when you make changes to the configurations (e.g. create vlan interfaces as in this example), you will see a "!" before the prompt. This is there to remind you that you've made changes that must be saved if you want them to survie a reboot. The command "save" intuitively saves the settings.
 The command `exit` lets you exit from contexts and enabled mode, or lets you log out of the switch if you were just in user mode.
+[[BR]]
+----
+== Creating and configuring VLANs and VLAN interfaces ==
+[[BR]]
+{{{
+!(config-if)# save
+(config-if)# exit
+(config)# exit
+#
+}}}
+=== Available commands / help pages ===
+Like with Cisco switches, typing `?` at the prompt will list the available commands along with a brief summary. If you are in a certain context, typing `?` will show you configuration options available for that context.
+=== switching contexts and autocompletion ===
+From the intitial configuration prompt, you can let the switch autocomplete contexts. For example:
+{{{
+sw-sb09(config)# int gi 0/34     <<-- instead of "interface gigabitethernet 0/34"
+sw-sb09(config-if)#
+}}}
+However, if you are already in a context, and you want to switch to another context, you must type the first word in full, else the switch will throw an error:
+{{{
+sw-sb09(config-if)# int gi 0/35
+int gi 0/35
+ ^
+% illegal parameter at '^' marker
+sw-sb09(config-if)# interface gi 0/35
+sw-sb09(config-if)#
+}}}
 ----
 == Setting up Telnet ==
 …
 }}}
+=== Using Telnet ===
+Once you've set up telnet on your switch, you can access the switch with the IP address you've assigned it during step 2 above. So for this switch you would issue the following command from your terminal:
+{{{
+$ telnet 192.168.10.1
+}}}
+The username and password are the same for this prompt once you connect.
+=== Troubleshooting ===
+ ...coming soon, if ever
+----
+== Creating and configuring VLANs and VLAN interfaces ==