On 22 June 2011 14:18, Giuseppe Modugno <[email protected]> wrote:
> Indeed I have other signals too: temperature, currents, RF powers and so on.
> Do you suggest to have a different table for each signal?
Yes.
> For example, I have only one temperature sensor: should I create a table
> with just one row?
Yes.
*At the moment* you just have one temperature sensor.
But think what happens when you bring out a new product
that include two temperature sensors.
If you're using scalar objects then you'll have to bring out a
new version of the MIB (and hope that everyone who's using
the old one will remember to upgrade).
If you're using a table, then everything will just continue working.
> At first, it seems to me the "fixed one-row table" approach is too
> complex compared with a single scalar/object approach.
It's a bit more work (for you) in the short term, but saves work
(for both you and your customers) in the long run.
In fact - rather than defining your own MIB tables, I'd
actually suggest that you look at using the existing
sensor tables.
Have a look at LM-SENSORS-MIB.txt
> I don't know the details about the SNMP table, but how the receiver can
> determine which voltage supply has broken?
The OID for an instance within a table includes the index value of that row.
For example "lmTempSensorsValue.27" contains the value being reported
by temperature sensor #27. So the varbinds within the notification will
indeed specify the relevant sensors.
Note that the LM sensor tables also includes column "lmTempSensorsDevice"
(or similar) which can provide a description of what each sensor represents.
Dave
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
