Please see my responses inline, prefixed by [SL].
> On Jul 20, 2016, at 11:14 PM, chetandeep singh <chetandeep.sin...@gmail.com> > wrote: > > We are just adding one physical port eth3 in OVS that does not have > IP/broadcast associated with it, eth2 still is primary port that has > gateway/netmask/IP and default ip route is through eth2. [SL] If you are adding only a single physical port to OVS (eth3), then a bridging loop is likely not the problem. The only other thing I can suggest is that you check your NIC driver and NIC firmware; for example, on early versions of the Intel XL710 driver/firmware, attaching the NIC to a bridge would cause ~50% packet loss. > On Wed, Jul 20, 2016 at 11:54 PM, Scott Lowe <scott.l...@scottlowe.org> wrote: > Please see my responses inline, prefixed by [SL]. > > > > On Jul 20, 2016, at 10:34 PM, chetandeep singh > > <chetandeep.sin...@gmail.com> wrote: > > > > Hi Scott, > > > > the idea with this is that with secondary port (no IP assigned) part of > > the bridge, and ip routes for all default packets set through primary port. > > We can have VM's interact with rest of network by adding taps into the > > bridge as well. I have been debugging why pings between host and VM are not > > happening and can see packets getting dropped in the bridge itself. > > > [SL] If you are adding multiple physical ports to the same OVS bridge, and > those physical ports belong to the same broadcast domain, then I believe > you're going to create a bridging loop. If you'd like to test to see if this > is the problem, enable STP on the OVS bridge before adding eth3. > > > > On Wed, Jul 20, 2016 at 11:17 PM, Scott Lowe <scott.l...@scottlowe.org> > > wrote: > > Please see my response below. > > > > > > > On Jul 20, 2016, at 5:04 PM, chetandeep singh > > > <chetandeep.sin...@gmail.com> wrote: > > > > > > Hi Ben > > > > > > I have a primary eth port eth2 and secondary Ethernet port eth3 that does > > > not have any ip assigned to the same. So machine does not get locked up. > > > The issue is that adding secondary port makes packets to get dropped in > > > bridge . Any ideas why ? > > > > > > On Wednesday, July 20, 2016, Ben Pfaff <b...@ovn.org> wrote: > > > On Wed, Jul 20, 2016 at 05:45:27PM -0500, chetandeep singh wrote: > > > > I am trying to run some basic setup with OVS like creating a bridge and > > > > adding taps for VM's in the bridge and a secondary ethernet port and > > > > then > > > > eventually put the machine on the network. What I see is that if I do > > > > below > > > > commands and add secondary eth3 port on the machine in the ovs bridge, I > > > > see that packets start getting dropped. If I do ifconfig eth3, I dont > > > > see > > > > any drops. > > > > > > > > Any idea why this might be happening in this case ? > > > > > > Forgive me for what seems to be a simple question, but is it possible > > you're creating a bridging loop? You indicated that you have a primary port > > (eth2) and the drops come when you add a secondary port (eth3), so a > > bridging loop seems like a plausible explanation. > > > > Good luck! > > -- > Scott > > > > > -- > " In financial markets, the majority is always wrong " _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
