On 08/09/06, Stuart Kendrick <[EMAIL PROTECTED]> wrote: > guru% snmpbulkwak -c public foo .iso > foo.walk > > i've found that snmpbulkwalk becomes unhappy when doing this against > some devices -- thus far, all Cisco switches
> -then, snmpbulkwalk reaches some portion of the MIB (close to the same > location from trial to trial, but not exactly in the same place) and > does not finish writing all the output from the current get-response to > the file Ummm... Sorry for not getting back to you sooner. All I can suggest is that you try running "snmpwalk" under a debugger. When it goes catatonic, use ^C to break in, and generate a backtrace. Maybe seeing where it is in the code might give some hint as to what is going wrong. Another possibility would be to use the option -D on snmpwalk, and capture the output. There'll probably be a *lot*, but the messages logged when it goes haywire might be informative too. Sorry not to be of any more immediate help. Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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
