Changes between Version 5 and Version 6 of Tutorials/m0SDN/cTutorial2

Timestamp:

Mar 14, 2010, 11:53:30 PM (14 years ago)

Author:

ssugrim

Comment:

—

Tutorials/m0SDN/cTutorial2

@@ -84 +84 @@
 }}}
 
-== ASIDE: TESTS for connectivity ==
-
-In case your expirement is failing, here are a few sanity checks. 
-
-=== The SNAC controller Web interface ===
-
- Assuming your flowvisor is passing along high priority traffic to snac,  the this:[[BR]]
-[[Image(snac.jpg)]]
-
-=== Inter-node traffic ===
-
-Once the data interfaces are brought up on each of the 4 nodes, they should be discovered by SNAC. Assuming we place them all in the same IP subnet, it should be possible to ping each node from every other node. A simple test can be done as follows:
-{{{
-for node1-i:
-
-ssh root@node1-i
-ifconfig eth0 up
-ifconfig eth0 192.168.1.i
-ping 192.168.1.(i-1)
-
-where i runs from 1 to 4.
-}}}
-
-This should be done with independent sessions, as each session will start display traffic information. Once completed SNAC should report an increase in production  traffic, and 4 discovered hosts with the specified ips. 
-
-=== High Numbered port Test ===
-
-Start a fresh NOX controller instance on sb9 and enable packet dumps
-{{{
-root@console:/root/nox/build/src# ./nox_core -i ptcp:6635 switch packetdump
-}}}
-
-Attempt to connect to a high numbered port on a different node (using the Ip of the data interface):
-{{{
-root@node1-1:~# telnet 192.168.1.2 10001
-Trying 192.168.1.2...
-telnet: Unable to connect to remote host: Connection refused
-}}}
-
-If the traffic is split properly, your controller should register event similar to this:
-
-{{{
-[(Giga-Byte Technology Co.,LTD.):84:9b:30>(Giga-Byte Technology Co.,LTD.):83:a0:5c:IP]([v:4hl:5l:60t:64]TCP cs:8a65[192.168.1.1>192.168.1.2]){44653>10001} seq:3830918239 ack:0 f:0x2
-[(Giga-Byte Technology Co.,LTD.):83:a0:5c>(Giga-Byte Technology Co.,LTD.):84:9b:30:IP]([v:4hl:5l:40t:64]TCP cs:b76c[192.168.1.2>192.168.1.1]){10001>44653} seq:0 ack:3830918240 f:0x14
-}}}
-
 == The experimental Traffic ==
 
@@ -218 +172 @@
 }}}
 
-
+== ASIDE: TESTS for connectivity ==
+
+In case your expirement is failing, here are a few sanity checks. 
+
+=== The SNAC controller Web interface ===
+
+ Assuming your flowvisor is passing along high priority traffic to snac,  the this:[[BR]]
+[[Image(snac.jpg)]]
+
+=== Inter-node traffic ===
+
+Once the data interfaces are brought up on each of the 4 nodes, they should be discovered by SNAC. Assuming we place them all in the same IP subnet, it should be possible to ping each node from every other node. A simple test can be done as follows:
+{{{
+for node1-i:
+
+ssh root@node1-i
+ifconfig eth0 up
+ifconfig eth0 192.168.1.i
+ping 192.168.1.(i-1)
+
+where i runs from 1 to 4.
+}}}
+
+This should be done with independent sessions, as each session will start display traffic information. Once completed SNAC should report an increase in production  traffic, and 4 discovered hosts with the specified ips. 
+
+=== High Numbered port Test ===
+
+Start a fresh NOX controller instance on sb9 and enable packet dumps
+{{{
+root@console:/root/nox/build/src# ./nox_core -i ptcp:6635 switch packetdump
+}}}
+
+Attempt to connect to a high numbered port on a different node (using the Ip of the data interface):
+{{{
+root@node1-1:~# telnet 192.168.1.2 10001
+Trying 192.168.1.2...
+telnet: Unable to connect to remote host: Connection refused
+}}}
+
+If the traffic is split properly, your controller should register event similar to this:
+
+{{{
+[(Giga-Byte Technology Co.,LTD.):84:9b:30>(Giga-Byte Technology Co.,LTD.):83:a0:5c:IP]([v:4hl:5l:60t:64]TCP cs:8a65[192.168.1.1>192.168.1.2]){44653>10001} seq:3830918239 ack:0 f:0x2
+[(Giga-Byte Technology Co.,LTD.):83:a0:5c>(Giga-Byte Technology Co.,LTD.):84:9b:30:IP]([v:4hl:5l:40t:64]TCP cs:b76c[192.168.1.2>192.168.1.1]){10001>44653} seq:0 ack:3830918240 f:0x14
+}}}