Bug ID 481974: Using an SCF to modify a self IP address might cause problems

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.6.0, 11.6.1, 11.6.2, 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, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.5.1, 11.5.9

Opened: Oct 01, 2014

Severity: 2-Critical

Related Article: K16338

Symptoms

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.

Impact

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

Conditions

This occurs when you load the SCF and try the delete/recreate a second time.

Workaround

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>.

Fix Information

Fixed a problem where the user loads an SCF that has a different self IP than the current configuration the IP does not change.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips