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 (Oliver Gorwits)
2. Re: auto-discovery (Ed Blom)
--- Begin Message ---
Thanks, that's a great suggestion for the docs!
On Thu, 12 Sep 2019 at 13:38, Stuart Kendrick <[email protected]>
wrote:
> OK, I don’t have a coherent story to tell, can someone help me fill this
> out?
>
>
>
> I got distracted for a few days, returned to this thread … and found that
> my Inventory is now populated with what I would expect, i.e. a quick glance
> suggests that Netdisco has found most if not all of my Devices
>
>
>
> - How does Netdisco get started? How does it find the first device to
> query using SNMP (from which it then starts examining CDP/FDP/LLDP tables
> to figure out where to go next)?
> - And does Netdisco use other techniques to find Devices? E.g.
> consult RIP / OSPF / EIGRP … tables to find ‘neighbors’?
>
>
>
> To answer your specific question: 10.1.2.3 is a Linux box (my desktop
> machine). It happens to run LLDPd … and see its local Ethernet switch as a
> neighbor (although I would claim, with some doubt around the unreliability
> of my memory, that Inventory stayed empty for a day or two, even after I
> had manually pointed netdisco-do at it, to produce the output I posted).
>
>
>
> If I understand Dominik correctly, installing Netdisco involves the
> process described here https://metacpan.org/pod/App::Netdisco#Installation
> and then, in fact, one must run a netdisco-do (via CLI or GUI) to discover
> the first device … and assuming that this first device can start walking
> the CDP/FDP/LLDP chain, then much progress will then occur.
>
>
>
> If this is the case, then I propose adding a ‘First Run’ section similar
> to the following:
>
>
>
> First Run
>
> After installing Netdisco for the first time, you must manually discover
> at least one device on your network. To do this, perform the following
> step:
>
> ~/bin/netdisco-do discover -D {name or IP address of a switch or router}
>
>
>
> Choose a device which speaks CDP, FDP, or LLDP and thus knows about its
> neighbors; Netdisco will then start following this chain of neighbors to
> discover the rest of your network
>
> *Upgrading from 2.x*
>
>
>
> --sk
>
>
>
>
>
>
>
> *From:* Oliver Gorwits <[email protected]>
> *Sent:* Monday, September 9, 2019 3:21 AM
> *To:* [email protected]
> *Subject:* Re: [Netdisco] auto-discovery
>
>
>
> *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.
> ------------------------------
>
> Hi Stuart
>
>
>
> I agree with Dominik. Looking a the logs from your earlier emails, these
> are relevant:
>
>
>
> [18523] 2019-09-08 11:22:21 debug [10.1.2.3:161
> <https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2F10.1.2.3%3A161&data=02%7C01%7C%7Cf935151f10b04f49b06d08d7351381b7%7C32669cd6737f4b398bddd6951120d3fc%7C0%7C0%7C637036230234487769&sdata=6IplQxMxdhGRkCuOtYRjEvyau9rcCTXNhjugjBLNEgw%3D&reserved=0>]
> try_connect with ver: 2, new class: SNMP::Info::Layer3::NetSNMP, comm:
> <hidden>
>
>
>
> in the above line we see that the device is only being identified as a
> generic system, and results would be better if there were an SNMP::Info
> specific class for the device model (e.g. Layer3::C6500). Can you share the
> device/model being discovered?
>
>
> [18523] 2019-09-08 11:22:21 debug [10.1.2.3] interfaces - added 1 new
> interfaces
>
>
>
> Surprising that there is only one interface on this switch/router, or is
> it a server or VM?
>
> [18523] 2019-09-08 11:22:21 debug [10.1.2.3] neigh - neighbor protocols
> are not enabled
>
>
>
> And finally, here is where Dominik mentions the CDP/FDP/LLDP needing to be
> enabled. They are protocols for walking the network from device to device.
>
>
>
> Perhaps reading this will help:
> https://github.com/netdisco/netdisco/wiki/Troubleshooting#understanding-nodes-and-devices
> <https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnetdisco%2Fnetdisco%2Fwiki%2FTroubleshooting%23understanding-nodes-and-devices&data=02%7C01%7C%7Cf935151f10b04f49b06d08d7351381b7%7C32669cd6737f4b398bddd6951120d3fc%7C0%7C0%7C637036230234497761&sdata=xsgS6BNP%2FqaQY1GRhCaMnrEggfVYGU3VekQbdRzVajM%3D&reserved=0>
>
>
>
> Good luck!
>
>
>
> regards,
>
> oliver.
>
>
>
> On Mon, 9 Sep 2019 at 10:40, Mueller, Dominik <[email protected]>
> wrote:
>
> Hi Stuart,
>
> I think the problem is, that a Macwalk and Discoverall will not bring the
> desired outcome.
> You have to add at least one device which utilizes lldp (CDP, FDP, etc...)
> to autodiscover other devices.
>
> Otherwise you have to insert all devices in a crontab.
>
> Best regards
>
>
> Dominik Müller
>
>
>
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
> <https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fnetdisco%2Fmailman%2Fnetdisco-users%2F&data=02%7C01%7C%7Cf935151f10b04f49b06d08d7351381b7%7C32669cd6737f4b398bddd6951120d3fc%7C0%7C0%7C637036230234497761&sdata=X6qGdETyR7RPNVQC62TSsg7hYCYk8v%2FaL939eTK8bbU%3D&reserved=0>
>
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
On the homepage of netdisco you can input a device to discover, so once
installed users need to be told to add a device, then hit discover. That would
be nice ot know in the documentation
On Thursday, September 12, 2019, 03:00:24 PM CDT, Oliver Gorwits
<[email protected]> wrote:
Thanks, that's a great suggestion for the docs!
On Thu, 12 Sep 2019 at 13:38, Stuart Kendrick <[email protected]>
wrote:
OK, I don’t have a coherent story to tell, can someone help me fill this out?
I got distracted for a few days, returned to this thread … and found that my
Inventory is now populated with what I would expect, i.e. a quick glance
suggests that Netdisco has found most if not all of my Devices
- How does Netdisco get started? How does it find the first device to query
using SNMP (from which it then starts examining CDP/FDP/LLDP tables to figure
out where to go next)?
- And does Netdisco use other techniques to find Devices? E.g. consult RIP
/ OSPF / EIGRP … tables to find ‘neighbors’?
To answer your specific question: 10.1.2.3 is a Linux box (my desktop
machine). It happens to run LLDPd … and see its local Ethernet switch as a
neighbor (although I would claim, with some doubt around the unreliability of
my memory, that Inventory stayed empty for a day or two, even after I had
manually pointed netdisco-do at it, to produce the output I posted).
If I understand Dominik correctly, installing Netdisco involves the process
described herehttps://metacpan.org/pod/App::Netdisco#Installation and then, in
fact, one must run a netdisco-do (via CLI or GUI) to discover the first device
… and assuming that this first device can start walking the CDP/FDP/LLDP chain,
then much progress will then occur.
If this is the case, then I propose adding a ‘First Run’ section similar to the
following:
First Run
After installing Netdisco for the first time, you must manually discover at
least one device on your network. To do this, perform the following step:
~/bin/netdisco-do discover -D {name or IP address of a switch or router}
Choose a device which speaks CDP, FDP, or LLDP and thus knows about its
neighbors; Netdisco will then start following this chain of neighbors to
discover the rest of your network
Upgrading from 2.x
--sk
From: Oliver Gorwits <[email protected]>
Sent: Monday, September 9, 2019 3:21 AM
To: [email protected]
Subject: Re: [Netdisco] auto-discovery
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.
Hi Stuart
I agree with Dominik. Looking a the logs from your earlier emails, these are
relevant:
[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>
in the above line we see that the device is only being identified as a generic
system, and results would be better if there were an SNMP::Info specific class
for the device model (e.g. Layer3::C6500). Can you share the device/model being
discovered?
[18523] 2019-09-08 11:22:21 debug [10.1.2.3] interfaces - added 1 new
interfaces
Surprising that there is only one interface on this switch/router, or is it a
server or VM?
[18523] 2019-09-08 11:22:21 debug [10.1.2.3] neigh - neighbor protocols are
not enabled
And finally, here is where Dominik mentions the CDP/FDP/LLDP needing to be
enabled. They are protocols for walking the network from device to device.
Perhaps reading this will help:
https://github.com/netdisco/netdisco/wiki/Troubleshooting#understanding-nodes-and-devices
Good luck!
regards,
oliver.
On Mon, 9 Sep 2019 at 10:40, Mueller, Dominik <[email protected]> wrote:
Hi Stuart,
I think the problem is, that a Macwalk and Discoverall will not bring the
desired outcome.
You have to add at least one device which utilizes lldp (CDP, FDP, etc...) to
autodiscover other devices.
Otherwise you have to insert all devices in a crontab.
Best regards
Dominik Müller
_______________________________________________
Netdisco mailing list
[email protected]
https://sourceforge.net/p/netdisco/mailman/netdisco-users/
_______________________________________________
Netdisco mailing list
[email protected]
https://sourceforge.net/p/netdisco/mailman/netdisco-users/
_______________________________________________
Netdisco mailing list
[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
