Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
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
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: New install failed to find a number of devices.
Recommendations for determining failure points and cleaning up
database? (Oliver Gorwits)
2. Re: New install failed to find a number of devices.
Recommendations for determining failure points and cleaning up
database? (David Bertagni)
--- Begin Message ---
Hi David, sure just send snmpwalk output using the command on the wiki page
to my email here, and I'll take a look. Should just be a few megabytes size
at the most.
regards
Oliver.
On Wed, 15 Nov 2023 at 20:15, David Bertagni <dberta...@brynmawr.edu> wrote:
> Hi Oliver,
>
> I'm game to try and figure out the inconsistencies. Any pointers on where
> and how to look other than the snmpwalk output? I can generate snmpwalk
> output for any of my devices. Let me know where to send them.
>
> Best,
> David Bertagni, Bryn Mawr College
>
> ------------------------------
> *From:* Oliver Gorwits <oli...@cpan.org>
> *Sent:* Wednesday, November 15, 2023 12:34 PM
> *To:* David Bertagni <dberta...@brynmawr.edu>;
> netdisco-users@lists.sourceforge.net <netdisco-users@lists.sourceforge.net
> >
> *Subject:* Re: [Netdisco] New install failed to find a number of devices.
> Recommendations for determining failure points and cleaning up database?
>
> Hi again David
>
> Seems I forgot that store_modules setting does exist:
> https://github.com/netdisco/netdisco/wiki/Configuration#store_modules
>
> However it is global so removes the functionality from all device
> discover. Would be nice to be an ACL so I'll leave the ticket open.
>
> Maybe this helps you complete the reinstallation though. Chassis/module
> info should not be needed for any other Netdisco function (unless you rely
> on the relevant reports of course).
>
> regards
> Oliver.
>
> On Tue, 14 Nov 2023 at 22:07, Oliver Gorwits <oli...@cpan.org> wrote:
>
> Hi David
>
> The different errors you describe all relate to the "Device Modules" tab
> entries, that is, the hardware components reported by the device. Invalid
> parent means the report is somehow inconsistent with itself, and the
> uninitialized error, while a bug in Netdisco, also points to some weird
> data back from the device.
>
> Unfortunately we don't have a feature in Netdisco to disable Entity
> gathering (which would just skip this stuff and allow the rest to
> continue). I've made a ticket for it:
> https://github.com/netdisco/netdisco/issues/1126
>
> The other option is to share with me the output of an snmpwalk if the
> device will allow it, and I can see if I can reproduce the issue(s) and fix
> them: https://github.com/netdisco/netdisco/wiki/Snapshot#share-a-snapshot
>
> Oh, I guess the other hack you could do locally is copy "worker_plugins"
> config from the default and remove the "Discover::Entities" item to disable
> it. https://github.com/netdisco/netdisco/blob/master/share/config.yml
>
> I also opened a ticket for the uninitialized value bug
> https://github.com/netdisco/netdisco/issues/1127
>
> Kind regards
> Oliver.
>
> On Tue, 14 Nov 2023 at 04:06, David Bertagni <dberta...@brynmawr.edu>
> wrote:
>
> Hi,
>
> Apologies if this is noted elsewhere and I missed it...
>
> I have an old instance, v2.39.19, on an old Ubuntu distribution that I'm
> replacing with a new from scratch instance, v2.68.1. I decided to not
> migrate anything but the basic configuration and allowed the new instance
> to find devices with a single seed to my core Juniper stack. It found
> _most_ of them, but I had to manually discover a dozen or so and I'm
> wondering how best to clean up the manual discovery as they all came up
> with "invalid parent" errors and a few reported this error:
> "Use of uninitialized value in sprintf at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Entities.pm
> line 109."
>
> I'm primarily a Juniper shop with some legacy HP and newer Aruba-CX type
> switches. I'm getting ready to deploy Extreme's universal switch line, as
> product becomes available.
>
> I'm not sure exactly why discovery failed as it was pretty random from my
> end. The switches are all configured identically and some were found while
> others skipped even on the same network.
>
> Happy to provide logs and other output as I'd like to get this instance up
> clean before retiring out the old.
>
> Thanks,
> David Bertagni
> Bryn Mawr College
>
>
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
>
--- End Message ---
--- Begin Message ---
Hi Oliver,
I'm game to try and figure out the inconsistencies. Any pointers on where and
how to look other than the snmpwalk output? I can generate snmpwalk output for
any of my devices. Let me know where to send them.
Best,
David Bertagni, Bryn Mawr College
________________________________
From: Oliver Gorwits <oli...@cpan.org>
Sent: Wednesday, November 15, 2023 12:34 PM
To: David Bertagni <dberta...@brynmawr.edu>;
netdisco-users@lists.sourceforge.net <netdisco-users@lists.sourceforge.net>
Subject: Re: [Netdisco] New install failed to find a number of devices.
Recommendations for determining failure points and cleaning up database?
Hi again David
Seems I forgot that store_modules setting does exist:
https://github.com/netdisco/netdisco/wiki/Configuration#store_modules
However it is global so removes the functionality from all device discover.
Would be nice to be an ACL so I'll leave the ticket open.
Maybe this helps you complete the reinstallation though. Chassis/module info
should not be needed for any other Netdisco function (unless you rely on the
relevant reports of course).
regards
Oliver.
On Tue, 14 Nov 2023 at 22:07, Oliver Gorwits
<oli...@cpan.org<mailto:oli...@cpan.org>> wrote:
Hi David
The different errors you describe all relate to the "Device Modules" tab
entries, that is, the hardware components reported by the device. Invalid
parent means the report is somehow inconsistent with itself, and the
uninitialized error, while a bug in Netdisco, also points to some weird data
back from the device.
Unfortunately we don't have a feature in Netdisco to disable Entity gathering
(which would just skip this stuff and allow the rest to continue). I've made a
ticket for it: https://github.com/netdisco/netdisco/issues/1126
The other option is to share with me the output of an snmpwalk if the device
will allow it, and I can see if I can reproduce the issue(s) and fix them:
https://github.com/netdisco/netdisco/wiki/Snapshot#share-a-snapshot
Oh, I guess the other hack you could do locally is copy "worker_plugins" config
from the default and remove the "Discover::Entities" item to disable it.
https://github.com/netdisco/netdisco/blob/master/share/config.yml
I also opened a ticket for the uninitialized value bug
https://github.com/netdisco/netdisco/issues/1127
Kind regards
Oliver.
On Tue, 14 Nov 2023 at 04:06, David Bertagni
<dberta...@brynmawr.edu<mailto:dberta...@brynmawr.edu>> wrote:
Hi,
Apologies if this is noted elsewhere and I missed it...
I have an old instance, v2.39.19, on an old Ubuntu distribution that I'm
replacing with a new from scratch instance, v2.68.1. I decided to not migrate
anything but the basic configuration and allowed the new instance to find
devices with a single seed to my core Juniper stack. It found _most_ of them,
but I had to manually discover a dozen or so and I'm wondering how best to
clean up the manual discovery as they all came up with "invalid parent" errors
and a few reported this error:
"Use of uninitialized value in sprintf at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Entities.pm
line 109."
I'm primarily a Juniper shop with some legacy HP and newer Aruba-CX type
switches. I'm getting ready to deploy Extreme's universal switch line, as
product becomes available.
I'm not sure exactly why discovery failed as it was pretty random from my end.
The switches are all configured identically and some were found while others
skipped even on the same network.
Happy to provide logs and other output as I'd like to get this instance up
clean before retiring out the old.
Thanks,
David Bertagni
Bryn Mawr College
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net<mailto:netdisco-users@lists.sourceforge.net>
https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
