>> one for indexing itself, another one for referencing >> the row number in the DHCP settings table. > > Note that these should occur in the opposite order. > First the row number in the DHCP settings table, > and *then* the distinguishing index for the IP Range > table itself. >
Thanks for the correction. I should have read your answer carefully :-) "...the core of this MIB is that the second (ipRange) table should be indexed by *two* values - the *FIRST* of these is what gives you the mapping into the dhcp pools" Since I still have the problem in my last post unsolved, I don't really understand why the order of indexes matters. /Pan ------------------------------------------------------------------------- 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
