On Fri, 2005-02-18 at 14:16, Thomas Anders wrote:
> Dave Shield wrote:
> > That wouldn't affect "exec name" configurations
> > as all, but existing configurations based on the "exec MIBNUM"
> > form would break at that point.
>
> Would you mind elaborating on the differences to help those who need to
> migrate from this?
Basically, the MIB layout of the output resulting from an "extend"
directive is different to that resulting from an "exec" directive.
In particular, the "extend" output consists of three separate
tables - one containing the configuration settings, and two
containing the results of running the extension command.
These tables are indexed using string values, rather than the
arbitrary integer indexes (and bogus MIB structure) of "exec".
The "extend MIBNUM" form reproduces this triple-table format
rooted at the specified OID, so can support several different
extension directives that all specify the same OID.
The "exec MIBNUM" form will ignore everything but the first.
The easiest way to see the difference is to set up a config file
such as:
exec .1.2.3.4.5 test1 echo "Hello, World! \nGoodbye Dolly"
extend .1.2.3.4.6 test2 echo "Hello, World! \nGoodbye Dolly"
and run snmpwalk on the two OIDs.
Then add another couple of directives:
extend .1.2.3.4.6 emew echo "What do you think of it so far?"
extend .1.2.3.4.6 bf echo "Nice to see you, to see you...."
and see how this affects the second walk.
Dave
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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/listinfo/net-snmp-users
