Bug ID 744930: IPv6 generic host unable to be probed when only IPv4 server objects are defined

Last Modified: May 01, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP DNS(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5

Opened: Sep 24, 2018
Severity: 4-Minor

Symptoms

After upgrading to 13.1.X you may find that IPv6 generic hosts are no longer able to be probed by server objects that only have IPv4 addresses defined. The code in 13.1 is a design change to make probing more reliable

Impact

Attempts to probe the IPv6 object will fail

Conditions

- Running 13.1.X or newer. - IPv6 Generic Host - Server objects with only IPv4 addresses i.e. gtm datacenter /Common/DC { } gtm server /Common/GTM { datacenter /Common/DC devices { /Common/GTM { addresses { 192.168.1.1 { } } } } monitor /Common/BIG-IP product BIG-IP } gtm server /Common/Generic { datacenter /Common/DC devices { /Common/Generic { addresses { fd12:3456:789a:1::1 { } } } } monitor /Common/gateway_icmp product generic-host virtual-servers { ipv6 { destination fd12:3456:789a:1::1.80 } } }

Workaround

Add an IPv6 address to the server object

Fix Information

None

Behavior Change