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


Ignore:
Timestamp:
Dec 14, 2009, 10:51:21 PM (15 years ago)
Author:
akoshibe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/OpenFlow/CLISetup

    v17 v18  
    271271}}}
    272272
     273== Elucidation (Or, Frequently asked questions) ==
     274
     275As of now, this is just a list of facts/ a flow-chart. Diagram to accompany coming soon.
     276Assuming you have a brand new IP8800 on your hands:
     277
     278=== Logging in for the first time. ===
     279
     280Telnet is not configured by default, so you need to log in via the console port.
     281
     2821. Name your switch.
     283
     2842. Acquire a RS-232 cable -  Hook up the cable to the port labeled 'console' on the switch.
     285
     2863. If not already there, install kermit on your machine. Kermit is recommended because its default settings can be used to connect to the switch.
     287
     2884. Connect via serial using the following commands (Make sure you are root):
     289 {{{
     290  /$ kermit
     291  C-Kermit>set line /dev/ttyS0
     292  C-Kermit>set carrier-watch off
     293  C-Kermit>connect
     294 }}}
     295
     296Or, you can use the shorthand for the above:
     297{{{
     298 kermit -l /dev/ttyS0
     299 connect
     300}}}
     301
     302`Ctrl-\ q` ends the kermit session.
     303The default username is `operator`, and the password is blank.   
     304
     305
     306== Configuration ==
     307For configuration, you need to be in privileged mode. The magic word is `enable`. `configure` brings you to the configuration prompt, which looks like this :
     308{{{
     309sw-sb09(config)#
     310}}}
     311
     312From here, you can enter different contexts according to what you are trying to set up:
     313 * `interface vlan n` - create/ configure VLAN n, n being the VLAN ID (some number)
     314 * `interface gigabitethernet 0/n` - configure specific port, n being number between 1 and 48
     315 * `line <vty|console>` - configure telnet or console parameters, respectively
     316when in a different context, you can tell from how the prompt becomes "(config-if)."
     317
     318==== VLAN creation and port configuration. ====
     319In order to do anything with the switch, you need to configure the following two:
     320
     321 * 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.
     322 
     323 * 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:
     324
     325 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.
     326 
     327 2- `switchport mode dot1q-tunnel` - frames from the port are tagged upon hitting the trunk and not dropped.
     328 
     329 3- `switchport mode trunk` - port is a trunk and can handle frames from multiple vlans.
     330
     331
     332 
     333
    273334
    274335