Changes between Version 2 and Version 3 of Internal/OpenFlow/VLANstitching

Timestamp:

Mar 9, 2012, 7:27:15 PM (14 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/VLANstitching

@@ -32 +32 @@
 }}}  
 
-Setting flow entries from the `config-switch` context is a matter of copy/pasting each line above, and exiting between different flow entries. Key points are:
+Setting flow entries from the `config-switch` context is a matter of copy/pasting each line above, and exiting contexts between different flow entries. Key points are:
  * The four ports of the NetFPGA are designated 1,2,3,4, not 0,1,2,3 as the nf2cx numbering might suggest.  
  * 'active True' must be specified to enable the flow policy since the default for any newly created flow is 'active False'
@@ -39 +39 @@
 
 === sanity checks ===
-For the sake of sanity checking, IP addresses were assigned to the VLAN interfaces for 5 and 3733 on sw-top and sw-outside, respectively. If successful, pings will work between the two VLAN interfaces. 
+The NetFPGA host implements !OpenFlow features via the following processes:
+{{{
+root      1374     1  0 10:55 ?        00:00:00 /opt/netfpga2.1.1/openflow/udatapath/ofdatapath -D punix:/var/run/test -d 002320080ff7 -i nf2c0 nf2c1 nf2c2 nf2c3
+root      1452     1  0 10:55 ?        00:00:00 /opt/netfpga2.1.1/openflow/secchan/ofprotocol -D unix:/var/run/test tcp:nox.orbit-lab.org:6633 --out-of-band
+}}}
+To check for flows on the host itself, `dpctl` should be used. The commands to pull the switch's status and current flows (e.g. traces) are:
+{{{
+dpctl show unix:/var/run/test
+dpctl status unix:/var/run/test
+dpctl montior unix:/var/run/test
+}}}
+This is similar to the commands `show [DPID] status` and `show [DPID] trace detail` on the controller CLI. 
+
+An external test involved IP address assignments to the VLAN interfaces for VLANs 5 and 3733 on sw-top and sw-outside, respectively. The IP addresses were pinged from each side; Pings pass between the two VLAN interfaces when stitched correctly.