OK. But what is your higher level goal? The best way to observe the inactivity probe message depends on how you plan to react to it. On May 15, 2013 11:07 PM, "akash sharma" <[email protected]> wrote:
> Thanks for the response. > It resolves my two queries. > Regarding query#2, I need to capture the "inactivity-probe" message sent > by the switch to the controller. > But I am not able to understand how can I capture the messages/packets > exchanged between the switch and the unix controller. > > Regards, > Akash > > On Thu, May 16, 2013 at 11:26 AM, Ben Pfaff <[email protected]> wrote: > >> On Thu, May 16, 2013 at 11:23:23AM +0530, akash sharma wrote: >> > 1. I need to disconnect the unix socket. >> > >> > I deleted the link created above using the following command: >> > >> > [root@user]rm /usr/local/var/run/openvswitch/br0.mgmt >> > >> > Am i correct or is there any other way to disconnect the unix socket >> from >> > bridge? >> >> ovs-vsctl del-controller br0 >> >> > 2. Also, I am not able to understand where to check for the >> > "inactivity-prove" message sent by the switch to the unix controller. >> >> What do you mean by "to check for" it? >> >> > 3. Does setting inactivity-probe to zero triggers the switch to enter >> in >> > fail-open mode? >> >> No. >> > >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
