Excluding interfaces from automatic discovery

Question

Apparently there is no good way to exclude some of the interfaces from automatic discovery (the ones that are down). So has anyone figured good way to put stuff to the ignore list? Currently I'm having something like 55k elements in SAM+NPM combination and going through every node one by one would be bit of pain in the ass. I already asked from support but it seems that there is no built-in feature for this so maybe someone is good with SQL and knows how to effectively create good ignore lists?

abdulraheemsidz · Answer

Another post showing capability to exclude some interfaces in discovery, would work with NPM 12..0 and above.

Network Sonar Discovery Exclusion by Vendor

FormerMember · Answer

I have tried to unmanage those interfaces but it seems that sometimes the automatic discovery "finds" those again and remanages those. So then we are back at the start.

I'll go through those link and hope to find something usefull.

HolyGuacamole · Answer

An ignore list for interfaces would certainly be handy.

If the interfaces are down, the network discovery shouldn't be selecting them by default during the import process, although they do show up in the scheduled discovery results.

Since you are monitoring 55k elements, you would be at the SLX license tier. One thing you could do is put these unwanted interfaces into a super long term maintenance mode. These interfaces will count for the licensed elements, but they wouldn't be polled.