[Expired for neutron because there has been no activity for 60 days.] ** Changed in: neutron Status: Incomplete => Expired
-- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1287485 Title: No traffic in GRE tunnel with ML2 Status in OpenStack Neutron (virtual network service): Expired Bug description: This is a multi-node installation with one controller node, one network node and one compute node. All nodes are VMs running in a XenServer 6.2 server. ML2 plugin is configured to support neutrun- server running in controller node. In both network node and dom0, br-int and br-tun are both existed and gre ports seem good. But if I tried to ping a VM from network node, I can only get traffic from br-int on network node. No traffic on the physical interface of network node which used to transmit inter VM data. Of course, the VM cannot get a IP address or ping the gateway. The same thing happened in Dom0: traffic can only be captured on br- int, but no data on physic interface. On network node: xxxx@os-network:~$ sudo ovs-vsctl show 65b85364-5313-4c6e-879a-47eb02eeeb62 Bridge br-tun Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port "gre-2" Interface "gre-2" type: gre options: {in_key=flow, local_ip="10.3.0.15", out_key=flow, remote_ip="10.3.0.10"} Bridge br-int Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "tapb3202ff8-84" tag: 4095 Interface "tapb3202ff8-84" type: internal Port br-int Interface br-int type: internal Port "qr-3faa3fe7-5c" tag: 1 Interface "qr-3faa3fe7-5c" type: internal Port "tap88bf4722-01" tag: 1 Interface "tap88bf4722-01" type: internal Bridge br-ex Port "qg-ac2d1761-c0" Interface "qg-ac2d1761-c0" type: internal Port "eth0" Interface "eth0" Port "qg-f90546e4-6c" Interface "qg-f90546e4-6c" type: internal Port br-ex Interface br-ex type: internal ovs_version: "1.10.2" On Dom0: [root@cloud-main ~]# ovs-vsctl show 88b05926-605a-48b0-9dfd-bfd519994720 Bridge "xapi3" fail_mode: standalone Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port "vif8.3" Interface "vif8.3" Port "vif9.0" Interface "vif9.0" Port "xapi3" Interface "xapi3" type: internal Bridge "xenbr2" fail_mode: standalone Port "eth2" Interface "eth2" Port "vif4.2" Interface "vif4.2" Port "xenbr2" Interface "xenbr2" type: internal Port "vif8.1" Interface "vif8.1" Bridge "xenbr1" fail_mode: standalone Port "vif8.0" Interface "vif8.0" Port "vif2.1" Interface "vif2.1" Port "eth1" Interface "eth1" Port "vif3.1" Interface "vif3.1" Port "xenbr1" Interface "xenbr1" type: internal Port "vif1.0" Interface "vif1.0" Port "vif4.1" Interface "vif4.1" Bridge "xenbr3" fail_mode: standalone Port "xenbr3" Interface "xenbr3" type: internal Port "eth3" Interface "eth3" Bridge "xenbr0" fail_mode: standalone Port "xenbr0" Interface "xenbr0" type: internal Port "vif3.0" Interface "vif3.0" Port "vif1.1" Interface "vif1.1" Port "vif4.0" Interface "vif4.0" Port "vif2.0" Interface "vif2.0" Port "eth0" Interface "eth0" Port "vif8.2" Interface "vif8.2" Bridge br-tun Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port "gre-1" Interface "gre-1" type: gre options: {in_key=flow, local_ip="10.3.0.10", out_key=flow, remote_ip="10.3.0.15"} Port br-tun Interface br-tun type: internal ovs_version: "1.4.6" To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1287485/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp