Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Are you monitoring EVERY interface discovered on Windows 2008 (R2) systems?

Are there benefits to monitoring all discovered interfaces in these sytems nowadays?

I mean really - this is getting crazy - a server with over 20 interfaces??????

Oh, I realize I don't have to Import every interface but what's going on here??? Again - what is the benefit? Is it IPv6? Or Tunnelling?

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

There's no benefit to monitoring all these interfaces. It's most likely you're not using Tunnel adapters anyway so there's no point in monitoring them. I'd recommend only monitoring the physical interfaces that are actually in use. You can also ignore the loopback adapters since there's not point in monitoring these interfaces either.

byrona

There's no benefit to monitoring all these interfaces. It's most likely you're not using Tunnel adapters anyway so there's no point in monitoring them. I'd recommend only monitoring the physical interfaces that are actually in use. You can also ignore the loopback adapters since there's not point in monitoring these interfaces either.

Agreed, we only monitor the physical interfaces as well.

kb1lxm

We monitor only three out of the million interfaces:

1.) The physical nics themselves
2.) The BASP Virtual Adapter formed by the network teaming
3.) If it's a Failover Cluster the Microsoft Cluster Failover Adapter

So this is what I do on our cluster nodes:

It would be nice if Solarwinds could distinguish between actual interfaces and virtual interfaces and make it so during a discovery you could choose to ignore the virtual interfaces. I understand it's just reporting back all the network interfaces returned by an SNMP query, so I dunno how hard that would be to do.

waxxworx

We are having this same problem. How do you handle this with Network Discovery? It's one thing to be able to pick and choose if you're manually adding nodes but we are using Network Discovery to add each week, anyone know how you might automate this?

alteon180e

ditto,

on discoveries we can pick up only active interfaces, and kill all categories except for ethernet (including loopback). im still stuck with a bunch of useless interfaces. any way of clearing these out besides clicking on hundreds of nodes one at a time? i know its a windows 2k8 change that caused this. just wondering as well.

sperera

Hi All,

I'm also having the same problem. Does anyone have a work around for this?

Many thanks