| Having thought about this, I think MIB extenstions are in fact the
answer. Now the next question is this: if an MCC director talks to an
SNMP managed object and gathers standard MIB and extension MIB data,
can the director display all of this data as if it were standard MIB.
Namely, do the SNMP access modules support additions to standard MIB's?
Thanks
Jahan
|
| > Having thought about this, I think MIB extenstions are in fact the
> answer. Now the next question is this: if an MCC director talks to an
> SNMP managed object and gathers standard MIB and extension MIB data,
> can the director display all of this data as if it were standard MIB.
> Namely, do the SNMP access modules support additions to standard MIB's?
MIB extensions must be describeed a priori to the DECmcc director
(accomplisehd via the MIB Translator utility). This allows the DECmcc
system to appropriately encode/decode the SNMP PDUs using the services
of the SNMP AM. In that respect, the SNMP AM is generic and there is
only 1 SNMP AM on the DECmcc system for many SNMP entities and their
private extensions.
This means that the problem is not with the DECmcc SNMP AM. Rather the
issues are:
1) that the Agent on the managed object is able to encode/decode
the 'special' extensions
2) that the Agent developers provide an RFC1212-compliant
MIB definition of their extensions for teh DECmcc MIB
Translator.
|