Re: [opennms-discuss] issue with textual convention ( i guess?)

[Rob W. <rw...@si...>]

Austin,

Would the following work?

Choose a server to do the raritan pdu2 collection from, so ONMS queries
your linux host (presuming you have lots of those just laying around,
doing other work) instead of your raritan.

Write a little script to walk the
SNMPv2-SMI::enterprises.13742.6.5.4.3.1.4.1.X.X area, and recreate it
with a proper index for ONMS to walk.  Or just dump it to discrete
values, then you can tell ONMS to get those exact values.  Populate it
in a private area of the enterprise MIB, maybe you would call it
private-raritan.

Now ONMS will find that PDU on a host, and I know that is a tad odd, but
you can do pretty much anything you want with the right perl and shell
fun.  Google search for

iostat.pl snmp parser

for a pretty cool script to parse a text file and hand things back via
snmpd.  My snmpd.local.conf has the following line in it:

pass .1.3.6.1.3.1 /usr/bin/perl /usr/local/bin/iostat.pl

You could also do this with one machine to collect from all of your
raritans, and then have ONMS get all of the data from that one server,
or you could use one server to query the two PDUs that serve the rack
that it was in, so this keeps a correlation between the physical
location of the data source and the physical location of the host
handing back the data.

I hope this helps.

Rob

On 10/31/11 5:43 AM, Austin Papp wrote:
> anyone ?
> 
> 
> 
> On Wed, Oct 26, 2011 at 10:38 AM, Austin Papp <ign...@gm...<mailto:ign...@gm...>> wrote:
> First, pardon my lack of knowledge here as I have only learned snmp by just doing it and learning as i go :) I'll do my best to explain the situation.
> 
> Anyway, I have a device (raritan pdu2) that I can't seem to properly collect data for in opennms. when staging data collection in datacollection-config.xml, anything that has multiple instances of the same object with the same properties, I simply reference the table index.
> 
> as we know, the below would collect outletActivePower for all instances that are referenced in outletIndex for raritan pdu.
> <mibObj oid=".1.3.6.1.4.1.13742.4.1.2.2.1.7" instance="outletIndex" alias="outletActivePower"     type="gauge" />
> and we know that active power for outlet 11 would be
> .1.3.6.1.4.1.13742.4.1.2.2.1.7.11
> 
> however, my issue is with the raritan pdu2.
> 
> to get measurements from the pdu2, i have to reference the unitSensorMeasurementsEntry
> .1.3.6.1.4.1.13742.6.5.1.3.1
> 
> The only values available to this table are
> .1.3.6.1.4.1.13742.6.5.1.3.1.2 = measurementsUnitSensorIsAvailable
> .1.3.6.1.4.1.13742.6.5.1.3.1.3 = measurementsUnitSensorState
> .1.3.6.1.4.1.13742.6.5.1.3.1.4 = measurementsUnitSensorValue
> .1.3.6.1.4.1.13742.6.5.1.3.1.5 = measurementsUnitSensorTimestamp
> 
> And that is really it in the mib. I have to walk .1.3.6.1.4.1.13742.6.5.1.3.1.4 to get the next outlet and values.
> 
> So if I want to reference Active Power for outlet 15, it would look like:
> SNMPv2-SMI::enterprises.13742.6.5.4.3.1.4.1.15.1 = Gauge32: 24
> SNMPv2-SMI::enterprises.13742.6.5.4.3.1.4.1.15.4 = Gauge32: 205
> SNMPv2-SMI::enterprises.13742.6.5.4.3.1.4.1.15.5 = Gauge32: 465 (textual conventions here for active power)
> SNMPv2-SMI::enterprises.13742.6.5.4.3.1.4.1.15.6 = Gauge32: 490
> SNMPv2-SMI::enterprises.13742.6.5.4.3.1.4.1.15.7 = Gauge32: 95
> SNMPv2-SMI::enterprises.13742.6.5.4.3.1.4.1.15.8 = Gauge32: 109194
> 
> translated, it looks like
> PDU-MIB::measurementsOutletSensorValue.1.15.activePower
> 
> so really the issue is SNMPv2-SMI::enterprises.13742.6.5.4.3.1.4.1.X.X
> 
> How do I deal with this type of sensor type enumeration ?
> 
> man i hope this makes SOME kind of sense to someone :)
> 
> thanks in advance
> - Austin
> 
>