Bug ID 1441549: Modifying the destination address of a virtual server leaves behind the associated virtual address.

Last Modified: Sep 02, 2026

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

Fixed In:
21.1.0.2, 17.5.1.9, 17.1.3.5

Opened: Dec 13, 2023

Severity: 3-Major

Symptoms

Stale, orphaned virtual addresses exist without any referencing virtual servers.

Impact

load sys config fails, and the license cannot be upgraded on an F5OS host when a DHCP virtual server is configured in a non-default route domain (RD).

Conditions

Create virtual server with same destination in default and non default route domains.

Workaround

To recover type in cli : root@(localhost)(cfg-sync Standalone)(Active)(/Common)(tmos)# save sys config Saving running configuration... /config/bigip.conf /config/bigip_base.conf /config/bigip_user.conf Saving Ethernet map ...done Saving PCI map ... - verifying checksum .../var/run/f5pcimap: OK done - saving ...done And the virtual server is again in the config root@(localhost)(cfg-sync Standalone)(Active)(/Common)(tmos)# list ltm virtual ltm virtual dhcp { auto-lasthop enabled creation-time 2023-11-18:03:02:15 destination 255.255.255.255%30:bootps dhcp-relay ip-protocol udp last-modified-time 2023-11-18:04:43:33 mask 255.255.255.255 profiles { dhcpv4 { } } serverssl-use-sni disabled source 0.0.0.0%30/0 translate-address enabled translate-port disabled vs-index 3 }

Fix Information

NA

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips