On Mon, 2005-04-11 at 13:22, Frithiof Jensen (AH/LMD) wrote: > Apparently, > the Tools (snmpget et. al.) does not "know" of any inetCidrRouteTable:
Quite likely. That table is only defined in the updated version of the IP-FORWARD-MIB, which hasn't been released as a full RFC yet. It's still very much "work in progress", so you'd probably need to install this file manually. > However *something* is known to the Agent because the OID "works": Yup. Remember that the agent typically doesn't use MIB files. It relies on hardcoded implementations, to return the appropriate information. The MIB file will have been used as part of the *design* of this code, but once the code is written, the MIB becomes irrelevant. That's as far as the agent is concerned - client-side tools will often still need the MIB in order to translate numeric OIDs into something more sensible. > > [EMAIL PROTECTED]: snmpwalk udp6:ip6-localhost .1.3.6.1.2.1.4.24 > IP-MIB::ip.24.7.1.7.2.16.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.7.2.16.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 > > = INTEGER: 3 > IP-MIB::ip.24.7.1.7.2.16.32.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.1.3.2.16.63.254.1.0.0.3.4.1.2.96.103.255.254.119.3.226 > > = INTEGER: 3 > IP-MIB::ip.24.7.1.7.2.16.63.254.1.0.0.3.4.1.0.0.0.0.0.0.0.0.64.1.2.2.16.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 > > = INTEGER: 3 > IP-MIB::ip.24.7.1.7.2.16.63.254.1.0.0.3.4.1.2.17.133.255.254.127.130.179.128.1.1.2.16.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 > > = INTEGER: 1 > IP-MIB::ip.24.7.1.7.2.16.254.128.0.0.0.0.0.0.0.0.0.0.0.0.0.0.64.1.5.2.16.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 > > = INTEGER: 3 > > .... > > Snipped many, many similar lines on the assumption that it is Garbage. No - it's not garbage. It simply hasn't been displayed in a "readable" form. But the values it's returning will be correct. All of the entries above are examples of inetCidrRouteIfIndex (ip.24.7.1.7) - so are reporting that this routing entry uses interface #3. The rest of each OID is the indexing for that entry: DestType: 2 Dest: (len 16) 0.0.0....0, (len 16) 32.0.0....0, etc PfxLen: 0, 3, etc Policy: (len 1) 7, (len 1) 3, etc NextHopType: 2 NextHop: (len 16) 0.0.0....0, (len 16) 64.254.1.0....3.226, etc > I do not like that the tools do not know of the "inetCidrRouteTable" The tools simply translate numeric OIDs (and values) back into a more meaningful representation. They can only do this if the necessary MIB files are available and loaded. Try going a Google search for inetCidrRouteTable, extract the MIB file from the Internet Draft that this should throw up, and install this file into your system. You should then see a more sensible representation of the output. But all that changes is the way this output is displayed. The actual values are correct already. > - I think the root cause is that the build is broken somehow?? No - it's just that you're working with the cutting edge of SNMP routing management, and you need to install the relevant MIBs yourself. There's nothing wrong with the build. 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-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
