[
https://issues.apache.org/jira/browse/CLOUDSTACK-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770100#comment-13770100
]
Paul Edwards commented on CLOUDSTACK-4690:
------------------------------------------
Further to this, if I then remove the extra allocated ip, instead of removing
ethernet interfaces, it created another one. So now I have nine. I restarted
the router, hoping it would clean up. Instead, the backup became the master,
and now it has 9 ethernet interfaces....
Sep 17 22:21:19 r-236-VM kernel: [81507.701760] pci 0000:00:00.0: no hotplug
settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.701765] pci 0000:00:00.0: using default
PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.701848] pci 0000:00:01.0: no hotplug
settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.701851] pci 0000:00:01.0: using default
PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.701901] ata_piix 0000:00:01.1: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.701904] ata_piix 0000:00:01.1: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.701954] uhci_hcd 0000:00:01.2: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.701957] uhci_hcd 0000:00:01.2: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.702006] piix4_smbus 0000:00:01.3: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.702009] piix4_smbus 0000:00:01.3: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.702058] pci 0000:00:02.0: no hotplug
settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.702061] pci 0000:00:02.0: using default
PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.712779] virtio-pci 0000:00:03.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.712784] virtio-pci 0000:00:03.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.712879] virtio-pci 0000:00:04.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.712882] virtio-pci 0000:00:04.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.712956] virtio-pci 0000:00:05.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.712959] virtio-pci 0000:00:05.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.713033] virtio-pci 0000:00:06.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.713036] virtio-pci 0000:00:06.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.713109] virtio-pci 0000:00:07.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.713112] virtio-pci 0000:00:07.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.713161] virtio-pci 0000:00:08.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.713164] virtio-pci 0000:00:08.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.713237] virtio-pci 0000:00:09.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.713240] virtio-pci 0000:00:09.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.713313] virtio-pci 0000:00:0a.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.713316] virtio-pci 0000:00:0a.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.713389] virtio-pci 0000:00:0b.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.713392] virtio-pci 0000:00:0b.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.713469] virtio-pci 0000:00:0c.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.713472] virtio-pci 0000:00:0c.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.713614] virtio-pci 0000:00:0d.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.713617] virtio-pci 0000:00:0d.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.713691] virtio-pci 0000:00:0e.0: no
hotplug settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.713694] virtio-pci 0000:00:0e.0: using
default PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.713817] pci 0000:00:0f.0: no hotplug
settings from platform
Sep 17 22:21:19 r-236-VM kernel: [81507.713820] pci 0000:00:0f.0: using default
PCI settings
Sep 17 22:21:19 r-236-VM kernel: [81507.715179] virtio-pci 0000:00:0f.0:
enabling device (0000 -> 0003)
Sep 17 22:21:19 r-236-VM kernel: [81507.797785] virtio-pci 0000:00:0f.0: PCI
INT A -> Link[LNKC] -> GSI 11 (level, high) -> IRQ 11
Sep 17 22:21:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:21:19 r-236-VM cloud: ipassoc.sh:Adding first ip xxx.xxx.245.59/24 on
interface eth9
Sep 17 22:21:19 r-236-VM cloud: ipassoc.sh:Added SourceNAT xxx.xxx.245.59/24 on
interface eth9
Sep 17 22:21:19 r-236-VM cloud: ipassoc.sh:Added first ip xxx.xxx.245.59/24 on
interface eth9
Sep 17 22:21:19 r-236-VM cloud: ipassoc.sh:Add routing xxx.xxx.245.59/24 on
interface eth9
Sep 17 22:21:20 r-236-VM cloud: ipassoc.sh:Add routing xxx.xxx.245.59/24 rules
added
Sep 17 22:21:20 r-236-VM cloud: ipassoc.sh: VPN chain for xxx.xxx.245.59
already exists
Sep 17 22:21:20 r-236-VM cloud: ipassoc.sh: firewall chain for xxx.xxx.245.59
already exists
Sep 17 22:26:17 r-236-VM Keepalived_vrrp: VRRP_Instance(inside_network)
Transition to MASTER STATE
Sep 17 22:26:18 r-236-VM Keepalived_vrrp: VRRP_Instance(inside_network)
Entering MASTER STATE
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM Keepalived_vrrp: Netlink: filter function error
Sep 17 22:26:19 r-236-VM kernel: [81807.468369] eth5: IPv6 duplicate address
fe80::47e:68ff:fe00:103 detected!
Sep 17 22:26:19 r-236-VM kernel: [81807.468881] eth6: IPv6 duplicate address
fe80::47e:68ff:fe00:103 detected!
Sep 17 22:26:19 r-236-VM kernel: [81807.469072] eth6: IPv6 duplicate address
fe80::47e:68ff:fe00:103 detected!
Sep 17 22:26:19 r-236-VM kernel: [81807.469102] eth5: IPv6 duplicate address
fe80::47e:68ff:fe00:103 detected!
Sep 17 22:26:19 r-236-VM kernel: [81807.469108] eth5: IPv6 duplicate address
fe80::47e:68ff:fe00:103 detected!
Sep 17 22:26:19 r-236-VM kernel: [81807.660375] eth8: IPv6 duplicate address
fe80::427:a8ff:fe00:103 detected!
Sep 17 22:26:19 r-236-VM kernel: [81807.660960] eth8: IPv6 duplicate address
fe80::427:a8ff:fe00:103 detected!
Sep 17 22:26:19 r-236-VM kernel: [81807.660980] eth8: IPv6 duplicate address
fe80::427:a8ff:fe00:103 detected!
Sep 17 22:26:19 r-236-VM kernel: [81807.661059] eth7: IPv6 duplicate address
fe80::427:a8ff:fe00:103 detected!
Sep 17 22:26:19 r-236-VM kernel: [81807.661065] eth7: IPv6 duplicate address
fe80::427:a8ff:fe00:103 detected!
Sep 17 22:26:20 r-236-VM kernel: [81808.276573] NET: Unregistered protocol
family 15
Sep 17 22:26:20 r-236-VM kernel: [81808.294283] padlock: VIA PadLock not
detected.
Sep 17 22:26:20 r-236-VM kernel: [81808.295493] padlock: VIA PadLock Hash
Engine not detected.
Sep 17 22:26:20 r-236-VM kernel: [81808.297672] padlock: VIA PadLock not
detected.
Sep 17 22:26:20 r-236-VM kernel: [81808.310213] NET: Registered protocol family
15
Sep 17 22:26:20 r-236-VM kernel: [81808.337568] Initializing XFRM netlink socket
Sep 17 22:26:20 r-236-VM kernel: [81808.339459] padlock: VIA PadLock not
detected.
Sep 17 22:26:20 r-236-VM kernel: [81808.340765] padlock: VIA PadLock Hash
Engine not detected.
Sep 17 22:26:20 r-236-VM kernel: [81808.342881] padlock: VIA PadLock not
detected.
Sep 17 22:26:20 r-236-VM pluto: adjusting ipsec.d to /etc/ipsec.d
> KVM Router - to many ethernet devices created
> ---------------------------------------------
>
> Key: CLOUDSTACK-4690
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4690
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM
> Affects Versions: 4.1.1
> Environment: Centos 6.4
> Reporter: Paul Edwards
> Priority: Critical
> Attachments: management-server.log, router.log
>
>
> We have setup cloudstack with advanced networking. We have a network created
> 172.16.24.0/23, called news preprod. This has a number of vms created under
> it. When we initially set this up, we noticed that the router we created with
> 4 ethernet interfaces. This was unexpected, but didn't seem to be effecting
> the running of the router, so we didn't worry about it. The interfaces were:
> eth0 172.16.24.14, eth1 169.254.1.91, and both eth2 and eth2 were given the
> external ip (xxx.xxx.245.59). We investigated why we were getting 2
> externals, but couldn't figure it out. We also configured the router to have
> a redundant, with keepalived. They were working fine.
> Now I needed to add another external ip to the network. Did that, and
> restarted the network. I now have 8 (eight) eth interfaces. The new external
> ip is NOT one of them. Heres the ifconfig output:
> root@r-235-VM:~# ifconfig
> eth0 Link encap:Ethernet HWaddr 02:00:68:e1:00:1a
> inet addr:172.16.24.14 Bcast:172.16.25.255 Mask:255.255.254.0
> inet6 addr: fe80::68ff:fee1:1a/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:5485 errors:0 dropped:0 overruns:0 frame:0
> TX packets:21101 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:325618 (317.9 KiB) TX bytes:1581746 (1.5 MiB)
> eth1 Link encap:Ethernet HWaddr 0e:00:a9:fe:01:5b
> inet addr:169.254.1.91 Bcast:169.254.255.255 Mask:255.255.0.0
> inet6 addr: fe80::c00:a9ff:fefe:15b/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:22118 errors:0 dropped:0 overruns:0 frame:0
> TX packets:21148 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:3942785 (3.7 MiB) TX bytes:4287970 (4.0 MiB)
> eth2 Link encap:Ethernet HWaddr 06:16:06:00:01:03
> inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0
> inet6 addr: fe80::416:6ff:fe00:103/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:17331 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3930 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1063053 (1.0 MiB) TX bytes:234546 (229.0 KiB)
> eth3 Link encap:Ethernet HWaddr 06:d7:ec:00:01:03
> inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0
> inet6 addr: fe80::4d7:ecff:fe00:103/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:13603 errors:0 dropped:0 overruns:0 frame:0
> TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:792907 (774.3 KiB) TX bytes:704 (704.0 B)
> eth4 Link encap:Ethernet HWaddr 06:8b:5a:00:01:03
> inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0
> inet6 addr: fe80::48b:5aff:fe00:103/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:13319 errors:0 dropped:0 overruns:0 frame:0
> TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:779753 (761.4 KiB) TX bytes:704 (704.0 B)
> eth5 Link encap:Ethernet HWaddr 06:7e:68:00:01:03
> inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0
> inet6 addr: fe80::47e:68ff:fe00:103/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:13080 errors:0 dropped:0 overruns:0 frame:0
> TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:762111 (744.2 KiB) TX bytes:704 (704.0 B)
> eth6 Link encap:Ethernet HWaddr 06:7e:68:00:01:03
> inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0
> inet6 addr: fe80::47e:68ff:fe00:103/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:13086 errors:0 dropped:0 overruns:0 frame:0
> TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:762655 (744.7 KiB) TX bytes:774 (774.0 B)
> eth7 Link encap:Ethernet HWaddr 06:27:a8:00:01:03
> inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0
> inet6 addr: fe80::427:a8ff:fe00:103/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:13064 errors:0 dropped:0 overruns:0 frame:0
> TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:761153 (743.3 KiB) TX bytes:704 (704.0 B)
> eth8 Link encap:Ethernet HWaddr 06:27:a8:00:01:03
> inet addr:xxx.xxx.245.59 Bcast:xxx.xxx.245.255 Mask:255.255.255.0
> inet6 addr: fe80::427:a8ff:fe00:103/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:13043 errors:0 dropped:0 overruns:0 frame:0
> TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:759287 (741.4 KiB) TX bytes:704 (704.0 B)
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:6 errors:0 dropped:0 overruns:0 frame:0
> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:414 (414.0 B) TX bytes:414 (414.0 B)
> The cloudstack management browser still shows the router as only supposed to
> have 3 nics.
> The agent log on the physical host has nothing in it (I was tailing that log
> when I did this, as I would have thought that the agent has to create the
> devices for the vm to get them).
> I have attached the management log from just before to just after. (Time of
> change was 9:39am). I do not know why the router timestamp is not the same as
> the host.
> I have also attached the log of the router restart.
> The physical server is Centos 6.4, and all the vms that we have created are
> Centos 6.4. KVM is the hypervisor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
