Kb172

Emulab FAQ: Testbed Operations: How to deal with stranded VLANs?

Something hiccuped again and left VLAN turds. This time it was cisco3 that got stuck with VLANs 266-288 and 333-336.

Of course, I didn't remember what Rob told me last time about the easiest way to fix it! A simple "snmpit -o " didn't work because the VLAN was not in the DB, just in one switch. So I just logged into the switches to see where they existed, made sure no ports were in them, and removed them.

Hmm, that should work: snmpit -o actually only consults the DB to see if you have permission to modify the VLAN. If you used wap, it should have worked fine.

But deleting the VLANs by hand was just fine too.