Exclude Uncontrolled/Controlled Interfaces on Cisco SUP8-based switches

I find it really odd of Cisco to add this feature on only 1 platform. Just sayin ...

If I understand Cisco's rationale for creating these interfaces, they target additional functionality in security through DOT1X.

There are a number of comments/requests in Thwack about them:  (https://thwack.solarwinds.com/search.jspa?q=controlled%20uncontrolled )

For my environment, with 50 fully-populated 4510's, they represent 38,400 elements I don't want to monitor.  Ensuring there's an easy way to exclude them from discovery (including monitoring by UDT) is important.  I've tried various options in preventing these from being discovered; none seem to be reliable.

If you find a way to discover a 4510's ports, and NOT select Controlled and NOT select Uncontrolled interfaces, I'm up for learning your process.

I'm very interested in a way to automatically exclude these. We're adding a bunch of new 4510R+E switches, and at approximately 500 ports per switch, including these "managed" and "unmanaged" ones brings that number to 1500 elements each. Multiply by hundreds of new switches and that's a significant impact, not to mention a mess in the interface list.

Your best bets are to:

• Create this as a new Feature Request (I know, it's already out there as one.  But it gets people's attention, generates more votes)
• Contact your SE and request it.
• Open a Support Ticket with SW and ask for it.  When they say it's not possible yet, ask when it will be.  When they can't tell you when, ask for a work around.
• Post your results here so we all can see your experience, and learn what you learned.

I asked our network group here about them before deleting them.  They were not 'interesting' interfaces for them.  Things could change over time, and they may change their minds, but until they do, it was nice to get those out of the system.

I'll have to look into it more deeply now that we're deploying ISE across the enterprise.  It's possible those controlled/uncontrolled interfaces may be playing with ISE, and there could be interesting things to learn if they were monitored.

But I'm loathe to "waste" more element counts on the project if the ROI isn't useful.

About the 2nd week I started this current job, I went through SolarWinds and deleted all those types of interfaces.  Now I manually make sure they don't get imported when new devices are added.  This type of interface being disabled by default would be even better.

Any chance this will be fixed soon? (weeks,months, etc...)

I'm still wanting this . . . 

Major Unreasonably Ridiculous Bump!

German Speed Bump - YouTube

A good idea is worth a