I thought they fixed this in NMC 6.x...? In 5.x and earlier it would actually kill the whole IP stack on the card and you had to reboot the NMC. I thought I tested 6.1.7 and it didn't kill the card anymore. (They finally fixed all those off-by-one Radius accounting bugs too.) Anyway, the reason I have that ma_snmp.pm wrapper around all my SNMP code is because there's a workaround for that bug in there, among other things... It takes the array of OIDs you're going to query and breaks them up into chunks small enough to make the card happy, then reassembles the responses. Mike Andrews (MA12) * mandrews@dcr.net * http://www.bit0.com/ VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY Internet services for Frankfort, Lawrenceburg, Owenton, & Shelbyville "With sufficient thrust, pigs fly just fine." -- RFC 1925 On Mon, 11 Oct 1999, Jeff Mcadams wrote:
What's the plan on fixing the NMC's so they'll handle SNMP PDU's larger than 1500 bytes (or whatever it is around that number that is the actual limitation)? Now that I'm starting to write some SNMP scripting...I'm *quickly* running into this limitation, and its gonna really suck to have to code around it.
Can the NMC's IP stack not reassemble or something? Isn't that terribly broken?
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.