Created attachment 1129182 [details] This picbure has 3 instance but one instance has two nic. but it can't work both nic in instance Description of problem: I refered to use existing external network for eth0 by below link https://www.rdoproject.org/networking/neutron-with-existing-external-network/ and I asked on openstack community page https://ask.openstack.org/en/question/88188/i-would-like-to-use-also-second-nic-as-existing-external-network/ I refered below link to make more external network. http://dbaxps.blogspot.com/2015/10/multiple-external-networks-with-single.html one nic per one instance can work. but no proper answers are not recived from my ask. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Two nic can work properly. Expected results: First NIC is down and second nic is available. Additional info:
Can you please paste ovs-agent and l3-agent config files here? What does it mean that your vm with two nic can't work (what exactly doesn't work as you expect)? Can you please also paste routes from within your guest with two nics?
Created attachment 1135070 [details] /etc/neutron/plugins/ml2/openvswitch_agent.ini
Created attachment 1135071 [details] /etc/neutron/l3_agent.ini
Created attachment 1135075 [details] 3 instance's network pictures two interface for external public and external private instance network Demo-Network1 192.168.100.3, 192.168.15.2 Demo-Network2 192.168.200.3, 172.16.0.3 one interface for external public instance network Demo-Network1 192.168.100.4, 192.168.15.3 one interface for external private instance network Demo-Network2 192.168.200.4, 172.16.0.4 192.168.15.0/24 is external public(br-ex) and 172.16.0.0/24 is external private(br-ex2) for openstack
192.168.15.254 in the picture is gateway ip 172.16.0.123 in the picture is another computer's private network ip
In two interface for external public and external private picture, you can see private ping(172.16.0.123) success but not public ping(192.168.15.254).
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.