We’re noticing that the VLANs page (Ports-->VLANs) is less useful than it could be, because it seems to keep around every VLAN that has ever existed on every device that has ever existed. I also don’t see anything in …/includes/housekeeping/* that would address this.
It’s so bad/useless at this point that 1701 records are from devices that don’t even exist anymore (vs. 4409 where the parent device at least still exists, even if the VLAN doesn’t). A similar problem exists in vlans_fdb.
Is there some housekeeping mechanism that is supposed to take care of this, that I can go troubleshoot? Or is it just an oversight/omission? And if not, can I just do a “DELETE FROM vlans WHERE NOT EXISTS ( <query on ‘device’> )” (and something similar on vlans_fdb) to clean it up?
Thanks, -Adam
Adam Thompson Consultant, Infrastructure Services [MERLIN] 100 - 135 Innovation Drive Winnipeg, MB, R3T 6A8 (204) 977-6824 or 1-800-430-6404 (MB only) athompson@merlin.mb.camailto:athompson@merlin.mb.ca www.merlin.mb.cahttp://www.merlin.mb.ca/
