paul> I tried the following command:
paul> snmpgetnext -v1 -c community localhost -r 0 -t 60
paul> IP-MIB::ipAdEntAddr.127.0.0.1
paul> Timeout: No Response from localhost.
But presumably it does work if you issue an 'snmpget' on
IP-MIB::ipAdEntAddr.127.0.0.1 ?
If not, then Wes' suggestion of access control is the most
likely. But I got the impression that you *could* see
things up to (and including) ipAdEntAddr.127.0.0.1
Which would tend to point the finger elsewhere.
What else can you see?
Try an snmpgetnext on each of the mib-2 groups:
snmpgetnext .... system
snmpgetnext .... interfaces
snmpgetnext .... ip
snmpgetnext .... icmp
snmpgetnext .... tcp
snmpgetnext .... udp
snmpgetnext .... snmp
(and I'd probably suggest restarting the agent between each one,
just to be on the safe side).
paul> Is this a known issue on 5.1.2?
It's a bit difficult to answer that until we know what the
problem actually is.
Have you tried with a more recent version of the agent yet?
Dave
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
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
