Nevertheless, it should be ok if you change the port on every agent, and use the same port.
regards On Thu, Oct 10, 2013 at 4:04 PM, P Balaji-B37839 <b37...@freescale.com> wrote: > Hi Rohon, > > Thanks for confirmation. > > We will file a bug on this. > > Regards, > Balaji.P > >> -----Original Message----- >> From: Mathieu Rohon [mailto:mathieu.ro...@gmail.com] >> Sent: Thursday, October 10, 2013 6:43 PM >> To: OpenStack Development Mailing List >> Subject: Re: [openstack-dev] [Neutron] OVS Agent and VxLan UDP Ports >> >> hi, >> >> good point Balaji, the dst_port is the port on which ovs is listening for >> vxlan packets, but I don't know what is the option in ovs-vsctl to set >> the remote port of the vxlan unicast tunnel interface. >> But it looks like a bug since you're right, tunnel_sync and tunnel_update >> RPC messages should handle the VXLAN udp port, additionnaly to the vxlan >> remote ip. >> >> Kyle is away for the moment, he should know the good option to set in >> ovs-vsctl to specify a remote port for a vxlan tunnel. But you should >> fill a bug for that, to track this issue. >> >> Thanks for playing with vxlan, and helping us to debug it! >> >> >> On Wed, Oct 9, 2013 at 6:55 AM, P Balaji-B37839 <b37...@freescale.com> >> wrote: >> > Any comments on the below from community using OVS will be helpful. >> > >> > Regards, >> > Balaji.P >> > >> >> -----Original Message----- >> >> From: P Balaji-B37839 >> >> Sent: Tuesday, October 08, 2013 2:31 PM >> >> To: OpenStack Development Mailing List; Addepalli Srini-B22160 >> >> Subject: [openstack-dev] [Neutron] OVS Agent and VxLan UDP Ports >> >> >> >> Hi, >> >> >> >> Current OVS Agent is creating tunnel with dst_port as the port >> >> configured in INI file on Compute Node. If all the compute nodes on >> >> VXLAN network are configured for DEFAULT port it is fine. >> >> >> >> When any of the Compute Nodes are configured for CUSTOM udp port as >> >> VXLAN UDP Port, Then how does the tunnel will be established with >> remote IP. >> >> >> >> It is observed that the fan-out RPC message is not having the >> >> destination port information. >> >> >> >> Regards, >> >> Balaji.P >> > >> > >> > >> > _______________________________________________ >> > OpenStack-dev mailing list >> > OpenStack-dev@lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev