Thanks for the explanations! > On Apr 23, 2016, at 10:15 AM, Ben Pfaff <b...@ovn.org> wrote: > > On Fri, Apr 22, 2016 at 11:25:26PM -0700, Ben Warren wrote: >> As you can see, the disconnects happen when the datapath ID changes, >> presumably due to adding interfaces? Only the addition of the first >> two interfaces seem to bring it down. > > OVS disconnects OpenFlow connections when the datapath ID changes > because the datapath ID is important to some controllers and OpenFlow > provides no way for a switch to notify a controller that the datapath ID > has changed. > OK, so what causes the datapath ID to change (Linux kernel 3.10 datapath in this case)? Does it come from the kernel or is it an OVS thing? >> On the client side, I’m really confused. As you can see, I re-open >> the connection with a HELLO message, and the HELLO response comes back >> with an earlier XID (0x80 vs. the expected 0x86). Message 0x83 was a >> BARRIER response, and a valid BARRIER reply was received, so it would >> seem that messages after 0x80 were accepted: > > HELLO is not a request/response message. Rather, both sides of the > OpenFlow connection send a hello message at the initiation of the > connection. Each side chooses its own xid as it wishes, so one cannot > expect the xids to match. The xid for a hello message is only > significant for sending an OFPT_ERROR response, if necessary.
OK, is this understanding correct: for send/receive (GetConfig, Feature etc.) messages ovs-vswitchd will mirror back the XID of the request, but for HELLO it keeps a static monotonically increasing counter? Looking at my data, the previous HELLO from the switch had an XID of 0x7f, so the 0x80 I see after the connection restart is not a rollback of overall messages, but the logical next value for HELLO? thanks again! I always appreciate your quick, helpful responses! —Ben
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
