Send netdisco-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: [EXTERNAL MSG:]Re: [EXTERNAL MSG:]Re: Jobs running but no
results (Denny Sabu)
--- Begin Message ---
Hi Oliver,
That makes sense. One other thing, we’re trying to query a Cisco Meraki
appliance, and following their instructions for SNMP we are able to get
information back from snmpwalk. We’ve had to add an MIB file, and are using
snmp.meraki.com instead of the IP, which is what the documentation says. If we
use the IP, we get the same timeout no response message.
Is there anyway to pass that snmp.meraki.com address to Netdisco?
From: Oliver Gorwits <[email protected]>
Date: Tuesday, May 11, 2021 at 3:13 PM
To: Denny Sabu <[email protected]>
Cc: [email protected] <[email protected]>
Subject: [EXTERNAL MSG:]Re: [EXTERNAL MSG:]Re: [Netdisco] Jobs running but no
results
WARNING: This email originated from outside of Sensato. Do not click links or
open attachments unless you verify by phone with the sender.
Hi Denny
If snmpstatus cannot contact to the router then it’s not an issue with Netdisco
- there is an issue either with a firewall or the router config or your snmp
settings.
snmpstatus is independent of Netdisco which is why it’s a good backup check to
see if things work.
Oliver.
On Tue, 11 May 2021 at 19:37, Denny Sabu
<[email protected]<mailto:[email protected]>> wrote:
Hi Oliver,
Thanks for the reply. snapstatus reported back as timing out with no response
from the routers.
The -DI option certainly added more output, I’ve pasted a few lines that stood
out:
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global(uptime) Timeout at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Transport/SNMP.pm line 245.
[79624] 2021-05-11 18:31:30 debug [192.168.112.1:161<http://192.168.112.1:161>]
try_connect with ver: 1, class: SNMP::Info, comm: <hidden>
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global(uptime) Timeout at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Transport/SNMP.pm line 245.
[79624] 2021-05-11 18:31:33 debug discover failed: could not SNMP connect to
192.168.112.1
Seems like the timeout is the issue.
I’ll look through the troubleshooting wiki.
Best,
Denny
From: Oliver Gorwits <[email protected]<mailto:[email protected]>>
Date: Tuesday, May 11, 2021 at 10:36 AM
To: Denny Sabu <[email protected]<mailto:[email protected]>>
Cc:
[email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>
Subject: [EXTERNAL MSG:]Re: [Netdisco] Jobs running but no results
WARNING: This email originated from outside of Sensato. Do not click links or
open attachments unless you verify by phone with the sender.
Hi Denny
Can you run snmpstatus to the router with the same SNMP config you put into
Netdisco?
for example: snmpstatus -v 2c -c public 1.2.3.4
Perhaps the router does not want to talk/reply to your server for some reason.
Also some routers have access control lists which might allow basic SNMP but
not enough to get what Netdisco needs (see the troubleshooting doc in the wiki).
You can also add debug option -DI to the netdisco-do command to get more
verbose reporting.
regards
oliver.
On Tue, 11 May 2021 at 15:17, Denny Sabu
<[email protected]<mailto:[email protected]>> wrote:
Hi all,
I just had a follow up to the question John had asked yesterday about jobs not
starting. We started the backend process and the jobs started running and the
server ran many jobs overnight but there are no results available to view.
Running ~/bin/netdisco-do discover -d {name or IP address of a switch or
router} against our router which should be speaking LLDP/CDP as the
documentation asks for returns:
“info discover: status defer: discover failed: could not SNMP connect to…”
Any thoughts on where we’re going wrong?
Thanks,
Denny
_______________________________________________
Netdisco mailing list
[email protected]<mailto:[email protected]>
https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
