Filtering SNMP Results in Data Query

[lints]

Hey,

I've recently installed some Windows Server 2008 R2 Core servers and I'd like to add them to Cacti to graph.

I can get everything to work just fine, except the Interface graphs. The Data Query returns data, but it's actually the amount of data it returns that's the problem. It seems that W2K8 R2 Core thinks it has 1024 tunnel adapters, so I've got to scroll through 22 pages of choices to find the interfaces that actually exist in the graph creation page.

I've been looking at the 'interfaces.xml' file (as well as the documentation here about it's format) and began to think I could use a VALUE/REGEXP on a given field to filter out the indices I don't want.

The problem is, I can't seem to get it work properly. I don't even know if this is how I should be doing it because I figure if it starts to fetch the item, it's already got the row and it's probably a moot point.

I'm beginning to think that the 'oid_index_parse' field is more what I'm looking for, but I find the documentation a little vague.

Basically what I'm trying to do is filter out the rows that have a particular IfType or ifOperStatus.

If screen shots or snmpwalk listings are needed let me know.

[BSOD2600]

same basic question was asked a few weeks ago here with no direct solution...

OT: Why in the heck are there so many adapters on the server anyways?

[lints]

Yeah... I don't know if that's going to really help me.

Would the 'oid_index_parse' field do what I want, or does this functionality just not exist in Cacti?

OT: I have NO idea why it *thinks* it has that many adapters. It's a VMware machine and I know it only has 1 NIC. I've got 40 other Windows 2008 R2 machines (non-core) that are fine. It's just the Core boxes. I mean, I know the Windows SNMP agent is pretty terrible, but this is ridiculous.

[BSOD2600]

'oid_index_parse' is used to split off a part of an OID, so it's not really what you're after.

Does ipconfig /all list all 1024 adapters? Appears you're not alone with this problem, microsoft forum link. If not using IPv6, disable/remove that stuff.

IMO, solve the underlying Microsoft tunnel problem and Cacti will work as expected.

[lints]

Well, I tried everything they said to try and I hasn't helped me any..

I don't know if it's an IPv6 issue or what because I don't see any of these tunnel adapters in the 'ipconfig /all' listing. They only show up while querying SNMP.

Maybe I should call MS and see if they can point me in the right direction.

Is nobody out there running Windows Server 2008 R2 Standard CORE?

[BSOD2600]

yea, guess I'd try microsoft support or continue Googling the issue. 'cause either way 1000+ adapters isn't normal.


I've got a fresh 2008 R2 x64 server with only the following adapters:

Code: Select all

IF-MIB::ifDescr.1 = STRING: Software Loopback Interface 1
IF-MIB::ifDescr.2 = STRING: WAN Miniport (SSTP)
IF-MIB::ifDescr.3 = STRING: WAN Miniport (IKEv2)
IF-MIB::ifDescr.4 = STRING: WAN Miniport (L2TP)
IF-MIB::ifDescr.5 = STRING: WAN Miniport (PPTP)
IF-MIB::ifDescr.6 = STRING: WAN Miniport (PPPOE)
IF-MIB::ifDescr.7 = STRING: WAN Miniport (IPv6)
IF-MIB::ifDescr.8 = STRING: WAN Miniport (Network Monitor)
IF-MIB::ifDescr.9 = STRING: WAN Miniport (IP)
IF-MIB::ifDescr.10 = STRING: RAS Async Adapter
IF-MIB::ifDescr.11 = STRING: Microsoft Teredo Tunneling Adapter
IF-MIB::ifDescr.12 = STRING: Microsoft 6to4 Adapter
IF-MIB::ifDescr.13 = STRING: Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)
IF-MIB::ifDescr.14 = STRING: Microsoft ISATAP Adapter
IF-MIB::ifDescr.15 = STRING: WAN Miniport (IPv6)-QoS Packet Scheduler-0000
IF-MIB::ifDescr.16 = STRING: WAN Miniport (IP)-QoS Packet Scheduler-0000
IF-MIB::ifDescr.17 = STRING: WAN Miniport (Network Monitor)-QoS Packet Scheduler-0000
IF-MIB::ifDescr.18 = STRING: Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)-QoS Packet Scheduler-0000
IF-MIB::ifDescr.19 = STRING: Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)-WFP LightWeight Filter-0000