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: auto-discovery bumps (Stuart Kendrick)
--- Begin Message ---
Admin-> SNMP Connect Failures is empty ... "No significant events to report"

Manual discovery works fine - I now see a single device in Inventory (see 
'netdisco-do discover' output below)

Seems to me that at least one aspect of automated discovery is working fine, in 
that bulkwalks return ... but the results are not being inserted into the 
database ... what can break between bulkwalks returning and database insertion?


guru% bin/netdisco-do discover -D -d my-workstation
[18523] 2019-09-08 11:22:17  info App::Netdisco version 2.042010 loaded.
[18523] 2019-09-08 11:22:17  info discover: [10.1.2.3] started at Sun Sep  8 
04:22:17 2019
[18523] 2019-09-08 11:22:17 debug discover: running with timeout 600s
[18523] 2019-09-08 11:22:17 debug => running workers for phase: check
[18523] 2019-09-08 11:22:17 debug -> run worker check/_base_/0
[18523] 2019-09-08 11:22:17 debug Discover is able to run.
[18523] 2019-09-08 11:22:17 debug => running workers for phase: early
[18523] 2019-09-08 11:22:17 debug -> run worker early/properties/100
[18523] 2019-09-08 11:22:17 debug snmp reader cache warm: [10.1.2.3]
[18523] 2019-09-08 11:22:17 debug [10.1.2.3:161] try_connect with ver: 2, 
class: SNMP::Info, comm: <hidden>
[18523] 2019-09-08 11:22:21 debug [10.1.2.3:161] try_connect with ver: 2, new 
class: SNMP::Info::Layer3::NetSNMP, comm: <hidden>
[18523] 2019-09-08 11:22:21 debug -> run worker early/properties/100
[18523] 2019-09-08 11:22:21 debug -> run worker early/properties/100
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] device - aliased as 10.128.72.11
[18523] 2019-09-08 11:22:21 debug  resolving 1 aliases with max 50 outstanding 
requests
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] device - removed 0 aliases
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] aliases - added 1 new aliases
[18523] 2019-09-08 11:22:21 debug -> run worker early/properties/100
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] interfaces - ignoring 1 (lo) 
(softwareLoopback)
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] db/ports - removed 0 port entries 
from DevicePortPower
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] db/ports - removed 0 port entries 
from DevicePortProperties
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] db/ports - removed 0 port entries 
from DevicePortVlan
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] db/ports - removed 0 port entries 
from DevicePortWireless
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] db/ports - removed 0 port entries 
from DevicePortSsid
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] interfaces - removed 0 interfaces
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] interfaces - added 1 new 
interfaces
[18523] 2019-09-08 11:22:21 debug => running workers for phase: main
[18523] 2019-09-08 11:22:21 debug -> run worker main/canonicalip/100
[18523] 2019-09-08 11:22:21 debug -> run worker main/entities/100
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] modules - removed 0 chassis 
modules
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] modules - 0 chassis components 
(added one pseudo for chassis)
[18523] 2019-09-08 11:22:21 debug -> run worker main/neighbors/100
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] neigh - removed 0 outdated manual 
topology links
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] neigh - setting manual topology 
links
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] neigh - neighbor protocols are 
not enabled
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] neigh - processed 0 neighbors
[18523] 2019-09-08 11:22:21 debug -> run worker main/neighbors/100
[18523] 2019-09-08 11:22:21 debug -> run worker main/portpower/100
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] power - 0 power modules
[18523] 2019-09-08 11:22:21 debug -> run worker main/portproperties/100
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] properties/speed - local port lo 
already skipped, ignoring
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] properties/ifindex - local port 
lo already skipped, ignoring
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] properties - removed 0 ports with 
properties
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] properties - added 1 new port 
properties
[18523] 2019-09-08 11:22:21 debug -> run worker main/vlans/100
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] vlans - removed 0 port VLANs
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] vlans - added 0 new port VLANs
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] vlans - removed 0 device VLANs
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] vlans - added 0 new device VLANs
[18523] 2019-09-08 11:22:21 debug  [10.1.2.3] vlans - discovered for ports and 
device
[18523] 2019-09-08 11:22:21 debug -> run worker main/wireless/100
[18523] 2019-09-08 11:22:21 debug -> run worker main/withnodes/0
[18523] 2019-09-08 11:22:21  info discover: finished at Sun Sep  8 04:22:21 2019
[18523] 2019-09-08 11:22:21  info discover: status done: Ended discover for 
10.1.2.3
guru%

--sk

From: Nick Nauwelaerts <[email protected]>
Sent: Saturday, September 7, 2019 6:41 AM
To: Stuart Kendrick <[email protected]>; 
[email protected]
Subject: RE: auto-discovery bumps

CAUTION: This email originated from outside the Allen Institute. Please do not 
click links or open attachments unless you've validated the sender and know the 
content is safe.
________________________________
sure,
in the web interface go to to admin -> snmp connect failures. take any device 
ip you see there and then run a discovery of that device on the commandline:

netdisco-do discover -DI -d __device_ip__

that should give you a hint why discovery is failing. if it's not something 
obvious you see there then please send the output of that command to the 
mailing list so we can have a closer look;

good luck.

// nick

From: Stuart Kendrick [mailto:[email protected]]
Sent: Saturday, September 7, 2019 15:11
To: 
[email protected]<mailto:[email protected]>
Subject: [Netdisco] auto-discovery bumps

BRIEF

  *   I have a new NetDisco installation ... but the Inventory is empty
  *   How might I trouble-shoot the connection between data gathering 
(bulkwalks) and insertion into the postgres/netdisco database?


DETAIL
I have a brand-new Netdisco installation:
App::Netdisco 2.42.10
SNMP::Info 3.68
DB Schema 58
PostgreSQL 9.2.24
Perl 5.20.1

Guru% bin/netdisco-backend status
Netdisco Backend                                              [Running]
Guru%

I can bring up the Web interface and log in ...

The host is running lots of Netdisco-related processes ...

guru% ps -ef | grep netdisco
netdisco  1365     1  0 09:29 ?        00:00:00 perl 
/home/netdisco/bin/netdisc-web start
netdisco  1370  1365  0 09:29 ?        00:00:00 starman master 
--disable-keepalive --user 5001 --group 5000 
/home/netdisco/perl5/bin/netdisco-web-fg
netdisco  1385     1  0 09:29 ?        00:00:00 netdisco-backend
netdisco  1389  1385  0 09:29 ?        00:00:00 nd2: master
netdisco  1431  1370  1 09:29 ?        00:00:00 starman worker 
--disable-keepalive --user 5001 --group 5000 
/home/netdisco/perl5/bin/netdisco-web-fg
netdisco  1432  1370  0 09:29 ?        00:00:00 starman worker 
--disable-keepalive --user 5001 --group 5000 
/home/netdisco/perl5/bin/netdisco-web-fg
netdisco  1433  1370  0 09:29 ?        00:00:00 starman worker 
--disable-keepalive --user 5001 --group 5000 
/home/netdisco/perl5/bin/netdisco-web-fg
netdisco  1434  1370  0 09:29 ?        00:00:00 starman worker 
--disable-keepalive --user 5001 --group 5000 
/home/netdisco/perl5/bin/netdisco-web-fg
netdisco  1435  1370  0 09:29 ?        00:00:00 starman worker 
--disable-keepalive --user 5001 --group 5000 
/home/netdisco/perl5/bin/netdisco-web-fg
netdisco  1564  1389  0 09:29 ?        00:00:00 nd2: #1 sched: idle
netdisco  1565  1389  0 09:29 ?        00:00:00 nd2: #2 mgr: idle
netdisco  1566  1389  0 09:29 ?        00:00:00 nd2: #3 poll: idle
netdisco  1567  1389  0 09:29 ?        00:00:00 nd2: #4 poll: idle
netdisco  1568  1389  0 09:29 ?        00:00:00 nd2: #5 poll: idle
netdisco  1569  1389  0 09:29 ?        00:00:00 nd2: #6 poll: idle
postgres  1608  1296  0 09:29 ?        00:00:00 postgres: netdisco netdisco 
127.0.0.1(35800) idle
postgres  1609  1296  0 09:29 ?        00:00:00 postgres: netdisco netdisco 
127.0.0.1(35802) idle
postgres  1611  1296  0 09:29 ?        00:00:00 postgres: netdisco netdisco 
127.0.0.1(35804) idle
postgres  1612  1296  0 09:29 ?        00:00:00 postgres: netdisco netdisco 
127.0.0.1(35806) idle
postgres  1614  1296  0 09:29 ?        00:00:00 postgres: netdisco netdisco 
127.0.0.1(35808) idle
postgres  1616  1296  0 09:29 ?        00:00:00 postgres: netdisco netdisco 
127.0.0.1(35810) idle

But the Inventory 'System Information' screen is blank, i.e. the GUI tells me 
things like:

0 devices with 0 IPs

0 interfaces of which 0 are up

[...]

The CLI confirms this:
Guru% bin/netdisco-do psql -e 'SELECT ip, dns FROM device'
[3187] 2019-09-06 17:18:50  info App::Netdisco version 2.042010 loaded.
[3187] 2019-09-06 17:18:50  info psql:  started at Fri Sep  6 10:18:50 2019
ip | dns
----+-----
(0 rows)

[3187] 2019-09-06 17:18:50  info psql: finished at Fri Sep  6 10:18:50 2019
[3187] 2019-09-06 17:18:50  info psql: status done: psql session closed.
Guru%

Grabbing a pcap, I can see tens of thousands of SNMP bulkwalks against IP 
addresses I recognize (mgmt. agents on my Ethernet switches, for example) ... 
along with the suitable replies from my gear.

Suggestions for the next trouble-shooting step?

--sk


Do you support IT systems used for research?  Consider joining us in Seattle on 
Friday October 18, 2019 for Partly-Cloudy 
http://partly-cloudy.fredhutch.org<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpartly-cloudy.fredhutch.org&data=02%7C01%7C%7Ccea756dd488f4b32678008d7339904f2%7C32669cd6737f4b398bddd6951120d3fc%7C0%7C0%7C637034604646845621&sdata=Gb5bPknJsTyYvM4jjsEQgp7sgi9WqfqLGNEFONKlpP4%3D&reserved=0>,
 a one-day meeting bringing together line staff and their management to kick 
around what works / what doesn't when sloshing between Cloud and on-prem systems



________________________________

Volg Aquafin op 
Facebook<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2FAquafinNV&data=02%7C01%7C%7Ccea756dd488f4b32678008d7339904f2%7C32669cd6737f4b398bddd6951120d3fc%7C0%7C0%7C637034604646855614&sdata=7upVWhftqvZbvKRbn5cVf%2FiwJNVpRgluUpbsjrNW%2FJA%3D&reserved=0>
 | 
Twitter<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Faquafinnv&data=02%7C01%7C%7Ccea756dd488f4b32678008d7339904f2%7C32669cd6737f4b398bddd6951120d3fc%7C0%7C0%7C637034604646855614&sdata=JVOTu5nwZVn7Je8yK%2FbNvrumlNzQzhbfqfNlUjZ%2FtVI%3D&reserved=0>
 | 
YouTube<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.youtube.com%2Fchannel%2FUCk_4P5BJ-MtEEDCkCsR_KqQ%3Ffeature%3Dmhee&data=02%7C01%7C%7Ccea756dd488f4b32678008d7339904f2%7C32669cd6737f4b398bddd6951120d3fc%7C0%7C0%7C637034604646865613&sdata=ZzvBodKMNnImPtUnAGKbe4b7B7QRawpqTPXClL%2BaaMg%3D&reserved=0>
 | 
LinkedIN<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fcompany%2Faquafin%2Fproducts&data=02%7C01%7C%7Ccea756dd488f4b32678008d7339904f2%7C32669cd6737f4b398bddd6951120d3fc%7C0%7C0%7C637034604646875600&sdata=Av2GSPHLe0RkrAppx70x8BD1wc%2BK%2BlXDlNLP3LVssa4%3D&reserved=0>
 | 
Instagram<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.instagram.com%2Faquafin_nv%2F&data=02%7C01%7C%7Ccea756dd488f4b32678008d7339904f2%7C32669cd6737f4b398bddd6951120d3fc%7C0%7C0%7C637034604646875600&sdata=53qcKCknC1Oj%2F1l10d04mTekIDw0QTr2JrIv9rDc4UY%3D&reserved=0>

In het kader van de uitoefening van onze taken verzamelen we bij Aquafin 
persoonsgegevens. Hoe we omgaan met deze gegevens en wat de rechten van de 
betrokkenen zijn, kan je nalezen in onze privacy 
policy<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.aquafin.be%2Fnl-be%2Fprivacy-policy&data=02%7C01%7C%7Ccea756dd488f4b32678008d7339904f2%7C32669cd6737f4b398bddd6951120d3fc%7C0%7C0%7C637034604646887620&sdata=7mvnzUUgNxzOH66K2WIexCEf7bBQfN9V5WE6v1P3kys%3D&reserved=0>.

  P Denk aan het milieu. Druk deze mail niet onnodig af.

--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to