[CLOUDSTACK-9097] Extra public ip addresses do not work immediately

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 4.6.0, 4.6.1
• Component/s: SystemVM
• Security Level: Public (Anyone can view this level - this is the default.)
• Assignee: Remi Bergsma
• Reporter: Remi Bergsma
• Created: 01/Dec/15 13:46
• Updated: 04/Dec/15 10:05
• Resolved: 04/Dec/15 10:01

Description

Sometimes public ip addresses do not work immediately, this is in case they are used as a secondary ip on an interface.

Service on secondary ip which is recently used by other routervm and therefore cached on the gateway:

root@r-547-VM:~# tcpdump -e -i eth1 icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
13:23:27.709762 5c:5e:ab:29:bf:ca (oui Unknown) > 06:0e:ee:00:00:24 (oui Unknown), ethertype IPv4 (0x0800), length 98: 52D9557D.cm-11-1b.dynamic.ziggo.nl > x.y.237.226: ICMP echo request, id 10107, seq 1127, length 64
13:23:28.701694 5c:5e:ab:29:bf:ca (oui Unknown) > 06:0e:ee:00:00:24 (oui Unknown), ethertype IPv4 (0x0800), length 98: 52D9557D.cm-11-1b.dynamic.ziggo.nl > x.y.237.226: ICMP echo request, id 10107, seq 1128, length 64
^C

Packets arrive, but with incorrect / cached mac and are ignored by the routervm kernel.
Run arping to update the arp-cache on the gateway and things start to work:

root@r-547-VM:~# arping -S x.y.237.226 x.y.237.129
ARPING x.y.237.129
60 bytes from 00:00:5e:00:01:a0 (x.y.237.129): index=0 time=1.372 msec
60 bytes from 00:00:5e:00:01:a0 (x.y.237.129): index=1 time=893.665 usec
^C
— x.y.237.129 statistics —
2 packets transmitted, 2 packets received, 0% unanswered (0 extra)
root@r-547-VM:~# tcpdump -e -i eth1 icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
13:23:51.922328 5c:5e:ab:29:bf:ca (oui Unknown) > 06:47:88:00:00:24 (oui Unknown), ethertype IPv4 (0x0800), length 98: 52D9557D.cm-11-1b.dynamic.ziggo.nl > x.yy.237.226: ICMP echo request, id 8422, seq 9, length 64
13:23:51.922368 06:47:88:00:00:24 (oui Unknown) > 00:00:5e:00:01:a0 (oui Unknown), ethertype IPv4 (0x0800), length 98: x.y.237.226 > 52D9557D.cm-11-1b.dynamic.ziggo.nl: ICMP echo reply, id 8422, seq 9, length 64

Suggested solution: update routervm scripting to run arping when adding a secondary ip.

Ping wilder.rodrigues