I popped these OIDs into the config file. Marking as fixed.

commit 2a7e96a2d8fb630b52df60f4e115425a816c93c4

I don't know the code enough,but basically it's just telling linkd how to co poke around for getting a table of the VLANs. Possibly you could do some regexp matching to the sysDescr.0 to see if it's a real Cisco box (and not a Linksys, which tends to be embedded Linux):

SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(40)SE, RELEASE SOFTWARE (fc3)
Copyright (c) 1986-2007 by Cisco Systems, Inc.

As long as you find "Cisco IOS" then I haven't seen a device that haven't needed to get it's OID on the list. Another Possible strategy would be to match the model number, (C29..) and other known model servies 35xx, 36xx, 37xx, 65xx, etc.

Antionio would be the one to ask, as he built it this way.

But in the short term, just commit the specifics and score a cheap bug close.

I don't know enough about the equipment, but is there a reason we need to have this huge list of hardcoded specifics, or is it something that can be determined at scan-time? Seems silly to have to keep updating that every time there are new devices.

And another: 1.615
Cisco IOS Software, C3560 Software (C3560-IPBASE-M), Version 12.2(25)SEB4, RELEASE SOFTWARE (fc1)
Model revision number : C0
Motherboard revision number : A0
Model number : WS-C3560G-24TS-S

Here's another missing one: 1.359
IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(22)EA6, RELEASE SOFTWARE (fc1)
Model revision number: M0
Motherboard revision number: B0
Model number: WS-C2950T-24