[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
On 25 November 2011 13:45, Nathan Harris
<[email protected]> wrote:
> I know its very odd, networks have checked there is no ACL in place (you can
> ping the device for instance)
That doesn't necessarily follow.
It's perfectly possible to have filter rules that apply to a particular source
or destination port, and will only allow specific hosts to manage the box.
But that's something that would need to be explicitly configured,
in which case, someone should know about it!
> I am beginning to think its the microprocessor on the meter, I awaiting more
> data from the manufacturer, I am not sure if it has a snmp.conf, it may be
> ASM, I don't expect it has a OS as such
No - 'snmp.conf' controls the configuration of the *client* side, not the agent.
("snmpget" in this case).
Please try the command
snmpget --16bitIDs=yes -v1 -c public 10.3.9.11 1.3.6.1.4.1.29711.7709
Dave
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
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
