Bug ID 511588: Invalid virtual-address configuration fails to load

Last Modified: Mar 17, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(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

Fixed In:
12.0.0

Opened: Mar 10, 2015
Severity: 3-Major
Related AskF5 Article:
K91528447

Symptoms

Configuration fails to load when the system encounters a non-/Common partition in which two virtual addresses share the 'any' address (0.0.0.0). One must belong to the route-domain of the partition (that is, a route domain other than route-domain 0) and the other must belong to route-domain 0.

Impact

The configuration does not load once it is saved.

Conditions

Two virtual address items must be present in an alternate partition from /Common. The address field of one must be 'any%0', the other must be 'any'. This means that the alternate partition must belong to a route-domain other than 0 (zero), and one virtual address must belong to that route-domain

Workaround

In the partitioned config files /config/partitions/partition_name/bigip.conf), replace all references to 'any' with '0.0.0.0' and reload.

Fix Information

The system now correctly handles the case in which two virtual addresses share the 'any' address (0.0.0.0), one in a route domain other than 0 (zero), and one in route domain 0.

Behavior Change