Bug ID 609402: When upgrading from v10.2.4 to v11.5.x or v11.6.x, with fallback set to null in a wideip pool, the new pool will have fallback-ipv4 set to any6.

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP DNS, GTM, Install/Upgrade(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Opened: Aug 05, 2016
Severity: 4-Minor
Related Article:
K59134660

Symptoms

When upgrading from v10.2.4 to v11.5.x or v11.6.x, with fallback set to null in a wideip pool, the new pool will have fallback-ipv4 set to any6.

Impact

The fallback-ipv4 is incorrectly set to an IPv6 address rather than an IPv4 address.

Conditions

-- Upgrading from v10.2.4 to v11.5.x or v11.6.x. -- Fallback set to null in a wideip pool.

Workaround

The only workaround is to set Fallback to a different value before upgrading, and then set back after upgrade is complete.

Fix Information

None

Behavior Change