Some general questions:

Will the datapath actively leave the network if it is burdened? Or
only link_timeouts at discovery module will make them leave.

My program has following messages:
00016|openflow|WARN:stream: send error: Broken pipe
00017|routingMR|ERR:Add flow entry to dp:f7cae4000064 failed with
32:Broken pipe.
00018|openflow|WARN:stream: receive error: Bad file descriptor
00019|nox|WARN:stream: disconnected (Bad file descriptor)
Datapath leave, f7:ca:e4:00:00:64

What does "Broken pipe" usually imply? I cant find where it is from.

On Tue, Dec 22, 2009 at 10:41 AM, Guanyao Huang <[email protected]> wrote:
> But I am now in UCdavis. I will start my intern next quarter....
>
> On Tue, Dec 22, 2009 at 5:18 AM, Rob Sherwood <[email protected]> 
> wrote:
>> Hi Guanyao,
>>
>> I'm going to be in the lab today ... let's try to find some time to
>> talk about this.
>>
>> - Rob
>> .
>>
>>
>>
>> On Tue, Dec 22, 2009 at 5:17 AM, Rob Sherwood <[email protected]> 
>> wrote:
>>> On Mon, Dec 21, 2009 at 12:47 PM, Martin Casado <[email protected]> wrote:
>>>> I agree that if the problem is timeout due to loss from overload, then the
>>>> only solution is prioritization.
>>>
>>> In general yes, but the current discovery algorithm is fairly brittle.
>>>  With a large number of ports (48) on a hardware switch, even a small
>>> amount of packet loss it can falsely report down links.  Part of the
>>> goal of the rewrite is to address this issue.
>>>
>>>> Question for the slicing folks, does slicing extend to the control channel
>>>> (packets set to the controller?)
>>>
>>> In addition to what Yiannis said (short story == "not yet"), Jean from
>>> HP developed a "rate limiter" openflow action as a vendor extension
>>> that can affect control and data traffic, so that could be used here.
>>> I think this is a useful primitive and something I'm hoping will
>>> making it into a future release of openflow (1.1?).
>>>
>>> - Rob
>>> .
>>>
>>
>

_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Reply via email to