Network connectivity issue
Hi,
Im following this guide 1.) to set up Red Hat RDO packstack openstack with an existing network. It says to use the current ip of your eth0 interface for the br-ex device instead and remove it from eth0. But when I do this, I get weird connectivity issues where even a single ping to the default gateway fails 95% of the time, but not always: some pings come through alright. A simple network restart or reboot does not change anything.
The problem (temporarily) goes away (but returns later) when I use a previously unused ip in the same range for the br-ex device, but I wonder what the issue could be ? Could it be as simple as an arp cache entry somewhere (my internet cable modem ?) or something ?
Ive added the contents of ifcfg-br-ex and ifcfg-eth0, and the output of 'ovs-vsctl show'
1.) http://openstack.redhat.com/Neutron_with_existing_external_network (http://openstack.redhat.com/Neutron_w...)
# cat /etc/sysconfig/network-scripts/ifcfg-br-ex
DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=none
IPADDR=192.168.178.27 # Old eth0 IP since we want the network restart to not kill the connection, otherwise pick something outside your dhcp range
NETMASK=255.255.255.0 # your netmask
GATEWAY=192.168.178.1 # your gateway
DNS1=192.168.178.1 # your nameserver
ONBOOT=yes
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
HWADDR=00:0C:29:5E:C4:5D
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes
# ovs-vsctl show
c418fb29-4fb4-45ae-a3b4-ea86ff356135
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port "eth0"
Interface "eth0"
Bridge br-int
Port br-int
Interface br-int
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
ovs_version: "1.11.0"
Could you post ifcfg-br-ex and ifcfg-eth0. Also output
ovs-vsctl show
You wrote :-
Yes 192.168.178.1 is functioning as the DNS server for the network.
Would try
# tcpdump -vv -i br-ex
during pinging gateway. Issue should be caught via (-vv)
Also, it only happens if I run 'packstack --allinone --provision-all-in-one-ovs-bridge=n' and manually edit the ifcfg files, and not if i omit the '--provision-all-in-one-ovs-bridge=n'' and just run 'packstack --allinone'. I guess thats because when you run packstack that way, it doenst attempt to modify your existing network ?
When I run packstack like that, I get this :