From: Ken C. <kco...@ry...> - 2015-11-11 20:28:52
|
If you can get a value back via snmpwalk, then I'd say go the "baby steps" route and start with just one. I've seen where some oids which are not valid mess up everything else in the mix....kinda like a domino effect. On Nov 11, 2015 3:24 PM, "Steve B" <rec...@gm...> wrote: > I have also seen quite a few that don't work or wrongly programmed as > branch when should be leaf. > > Snmpwalk does work and gives a value, just not with a zero on the end. > > On Wed, Nov 11, 2015 at 7:06 PM, Ken Connell <kco...@ry...> wrote: > > > If you can't get a value back manually via snmpwalk, then your SOL. > > > > I find many times there are branches & leaf oid objects listed which > never > > work for that host or code level. > > On Nov 11, 2015 1:00 PM, "Steve B" <rec...@gm...> wrote: > > > > > Had tried it with a zero at the end already: By the way, if I snmpwalk > > with > > > a zero I get: > > > SNMPv2-SMI::experimental.94.1.6.1.3.0 = No Such Instance currently > exists > > > at this OID > > > so no dice on that alas. > > > > > > On Wed, Nov 11, 2015 at 6:06 PM, Ken Connell <kco...@ry...> > > wrote: > > > > > > > Are you sure the leaf objects don't end with a .0 ? > > > > > > > > >From the top of my head I'm pretty sure they do.....so tac it on and > > > try. > > > > On Nov 11, 2015 11:40 AM, "Steve B" <rec...@gm...> wrote: > > > > > > > > > Hi All, > > > > > > > > > > I am making a template for an HP P2000 G3 and I have a nice table > > > showing > > > > > all the status for the sensors. They look like this: > > > > > > > > > > SensorHex : .1.3.6.1.3.94.1.8.1.1 : branch > > > > > SensorIdx : .1.3.6.1.3.94.1.8.1.2 : branch > > > > > SensorName : .1.3.6.1.3.94.1.8.1.3 : branch > > > > > SensorStatus : .1.3.6.1.3.94.1.8.1.4 : branch > > > > > SensorValue : .1.3.6.1.3.94.1.8.1.6 : branch > > > > > SensorType : .1.3.6.1.3.94.1.8.1.7 : branch > > > > > SensorMetric : .1.3.6.1.3.94.1.8.1.8 : branch > > > > > > > > > > I am using the FCMGMT-MIB for this. > > > > > > > > > > Now say I want to make a new check, connectivity and start looking > > at: > > > > > > > > > > connUnitType : .1.3.6.1.3.94.1.6.1.3 : > leaf > > > > > connUnitNumports : .1.3.6.1.3.94.1.6.1.4 : > leaf > > > > > connUnitState : .1.3.6.1.3.94.1.6.1.5 : > leaf > > > > > connUnitStatus : .1.3.6.1.3.94.1.6.1.6 : > leaf > > > > > connUnitProduct : .1.3.6.1.3.94.1.6.1.7 : > leaf > > > > > > > > > > after putting these into the message file, I have 'unknown' for all > > the > > > > > oids on my html page and in the devmon log file I have No SNMP data > > > found > > > > > for connUnitType etc When I look at the mib info here: > > > > > > > > > > http://www.circitor.fr/Mibs/Html/FCMGMT-MIB.php > > > > > or > > > > > http://www.oidview.com/mibs/0/FCMGMT-MIB.html > > > > > > > > > > it looks as if this is branch info even if it's only on one line. > So > > I > > > > > tried using branch instead of leaf and made a table entry in > message > > > and > > > > > then I had worldwide purple for devmon and had to restart it. Too > > many > > > > > forks or similar..iirc > > > > > > > > > > Now I know this is a tough question but does anyone know why this > is > > > > > happening? I should still be able to use this as a leaf (the > snmpwalk > > > > gives > > > > > the value I am expecting to see) but it just won't digest my > > > > information. I > > > > > am spefically interested in the 'No SNMP data found' and the > unknown > > > > when a > > > > > manual snmpwalk -v2c -c blabla is fine > > > > > > > > > > cheers > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > > _______________________________________________ > > > > > Devmon-support mailing list > > > > > Dev...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/devmon-support > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > > > Devmon-support mailing list > > > > Dev...@li... > > > > https://lists.sourceforge.net/lists/listinfo/devmon-support > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > > > Devmon-support mailing list > > > Dev...@li... > > > https://lists.sourceforge.net/lists/listinfo/devmon-support > > > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Devmon-support mailing list > > Dev...@li... > > https://lists.sourceforge.net/lists/listinfo/devmon-support > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Devmon-support mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devmon-support > |