I would honestly say that this is less a weakness with the PRTG product and more with the fragmented structure of SNMP. This is the same problem we encountered years ago when looking for a product.
Ultimately I switched from trying and only occasionally being able to successfully parse malformed MIB files or alternately being able to load the MIB correctly but then having to search through thousands of items for what I was looking for. Instead, I either search out the specific MIB variable that I'm looking for using one of a variety of sites that actually correlate the OID to the textual MIB equivalent. This allows you to select only the elements you want using the specific OID instead of auto-discovering 1000 sensors for a single device and deleting all but the couple you are looking for.
I have already built out Extreme templates for our organization using this method so I'll provide the OID values I'm using for CPU and Memory below. For your future efforts using whichever SNMP monitoring tool you end up with, however, the following sites (each links to the Extreme MIB you're looking to incorporate) are great to use:
-MIB Depot - http://www.mibdepot.com/cgi-bin/getmib3.cgi?win=mib_a&r=extreme&f=ExtremeXOS_12.0.2.25_MIB-23&v=v2&t=tree
-SNMPLink - http://www.snmplink.org/OnLineMIB/Extreme/ (See EXTREME-SOFTWARE-MONITOR.mib)
-OIDView - http://www.oidview.com/mibs/1916/EXTREME-SYSTEM-MIB.html (This is not the same MIB as the 2 above...unfortunately not all sites will have the MIB but OIDView is typically the best, followed by MIB Depot)
My typical discovery process is as follows:
1. Run an SNMPwalk of the device in question using no MIBs to obtain all responsive OID values with no MIB textual correlation.
2. Run another SNMPwalk of the device using the MIBs (if available - see the SNMPwalk documentation for how to include MIB files) to have a comparative list with the textual equivalents. Place both the OID list and the MIB list next to one another in Excel or using another method so that you have a line-by-line direct correlation between the OID value and the readable text MIB version and then simply search for CPU, Mem, Temp, or whatever other variables you're looking to monitor.
3. If you cannot find a MIB to use, search Google for "Extreme x450 CPU OID" or whatever else you're looking for and many times that value has already been found. Even if you are not looking for CPU or memory, those are the most common and can sometimes lead you to the correct OID tree to search for. If, for example, someone identifies Extreme CPU as 1.3.6.1.4.1.1916.1.32.1.4.1.7.1, simply paste this value into Google, remove the .1 on the end as this is a specific instance ID (if you had multiple devices the second would be .2, third .3 and so on), and search. Many times you will come up with a link to one of the above sites that will take you into the actual OID tree and you can see all of the OID values there and find the appropriate one. Remember, though, that you always need an instance ID. Take the OID value from the tree you've found and find that value in the SNMPwalk of the device to discover which instance IDs are responding.
4. If you cannot find the OIDs you are looking for but you can obtain the MIB file for the device, you can always extrapolate the OID value from the MIB file. Open the MIB file and near the top will be your first OID textual equivalent looking something like the below:
extremenetworks MODULE-IDENTITY
LAST-UPDATED "0211230000Z"
ORGANIZATION "Extreme Networks, Inc."
CONTACT-INFO "www.extremenetworks.com"
DESCRIPTION "Extreme Wireless Access Tables"
::= { enterprises 1916 }
extremeV1Traps OBJECT IDENTIFIER ::= { extremenetworks 0 }
extremeAgent OBJECT IDENTIFIER ::= { extremenetworks 1 }
extremeProduct OBJECT IDENTIFIER ::= { extremenetworks 2 }
extremeMisc OBJECT IDENTIFIER ::= { extremenetworks 3 }
extremeV2Traps OBJECT IDENTIFIER ::= { extremenetworks 4 }
Both the extremenetworks MODULE-IDENTITY
Add comment