On 10/04/2008, McCann, Brian wrote:
> extend .1.3.6.1.4.1.22124.1.1.1 PartitionUse-/
> /usr/local/bin/partuse.sh /


> SNMPv2-SMI::enterprises.22124.1.1.1.4.1.2.14.80.97.114.11 6.105.116.105.1
> 11.110.85.115.101.45.47.3 = STRING: "2025948"


Which is effectively

enterprises.22124.1.1.1.nsExtendOutput2Table(4).
nsExtendOutput2Entry(1).nsExtendOutLine(2).
"PartitionUser-/".3

i.e. line 3 of the output for the extend directive "PartitionUser-/"


One of the differences between "extend" and "exec" is that
the extend token uses the NAME field to index the table
(rather than the order in which the snmpd.conf file entries
were read in).
So adding a new "extend" directive to snmpd.conf won't
affect the OIDs of any other entry. Adding an "exec" line
would shift everything read later up one.


As Thomas has said, see NET-SNMP-EXTEND-MIB for
the structure of this MIB. If you take a copy of this file
and change the root (nsExtendObjects) to point to your
specified OID, then snmpwalk should use meaningful
names, and interpret the indexes properly.
(But don't forget to change the module name too!)

Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757...un.com/javaone
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/...net-snmp-users