Changes between Version 14 and Version 15 of Tutorials/m0SDN/aHowTo
- Timestamp:
- Aug 27, 2009, 4:58:57 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tutorials/m0SDN/aHowTo
v14 v15 23 23 [[Image(wiki:Documentation/OpenFlow/OFHowTo:OFSetup.jpg, 450)]] 24 24 25 The blue switch (sw_sb09) represents the !OpenFlow enabled NEC IP8800/S3640-48T2XW switch, currently running firmware supporting !OpenFlow v0.8.9. The switch is pre-configured so that ports 25-36 (the data VLAN, in red) is an !OpenFlow virtual switch that listens for a controller running on the SB9 Console. Two trunked connections exist - one connects the setup with the ORBIT network (through sw_sb_top), and the other not only allows the console to communicate with the nodes, but also provides the secure controller-switch VLAN needed for the !OpenFlow setup. The experimenter would be able to monitor and manipulate the setup from the Console.25 The dotted box (labeled sw_sb09) represents the !OpenFlow enabled NEC IP8800/S3640-48T2XW switch, currently running firmware supporting !OpenFlow v0.8.9. The switch is pre-configured so that ports 25-36 (the data VLAN, in red) is an !OpenFlow virtual switch that listens for a controller running on the SB9 Console. There exists a virtual connection between the controller and virtual switch, represented by the dotted red line. Two trunked connections exist - one connects the setup with the ORBIT network (through sw_sb_top), and the other not only allows the console to communicate with the nodes, but also provides the secure controller-switch VLAN needed for the !OpenFlow setup. The experimenter would be able to monitor and manipulate the setup from the Console. 26 26 27 == Installing the controller == 27 ---- 28 We can run the controller on the console or on one of the nodes as they each can have equal access the the openflow controling vlan. 29 30 == Installing the controller (on a node) == 31 28 32 Two distinct controllers, one from the !OpenFlow reference System (v0.8.9r2) and another from NOX-core (v0.5.0), have been successfully installed and tested on the Console. These can be downloaded from the following places: 29 33 … … 65 69 }}} 66 70 67 === Installing NOX ===71 === Installing NOX (on a node) === 68 72 It is not only recommended but also much simpler to use git to install NOX. Therefore the following instructions assume you are using git. The full instructions are found at noxrepo.org: http://noxrepo.org/manual/installation.html [[BR]] 69 73 … … 92 96 }}} 93 97 98 ---- 99 100 == Controllers on the Console == 101 102 A sub-set of these instructions can be used to install a "custom" controller in userspace on the console. Most of the requsite libraries should already be installed. 103 104 ''TODO'' list subset. 105 94 106 == Starting the controller == 95 107 Both commands start the controller and establish a connection with the !OpenFlow switch. The -v is for verbose. -h for both will give you the help files for the controllers. In the reference system, the controller is found under .../openflow/controller/ … … 103 115 `ptcp:6633` refers to a passive connection to TCP 6633, the default !OpenFlow port. An active connection method using standard TCP exists, however this does not work on this setup. In the !OpenFlow reference system, a log of the verbose output can be saved by appending `--log-file [filename]`. 104 116 105 == Other Resources == 117 118 ---- 119 = Available Tools = 120 121 Some of these tools require root privlages and will thus require a custom installation on a node. Otherse can be run from the console directly in an unprivlaged mode. 122 123 ''TODO'' indicate what credentails are required for each tool. 106 124 107 125 === the Wireshark plugin === … … 144 162 === Demo Video === 145 163 164 ''TODO'' move this onto the orbit webserver. 165 146 166 A video Demonsration of the usage of the refrence controller can be found at: http://www.winlab.rutgers.edu/~ssugrim/Projects.html 147 167
