[Check_mk (english)] Myriad of Windows interfaces

Hello,

It seems that the newer the Windows Server generation, the more network
interfaces are discovered by Check_MK. Examples:

Teredo Tunneling Pseudo-Interface
WAN Miniport IP
WAN Miniport IPv6
WAN Miniport Network Monitor
WAN Miniport IP-QoS Packet Scheduler-0000
isatap.{...}
QLogic BCM57810 10 Gigabit Ethernet [NDIS VBD Client]

The example above if a small subset from a Windows Server 2012R2 running
on Dell hardware. Check_MK finds more than 20 interfaces on the server
when inventoring. Many of the interfaces are completely unused; others
yield false alerts once in a while when their speeds seem to change for
no particular reason (and with no consequence at all).

In order to cut down on false alerts, for most Windows Servers, we have
set up a rule which asks Check_MK to disregard all but the first NIC. But
I'm hoping that there might be a better way to handle this. I'm basically
not interested in all sorts of virtual interfaces like a package
scheduler, a wan miniport or an isatap interface. At the same time, I'm
not fond of having to manually configure each and every Windows server in
Check_MK in order to get a relevant set of NICs monitored.

Any ideas? - Can Check_MK be configured to disregard anything but "real
interfaces" + link aggregations?

···

--
Troels

Hi Troels,

If this interfaces discovered on your system you use an older agent or the wrong plugins to check interfaces.
With actual agent you get only isatap and teredo pseudo interfaces and they can easily ignored with some rules.

Best regards
Andreas

···

Troels Arvin troels@arvin.dk schrieb am So., 10. Apr. 2016 um 14:52:

Hello,

It seems that the newer the Windows Server generation, the more network

interfaces are discovered by Check_MK. Examples:

Teredo Tunneling Pseudo-Interface

WAN Miniport IP

WAN Miniport IPv6

WAN Miniport Network Monitor

WAN Miniport IP-QoS Packet Scheduler-0000

isatap.{…}

QLogic BCM57810 10 Gigabit Ethernet [NDIS VBD Client]

The example above if a small subset from a Windows Server 2012R2 running

on Dell hardware. Check_MK finds more than 20 interfaces on the server

when inventoring. Many of the interfaces are completely unused; others

yield false alerts once in a while when their speeds seem to change for

no particular reason (and with no consequence at all).

In order to cut down on false alerts, for most Windows Servers, we have

set up a rule which asks Check_MK to disregard all but the first NIC. But

I’m hoping that there might be a better way to handle this. I’m basically

not interested in all sorts of virtual interfaces like a package

scheduler, a wan miniport or an isatap interface. At the same time, I’m

not fond of having to manually configure each and every Windows server in

Check_MK in order to get a relevant set of NICs monitored.

Any ideas? - Can Check_MK be configured to disregard anything but "real

interfaces" + link aggregations?

Troels


checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en