Changes between Version 11 and Version 12 of Internal/OpenFlow/SandBoxSetup


Ignore:
Timestamp:
Jul 21, 2009, 3:48:42 AM (15 years ago)
Author:
akoshibe
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/OpenFlow/SandBoxSetup

    v11 v12  
    4141
    4242= Making the controller from the !OpenFlow Reference System Code. (7/14, 7/15) =
     43=== Configuring the Console ===
    4344The !OpenFlow reference system contains code for a controller that makes an !OpenFlow switch into a learning switch. This was built (but not installed) on the Console by following instructions on the !OpenFlow site: http://www.openflowswitch.org/wk/index.php/Ubuntu_Install
    4445
    4546The console was then configured to be VLAN aware for VLANs 27,28, and 100. The site referenced: http://ubuntuforums.org/showthread.php?t=703387
    4647
    47 The interfaces looked like this at the end:
     48/etc/network/interfaces looked like this at the end:
    4849{{{
    4950# The primary network interface
    … …  
    7172}}}
    7273
    73 Eth1 was then connected to a reconfigured trunk port that allowed VLANs 27,28, and 100. The IP's for the VLAN interfaces were assigned arbitrarily within the same subnet as the ones set for Sandbox9. The commands used for re-configuring trunk port 0/37:
     74=== Configuring the switchport ===
     75Eth1 of the Console was connected to a reconfigured trunk port that allowed VLANs 27,28, and 100. The IP's for the VLAN interfaces were assigned arbitrarily within the same subnet as the ones set for Sandbox9. An arbitraty trunk port (0/37) was chosen and reconfigured for this step. The commands:
    7476{{{
    7577sw-sb09(config)# sh int gi 0/37
    … …  
    9395!sw-sb09(config-if)# save
    9496}}}
     97The port ended up looking like this:
     98{{{
     99sw-sb09(config-if)# sh
     100interface gigabitethernet 0/37
     101  switchport mode trunk
     102  switchport trunk allowed vlan 27-28,100
     103}}}
    95104
    96105We later realized that VLAN interfaces for VLANs 27 and 28 also need to be assigned IP addresses in order for the switch to be able to communicate with the controller's VLAN interfaces.
    … …  
    124133}}}
    125134
    126 === establishing switch-controller connections ===
    127 The code for the controller is found intuitively in the controller directory. Using `ptcp:[port]` as the connection method seems to work.
    128 we also wanted an output and a log of everything, so the full command was this (from the controller's directory) :
     135== establishing switch-controller connections ==
     136The code for the controller is found intuitively in the controller directory. Using `ptcp:[port]` as the connection method seems to work. We also wanted an output and a log of everything, so the full command was this (from the controller's directory) :
    129137
    130138./controller ptcp:6633 -v --log-file=test.log
    … …  
    160168}}}
    161169
     170== Setting up the demo. ==
    162171=== packet sniffing ===
    163 The experiment that was packet-sniffed included the following steps:
     172The first experiment involved packet sniffing, and included the following steps:
    164173 
    165174 1. unplug all hosts connected to the virtual switch (VLAN 28 ports)
    … …  
    171180 tcpdump -i eth1.100 -w foo.pcap
    172181
    173 Here, the log is saved in foo.pcap. This was later opened in wireshark on another PC (Given X11 didn't break, wireshark on sb9 would would have worked) using the command
     182Here, the log is saved in foo.pcap. This was later opened in wireshark on another PC (Given X11 didn't break, wireshark on sb9 would have worked) using the command
    174183
    175184 wireshark -r foo.pcap &
    … …  
    179188
    180189The logs in wireshark are a bit harder to interpret than the verbose outputs of the controller itsself:
    181 [[Image(wiki:Documentation/OpenFlow/SandBoxSetup:)]]
     190[[Image(wiki:Documentation/OpenFlow/SandBoxSetup:wiresharkscreen.png)]]
    182191
    183192The experiment was later recreated with the Sandbox nodes.
    … …  
    191200
    192201== Getting the nodes to work ==
    193 
    194202=== IP8800 configurations: setting port speed (7/17) ===
    195 The default port setting is autonegotiation. The port speeds can be forced to different speeds, but this breaks imaging especially if the nodes aren't willing to negotiate to 1Gbps. If set to autonegotiate at a certain speed, the port will be shut down unless the host also negotiates to that speed. the nodes seemed to have issues even if the port was purely set to function at 1Gbps and not to autonegotiate.
     203Detail on syntax and configurations regarding port speed: wiki:Documentation/OpenFlow/CLISetup
     204
     205The ideal is for the nodes to negociate to 1Gbps on the Control and Data VLANs, and 10Mbs on the CM. For some reason, the nodes sometimes negociated to 100Mbs. Forcing the ports to 1Gbps with autonegotiation only caused to ports to shut down when the nodes negotiated to 100Mbps. Ultimately the ports were left configured to `speed auto`.
    196206
    197207=== disabling '''all''' forms of spanning tree ===