On 23/05/07, Steve Friedl <[EMAIL PROTECTED]> wrote: > Let's start by walking the leading part: > > $ snmpbulkwalk localhost bgp4PathAttrASPathSegment.64.160 > ?? where is 64.160.0.0 ? > bgp4PathAttrASPathSegment. 64.160.71.0 .24. 10.1.1.4 = (data)
First thing - I'd suggest you test this using "snmpgetnext" rather that "snmpwalk". Secondly - yes this looks like a bug. The next step is to locate exactly where this problem arises. Try restarting the master agent using the '-d' flag, and running the same snmpgetnext command. What do the packet dumps look like? Dave ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
