Changes between Version 16 and Version 17 of ClickExampleExperiment

Timestamp:

06/22/12 14:47:40 (12 years ago)

Author:

Mark Berman

Comment:

--

ClickExampleExperiment

@@ -157 +157 @@
 Once you have the '''myslice.png''' on your local machine, open it in a browser other viewer program. Your slice will look something like the one below (see [attachment:sampleDiagram.png]). The overall configuration should be the same, with two end hosts, named hostA and hostB, and four routers (top, left, right, bottom) in a diamond configuration. The host names, interface names, and MAC addresses will be different, depending on the actual resources assigned to your slice.
 
-[[Image(sampleDiagram.png, nolink, 25%)]]
+[[Image(myslice.png, nolink, 25%)]]
 
 The four routers interconnected by solid lines are your "core network," which will run a non-standard, non-IP protocol. The dashed lines out to the end hosts carry standard IP traffic.
@@ -252 +252 @@
 Please note: the interface names and MAC addresses below are for the sample configuration shown in the figure above. You will want to refer to your network diagram to get the correct interfaces and addresses for your configuration.
 
-Let's take a look at what's happening in the four routers in your configuration. There are two basic router configurations.
+Let's take a look at what's happening in the four routers in your configuration. There are two basic router configurations. (You can find all of these files on any of your router hosts.)
 
 === Packet transformation ===
@@ -272 +272 @@
     modify;
 
-route[0] -> left :: EtherEncap(0x7744, 00:02:b3:35:f1:b7, 00:02:b3:86:1d:13) ->
+route[0] -> left :: EtherEncap(0x7744, 00:04:23:b7:14:76, 00:04:23:b7:18:fa) ->
     SimpleQueue ->
     Print(outL) ->
-    ToDevice(eth1);
-
-route[1] -> right :: EtherEncap(0x7744, 00:03:47:94:c7:fd, 00:02:b3:65:d1:2b) ->
+    ToDevice(eth2);
+
+route[1] -> right :: EtherEncap(0x7744, 00:04:23:b7:1c:e0, 00:04:23:b7:19:2e) ->
     SimpleQueue ->
     Print(outR) ->
-    ToDevice(eth2);
+    ToDevice(eth4);
 
 // This portion accepts non-IP packets
@@ -288 +288 @@
 restore :: SimpleQueue ->
     Strip(30) ->
-    EtherEncap(0x800, 00:03:47:73:8e:bd, 00:02:b3:3f:7a:a1) ->
+    EtherEncap(0x800, 00:04:23:b7:14:77, 00:04:23:b7:20:00) ->
     ToDevice(eth3);
 
-FromDevice(eth1) -> Classifier(12/7744) -> Print(inL) -> restore;
-FromDevice(eth2) ->  Classifier(12/7744) -> Print(inR) -> restore;
+FromDevice(eth2) -> Classifier(12/7744) -> Print(inL) -> restore;
+FromDevice(eth4) ->  Classifier(12/7744) -> Print(inR) -> restore;
 }}}
 
@@ -307 +307 @@
 {{{
 // Copy packets from top to bottom.
-FromDevice(eth1) ->
-    StoreEtherAddress(00:02:b3:86:1a:4b, dst) ->
-    StoreEtherAddress(00:03:47:95:7a:fe, src) ->
+FromDevice(eth2) ->
+    StoreEtherAddress(00:04:23:b7:42:b6, dst) ->
+    StoreEtherAddress(00:04:23:b7:18:fb, src) ->
     SimpleQueue ->
     Print(top) ->
-    ToDevice(eth2);
+    ToDevice(eth3);
 // Copy packets from bottom to top.
-FromDevice(eth2) ->
-    StoreEtherAddress(00:02:b3:35:f1:b7, dst) ->
-    StoreEtherAddress(00:02:b3:86:1d:13, src) ->
+FromDevice(eth3) ->
+    StoreEtherAddress(00:04:23:b7:14:76, dst) ->
+    StoreEtherAddress(00:04:23:b7:18:fa, src) ->
     SimpleQueue ->
     Print(bottom) ->
-    ToDevice(eth1);
+    ToDevice(eth2);
 }}}
 
@@ -326 +326 @@
 === Monitoring your core network ===
 
-Let's watch how the packets travel through the network. In addition to the windows you already have open to the two end hosts, you'll need four more windows to watch the logs for all four routers.  In each window, you should use '''ssh''' to connect to one router host, '''ssh -F ssh_config top''', '''ssh -F ssh_config left''', '''ssh -F ssh_config right''' and '''ssh -F ssh_config bottom'''. You can monitor the click log files with '''tail''':
-
-{{{
-[mberman@top ~]$ tail -f click.log 
-}}}
-
-The log files may have a couple of warnings at the top complaining that your interfaces have no IPv4 addresses. No worries, we did that on purpose, since we don't use IP in the core network. Other than those warnings, you should just see packet log messages, one line per packet. Type <enter> a few times in each router window to create a space below the existing log entries, so you can identify new log messages as they appear.
+Let's watch how the packets travel through the network. The terminal windows on your four router hosts show the log output from the '''Print''' statements shown above, one line per packet.
+
+Type <enter> a few times in each router window to create a space below the existing log entries, so you can identify new log messages as they appear.
 
 Now go to your window for hostA, where your '''nc''' command is still running. Type a message into this window. You should see a log message in three of your four router windows. In this example, you might see:
@@ -338 +334 @@
 In the '''top''' router log:
 {{{
-outR:   76 | 0002b365 d12b0003 4794c7fd 7744416c 69636557 61734865
-}}}
-
-This log entry says that the '''top''' router received a packet from '''hostA''', modified it, and sent it out to the '''right''' router. If the entry started with '''outL''', that would indicate that it sent the packet out to the '''left''' router. Let's look a bit at the start of the packet (the first 24 bytes are logged). It starts with an Ethernet header. The first six bytes are the MAC address of the destination interface, that's 00:02:b3:65:d1:2b, the MAC address of '''eth1''' on '''right'''. The next six bytes are the MAC address of the source interface, 00:03:47:94:c7:fd, or '''eth2''' on '''top'''. Next comes your ether type, 0x7744. The remaining bytes, "416c 69636557 61734865" are the start of the first field in your new protocol, "!AliceWasHe" in ASCII.
-
-Since this packet was routed to the right, there's an entry in the '''right''' router log. This entry indicates that a packet was received from '''top'''. The logged contents show the packet sent to '''bottom''', with rewritten MAC addresses, corresponding to '''eth2''' on '''bottom''' and '''eth2''' on '''right'''.
-
-{{{
-top:   76 | 00034794 c7fc0003 4794c1f7 7744416c 69636557 61734865
+outR:   76 | 000423b7 192e0004 23b71ce0 7744416c 69636557 61734865
+}}}
+
+This log entry says that the '''top''' router received a packet from '''hostA''', modified it, and sent it out to the '''right''' router. If the entry started with '''outL''', that would indicate that it sent the packet out to the '''left''' router. Let's look a bit at the start of the packet (the first 24 bytes are logged). It starts with an Ethernet header. The first six bytes are the MAC address of the destination interface, that's 00:04:23:B7:19:2E, the MAC address of '''eth4''' on '''right'''. The next six bytes are the MAC address of the source interface, 00:04:23:B7:1C:E0, or '''eth4''' on '''top'''. Next comes your ether type, 0x7744. The remaining bytes, "416c 69636557 61734865" are the start of the first field in your new protocol, "!AliceWasHe" in ASCII.
+
+Since this packet was routed to the right, there's an entry in the '''right''' router log. This entry indicates that a packet was received from '''top'''. The logged contents show the packet sent to '''bottom''', with rewritten MAC addresses, corresponding to '''eth5''' on '''bottom''' and '''eth5''' on '''right'''.
+
+{{{
+top:   76 | 000423b7 42590004 23b7192f 7744416c 69636557 61734865
 }}}
 
 Finally, here's the entry on '''bottom''':
 {{{
-inR:   76 | 00034794 c7fc0003 4794c1f7 7744416c 69636557 61734865
+inR:   76 | 000423b7 42590004 23b7192f 7744416c 69636557 61734865
 }}}
 
@@ -365 +361 @@
 
 {{{
-/path/to/omni/src/omni.py deletesliver -a http://www.emulab.net/protogeni/xmlrpc/am StupidSliceName
+omni.py deletesliver -a http://www.emulab.net/protogeni/xmlrpc/am StupidSliceName
 }}}