Faucet on NoviFlow¶
Introduction¶
NoviFlow provide a range of switches known to work with FAUCET.
These instructions have been tested on NS1248, NS1132, NS2116, NS2128, NS2122, NS2150, NS21100 switches, using software versions NW400.1.8 to NW400.3.1, running with FAUCET v1.6.4.
When using a more recent FAUCET version, different table configurations may be required.
Setup¶
Configure the CPN on the switch¶
In this example, the server running FAUCET is 10.0.1.8; configuration for CPN interfaces is not shown.
set config controller controllergroup faucet controllerid 1 priority 1 ipaddr 10.0.1.8 port 6653 security none
set config controller controllergroup gauge controllerid 1 priority 1 ipaddr 10.0.1.8 port 6654 security none
set config switch dpid 0x1
Configure the tables¶
These matches are known to pass the unit tests as of FAUCET 1.6.18, but take care to adjust ACL tables matches based on the type of ACL rules defined in the configuration file. Different FAUCET releases may also use different match fields in the other tables.
set config pipeline tablesizes 1524 1024 1024 5000 3000 1024 1024 5000 1024 tablewidths 80 40 40 40 40 40 40 40 40
set config table tableid 0 matchfields 0 3 4 5 6 10 11 12 13 14 23 29 31
set config table tableid 1 matchfields 0 3 4 5 6
set config table tableid 2 matchfields 0 5 6 10 11 12 14
set config table tableid 3 matchfields 0 3 4 5 6 10
set config table tableid 4 matchfields 5 6 12
set config table tableid 5 matchfields 5 6 27
set config table tableid 6 matchfields 3 5 10 23 29
set config table tableid 7 matchfields 3 6
set config table tableid 8 matchfields 0 3 6
Note that this table configuration will allow most of the automated test cases to pass, except FaucetIPv6TupleTest (which requires IPv6 Src and Dst matching in the ACL table). In order to run this test, table 0 must be configured as follows:
set config table tableid 0 matchfields 0 5 6 10 26 27 13 14
Create faucet.yaml¶
vlans:
100:
name: "test"
dps:
noviflow-1:
dp_id: 0x1
hardware: "NoviFlow"
interfaces:
1:
native_vlan: 100
2:
native_vlan: 100
Run FAUCET¶
faucet --verbose
Test connectivity¶
Host(s) on ports 1 and 2 should now be able to communicate, and FAUCET’s log file should indicate learning is occurring:
May 14 17:06:15 faucet DEBUG DPID 1 (0x1) connected
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Configuring DP
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Delete VLAN vid:100 ports:1,2,3,4
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) VLANs changed/added: [100]
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Configuring VLAN vid:100 ports:1,2,3,4
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Configuring VLAN vid:100 ports:1,2,3,4
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Port 1 added
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Sending config for port 1
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Port 2 added
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Sending config for port 2
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Port 3 added
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Sending config for port 3
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Port 4 added
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Sending config for port 4
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Packet_in src:62:4c:f5:bb:33:3c in_port:2 vid:100
May 14 17:06:15 faucet.valve INFO learned 1 hosts on vlan 100
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Packet_in src:62:4c:f5:bb:33:3c in_port:2 vid:100
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Packet_in src:2a:e1:65:3c:49:e4 in_port:3 vid:100
May 14 17:06:15 faucet.valve INFO DPID 1 (0x1) Packet_in src:2a:e1:65:3c:49:e4 in_port:3 vid:100
May 14 17:06:15 faucet.valve INFO learned 2 hosts on vlan 100