Using Neutron networking and virtual IPs are exposing themselves to the external network. Why?

asked 2014-06-12 13:47:48 -0600

thomaslouis18 gravatar image

updated 2014-06-13 15:43:53 -0600

smaffulli gravatar image

Running ICE HOUSE implementation with NEUTRON networking ML2 plugin.

Have 6 compute nodes. Compute nodes 1 - 4 do not expose the virtual IPs to external network (work as expected).

Compute nodes 5 and 6 expose the virtual IPs.

When using ping comannd from VM running on compute node 5 or 6 to an external IP the external IP being pinged receives both a ping from 192.x.x.x. (virtual internal IP) and from the floating IP external address.

All 6 compute nodes are configured identically (NOVA CONFIG, NEUTRON CONFIG, ML2_CONFIG.INI)

edit retag flag offensive close merge delete


Interesting problem. Can someone explain where in this configuration( Neutron, ML2, gre tunnels) where the nat'ing of the private to public (floating ) address takes place? on the compute node or network node?

pap gravatar imagepap ( 2014-06-12 15:56:11 -0600 )edit

We think it may be a glitch in the monitoring system in our environment?? We'll update this question as we verify that is indeed the issue.

thomaslouis18 gravatar imagethomaslouis18 ( 2014-06-13 08:45:09 -0600 )edit