Normally the OpenFlow reference implementation and Open vSwitch log a message when a connection closes.
On Wed, Feb 03, 2010 at 12:59:16PM -0800, Guanyao Huang wrote: > Hi > What are the logs you were talking about? > I saw the following messages. The CPU is only around 30%. > > 00038|openflow|WARN:stream: send error: Broken pipe > 00039|routingMR|ERR:Add flow entry to dp:f7cae4000064 failed with > 32:Broken pipe. > 00040|openflow|WARN:stream: send error: Bad file descriptor > 00041|routingMR|ERR:Send packet to dp:f7cae4000064 failed with 9:Bad > file descriptor. > 00042|openflow|WARN:stream: send error: Broken pipe > 00043|routingMR|ERR:Add flow entry to dp:f7cae40001f4 failed with > 32:Broken pipe. > 00044|openflow|WARN:stream: send error: Bad file descriptor > 00045|routingMR|ERR:Send packet to dp:f7cae40001f4 failed with 9:Bad > file descriptor. > 00046|openflow|WARN:stream: send error: Broken pipe > 00047|routingMR|ERR:Add flow entry to dp:f7cae40000c8 failed with > 32:Broken pipe. > 00048|openflow|WARN:stream: send error: Bad file descriptor > 00049|routingMR|ERR:Send packet to dp:f7cae40000c8 failed with 9:Bad > file descriptor. > 00050|openflow|WARN:stream: send error: Broken pipe > 00051|routingMR|ERR:Add flow entry to dp:f7cae400012c failed with > 32:Broken pipe. > 00052|openflow|WARN:stream: send error: Bad file descriptor > 00053|routingMR|ERR:Send packet to dp:f7cae400012c failed with 9:Bad > file descriptor. > 00054|openflow|WARN:stream: send error: Broken pipe > 00055|routingMR|ERR:Add flow entry to dp:f7cae4000190 failed with > 32:Broken pipe. > 00056|openflow|WARN:stream: send error: Bad file descriptor > 00057|routingMR|ERR:Send packet to dp:f7cae4000190 failed with 9:Bad > file descriptor. > 00058|openflow|WARN:stream: receive error: Bad file descriptor > 00059|nox|WARN:stream: disconnected (Bad file descriptor) > 00060|openflow|WARN:stream: receive error: Bad file descriptor > 00061|nox|WARN:stream: disconnected (Bad file descriptor) > 00062|openflow|WARN:stream: receive error: Bad file descriptor > 00063|nox|WARN:stream: disconnected (Bad file descriptor) > 00064|openflow|WARN:stream: receive error: Bad file descriptor > 00065|nox|WARN:stream: disconnected (Bad file descriptor) > 00066|openflow|WARN:stream: receive error: Bad file descriptor > 00067|nox|WARN:stream: disconnected (Bad file descriptor) > Datapath leave, f7:ca:e4:00:00:64 > Datapath leave, f7:ca:e4:00:01:f4 > Datapath leave, f7:ca:e4:00:00:c8 > Datapath leave, f7:ca:e4:00:01:2c > Datapath leave, f7:ca:e4:00:01:90 > > > On Tue, Feb 2, 2010 at 9:33 PM, Ben Pfaff <b...@nicira.com> wrote: > > On Tue, Feb 02, 2010 at 09:23:52PM -0800, Guanyao Huang wrote: > >> I am wondering what is the usual cause for a datapath to proactively > >> leaves the network. Is it because it is overburdened or some probe > >> messages time-out? > > > > The easiest way to find out is to look at the logs on the switches. > > _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
