Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP ASM, LTM
Known Affected Versions:
10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 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.5.9, 11.5.10
Fixed In:
11.4.1 HF6, 11.2.1 HF11, 10.2.4 HF8
Opened: Mar 07, 2014 Severity: 3-Major Related Article:
K15620
Interface names for VLANs with long names are generated by truncating the VLAN leaf name and adding a numeric suffix (e.g. ~1, ~2, etc.). If the truncated interface names have the same prefix (e.g. long_name~1 and long_name~2), then if you perform create and destroy operations with these VLANs, and then save and reload the configuration, this may result in the MCP's internal mapping not matching the actual interface name that the OS is using. MCP's internal interface name mapping was getting reset when the configuration was reloaded.
The user may be unable to alter the VLANs in question (or create objects referencing these VLANs, such as self-IPs), and MCP must be restarted to restore full functionality.
There must be multiple VLANs with long leaf names that, when truncated, have the same exact prefix. This could also happen to shorter VLAN names that have the same leaf name but different paths (e.g. /Common/myvlan and /Test/myvlan). This results in a scenario where interface names have the same prefix followed by a numeric suffix (e.g. long_name~1, long_name~2, etc.). The configuration must have been saved and reloaded after deleting one or more of these VLANs.
Do not use long names (or matching names, in the case where the path names are different). If this is not possible, ensure that long names do not match each other when truncated to interface names (i.e. have something different in their first 9 characters).
We now preserve the MCP interface name mapping for VLANs when performing a configuration load operation.