afaik, if ti's the same stuff - then it's here: https://issues.apache.org/jira/browse/CLOUDSTACK-9999
cheers On Fri, 9 Nov 2018 at 06:00, Ivan X Yue <ivan...@ca.ibm.com> wrote: > We are using CloudStack 4.9.3.1. We are using advance networking, and > create VPC network with multiple guest networks. Each guest network has a > few VMs and a few public IPs. Everything works well until we add the 9th > guest network to the VPC. After creating it and adding a VM there, the > Virtual Router is corrupted. All the public IPs that works before stop > working. > > When we check out the virtual router, it seems that when it setup the 9th > network, it creates eth10. However, instead of adding the inet info to > eth10, it is added to eth1 instead. We observe the same issue in > /etc/dnsmasq.d/cloud.conf. The DNS info is added to eth1 instead of > eth10. As the result, the cloud.conf file is corrupted and dnsmasq fails > to start. > > Is it a known issue? Is there any patch or work around? > > > root@r-514-VM:/etc/dnsmasq.d# ip addr > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UP qlen 1000 > link/ether 0e:00:a9:fe:01:72 brd ff:ff:ff:ff:ff:ff > inet 169.254.1.114/16 brd 169.254.255.255 scope global eth0 > 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UP qlen 1000 > link/ether 06:76:18:00:00:0a brd ff:ff:ff:ff:ff:ff > inet 10.125.18.81/26 brd 10.125.18.127 scope global eth1 > inet 172.16.8.1/24 brd 172.16.8.255 scope global eth1 > inet 10.125.18.82/26 brd 10.125.18.127 scope global secondary eth1 > inet 10.125.18.92/26 brd 10.125.18.127 scope global secondary eth1 > inet 10.125.18.99/26 brd 10.125.18.127 scope global secondary eth1 > inet 10.125.18.91/26 brd 10.125.18.127 scope global secondary eth1 > inet 10.125.18.101/26 brd 10.125.18.127 scope global secondary eth1 > inet 10.125.18.102/26 brd 10.125.18.127 scope global secondary eth1 > inet 10.125.18.115/26 brd 10.125.18.127 scope global secondary eth1 > inet 10.125.18.98/26 brd 10.125.18.127 scope global secondary eth1 > 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UP qlen 1000 > link/ether 02:00:67:af:00:02 brd ff:ff:ff:ff:ff:ff > inet 172.16.0.1/24 brd 172.16.0.255 scope global eth2 > 5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UP qlen 1000 > link/ether 02:00:5e:46:00:02 brd ff:ff:ff:ff:ff:ff > inet 172.16.1.1/24 brd 172.16.1.255 scope global eth3 > 6: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UP qlen 1000 > link/ether 02:00:27:b8:00:02 brd ff:ff:ff:ff:ff:ff > inet 172.16.2.1/24 brd 172.16.2.255 scope global eth4 > 7: eth5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UP qlen 1000 > link/ether 02:00:27:4b:00:02 brd ff:ff:ff:ff:ff:ff > inet 172.16.3.1/24 brd 172.16.3.255 scope global eth5 > 8: eth6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UP qlen 1000 > link/ether 02:00:79:f7:00:02 brd ff:ff:ff:ff:ff:ff > inet 172.16.4.1/24 brd 172.16.4.255 scope global eth6 > 9: eth7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UP qlen 1000 > link/ether 02:00:67:91:00:02 brd ff:ff:ff:ff:ff:ff > inet 172.16.5.1/24 brd 172.16.5.255 scope global eth7 > 10: eth8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP qlen 1000 > link/ether 02:00:4b:40:00:02 brd ff:ff:ff:ff:ff:ff > inet 172.16.6.1/24 brd 172.16.6.255 scope global eth8 > 11: eth9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP qlen 1000 > link/ether 02:00:44:40:00:02 brd ff:ff:ff:ff:ff:ff > inet 172.16.7.1/24 brd 172.16.7.255 scope global eth9 > 12: eth10: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 > link/ether 02:00:1d:61:00:02 brd ff:ff:ff:ff:ff:ff > > > Please let me know if there is any suggestion. Thx for any help in > advance. > > Thanks, > Ivan > > > -- Andrija Panić
