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. More forgiving neighbor map ([email protected])
--- Begin Message ---
I get that Netdisco's neighbors are trying to be true to the L2 rules, e.g.
trying to ensure that a connected device is not reported when there may be a
dumb hub in between.
But sometimes I think it is more useful if we could get a bit more lax
interpretation, especially one that includes discovered Windows servers, which
due to Microsoft's idiocy never have done LLDP correctly.
I've rearranged one module a bit to test, and am getting good results, and
would like to share and get feedback.
I do not have any idea if a more lax mode would be of interest to incorporate,
but if you find this useful it's easy to patch.
And if it's broken in a fundamental way, I'd love to know.
The only changes are in the SQL itself. There are two changes -- above the
union statement is a change so that the elimination of duplicates is more
explicit, which permits one-sided LLDP/CDP discovery to work. A discussion of
this is here:
https://github.com/netdisco/netdisco/issues/436
The second is the sql below the union, which selects some specific device types
that normally cannot appear because they do not support LLDP/CDP, and forces a
connection based on node mac visibility. Note that this might cause double
links (e.g. VM's inside a Hypervisor), or other links that are not true L2
links. Also, if you manage to run LLDP on Windows it might double up (though
I've never gotten that to work correctly). It's a bit of a blunt instrument
and might benefit from some fine tuning.
At a larger client I have a bit over 500 nodes. The first change connected up
about 100 of them not otherwise connected, and the second one included a few
dozen UPS and Windows Servers as well, leaving only a few not connected. So
far I have not found any actual errors in the connections.
Anyway, presented in case you find it useful, feedback solicited.
Linwood
DeviceLinks.pm
Description: DeviceLinks.pm
--- End Message ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
