On Thu, Mar 5, 2015 at 11:21 AM, Ben Pfaff <b...@nicira.com> wrote:
> On Thu, Mar 05, 2015 at 09:40:44AM -0800, Gurucharan Shetty wrote:
>> On Thu, Mar 5, 2015 at 8:50 AM, Ben Pfaff <b...@nicira.com> wrote:
>> > I've explained this a lot over the years.
>> >
>> > Signed-off-by: Ben Pfaff <b...@nicira.com>
>> > ---
>> >  FAQ.md | 24 ++++++++++++++++++++++++
>> >  1 file changed, 24 insertions(+)
>> >
>> > diff --git a/FAQ.md b/FAQ.md
>> > index 5ee529c..fc4161c 100644
>> > --- a/FAQ.md
>> > +++ b/FAQ.md
>> > @@ -772,6 +772,30 @@ A: If you add them one at a time with ovs-vsctl, it 
>> > can take a long
>> >
>> >     takes seconds, not minutes or hours, in the OVS sandbox environment.
>> >
>> > +Q1: I created a bridge named br0.  My bridge shows up in "ovs-vsctl
>> > +    show", but "ovs-ofctl show br0" just prints "br0 is not a bridge
>> > +    or a socket".
>> > +Q2: I have a bridge br0.  I added a new port vif1.0, and it shows
>> > +    up in "ovs-vsctl show", but "ovs-vsctl list port" says that it has
>> > +    OpenFlow port ("ofport") -1, and "ovs-ofctl show br0" doesn't show
>> > +    vif1.0 at all.
>> I think the Q2 is no longer true.
>>
>> root@ubuntu-test:~# ovs-vsctl add-port br0 p20
>> ovs-vsctl: Error detected while setting up 'p20'.  See ovs-vswitchd
>> log for details.
>> root@ubuntu-test:~# ovs-vsctl show
>> b1d3db14-03d2-4f3d-9db8-95d16441589a
>>     Bridge "br0"
>>         Port "p0"
>>             Interface "p0"
>>         Port "p20"
>>             Interface "p20"
>>                 error: "could not open network device p20 (No such device)"
>>         Port "br0"
>>             Interface "br0"
>>                 type: internal
>>     ovs_version: "2.3.90"
>> root@ubuntu-test:~#
>
> Yeah, it's true that newer versions are more helpful, but we still get
> the question because not everyone is using the newest version.
>
> How about this version?
>
> --8<--------------------------cut here-------------------------->8--
>
> From: Ben Pfaff <b...@nicira.com>
> Date: Thu, 5 Mar 2015 11:20:56 -0800
> Subject: [PATCH] FAQ.md: Explain why "ovs-vsctl show" shows a port but it
>  isn't there.
>
> I've explained this a lot over the years.
>
> Signed-off-by: Ben Pfaff <b...@nicira.com>
> ---
>  FAQ.md |   34 ++++++++++++++++++++++++++++++++++
>  1 file changed, 34 insertions(+)
>
> diff --git a/FAQ.md b/FAQ.md
> index 5ee529c..0519721 100644
> --- a/FAQ.md
> +++ b/FAQ.md
> @@ -772,6 +772,40 @@ A: If you add them one at a time with ovs-vsctl, it can 
> take a long
>
>     takes seconds, not minutes or hours, in the OVS sandbox environment.
>
> +### Q: I created a bridge named br0.  My bridge shows up in "ovs-vsctl
> +    show", but "ovs-ofctl show br0" just prints "br0 is not a bridge
> +    or a socket".
> +
> +A: Open vSwitch wasn't able to create the bridge.  Check the
> +   ovs-vswitchd log for details (Debian and Red Hat packaging for Open
> +   vSwitch put it in /var/log/openvswitch/ovs-vswitchd.log).
> +
> +   In general, the Open vSwitch database reflects the desired
> +   configuration state.  ovs-vswitchd monitors the database and, when
> +   it changes, reconfigures the system to reflect the new desired
> +   state.  This normally happens very quickly.  Thus, a discrepancy
> +   between the database and the actual state indicates that
> +   ovs-vswitchd could not implement the configuration, and so one
> +   should check the log to find out why.  (Another possible cause is
> +   that ovs-vswitchd is not running.  This will make "ovs-vsctl"
> +   commands hang, if they change the configuration, unless one
> +   specifies "--no-wait".)
> +
> +### I have a bridge br0.  I added a new port vif1.0, and it shows
Missing 'Q'
Acked-by: Gurucharan Shetty <gshe...@nicira.com>
> +    up in "ovs-vsctl show", but "ovs-vsctl list port" says that it has
> +    OpenFlow port ("ofport") -1, and "ovs-ofctl show br0" doesn't show
> +    vif1.0 at all.
> +
> +A: Open vSwitch wasn't able to create the port.  Check the
> +   ovs-vswitchd log for details (Debian and Red Hat packaging for Open
> +   vSwitch put it in /var/log/openvswitch/ovs-vswitchd.log).  Please
> +   see the previous question for more information.
> +
> +   You may want to upgrade to Open vSwitch 2.3 (or later), in which
> +   ovs-vsctl will immediately report when there is an issue creating a
> +   port.
> +
> +
>  Quality of Service (QoS)
>  ------------------------
>
> --
> 1.7.10.4
>
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to