> here is a snippet from the ethereal
> trace, taken running my script as designed:
>
> Source Destination Protocol Info
> 140.107.74.123 140.107.50.5 SNMP GET ccitt.1
> 140.107.50.5 140.107.74.123 SNMP RESPONSE ccitt.1
> 140.107.74.123 140.107.50.5 SNMP GET ccitt.2
> 140.107.50.5 140.107.74.123 SNMP RESPONSE ccitt.2
>
> this of course is the same behavior i saw under 5.1.2pre2.
>
> and here is a snippet taken when running my script as modified in the way
> you suggested, i.e. asking for ".1.3.6.1.4.1.9.5.1.4.1.1.6.1.99" instead
> of "portOperStatus.1" and "portOperStatus.2".
>
> Source Destination Protocol Info
> 140.107.74.123 140.107.50.5 SNMP GET iso.3.6.1.4.1.9.5.1.4.1.1.6.1.99
<etc>
Hmmm....
Ok - can you please try asking for
".1.3.6.1.4.1.9.5.1.4.1.1.6.1"
(i.e. the numeric version of portOperStatus.1)
and "portOperStatus.99"
If you see a successful request for the first, followed by a request for
"ccitt.99" (or a failure to build the request at all) then that would
definitely point the finger at the MIB OID translation.
Otherwise we'll have to look elsewhere....
Dave
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
