Bug ID 1967441: Reserved VLAN names in F5OS cause MCPd configuration failures in Tenant

Last Modified: Apr 20, 2026

Affected Product(s):
BIG-IP F5OS-A, F5OS-C, TMOS(all modules)

Known Affected Versions:
17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1

Opened: Jun 12, 2025

Severity: 3-Major

Symptoms

When a VLAN is created using a reserved name and assigned to a tenant, MCPd fails to load the configuration. The following errors are observed: - 01070088:3: The requested object name (/Common/mgmt) is invalid - 01070712:3: Internal error, object is not in a folder: type: vlan id: /Common/mgmt - Cannot set MAC address for to '<mac_address>' in rd0 - ioctl failed: No such device

Impact

MCPd is unable to load the configuration or list VLANs, potentially causing tenant network connectivity issues and preventing VLAN management operations.

Conditions

- F5OS environment with tenant configuration - VLAN created with a reserved system name such as mgmt, eth0, tmm, or tmm_bp - VLAN assigned to a tenant

Workaround

Avoid using reserved names (mgmt, eth0, tmm, tmm_bp, etc.) when creating VLANs in F5OS. Use alternative, non-reserved naming conventions for VLAN objects.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips