Hello All,
I'm working for implementing a new feature for our system engineering
about duplicate object name (not OID). I have searched the
net-snmp-users mailing list archive and got little bit information about
the duplicate object name about SNMP but I need more about it.
>From RFC I can see that duplicate object name can be occurred in
different information module but can not be occurred in the same
information module. I was trying to define a duplicate object name in my
MIB files to make it work with net-snmp, but, it seems the mib2c doesn't
support duplicate object name. It's caused by the mib2c call the
$SNMP::MIB() (Perl) to retrieve object node corresponding information,
for example, subid, parent, oidlength, etc. Because mib2c uses the leaf
object name to retrieve the node and it always returns the same one for
the duplicate object name scattering in different module.
It seems we need to modify the mib2c. Can someone give me more
information/suggestion about it? For example, sharing you experience
about my feature; giving a simple solution you can find.
Furthermore, whether net-snmp MIB tree corresponding source code
entirely supports duplicate object name in different information module?
For example, the IMPORT key word can be used to import correct object. I
took notice Perl SNMP shares the same implementation with net-snmp C
source code to populate the MIB tree from MIB files.
Thank you for your any help.
Best regards,
Yun.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
