Hi, working at the same company, perhaps I can clarify this a bit. Firstly, we are using openvswitch v1.2.2, the linux kernel datapath implementation and the test-openflowd openflow switch (we have good reasons not to use ovs-vswitchd).
Restarting the controller means we've restarted (after SIGTERMinating) the test-openflowd user space daemon previously attached to a datapath in order to check whether our system recovers from test-openflowd crashes. After the restart, the switch successfully reconnects to our openflow controller but approx. every 10 seconds, nothing received at the datapath's local port is properly forwarded (to a physical switch port or our controller). This situation persists for a few seconds until it seems to recover and work properly again for about 10 seconds, etc. btw. I guess the "received packet on unknown port 65534" message alludes to an openvswitch bug since 65534 is the openflow LOCAL port while the source code states that an "odp" port should be logged. LOCAL however is odp-port 0. So it appears that somehow the two port types got mixed up. cheers, Robin Haberkorn ----- Original Message ----- > Hi, > > We have encountered a strange behavior. After restarting the > controller process and even after removing and reinserting the > datapath module, ARP packets are forwarded from dp0 to the real port > intermittently. > tcpdump confirms that the ARP request is seen on dp0, but not on the > physical port (eth1). > At the same time the following sequence on log messages appear: > > Oct 18 12:22:54|00344|netlink_socket|DBG|nl_sock_recv__ (Success): > nl(len:24, type=30(ovs_packet), flags=0, seq=0, > pid=0(0:0)),genl(cmd=1,version=1) > Oct 18 12:22:54|00345|dpif|DBG|system@dp0: miss upcall: > in_port(0),eth(src=00:23:20:fc:70:43,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=172.28.0.1,tip=172.28.0.19,op=1,sha=00:23:20:fc:70:43,tha=00:00:00:00:00:00) > 00:23:20:fc:70:43 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length > 42: Request who-has 172.28.0.19 tell 172.28.0.1, length 28 > Oct 18 12:22:54|00346|ofproto_dpif|WARN|bridge dp0: received packet > on unknown port 65534 > Oct 18 12:22:54|00347|netlink_socket|DBG|nl_sock_transact_multiple__ > (Success): nl(len:140, type=30(ovs_packet), flags=1[REQUEST], > seq=4e9d5835, pid=75500397(2925:18)),genl(cmd=3,version=1) > Oct 18 12:22:54|00348|netlink_socket|DBG|nl_sock_transact_multiple__ > (Success): nl(len:92, type=29(ovs_flow), flags=5[REQUEST][ACK], > seq=4e9d5836, pid=75500397(2925:18)),genl(cmd=1,version=1) > Oct 18 12:22:54|00349|netlink_socket|DBG|nl_sock_recv__ (Success): > nl(len:36, type=2(error), flags=0, seq=4e9d5836, > pid=75500397(2925:18)) error(0, in-reply-to(nl(len:92, > type=29(ovs_flow), flags=5[REQUEST][ACK], seq=4e9d5836, > pid=75500397(2925:18)))) > > There clearly is something strange going on. How can the dp receive > something on an unknown port? > > Any hints? > > Regards > Andreas > -- > -- > Dipl. Inform. > Andreas Schultz > > email: a...@travelping.com > phone: +49-391-819099-224 > mobil: +49-179-7654368 > > ------------------ managed broadband access ------------------ > > Travelping GmbH phone: +49-391-8190990 > Roentgenstr. 13 fax: +49-391-819099299 > D-39108 Magdeburg email: i...@travelping.com > GERMANY web: http://www.travelping.com > > Company Registration: HRB21276 Handelsregistergericht Chemnitz > Geschaeftsfuehrer: Holger Winkelmann | VAT ID No.: DE236673780 > -------------------------------------------------------------- > > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
