Last Modified: Aug 19, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.5.1, 11.5.1 hf1, 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.1 hf10, 11.5.1 hf11, 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.5.10, 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 Article:
K91528447
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.
The configuration does not load once it is saved.
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
In the partitioned config files /config/partitions/partition_name/bigip.conf), replace all references to 'any' with '0.0.0.0' and reload.
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.