How to exclude lightweight APs from Ciscoworks Discovery

Now that Cisco has fixed the "cisco.com" suffix in CDP on lightweight APs, I need another way to exclude these devices from Ciscoworks Discovery (isn't it funny how a "bug" can sometimes be useful?). I've considered sysobjectid, but since they don't support SNMP this doesn't work. I can't use IP addresses (practically) because they are DHCP and it's too big a burden managing the exclusion list. I've tried DNS suffix, but that doesn't seem to work . . . but I may be doing something wrong. Any other ideas? Thanks!

You can edit NMSROOT/conf/csdiscovery/system-config.xml, and add the CDP IDs of the LWAPPs there. The CDPID section looks like:

This system-config.xml file will only be used for ad hoc discoveries and newly scheduled discovery jobs. If you need to modify an existing discovery job, you'll have to do that under NMSROOT/objects/csdiscovery/JODIB.

By very careful when editing these files. If you break the well-formedness, Discovery will not work.

Replies

You can edit NMSROOT/conf/csdiscovery/system-config.xml, and add the CDP IDs of the LWAPPs there. The CDPID section looks like:

This system-config.xml file will only be used for ad hoc discoveries and newly scheduled discovery jobs. If you need to modify an existing discovery job, you'll have to do that under NMSROOT/objects/csdiscovery/JODIB.

By very careful when editing these files. If you break the well-formedness, Discovery will not work.

did the trick, but only after we got a modified discovery.jar which took care of some bug.

But, it turns out that both lightweight AND autonomous APs was excluded since they both report the same CDP neighbor.

This behaviour started after version X of the autonomous IOS, I have a older autonomous which report "AIR-APxxxxx".

So now im out of ideas on how to exclude the lightweight APs, they make the discovery very slow right now.

I was thinking of doing an export of all the ligthweight APs IP adresses from WCS, and then import it as filter in Ciscoworks, but the filter dialog doesnt support file import like the seed list dialog does.

Is there maybe some other way of importing a filter list, can it be done by modifying some file or similar?

Autonomous really uses LAP in the CDP ID? I thought that was specific to LWAPPs. My 1242 at home (autonomous) has a platform ID of cisco AIR-AP1242AG-A-K9 and it's running the latest autonomous code (12.4(25d)JA1).

You could add the list of IPs directly to the CSDiscovery-conf.xml file (you could script that), but there is no import mechanism.