Last Modified: Jul 18, 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.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
Fixed In:
12.0.0, 11.6.5.1, 11.5.9
Opened: Oct 01, 2014 Severity: 2-Critical Related Article:
K16338
The system encounters issues when you save a self IP in one SCF, then delete the self IP and recreate it using the same name but specifying a different IP address.
The system posts an error similar to the following: 01070712:3: Cannot create IP address 10.10.10.5/27 in vlan 'internal' in rd0 - netlink error: 17 (File exists) - net/validation/routing.cpp, line 701
This occurs when you load the SCF and try the delete/recreate a second time.
To work around this, you can run the command bigstart restart mcpd. As an alternative, you can issue the following commands prior to loading the scf file: 'tmsh delete net self <self_name>' 'ip addr delete <IpAddress>/<netmask> dev <vlan_name>.
Fixed a problem where the user loads an SCF that has a different self IP than the current configuration the IP does not change.