Bug ID 637827: VADC: after re-deploying a single-nic VM with multiple nics, a load can fail due to stp member 1.0

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP MA-VE(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1

Opened: Jan 09, 2017
Severity: 3-Major

Symptoms

The configuration fails to load with the following message: 01070523:3: No Vlan association for STP Interface Member 1.0 Unexpected Error: Loading configuration process failed.

Impact

Load fails and requires manual intervention. Otherwise, the STP member is benign because vADC does not support STP.

Conditions

In single-nic mode, the interface 1.0 exists and can be saved as a VLAN member. Upon re-deploying the virtual-machine from single nic mode to multi-nic, the 1.0 interface becomes pending and should no longer impact any configuration. However, a condition exists after a VLAN delete, where the associated (automatically created) stp member is not removed from the running config and can cause a load error.

Workaround

Remove the STP interface member 1.0 and reload.

Fix Information

None

Behavior Change