# Should I see ports configured on compute br-int? [closed]

I'm having trouble spawning an instance and I keep seeing vif_type binding errors (see https://ask.openstack.org/en/question... ). When I compare the output of ovs-vsctl show on the network node I see:

admin@net001:~$sudo ovs-vsctl show fc1e005e-9978-4a36-8e60-758c2a4366cf Bridge br-int fail_mode: secure Port "tapd3acfcd6-a7" tag: 4 Interface "tapd3acfcd6-a7" type: internal Port "qr-6dfff92e-30" tag: 4 Interface "qr-6dfff92e-30" type: internal Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port br-int Interface br-int type: internal Bridge br-ex Port br-ex Interface br-ex type: internal Port "qg-d37a0bb0-1e" Interface "qg-d37a0bb0-1e" type: internal Port "eth2" Interface "eth2" Bridge br-tun Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port br-tun Interface br-tun type: internal ovs_version: "2.0.2"  where as on the compute node I the get the following with no ports defined. I can setup networks, routers successfully. admin@compute001:/$ sudo ovs-vsctl show
37916218-40fb-4999-a353-dbf06b54c5d0
Bridge br-int
fail_mode: secure
Port br-int
Interface br-int
type: internal
ovs_version: "2.0.2"


My question is this what I should be seeing.

edit retag reopen merge delete

### Closed for the following reason the question is answered, right answer was accepted by TVA close date 2014-10-16 22:21:52.179080

Sort by » oldest newest most voted

The diagram in this article shows you pretty much what you would expect to see on your compute node. The short answer is that yes, you should see ports on br-int -- this is where virtual instances are connected.

The "binding failed" errors usually indicate a problem with your neutron configuration. You probably want to look closely at the neutron openvswitch-agent log on your compute node and see if there's anything there. If you do find some errors, please update your question to include them.

If there's nothing there, you probably want to take a closer look at the neutron logs on the network host. You can reduce the number of logs you have to look through by limiting your search to lines that are contemporary with the failed nova boot attempt.

more

# Get to know Ask OpenStack

Resources for moderators