Figured it out.
I had started restricting access to snmp on newer MT installs to our
management subnet (10.13.0.0/16). As it happens, they are all on
various versions of 5.xx.
The linux server having the problem is multi homed. It was going out
its public IP with snmp. So I just needed to add a static route for
access to the 10.13.0.0/16 network. Once I did that it's working normally.
bp
On 12/25/2012 10:08 AM, Josh Luthman wrote:
SNMP config?
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St Suite 1337
Troy, OH 45373
On Dec 25, 2012 12:46 PM, "Bill Prince" <[email protected]>
wrote:
I've only tested this on 5.20 and 5.22 so far, but from "some" hosts, I
get a non-response from ROS devices running (at least) these versions of
ROS.
It doesn't affect all hosts, but on the hosts it does affect, I
essentially get a timeout to SNMP queries.
Example attempting to do a walk on a 5.22 ROS device:
snmpwalk -Lo -v 1 -c <community> 10.13.100.24 system
Timeout: No Response from 10.13.100.24
Example attempting to do a walk on a 4.17 device:
snmpwalk -Lo -v 1 -c <community> 10.13.100.18 system
SNMPv2-MIB::sysDescr.0 = STRING: router
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.14988.**1
DISMAN-EVENT-MIB::**sysUpTimeInstance = Timeticks: (2037440000) 235
days, 19:33:20.00
SNMPv2-MIB::sysContact.0 = STRING: <contact>
SNMPv2-MIB::sysName.0 = STRING: <name>
SNMPv2-MIB::sysLocation.0 = STRING: <loc>
SNMPv2-MIB::sysServices.0 = INTEGER: 78
Curiously, when I attempt the same thing on the same two devices from a
different linux host, both queries work. Routing to both hosts is the same
(and checks out).
I've got an open topic on the mikrotik forum: http://forum.mikrotik.com/**
viewtopic.php?f=2&t=68437<http://forum.mikrotik.com/viewtopic.php?f=2&t=68437>
No responses; I suspect everyone is on holiday.
--
bp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.butchevans.com/**pipermail/mikrotik/**
attachments/20121225/c8181395/**attachment.html<http://www.butchevans.com/pipermail/mikrotik/attachments/20121225/c8181395/attachment.html>
______________________________**_________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik>
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.butchevans.com/pipermail/mikrotik/attachments/20121225/f8fb0d4c/attachment.html>
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
_______________________________________________
Mikrotik mailing list
[email protected]
http://www.butchevans.com/mailman/listinfo/mikrotik
Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
