BugZero found this defect 2215 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/26/2024
BIG-IP
BIG-IP MA-VE
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
No fixed releases provided.
Bug ID 637827: VADC: after re-deploying a single-nic VM with multiple nics, a load can fail due to stp member 1.0 ... 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. ... 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