[ovs-dev] Loss of Network Connectivity

Timothy Ficarra t.ficarra at yahoo.com
Mon Dec 7 14:24:25 PST 2009 

Here's the information you requested. Also, the configuration was causing a the computer to crash. Before the system crashed, though, a data loop was created on the public network which resulted in the machine's IP being deactivated.

dp0:
	flows: cur:3, soft-max:512, hard-max:262144
	ports: cur:3, max:1024
	groups: max:16
	lookups: frags:0, hit:18864579, missed:6 lost:0
	queues: max-miss:100, max-action:100
	port 0: br0 (internal)
	port1: eth1
	port 2: vif0.1

Dec 07 16:58:14|00001|oftl|INFO|connecting to unix:/usr/local/var/run/br0.mgmt stats_reply (xid=0x5471e644): flags=none type=1(flow)
 duration=46s, table_id=1, priority=0, n_packets=40588117, n_bytes=1704700914, actions=NORMAL


Regards,
T Ficarra

--- On Mon, 7/12/09, Justin Pettit <jpettit at nicira.com> wrote:

> From: Justin Pettit <jpettit at nicira.com>
> Subject: Re: [ovs-dev] Loss of Network Connectivity
> To: "Timothy Ficarra" <t.ficarra at yahoo.com>
> Cc: dev at openvswitch.org
> Date: Monday, 7 December, 2009, 4:29 PM
> What do the RX and TX counters look
> like now?  Can you dump the output of "ovs-dpctl show"
> and "ovs-ofctl dump-flows br0"?
> 
> --Justin
> 
> 
> On Dec 7, 2009, at 1:27 PM, Timothy Ficarra wrote:
> 
> > Ok. I re-configured the setup such that there was one
> bridge, br0, to which eth1 (uplink) and vif0.1 (dom0) were
> connected. Unfortunately I am still unable to talk outside
> of the computer. Attempting a ping will merely hang.
> > 
> > Regards,
> > T Ficarra
> > 
> > --- On Mon, 7/12/09, Justin Pettit <jpettit at nicira.com>
> wrote:
> > 
> >> From: Justin Pettit <jpettit at nicira.com>
> >> Subject: Re: [ovs-dev] Loss of Network
> Connectivity
> >> To: "Timothy Ficarra" <t.ficarra at yahoo.com>
> >> Cc: dev at openvswitch.org
> >> Date: Monday, 7 December, 2009, 3:57 PM
> >> Just as you would with the bridge,
> >> you need to have all the devices you want to
> communicate on
> >> bridges.  The way you have it currently
> configured,
> >> eth0 and eth1 will pass traffic between
> themselves, but your
> >> VM won't see any traffic.  In the Xen setups
> I've seen,
> >> each PIF gets its own bridge and VIFs are attached
> to the
> >> appropriate bridge.  I would have expected
> your config
> >> file to look more like this:
> >> 
> >> bridge.br0.port=br0
> >> bridge.br0.port=eth0
> >> bridge.br0.port=vif0.1
> >> bridge.br1.port=br1
> >> bridge.br1.port=eth1
> >> 
> >> (This is assuming that vif0.1 is connected to
> eth0. 
> >> Move it to br1, if it should communicate through
> eth1.)
> >> 
> >> If you have OVS installed on your computer with
> the bridge
> >> compatibility code, then Xen should be making
> bridge calls
> >> that OVS will intercept and make work
> properly.  
> >> 
> >> If instead you want to do all this configuration
> by hand,
> >> then you may want to check how Xen set up the
> bridge
> >> initially (you can see this with "brctl
> show").  Then,
> >> just recreate the configuration in
> ovs-vswitchd.conf.
> >> 
> >> --Justin
> >> 
> >> 
> >> On Dec 7, 2009, at 12:43 PM, Timothy Ficarra
> wrote:
> >> 
> >>> I am running ovs-vswitchd and ovs-brcompatd.
> >>> The RX counters increase on lo, peth1, and
> vif0.1
> >>> 
> >>> eth1 is registering a flat zero on TX and RX.
> >>> 
> >>> T Ficarra
> >>> 
> >>> --- On Mon, 7/12/09, Justin Pettit <jpettit at nicira.com>
> >> wrote:
> >>> 
> >>>> From: Justin Pettit <jpettit at nicira.com>
> >>>> Subject: Re: [ovs-dev] Loss of Network
> >> Connectivity
> >>>> To: "Timothy Ficarra" <t.ficarra at yahoo.com>
> >>>> Cc: dev at openvswitch.org
> >>>> Date: Monday, 7 December, 2009, 3:36 PM
> >>>> I assume you're running ovs-vswitchd
> >>>> and ovs-brcompatd, correct?  Do you
> see the
> >> RX counters
> >>>> going up on your network devices when you
> run
> >> ifconfig?
> >>>> 
> >>>> --Justin
> >>>> 
> >>>> 
> >>>> On Dec 7, 2009, at 12:23 PM, Timothy
> Ficarra
> >> wrote:
> >>>> 
> >>>>> Here are the details of the problem:
> >>>>> 
> >>>>> ovs version:
> >>>>> open vswitch 0.90.7
> >>>>> 
> >>>>> no git
> >>>>> no patches
> >>>>> 
> >>>>> os version:
> >>>>> Linux version 2.6.18-164.6.1.el5xen 
> >>>>> gcc version 4.1.2 20080704
> >>>>> 
> >>>>> Contents of ovs-vwitchd.conf:
> >>>>> bridge.br0.port=br0
> >>>>> bridge.br0.port=eth0
> >>>>> bridge.br0.port=eth1
> >>>>> 
> >>>>> output of ovs-dpctl show:
> >>>>> dp0:
> >>>>>      flows: cur:0,
> >> soft-max:512,
> >>>> hard-max:262144
> >>>>>      ports: cur:3,
> >> max:1024
> >>>>>      groups: max:16
> >>>>>      lookups: frags:0,
> >> hit:0, missed:0,
> >>>> lost:0
> >>>>>      queues:
> max-miss:100,
> >>>> max-action:100
> >>>>>      port 0: br0
> >> (internal)
> >>>>>      port 1: eth0
> >>>>>      port 2: eth1
> >>>>> 
> >>>>> What actually happened:
> >>>>>      loss of network
> >> connectivity after
> >>>>>      % rmmod bridge
> >>>>>      % insmod
> >>>> datapath/linux-2.6/openvswitch_mod.ko
> >>>>>      % insmod
> >>>> datapath/linux-2.6/brcompat_mod.ko
> >>>>> What was expected to happen:
> >>>>>      no loss of
> network
> >> connectivity 
> >>>>> 
> >>>>> 
> >>>>> Regards,
> >>>>> T Ficarra
> >>>>> 
> >>>>> 
> >>>>> --- On Mon, 7/12/09, Ben Pfaff <blp at nicira.com>
> >>>> wrote:
> >>>>> 
> >>>>>> From: Ben Pfaff <blp at nicira.com>
> >>>>>> Subject: Re: [ovs-dev] Loss of
> Network
> >>>> Connectivity
> >>>>>> To: "Timothy Ficarra" <t.ficarra at yahoo.com>
> >>>>>> Cc: dev at openvswitch.org
> >>>>>> Date: Monday, 7 December, 2009,
> 12:05 PM
> >>>>>> Timothy Ficarra <t.ficarra at yahoo.com>
> >>>>>> writes:
> >>>>>> 
> >>>>>>> After following the steps in
> 'Using
> >> Open
> >>>> vSwitch in
> >>>>>> place of
> >>>>>>> Linux bridging' the system is
> left in
> >> a state
> >>>> without
> >>>>>> network
> >>>>>>> connectivity. Is there any
> further
> >>>> configuration which
> >>>>>> must be
> >>>>>>> completed in order for the
> switch to
> >> function
> >>>>>> properly?
> >>>>>> 
> >>>>>> There's too little information
> here to
> >> guess what
> >>>> went
> >>>>>> wrong.
> >>>>>> Could you include the information
> from
> >> the
> > 
> >>>> REPORTING-BUGS
> >>>>>> file:
> >>>>>>       
>    http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=REPORTING-BUGS;hb=HEAD
> >>>>>> This additional information might
> give us
> >>>> something to work
> >>>>>> from.
> >>>>>> 
> >>>>> 
> >>>>> 
> >>>>>        New Email
> names
> >> for you! 
> >>>>> Get the Email name you've always
> wanted on the
> >> new
> >>>> @ymail and @rocketmail. 
> >>>>> Hurry before someone else does!
> >>>>> http://mail.promotions.yahoo.com/newdomains/aa/
> >>>>> 
> >>>>> 
> >> _______________________________________________
> >>>>> dev mailing list
> >>>>> dev at openvswitch.org
> >>>>> http://openvswitch.org/mailman/listinfo/dev_openvswitch.org
> >>>> 
> >>>> 
> >>> 
> >>> 
> >>>       Get your new
> Email address!
> >>> Grab the Email name you've always wanted
> before
> >> someone else does!
> >>> http://mail.promotions.yahoo.com/newdomains/aa/
> >>> 
> >>>
> _______________________________________________
> >>> dev mailing list
> >>> dev at openvswitch.org
> >>> http://openvswitch.org/mailman/listinfo/dev_openvswitch.org
> >> 
> >> 
> > 
> > 
> >      New Email names for you! 
> > Get the Email name you've always wanted on the new
> @ymail and @rocketmail. 
> > Hurry before someone else does!
> > http://mail.promotions.yahoo.com/newdomains/aa/
> 
> 


      Get your preferred Email name!
Now you can @ymail.com and @rocketmail.com. 
http://mail.promotions.yahoo.com/newdomains/aa/

More information about the dev mailing list