I have out of band management configured with:

ovs-vsctl set controller <bridge> connection-mode=out-of-band
ovs-vsctl set bridge <bridge> other-config:disable-in-band=true

The out of band NIC is not added to an ovs bridge. When I connect it to my 
openDayLight controller (v0.8.4), that is when the recursion errors show up. 
Running 2.5.5 (ovs), it works perfectly.

f0fc01b4-904d-407b-a3bb-03fd3e004926
    Manager "tcp:10.246.49.188:6640"
        is_connected: true
    Bridge data
        Controller "tcp:10.246.49.188:6633"
            is_connected: true
        fail_mode: secure
        Port "vlan1"
            tag: 1
            Interface "vlan1"
                type: internal
        Port "ens256"
            tag: 10
            Interface "ens256"
        Port "ens224"
            tag: 1
            Interface "ens224"
        Port "vxlan3"
            Interface "vxlan3"
                type: vxlan
                options: {key=flow, remote_ip="10.246.48.149"}
        Port data
            Interface data
                type: inte

Dennis Heim | Domain Architect (Collaboration Labs)
World Wide Technology, Inc. | +1 314-212-1814


"The most powerful person in the world is the story teller. The storyteller 
sets the vision, values and agenda of an entire generation that is to come" - 
Steve Jobs
"Leaders who don't listen will eventually be surrounded by people who have 
nothing to say" --- Andy Stanley
"Worry less about who you might offend, and more about who you might inspire" 
-- Tim Allen
"Imagination is more important than knowledge."  -- Albert Einstein
"If you can raise the level of effort and performance in those around you, you 
are officially a leader" - Urban Meyer
"The greatest danger for most of us is not that our aim is too high and we miss 
it, but that it is too low and we reach it." -- Michelangelo Buonarroti
"Mediocore managers play checkers (assuming everyone is the same). Great 
managers play chess (acknowledging that everyone is unique)" - Marcus Buckingham
"If you're not failing every now and again, it's a sign you're not doing 
anything very innovative" - Woody Allen

Click here to join me in my Collaboration Meeting Room

-----Original Message-----
From: Ben Pfaff <[email protected]> 
Sent: Thursday, June 27, 2019 10:01 AM
To: Heim, Dennis <[email protected]>
Cc: [email protected]
Subject: Re: [ovs-discuss] Error ovs recursion limit reached on datapath

On Thu, Jun 27, 2019 at 04:48:45AM +0000, Heim, Dennis wrote:
> Any idea what causes the error message "ovs recursion limit reached on 
> datapath"? I have the configuration working on 2.5.5, but if I run 2.9 
> or 2.11, I get that error message.

It could be a bug in OVS or it could be an OpenFlow flow table that does 
something odd, for example, recursively executing connection tracking or 
tunneling from a system to itself.  You might be able to track it down by 
looking at the kernel flows with "ovs-dpctl dump-flows" or by tracing 
microflows or packets with "ovs-appctl ofproto/trace".
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to