On 9 July 2012 06:41, Harvey Shepherd <[email protected]> wrote:
> I’m trying to design a MIB that contains two tables as follows:
[snip]
> Is it valid to define a table that is indexed by an external table’s object
> that is not itself an index (hwAlarmDescPrivileged)?
>
> Any advice greatly appreciated.
I'm not sure offhand whether it's valid or not.
But my immediate reaction would be to structure the indexing
of the two tables in the same way.
i.e.
hwAlarmDescTable
(indexed by hwAlarmDescPrivileged, hwAlarmDescIndex)
hwAlarmStatusTable
(indexed by entPhysicalIndex, hwAlarmDescPrivileged, hwAlarmDescIndex)
or by hwAlarmDescPrivileged, hwAlarmDescIndex, entPhysicalIndex)
Whether you define the second table using (hardware/alarm) or (alarm/hardware)
will depend in part on how it's expected to be used.
The second might well be easier from an implementation point of view - but if
you're mostly going to be looking at all the alarms for a given piece
of kit (rather
than all the boxes exhibiting a particular characteristic), then the
first approach
might make more sense.
But it you want to use hwAlarmDescPrivileged as an index in the Status table,
then I'd make it one in the Desc table as well.
Dave
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
