miliheaven.blogg.se

Intermapper crack
Intermapper crack





intermapper crack intermapper crack

I happened to be looking through the options for snmpwalk, and notice the “-O n” option, which prints out the OID numerically. So this morning I come into work figuring I would give it a fresh go. So I figure I just completely messed up writing the probe. But none of them work, InterMapper claims none of those OIDs are available in the switch. I get a value and everything! So I write the custom SNMP probe for InterMapper with the 3 OIDs I want to watch. This might be an issue with our version of intermapper, because if I use snmpwalk like this: But of course the only one of those that is actually in our version of the 6509 is cpmCPUTotal5sec.Īnyway, It sure would be nice if the OID was listed in that mib file. If you go to the cpmCPUTotal5secRev section, it says it was deprecated by cpmCPUTotalMonInterval, which when you go to that section. As you can see in the mib excerpt, cpmCPUTotal5sec was deprecated by cpmCPUTotal5secRev. Part of the fine is the deprecation chain. This object is deprecatedīy cpmCPUTotal5secRev which has the changed range of This object obsoletes the busyPer object from "The overall CPU busy percentage in the last 5 second For the 5 second CPU Load according to the MIB file this is what I need: Look at the number of mibs available just for the 6500 series:Īll I am looking for is the CPU load and the amount of memory available. Granted I am not nearly as familiar with SNMP stuff as I would like to be, but come on. Sure, cisco has a nice repository of all the MIBs for all their equipment, but they are all uncompiled and missing the actual OIDs. so I spent hours yesterday trying to get it to work. I was trying to get the SNMP probe it has for cisco equipment to work with our Cisco 6509 switch, but apparantly cisco decided that it would be fun to use completely differant OIDs for that line of switches. At my work we use InterMapper to monitor all our equipment.







Intermapper crack