exporting custom OIDs ?

[renaatski]

Hi,

I've been using cacti on my Fedora Core 3 with great success for a variety of platforms (netapp, cisco). Cacti is doing a great job in keeping track of the metrics I selected.

I now have applications on a Windows platform (Real Media Encoder, Windows Media) that have lots of statistics I'm interested in. Unfortunately, they are not available to the Windows SNMP agent .

Under linux I would just write a script that I'd "link" to a reserved OID and have the script do whatever it takes (parse logfiles, whatever..) to return the values...
I would just put something in /usr/local/share/snmp/snmpd.conf along the lines of:

exec .1.3.6.1.4.1.2021.50 /usr/bin/perl /usr/local/sbin/display-bindstats.pl

So whenever I'd call the .1.3.6.1.4.1.2021.50 OID from the Cacti box, the script gets executed on the called SNMP agent , and returns the requested information.

How does that translate to windows ? Can I use this mechanism to obtain "foreign" counters ?

Kind regards,

Renaat

[TheWitness]

Get the Windows Resource kit and look for the MIBCC tool from Microsoft. If there is a counter, you can create an OID for it. Of course, Microsux's would rather you use WMI. Good luck.

TheWitness

[renaatski]

Hi Larry,

can you elaborate a bit on that ? Or do you have some examples, links for doing this ?

My colleague have been trying to compile stuff using MIBCC, but have been unable to do so...

Kind regards,

Renaat

[Guest]

Right, maybe this question needs some elaborating.

There isn't exactly a counter for what we're trying to do, but ... If we could make a customer OID known to Windows, we could with a local program on the server SET (using snmpset) a value into that OID.

Cacti would then be able to retrieve that OID, along with the default SMI stuff, and whatnot...

Now, we've created a bogus MIB:

STREAMPOWER-MIB DEFINITIONS ::= BEGIN

IMPORTS
enterprises, Counter, IpAddress, TimeTicks, Gauge
FROM RFC1155-SMI
PhysAddress, DisplayString
FROM RFC1213-MIB
TRAP-TYPE
FROM RFC-1215
OBJECT-TYPE
FROM RFC-1212;


streampower OBJECT IDENTIFIER ::= { enterprises 789 }

-- the current Streampower mib

streampower1 OBJECT IDENTIFIER ::= { streampower 1 }

productType OBJECT-TYPE
SYNTAX INTEGER {
eisa-based(1),
pci-based(2)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The product type representing the target platform."
::= { streampower1 1 }


END

I know that enterprise 789 is Network Appliance , but it only serves as a demo here.

When I check this MIB using http://www.simpleweb.org/Docs/ietf/mibs/validate/ this validates just fine.

Next we compile the mib:

c:\test> mibcc -owhatever.bin theabovesnippet.mib
Microsoft (R) SNMP MIB Compiler Version 2.00
Copyright (c) Microsoft Corporation 1998. All rights reserved.
mibcc: parsing theabovesnippet.mib
mibcc: total files processed: 1
mibcc: writing compiled file 'whatever.bin'

c:\test>

Next we copy the new mib over the existing one from windows:

c:\>test> copy whatever.mib c:\windows\system32\mib.bin
Overwrite C:\WINDOWS\system32\mib.bin? (Yes/No/All): a

I then restart the "SNMP Service" service.

Unfortunately, an snmpget/set of .1.3.6.1.4.1.789.1.1 just fails (as does walking the the tree). SNMPwalk just gives me the standard SMI tree.

The OID just isn't there (not offered by "SNMP service"). I don't get it.


What am I doing wrong here ?


Renaat