Hi KK, Hmm I was mistaken it does seem to catch it from those events ( I didn't see it last time since I had it going to the log instead of the screen or something).
00047|openflow|WARN:stream: connection closed by peer 00048|nox|WARN:stream: connection closed by peer Switch 6d60026f13fe480 has left the network 00049|openflow|WARN:stream: connection closed by peer 00050|nox|WARN:stream: connection closed by peer Switch 6d00026f13fe480 has left the network 00051|nox|WARN:stream: closing connection due to timeout after 5 seconds in receiving features reply state 00052|nox|WARN:stream: closing connection due to timeout after 5 seconds in receiving features reply state 00053|nox|WARN:stream: closing connection due to timeout after 5 seconds in sending features request state 00054|nox|WARN:stream: closing connection due to timeout after 5 seconds in sending features request state Switch 6d60026f13fe480 has joined the network Switch 6d00026f13fe480 has joined the network On Fri, Jul 15, 2011 at 12:42 PM, kk yap <[email protected]> wrote: > On 15 July 2011 09:36, Aaron Rosen <[email protected]> wrote: >> Sorry one more thing, >> >> When this error occurs NOX does not seem to alert, >> register_for_datapath_leave(datapathleave_callback) or datapath_join() > > Can you explain this one? You register for datapath leave and did not see it? > >> So if in my controller I send a packet during the time the switch is >> disconnected NOX will return: >> >> no datapath with id 6d00026f13fe480 registered at nox > > The switch is disconnected and then removed from the list of active > sockets (hopefully sending a datapath leave in the process). Then, > when you send the packet with this datapath id, NOX cannot from a > socket with this datapath ('cos it's removed). Hence, the error. > > Regards > KK > > >> >> Aaron >> >> >> >> On Fri, Jul 15, 2011 at 12:21 PM, Aaron Rosen <[email protected]> wrote: >>> Hi Nick, >>> >>> http://codepad.org/0doGkR8G >>> >>> Also the machine does have an ipv6 address for the local lan >>> >>> arosen@expedient:~$ ip -6 route >>> fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit >>> 0 >>> >>> Though all the switches are on this same LAN so ipv6 here should be >>> working between the too. >>> >>> Is there an easy way to tell flowvisor not to use v6? Or should I >>> disable it in the OS? >>> >>> Thanks, >>> >>> Aaron >>> >>> >>> >>> >>> On Fri, Jul 15, 2011 at 6:03 AM, Nicholas Bastin <[email protected]> >>> wrote: >>>> Are you sure it's really not talking on an ipv6 socket? I imagine >>>> it's very likely that Clemson is doing some 6to4, as are most >>>> campuses. What does netstat -an say? Also, you might want to try to >>>> tell flowvisor to bind to v4 sockets only. >>>> >>>> -- >>>> Nick >>>> >>> >>> >>> >>> -- >>> Aaron O. Rosen >>> Masters Student - Network Communication >>> 306B Fluor Daniel >>> >> >> >> >> -- >> Aaron O. Rosen >> Masters Student - Network Communication >> 306B Fluor Daniel >> _______________________________________________ >> openflow-discuss mailing list >> [email protected] >> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss >> > -- Aaron O. Rosen Masters Student - Network Communication 306B Fluor Daniel _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
