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. Arpwalk, Macsuck or Discover not successful on some devices
(Charlie Butera)
2. Re: Arpwalk, Macsuck or Discover not successful on some
devices (Christian Ramseyer)
3. Re: Arpwalk, Macsuck or Discover not successful on some
devices (Charlie Butera)
--- Begin Message ---
I am having an issue where on random devices Arpnip, Macsuck or Discover
will be failing consistently. I am using the default schedule for polling
(I initially was not but have since changed back to rule this out).
On one device:
Last Discover 2019-09-20 15:40
Last Arpnip 2019-09-20 17:50
Last Macsuck 2019-09-17 00:02
On another:
Last Discover 2019-09-20 15:38
Last Arpnip 2019-09-17 00:08
Last Macsuck 2019-09-20 18:20
Version Info:
Software Version
App::Netdisco 2.42.10
SNMP::Info 3.68
DB Schema 58
PostgreSQL 10.00.3
Perl 5.16.3
*Charles Butera*
*Network Engineer*
[email protected] <[email protected]>
Squarespace
Squarespace.com
--- End Message ---
--- Begin Message ---
Hi Charlie
Can you try to manually run the failing action on these devices and see
if you get any meaningful error message there?
E.g. the first device
netdisco-do macsuck -D -d <ip>
And the second one
netdisco-do arpnip -D -d <ip>
Also, with a big network and not enough CPU cores, the default schedule
might just not be able to process the whole network in a reasonable
time. You can check if you always have a lot of "nd2:" processes
running that are not saying "idle", or a high load average in top. This
would point to a resource contention on your polling system.
Cheers
Christian
On 20.09.19 20:45, Charlie Butera via netdisco-users wrote:
> I am having an issue where on random devices Arpnip, Macsuck or
> Discover will be failing consistently. I am using the default schedule
> for polling (I initially was not but have since changed back to rule
> this out).
>
> On one device:
> Last Discover 2019-09-20 15:40
> Last Arpnip 2019-09-20 17:50
> Last Macsuck 2019-09-17 00:02
>
> On another:
> Last Discover 2019-09-20 15:38
> Last Arpnip 2019-09-17 00:08
> Last Macsuck 2019-09-20 18:20
>
> Version Info:
> Software Version
> App::Netdisco 2.42.10
> SNMP::Info 3.68
> DB Schema 58
> PostgreSQL 10.00.3
> Perl 5.16.3
>
>
>
> *Charles Butera *
>
> *Network Engineer*
>
>
> [email protected] <mailto:[email protected]>
>
> Squarespace
>
> Squarespace.com <http://Squarespace.com>
>
>
>
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Christian,
When I run macsuck or arpnip using netdisco-do it runs successfully. But
when I schedule an arpwalk or macwalk it does not seem to schedule the
macsuck/arpnip for some devices.
*Charles Butera*
*Network Engineer*
[email protected] <[email protected]>
Squarespace
Squarespace.com
On Fri, Sep 20, 2019 at 3:49 PM Christian Ramseyer <[email protected]>
wrote:
> Hi Charlie
>
> Can you try to manually run the failing action on these devices and see if
> you get any meaningful error message there?
>
> E.g. the first device
>
> netdisco-do macsuck -D -d <ip>
>
> And the second one
>
> netdisco-do arpnip -D -d <ip>
>
> Also, with a big network and not enough CPU cores, the default schedule
> might just not be able to process the whole network in a reasonable time.
> You can check if you always have a lot of "nd2:" processes running that
> are not saying "idle", or a high load average in top. This would point to a
> resource contention on your polling system.
>
> Cheers
> Christian
>
>
>
>
>
> On 20.09.19 20:45, Charlie Butera via netdisco-users wrote:
>
> I am having an issue where on random devices Arpnip, Macsuck or Discover
> will be failing consistently. I am using the default schedule for polling
> (I initially was not but have since changed back to rule this out).
>
> On one device:
> Last Discover 2019-09-20 15:40
> Last Arpnip 2019-09-20 17:50
> Last Macsuck 2019-09-17 00:02
>
> On another:
> Last Discover 2019-09-20 15:38
> Last Arpnip 2019-09-17 00:08
> Last Macsuck 2019-09-20 18:20
>
> Version Info:
> Software Version
> App::Netdisco 2.42.10
> SNMP::Info 3.68
> DB Schema 58
> PostgreSQL 10.00.3
> Perl 5.16.3
>
>
>
> *Charles Butera *
>
> *Network Engineer*
>
> [email protected] <[email protected]>
>
> Squarespace
>
> Squarespace.com
>
>
> _______________________________________________
> Netdisco mailing
> [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
