Last Modified: Dec 20, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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.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.5.1, 17.5.1.2, 17.5.1.3, 21.0.0
Opened: Nov 25, 2025 Severity: 3-Major
After a configuration change, a virtual server is not accepting traffic
No traffic
If 2 Virtual servers destination IP are swapped via a cli transactions, no error messages are displayed leading to believe it was accepted. Although the configuration has changed, traffic is not processed. # create cli transaction [batch mode]# modify ltm virtual vs1 destination 20.20.20.20:80 Command added to the current transaction [batch mode]# modify ltm virtual vs2 destination 10.10.10.10:80 Command added to the current transaction [batch mode]# submit cli transaction tmm logs will show these messages: err tmm[2367]: 01010009:3: Failed to bind to address err tmm[2367]: 01010008:3: Listener config update failed for /Common/vs2: ERR:ERR_USE
Directly swap using tmsh directly using a 3rd temporary destination address: tmsh modify ltm virtual vs1 destination 30.30.30.30:80 tmsh modify ltm virtual vs2 destination 10.10.10.10:80 tmsh modify ltm virtual vs1 destination 20.20.20.20:80
None