Bug ID 1783649: New VLANs added to tenants on r2000 and r4000 appliances are created with MAC address "none"

Last Modified: Jun 19, 2025

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

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 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

Opened: Jan 03, 2025

Severity: 3-Major

Symptoms

This issue affects VLANs added to BIG-IP tenants on r2000 or r4000 series appliances which have previously encountered ID1596313. The newly added VLAN will appear in the tenant with the following set of symptoms: - The new VLAN appears in "tmsh show net vlan" output, however the output shows a MAC address of "none" for the VLAN. - The new VLAN does not appear in the output of "ip link" or "ifconfig" commands issued from the linux host. - The following error message is logged when adding a self IP address to the new VLAN: Cannot get device index for <VLAN> in rd<number> - ioctl failed: No such device You may also see the following error message associated with ID1596313 in /var/log/ltm: - mcpd[7883]: 01070712:3: Caught configuration exception (0), Invalid attempt to register an n-stage validator, the stage must be greater than the current stage, and within the range 1 to 101 inclusive, current stage: 7 registered: 5. Note that due to log rotation, this error message may not be present in /var/log/ltm unless the new VLAN addition is attempted shortly after encountering ID1596313.

Impact

The new VLAN cannot be associated with a self-ip and cannot be used for monitoring or other control-plane traffic.

Conditions

- You are running a BIG-IP tenant on a r2000 or r4000 series appliance. - You previously encountered ID1596313 on the BIG-IP tenant and the tenant was not rebooted since the encounter. - You add a new VLAN to the tenant.

Workaround

Reboot or restart mcpd on the affected tenant.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips