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: Pending Device Discovery (Les Begnaud)
--- Begin Message ---
Will do. Will try to make note to respond when I get a workflow sorted out.
Thanks again.
Les Begnaud
Systems Engineer (Sys Lord)
RADER
337.205.4652
[email protected]
From: Nick Nauwelaerts <[email protected]>
Sent: Saturday, February 9, 2019 1:31 PM
To: [email protected]
Subject: Re: [Netdisco] Pending Device Discovery
coolness,
i'm interested in the outcome either way, feedback that something works is just
as welcome as feedback that something doesn't.
// nick
From: Les Begnaud [mailto:[email protected]]
Sent: Monday, February 4, 2019 23:41
To: Nick Nauwelaerts <[email protected]>;
[email protected]
Subject: RE: Pending Device Discovery
We are running a pretty old install of netdisco, but I’m in the process of
migrating to the docker image, so let’s assume we’re using that one.
· All of our current staging discoveries are done via a direct
netdisco-do discover command
· Replacing a device sometimes we will reuse the IP, other times we
will use a new IP (if the old device is still functional, or if we are putting
in a switch with more ports, etc)
· I’m not sure the expire_jobs, max_deferrals, or retry_after would
help me with a device never discovered, but the snmp connect failures menu
seems interesting. If I understand correctly, that will work perfectly for what
I’m trying to do. Only issue is we run netdisco web in guest read-only mode… so
that view is not visible. I guess now that ospf discovery is a thing, I don’t
have to be as concerned as people accidentally nuking core nodes.
I appreciate the ideas. I’ll try these out and reply if I need any more
direction!
Les Begnaud
Systems Engineer (Sys Lord)
RADER
337.205.4652<tel:337.205.4652>
[email protected]
<mailto:[email protected]>
From: Nick Nauwelaerts <[email protected]>
Sent: Friday, February 1, 2019 4:18 PM
To: [email protected]
Subject: Re: [Netdisco] Pending Device Discovery
heya,
first things first, what version of netdisco are you running?
i'm not quite sure what you mean with the replacing part. when you're replacing
a failed device, do you use the same hostname? how does netdisco discover the
device you're staging, via lldp/cdp? remember that if you move a device you can
use netdisco-do renumber, but it's a manual operation:
https://metacpan.org/pod/distribution/App-Netdisco/bin/netdisco-do#renumber
for the queueing part, i think you have few options there. either with
expire_jobs setting
(https://github.com/netdisco/netdisco/wiki/Configuration#expire_jobs) and/or
max_deferrals and retry_after
(https://github.com/netdisco/netdisco/wiki/Configuration#backend-daemon).
somehow i seem to recall that jobs submitted via netdisco-do will never expire,
but that could have been a bug.
a third option is to try & get your device in the device_skip table (snmp
connect failures in the web interface), either that's a bug as well but those
don't seem to expire. the oldest one i have in there had his last retry
2018-12-05 11:33:23. then just assign someone to click the try again buttons
once every week. on 2.40.3 if i run a netdisco-do discover on a device that's
offline, it well end up in the device_skip table after a few minutes. my
biggest issue is getting devices _out_ of that table :)
worst option is to export your ipam or whatever once a week and run a forced
discovery on everything. it's brute force & resource intensive, but as a last
resort it could work.
finally, for the discovery without lldp, don't think there are many options
there. netdisco discovers via lldp/cdp/bgp/ospf/... well i guess you already
know, but if none of those are available options are limited. you can try to
discover each node, but i think that would be a very bad idea. other option
might be to go directly to the backend database. the node & node_ip tables
contain the mac address of each node, you can filter those on the oui of your
switch vendor(s) & run a discovery on those ip's once a week. device_port ->
remote_ip could also be an option, perhaps something else discovered the device
and you can get lucky that way.
// nick
From: Les Begnaud [mailto:[email protected]]
Sent: Friday, February 1, 2019 18:18
To:
[email protected]<mailto:[email protected]>
Subject: [Netdisco] Pending Device Discovery
We have a process in which we stage devices at our office before sending out
into the field. There are currently two situations where we can get into a
state that leaves a device not added to netdisco:
· Replacing a failed device
o The mgmt. IP of the device is not routable, as the IP is being routed to
the site, not to our office staging area
· Creating a brand new site
o If a user forgets to do the discovery, we have to wait until the device is
on site and online before running a discover
o This is prone to being forgotten and then we are left with the device not
being discovered until it is “found” later
I think a clean solution to both problems would be a way to stage a device to
discover. A simple solution would be to manually add it to the devices table in
the DB with some flag that says it’s undiscovered, a better solution might be
to update the schema to include a pending devices table that gets discovered on
a different interval than the regular devices.
It's also possible that this functionality already exists, and I just am not
looking in the right place.
As a side note, neighbor discovery helps us out often here, but the router
product that we use doesn’t support LLDP MIBS… so there’s a big break in the
dynamic discovery that can happen. The router can be discovered via OSPF, but
the switches behind it won’t be discovered (though a replaced device with a new
IP can be)
Les Begnaud
Systems Engineer (Sys Lord)
[cid:[email protected]]
337.205.4652<tel:337.205.4652>
[email protected]<mailto:[email protected]>
________________________________
Volg Aquafin op Facebook<https://www.facebook.com/AquafinNV> |
Twitter<https://twitter.com/aquafinnv> |
YouTube<http://www.youtube.com/channel/UCk_4P5BJ-MtEEDCkCsR_KqQ?feature=mhee> |
LinkedIN<http://www.linkedin.com/company/aquafin/products>
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://www.aquafin.be/nl-be/privacy-policy>.
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
