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: Netdisco2 sometimes misses connected hosts data & SSH
Collector (Oliver Gorwits)
--- Begin Message ---
Hi Muris
Please can you describe in a little more detail what's missing from the
web interface - is it the MAC addresses of nodes on the ports, or the IP
addresses of those nodes, or the neighbor relations to other devices?
Each of these is gathered by a different process.
You could try slowing down the pollers by setting sleep_time:
workers:
tasks: 'AUTO * 4'
sleep_time: 2
This makes each worker pause a little after it polls (the default is one
second). If your problem is UDP overload on your server then it might
help.
regards,
oliver.
On 2017-06-23 11:37, Muris wrote:
Hi All,
I would like to say thanks to the person who came up with the SSH
Collector for Nexus/ASA devices its really awesome and working well.
Can it also connect via telnet ?
I have come up with a problem, as i have around 3000 devices, for some
reason the macksuck and arp, on the automatic arpnips/walks dont fully
populate the data for a switch, when i go into the switch some ports
show up but blanks next to them on connected devices..
However, if i manually force a discover/arpnip/macwalk through the
webinterface the data populates straight away.
Is there any reason for this? How can it completely do it automated
without me refreshing a device manually? (Well the netdisco-backend
should be doing it but some reason some data dissapears when
displayed)
I was thinking the SSH Collector of arps maybe could be conflicting
with netdisco arps to populate data...not sure..but at the moment
needing the ssh collector due to mpls and nexus with vrfs etc.
To cater for this many devices, i have 8 CPUs set on a Xeon machine
with 16gb ram, and running the backend worker on AUTO * 4 in
deployment config.
Postgresql is optimised with pgtune, and running latest netdisco
version released 22/06/17
Any troubleshooting/recommendations would be appreciated :)
Thankyou, Muris
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- 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
