i am facing the bridge mapping problem, after adding the ovs external interface br-ext to the ext1 (physical public interface), connection lost to the server. I have applied manual configuration whatever mention in other blogs, but still issue is there.
Thank you very much for your reply.
have a look on this link .
https://www.rdoproject.org/networking/neutron-with-existing-external-network/ (https://www.rdoproject.org/networking...)
you can create the interface fie if not already done.
DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=192.168.122.212 # Old eth0 IP since we want the network restart to not
# kill the connection, otherwise pic your something outside your dhcp range
NETMASK=255.255.255.0 # your netmask
GATEWAY=192.168.122.1 # your gateway
DNS1=192.168.122.1 # your nameserver
ONBOOT=yes
And change the config file of your physical interface
DEVICE=eth0
HWADDR=52:54:00:92:05:AE # your hwaddr (find via ip link show eth0)
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes
I am in the same situation. I have installed openstack using devstack. Now I am at the point of linking br-ex interface to an external interface. I have used the above commands (ovs-vsctl , etc) and now I cannot access anymore my external interface only the br-ex interface IP. External interface is setup to use DHCP, is getting the IP but is not accessible from outside. When I am powering on instances they are hanging on powering on state. At the end, I have managed to regain access to external interface using command ovs-vsctl del-port br-ex ens160 Any suggestion to solve this situation ?
Assuming eth0 or ext1 interface is having internet access and br-ex bridge is set up,
this command will disconnect the acess of node, Login to console and set
Also ensure that br-ex is having the public ip address or the inter access network, if not , see it via CLI
This would bring back the connectivity.
Asked: 2016-01-16 03:35:59 -0500
Seen: 4,579 times
Last updated: Jan 18 '16
