Bug ID 1058765: Virtual Addresses created from an address list with prefix all say Offline (enabled)

Last Modified: Aug 19, 2026

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 15.1.10.7, 15.1.10.8, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.1.3.4, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8

Opened: Nov 01, 2021

Severity: 3-Major

Symptoms

A virtual address can report an availability of "offline" with the reason "The virtual address has no virtual servers", even though virtual servers using the address are available. The system may log messages similar to the following: mcpd[4913]: 010719e7:5: Virtual Address /Common/2001:db8::1 general status changed from BLUE to RED. mcpd[4913]: 010719e8:5: Virtual Address /Common/2001:db8::1 monitor status changed from UNCHECKED to DOWN. Or: mcpd[8071]: 010719e7:5: Virtual Address /Common/2001:db8::1 general status changed from GREEN to RED. mcpd[8071]: 010719e8:5: Virtual Address /Common/2001:db8::1 monitor status changed from UP to DOWN.

Impact

BIG-IP does not associate the affected virtual server with its virtual address for status calculation. The virtual address reports offline. If route health injection depends on that status, BIG-IP withdraws the virtual address from dynamic routing.

Conditions

A virtual server uses traffic matching criteria that references a destination address list, and an address in that list is configured with CIDR prefix notation, such as "192.0.2.1/32" or "2001:db8::1/128"

Workaround

Use one of the following, based on the address-list contents: - For a single destination address, replace the destination address list with an inline destination address in the traffic matching criteria. - For host addresses, remove the CIDR prefix from each affected address-list entry: - IPv4: replace 192.0.2.250/32 with 192.0.2.250. - IPv6: replace 2001:db8::250/128 with 2001:db8::250. Neither workaround supports address lists containing network prefixes: an IPv4 CIDR prefix other than /32, or an IPv6 CIDR prefix other than /128.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips