weizhouapache commented on pull request #5078:
URL: https://github.com/apache/cloudstack/pull/5078#issuecomment-857768234


   > > > It is weird though. We have one CloudStack (dev) environment where we 
use VXLAN with Multicast and not with BGP.
   > > > This script is in use there and is working just fine.
   > > 
   > > 
   > > @wido do you use linux bridge in the environment ?
   > > if not, it does not have this issue.
   > 
   > Yes. That environment uses Linux bridging:
   > 
   > root@n01:~# brctl show
   > bridge name        bridge id               STP enabled     interfaces
   > brvx-2001          8000.be3a51f8ca5e       no              vnet2
   >                                                    vxlan2001
   > brvx-2002          8000.1265359ad1da       no              vnet0
   >                                                    vxlan2002
   > brvx-2004          8000.3e7767b8c917       no              vnet1
   >                                                    vxlan2004
   > cloud0             8000.fe00a9fe017d       no              vnet3
   >                                                    vnet4
   >                                                    vnet5
   > cloudbr1           8000.86fab6316ec1       no              vxlan100
   > root@n01:~# cat /etc/cloudstack/agent/agent.properties|grep cloudbr
   > private.network.device=cloudbr1
   > guest.network.device=cloudbr0
   > public.network.device=cloudbr0
   > root@n01:~# 
   > Does this help?
   
   @wido yes, I think the main difference is, you use vxlan100 while I use eth1.
   (I followed the link 
http://docs.cloudstack.apache.org/en/latest/plugins/vxlan.html?highlight=vxlan#configure-in-ubuntu)
   
   can you also share the result of command `bridge fdb |egrep "vxlan100 |via"` 
on kvm host ?
   thanks.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to