Hi all,
We're working on our test setup for our demo at Stanford. Unfortunately
we're seeing some strange behavior that results in an ARP storm with a
fairly simple setup.
The setup is as follows:
NOX controller on one host (mvm-nox)
OpenFlow switch (kernel module -- built from git) on another host (mvm-root)
mvm-root has 5 ethernet ports:
eth0 -- controller connection to mvm-nox
eth{1,2,3,4} -- ports controlled by OF
Note: eth{1,4} are connected to a Cisco Cat6K -- the ports they are
connected to are on separate VLANs:
Here's the MAC addresses of the ports (relevant later)
eth0 Link encap:Ethernet HWaddr 00:15:f2:a6:6c:2a
eth1 Link encap:Ethernet HWaddr 00:0c:42:03:b8:bd
eth2 Link encap:Ethernet HWaddr 00:0c:42:03:b8:be
eth3 Link encap:Ethernet HWaddr 00:0c:42:03:b8:bf
eth4 Link encap:Ethernet HWaddr 00:0c:42:03:b8:c0
Various other hosts are connected to eth1 via the Cat6k, particularly
171.67.74.17 and 171.67.74.33 (mvm-17 and mvm-33 respectively).
Without NOX+OF running I see Dynamic Trunking Protocol (DTP) packets and
Cisco Discovery Protocol (CDP) packets on eth1 and eth4 of mvm-ofroot.
In addition I sometime see ARP requests from some of the hosts connected
to eth1.
When I run NOX and OF (with pyrouting and pyauthenticator as the active
modules for NOX), I initially see correct behavior. Packets received on
any of the ports are flooded to the other ports. I also start seeing
Link Layer Discovery Protocol (LLDP) packets on all 4 ports with a
source address of 00:15:f2:a6:6c:2a (corresponding to the MAC address of
the port used to connect to the controller). So far, so good...
Now, for the problems.
Eventually I see an ARP packet on eth1 from mvm-33 (for mvm-44:
171.67.74.44). This packet triggers a flood of ARP packet -- it seems
like it continually gets flooded out all ports.
Additionally, we also start to see entries about "Poisoning old primary"
in the NOX output (which probably happens before we see the arp storm):
00264|authenticator|ERR:Poisoning old primary ap:15f2a66c2a:0,
dl:163d467ca, nw:0 owns:0
To help with diagnosis I performed packet capture on all 5 ports and
recorded the output from NOX and OF. You can grab them from
http://yuba.stanford.edu/~grg/nox_prob_b.tgz
The dump files were actually started about 80 seconds before OF was
started. If you look at b.eth1.dump and b.eth4.dump the first packet
sent out by NOX are the packets at 86 and 87 s respectively. Note that
no packets were received on eth2 and eth3 before NOX was started so all
packets in those dumps are when NOX/OF was running.
Please let me know if I can be of further assistance in debugging (or if
there's something plainly wrong that I'm doing).
Glen
_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
