[ovs-dev] ovs-appctl returns code 400

xin zhang xing5820 at gmail.com
Mon Nov 29 18:24:51 UTC 2010

Thank you Ben

2010/11/29 Ben Pfaff <blp at nicira.com>:
> On Mon, Nov 29, 2010 at 05:56:19AM -0800, xin zhang wrote:
>>            I am not sure if I am in the right room, if this maillist
>> is not for open vswitch user, pls kindly redirect me to correct place.
> discuss at openvswitch.org is another list that you could use.  It is
> probably a better choice.  But we might as well answer your questions as
> long as they are here.
I will subscribe this

>>            I just followed example in "How to Install Open vSwitch on
>> Linux" to setup bridge "br0", now I want to list the bridge I create,
>> brctl tool never works.
> That is an imprecise statement.  What did you do with brctl, what did
> you expect to happen, and what actually happened?

I just want to see something like "brctl show" does, for example:
bridge name	bridge id		STP enabled	interfaces
virbr0		8000.000000000000	

>> Then I use "ovs-appctl show br0" or "ovs-appctl show", the outputs
>> just say: ovs-appctl: ovs-vswitchd: server returned reply code 400
>>            what the magic code means? is any tips for me to get a
>> readable print?
> ovs-appctl is the wrong program for this purpose.  You should use
> "ovs-dpctl show"  or "ovs-vsctl list-br" to list bridges.
> (Does something in the documentation suggest that you should use
> ovs-appctl for this?  If it does, then I would like to fix it.)

thank you, I got  ovs-appctl in "How to Use Open vSwitch with KVM".
for ovs-appctl, i see it from manual page of ovs-vswitchd,  in section of
"BRIDGE COMMANDS". It seems that's my misunderstanding.

>>            one more question, will open vswitch provide API for cloud
>> software integrates itself with vswitch? I don't see any API doc. or
>> it only provides a set of tools to easily play with vbridges?
> I'll leave this question for others who are better suited to answer it.

Thanks. Hope someone talks something about it.

Frank Zhang

More information about the dev mailing list