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

Timestamp:

Dec 14, 2009, 10:51:21 PM (14 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/CLISetup

@@ -271 +271 @@
 }}}
 
+== Elucidation (Or, Frequently asked questions) ==
+
+As of now, this is just a list of facts/ a flow-chart. Diagram to accompany coming soon.
+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):
+ {{{
+  /$ kermit
+  C-Kermit>set line /dev/ttyS0
+  C-Kermit>set carrier-watch off
+  C-Kermit>connect
+ }}}
+
+Or, you can use the shorthand for the above:
+{{{
+ kermit -l /dev/ttyS0
+ connect
+}}}
+
+`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 : 
+{{{
+sw-sb09(config)#
+}}}
+
+From here, you can enter different contexts according to what you are trying to set up:
+ * `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)." 
+
+==== 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. 
+ 
+ * 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:
+
+ 1- `switchport mode access` - the default port mode. Port is associated with a vlan, but frames from the port are not tagged - the frames are dropped if they are seen on the trunk.
+ 
+ 2- `switchport mode dot1q-tunnel` - frames from the port are tagged upon hitting the trunk and not dropped.
+ 
+ 3- `switchport mode trunk` - port is a trunk and can handle frames from multiple vlans. 
+
+
+  
+