It's the same code, but different issues. Khen suggested I turn on debugging for the no response issue, which appears to be host specific. For that, I'll put a sniffer on the wire as you suggest, but I'm not good at reading those. I think my current problem with why Net::SNMP doesn't do what I want is the following:

SolarWinds will do a MIB walk, starting on the branch OID that I specified and I'm assuming that's how it 'discovers' the other device specific OIDs. What I'm trying to do with Net::SNMP is essentially the same thing, but I now understand that the get_request and get_bulk_request methods are for known OIDs rather than a MIB walk. So it may turn out that Net::SNMP can't do a MIB walk? At this point I don't understand enough of the module to know for sure. I'll keep working on it and hopefully people will post back with other useful pointers for me.

Regards,
Scott

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.