Hi guys,
trying vxlan as isolation method, and although manual testing of vxlan
works fine (so kernel and IP binary are fine) - I'm dont have inter-host
communication at all...
Per documentation, I should have created a bridge (cloudbr3 in my example,
IP address is set on the bridge). trafic label set to "cloudbr3" when
deployed zone
Here is brctl show output (removed unneeded lines)
[root@compute2 ~]# brctl showc
bridge name bridge id STP enabled interfaces
brvx-5064 8000.ae4843b4b918 no vnet0
vxlan5064
cloudbr3 8000.089e01d9422b no eth3
[root@compute2 ~]# ip -d link show vxlan5064
10: vxlan5064: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue
master brvx-5064 state UNKNOWN
link/ether ae:48:43:b4:b9:18 brd ff:ff:ff:ff:ff:ff
vxlan id 5064 group 239.0.19.200 dev cloudbr3 port 32768 61000 ttl 10
ageing 300
VMs on one host can communicate between themselves, but VMs on different
host can not comunicate.
So, is this the right config that I have done - I should have done
everything per documentation.
This is ACS 4.4 clean install, Centos 6.5, elrepo kernel 3.10 and the
bultin iproute2 iproute-2.6.32 for the default kernel - I know I should
have coresponding iproute2 version - but this ones DOES work, as I
confirmed by manually createing vxlan interfaces, and pinging between hosts
etc.
Any suggestions ?
--
Andrija Panić
--------------------------------------
http://admintweets.com
--------------------------------------
