Changes between Version 18 and Version 19 of Internal/OpenFlow/CLISetup

Timestamp:

Dec 15, 2009, 2:59:56 AM (15 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/CLISetup

@@ -273 +273 @@
 == Elucidation (Or, Frequently asked questions) ==
 
-As of now, this is just a list of facts/ a flow-chart. Diagram to accompany coming soon.
+As of now, this is just a how-to/list of facts on how to configure the IP8800. 
+
+=== Logging in for the first time. ===
 Assuming you have a brand new IP8800 on your hands:
 
-=== Logging in for the first time. ===
-
 Telnet is not configured by default, so you need to log in via the console port.
 
-1. Name your switch. 
-
-2. Acquire a RS-232 cable -  Hook up the cable to the port labeled 'console' on the switch. 
-
-3. If not already there, install kermit on your machine. Kermit is recommended because its default settings can be used to connect to the switch.
-
-4. Connect via serial using the following commands (Make sure you are root):
+1. 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. 
+
+2. Acquire a RS-232 cable -  Hook up the cable to the port labeled 'console' on the switch, the other end to your PC.  
+
+3. If not already installed, install kermit on your PC. Kermit is recommended because its default settings can be used to connect to the switch.
+
+4. Connect via serial using the following commands at the console (Make sure you are root):
  {{{
   /$ kermit
@@ -300 +300 @@
 }}}
 
+You should then see something like below:
+
+{{{
+
+Connecting to /dev/ttyS0, speed 0
+ Escape character: Ctrl-\ (ASCII 28, FS): enabled
+Type the escape character followed by C to get back,
+or followed by ? to see other options.
+----------------------------------------------------
+
+
+login:
+
+}}}
+If the login prompt doesn't come up, hitting enter should bring it up. The default username is `operator`, and the password is blank.    
+
 `Ctrl-\ q` ends the kermit session. 
-The default username is `operator`, and the password is blank.    
 
 
 == Configuration ==
-For configuration, you need to be in privileged mode. The magic word is `enable`. `configure` brings you to the configuration prompt, which looks like this : 
+For configuration, you need to be in privileged mode. The magic word is "enable". "configure" brings you to the configuration prompt, which looks like this : 
 {{{
 sw-sb09(config)#
 }}}
 
-From here, you can enter different contexts according to what you are trying to set up:
+From here, you can enter different contexts according to what you are trying to configure:
+
  * `interface vlan n` - create/ configure VLAN n, n being the VLAN ID (some number)
  * `interface gigabitethernet 0/n` - configure specific port, n being number between 1 and 48
  * `line <vty|console>` - configure telnet or console parameters, respectively
-when in a different context, you can tell from how the prompt becomes "(config-if)." 
+
+when in a different context, you can tell from how the prompt becomes "(config-if)." [[BR]]
+Ranges of ports and VLANs can be specified. For example, to config ports 1-4 and 30 at once: 
+{{{
+ sw-sb09(config)# int range gigabitethernet 0/1-4, gigabitethernet 0/30
+ sw-sb09(config-if-range)# 
+}}}
+
+Note how the prompt becomes "(config-if-range)" in this case.
 
 ==== VLAN creation and port configuration. ==== 
 In order to do anything with the switch, you need to configure the following two:
 
- * Virtual interfaces - Also called "VLANs" by the switch. They do function as VLANs in the traditional sense, but in this case, are also associated with IP addresses used by the switch. 
+ * Virtual interfaces - Also called "VLANs" by the switch. They do function as VLANs in the traditional sense, but in this case, are also associated with IP addresses used by the switch (i.e. the IP address used when telnetting). 
  
  * Ports - By default all ports are assigned to VLAN 1. The ports must be assigned to different VLANs according to how you want the frames to/from the port are handled. Port settings are configured from the `interface gigabitethernet 0/n` context in configure mode. The three main contexts we need are:
@@ -328 +352 @@
  
  3- `switchport mode trunk` - port is a trunk and can handle frames from multiple vlans. 
+
+