netdisco-users Digest, Vol 176, Issue 6

[netdisco-users-request]

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. Netdisco IRC Channel Removed? (Jimmy Taylor)
   2. Re: Netdisco IRC Channel Removed? (Christian Ramseyer)
   3. Re: Netdisco IRC Channel Removed? (Jimmy Taylor)
--- Begin Message ---
I went to join #netdisco on freenode and noticed the channel is no longer
there. Has it moved to a different location or is it no longer in service?

-- 
Jimmy Taylor

*Network Engineer*

Office of Information Technology

Boise State University
--- End Message ---
--- Begin Message ---


On 17.03.21 15:25, Jimmy Taylor wrote:
> I went to join #netdisco on freenode and noticed the channel is no
> longer there. Has it moved to a different location or is it no longer in
> service?
> 


Hi

Seems to work fine for me and a bunch of people are there:

Netdisco: better than chocolate or tacos | http://netdisco.org |
https://metacpan.org/pod/App::Netdisco | http://paste.scsys.co.uk/

16:00 -!- rc9000 [~r...@exile.networkz.ch] has joined #netdisco
16:00 -!- Topic for #netdisco: Netdisco: better than chocolate or tacos
| http://netdisco.org | https://metacpan.org/pod/App::Netdisco |
  http://paste.scsys.co.uk/
16:00 -!- Topic set by oliver
[sid260132@gateway/web/irccloud.com/x-ixxkxgtkhchrtjjm] [Wed Apr  3
13:54:25 2019]
16:00 [Users #netdisco]
16:00 [@ChanServ] [ Brian- ] [ djhankb] [ hotdogs ] [ rc9000 ] [ weissbier]
16:00 [@oliver  ] [ Chestal] [ Domin  ] [ inphobia] [ Sthebig]
16:00 [ ard ] [ dasTor ] [ fiet   ] [ JvI_home] [ Vlad   ]
16:00 -!- Irssi: #netdisco: Total of 16 nicks [2 ops, 0 halfops, 0
voices, 14 normal]
16:00 -!- Channel #netdisco created Sun Nov 26 08:15:28 2006

Cheers
Christian


-- 
Christian Ramseyer, netnea ag
Network Management. Security. OpenSource.
https://www.netnea.com


--- End Message ---
--- Begin Message ---
Apologies. I'm in now.

Appears I mistyped it multiple times.

On Wed, Mar 17, 2021 at 9:04 AM Christian Ramseyer 
wrote:

>
>
> On 17.03.21 15:25, Jimmy Taylor wrote:
> > I went to join #netdisco on freenode and noticed the channel is no
> > longer there. Has it moved to a different location or is it no longer in
> > service?
> >
>
>
> Hi
>
> Seems to work fine for me and a bunch of people are there:
>
> Netdisco: better than chocolate or tacos | http://netdisco.org |
> https://metacpan.org/pod/App::Netdisco | http://paste.scsys.co.uk/
>
> 16:00 -!- rc9000 [~r...@exile.networkz.ch] has joined #netdisco
> 16:00 -!- Topic for #netdisco: Netdisco: better than chocolate or tacos
> | http://netdisco.org | https://metacpan.org/pod/App::Netdisco |
>   http://paste.scsys.co.uk/
> 16:00 -!- Topic set by oliver
> [sid260132@gateway/web/irccloud.com/x-ixxkxgtkhchrtjjm] [Wed Apr  3
> 13:54:25 2019]
> 16:00 [Users #netdisco]
> 16:00 [@ChanServ] [ Brian- ] [ djhankb] [ hotdogs ] [ rc9000 ] [ weissbier]
> 16:00 [@oliver  ] [ Chestal] [ Domin  ] [ inphobia] [ Sthebig]
> 16:00 [ ard ] [ dasTor ] [ fiet   ] [ JvI_home] [ Vlad   ]
> 16:00 -!- Irssi: #netdisco: Total of 16 nicks [2 ops, 0 halfops, 0
> voices, 14 normal]
> 16:00 -!- Channel #netdisco created Sun Nov 26 08:15:28 2006
>
> Cheers
> Christian
>
>
> --
> Christian Ramseyer, netnea ag
> Network Management. Security. OpenSource.
> https://www.netnea.com
>


-- 
Jimmy Taylor

*Network Engineer*

Office of Information Technology

Boise State University
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 176, Issue 1

[netdisco-users-request]

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. NETDISCO RADIUS Error (Jimmy Taylor)
--- Begin Message ---
Hello all,

I'm configuring RADIUS on NETDISCO and I'm getting the following error
message:

Chrome:
'ERR_INVALID_RESPONSE'

netdisco-web.log:
error request to POST /login crashed: Can't call method "add_attributes" on
an undefined value at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Web/Auth/Provider/DBIC.pm line
245.

I have verified RADIUS is configured correctly according to the
documentation, and I have installed freeradius along with copying the
proper freeradius dictionary directory to /etc/raddb/.

At a lost here as to how to proceed. At this point, I'm not even receiving
a RADIUS request to our RADIUS server.

Any suggestions?

Thank you.

-- 
Jimmy Taylor

*Network Engineer*

Office of Information Technology

Boise State University
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 176, Issue 8

[netdisco-users-request]

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. SNMP MIBs for Alcatel devices running AOS8 in Netdisco
  (Quentin Hunin)
--- Begin Message ---
Dear Netdisco users and developers,

We are using Netdisco with Cisco devices since several years now. Since
a few months, we are moving to Alcatel devices. Unfortunately, MAC
addresses and IP lookups do not work on those devices. We quickly found
out that the SNMP MIBs included in Netdisco are "outdated".

To try to fix this, we followed the procedure described at
https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs but we are
facing the following issue:

- If we try to update the existing MIBs, it fails because the MIBs
included in Netdisco are relevant for AOS6 but the recent models run on
AOS8. The two software versions are completely different in terms of
features and architecture. As a consequence, the scripts you provide
complain about OIDs that are no longer relevant in AOS8.

- If we try to define a new vendor, it complains about duplicate vendors.

Can you please indicate us a clean way to fix this? In a way or another,
we should be able to define the MIBs for AOS8 without impacting those
for AOS6.

Thanks in advance,

-- 
Quentin Hunin
Ingénieur réseau
Infrastructures de production du système d'information (SIPR)
Place des Sciences, 4 bte L6.08.01
B-1348 - Louvain-la-Neuve, Belgique
quentin.hu...@uclouvain.be



--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 175, Issue 10

[netdisco-users-request]

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. netdisco-deploy skipping environments/deployment.yml
  (Eric W. Bates)
--- Begin Message ---

I just successfully upgraded to App::Netdisco 2.47.4

Our firewall was blocking access to the oui.txt; so I'm re-running 
netdisco-deploy to pull that and now netdisco-deploy fails with:


...
You will be asked to confirm all changes to your system.

So, is all of the above in place? [y/N]: y

Would you like to deploy the database schema? [y/N]: y
DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently 
unversioned. Please call upgrade on your schema to sync the DB. at 
/home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121
DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: 
DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI 
connect('dbname=netdisco','changeme',...) failed: FATAL:  Peer 
authentication failed for user "changeme" at 
/home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1639. at 
/home/netdisco/perl5/bin/netdisco-db-deploy line 110 at 
/home/netdisco/perl5/bin/netdisco-db-deploy line 110

DB schema update complete.
DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently 
unversioned. Please call upgrade on your schema to sync the DB. at 
/home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121
DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI 
connect('dbname=netdisco','changeme',...) failed: FATAL:  Peer 
authentication failed for user "changeme" at 
/home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1639. at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Statistics.pm line 37

Updating statistics... netdisco@netdisco:~$


At a guess, it's using the default credentials "changeme" instead of the 
correct credentials listed in environments/deployment.yml


I'm running the script as user "netdisco" and the permissions to 
deployment.yml look fine.


netdisco-do has no trouble connecting:

netdisco@netdisco:~$ ./bin/netdisco-do psql
[10] 2021-02-24 13:19:06  info App::Netdisco version 2.047004 loaded.
[10] 2021-02-24 13:19:06  info psql:  started at Wed Feb 24 08:19:06 
2021

psql (12.6 (Ubuntu 12.6-0ubuntu0.20.04.1), server 9.5.19)
SSL connection (protocol: TLSv1.2, cipher: ECDHE-RSA-AES256-GCM-SHA384, 
bits: 256, compression: off)

Type "help" for help.

netdisco=>


--
Clark 159a, MS 46
508/289-3112




smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 175, Issue 11

[netdisco-users-request]

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. Supermicro mibs (Richard Klar)
   2. Re: Supermicro mibs (Oliver Gorwits)
--- Begin Message ---
Hi,

I have tried to discover some supermicro equipment most switches, but
netdisco can handle snmp answers from devices.
So it doesnt show links, mac addresses on ports, for example.
Has anybody else tried to discover supermicro devices?

It looks like supermicro mibs isnt included in netdisco mib bundle,
is it easy to include supermicro mibs to netdisco mib bundle?
--- End Message ---
--- Begin Message ---
Hi Richard

The procedure to add or update MIBs in the netdisco-mibs bundle is
documented here:
https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs

good luck

regards
oliver.

On Fri, 26 Feb 2021 at 08:02, Richard Klar  wrote:

> Hi,
>
> I have tried to discover some supermicro equipment most switches, but
> netdisco can handle snmp answers from devices.
> So it doesnt show links, mac addresses on ports, for example.
> Has anybody else tried to discover supermicro devices?
>
> It looks like supermicro mibs isnt included in netdisco mib bundle,
> is it easy to include supermicro mibs to netdisco mib bundle?
> ___
> Netdisco mailing list
> 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

netdisco-users Digest, Vol 177, Issue 4

[netdisco-users-request]

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: (no subject) (Jeroen van Ingen)
--- Begin Message ---

Hi Michael,

Currently I'm working on adding support for Aruba switches in the newer 
ArubaOS-CX product line. Aruba made some choices in the SNMP support 
that make it hard for us to add them; I'm trying to find a solution. 
Will probably take several weeks more before there's a somewhat usable 
level of support in a development version.



Regards,

Jeroen van Ingen, Network Engineer
University of Twente | Library, ICT Services & Archive (LISA)
P.O.Box 217, 7500 AE Enschede, The Netherlands


On 10-03-2021 22:17, Lavin, Michael (ITS) via netdisco-users wrote:

Hello,
My organization has purchased some new Aruba Wired Switches, 6200 
series, 6300 series.

Netdisco lists them as enterprises.47196.1.1.1.xxx
It seems to gather a lot of the other SNMP information just fine.
I was wondering if there are any plans underway to add these to 
Netdisco, or what the process of loading up the MIBs or other procedure 
for getting Netdisco to list them as Aruba switches with an Aruba OS on them


enterprises.47196.4.1.1.1.301
Aruba JL725A 6200F 24G CL4 4SFP+370W Swch ML.10.05.0021
enterprises.47196.4.1.1.1.100
Aruba JL658A 6300M 24SFP+ 4SFP56 Swch FL.10.05.0021
enterprises.47196.4.1.1.1.304
Aruba JL728A 6200F 48G CL4 4SFP+740W Swch ML.10.05.0021


Thank you, to everyone who works to maintain and expand Netdisco. It is 
a wonderful piece of software.


Sincerely,
Michael L.




--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 177, Issue 5

[netdisco-users-request]

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: (no subject) (Muris)
   2. Re: (no subject) (Zuntz Igal)
   3. Re: (no subject) (Jethro Binks)
--- Begin Message ---
Hi Jeroen, is it possible to include Aruba controllers? 

I think the controllers only need a slight tweak with snmp to pull arp tables 
and description of interfaces, as at the moment thats not working.


> On 7 Apr 2021, at 16:52, Jeroen van Ingen  
> wrote:
> 
> Hi Michael,
> 
> Currently I'm working on adding support for Aruba switches in the newer 
> ArubaOS-CX product line. Aruba made some choices in the SNMP support that 
> make it hard for us to add them; I'm trying to find a solution. Will probably 
> take several weeks more before there's a somewhat usable level of support in 
> a development version.
> 
> 
> Regards,
> 
> Jeroen van Ingen, Network Engineer
> University of Twente | Library, ICT Services & Archive (LISA)
> P.O.Box 217, 7500 AE Enschede, The Netherlands
> 
> 
>> On 10-03-2021 22:17, Lavin, Michael (ITS) via netdisco-users wrote:
>> Hello,
>> My organization has purchased some new Aruba Wired Switches, 6200 series, 
>> 6300 series.
>> Netdisco lists them as enterprises.47196.1.1.1.xxx
>> It seems to gather a lot of the other SNMP information just fine.
>> I was wondering if there are any plans underway to add these to Netdisco, or 
>> what the process of loading up the MIBs or other procedure for getting 
>> Netdisco to list them as Aruba switches with an Aruba OS on them
>> enterprises.47196.4.1.1.1.301
>> Aruba JL725A 6200F 24G CL4 4SFP+370W Swch ML.10.05.0021
>> enterprises.47196.4.1.1.1.100
>> Aruba JL658A 6300M 24SFP+ 4SFP56 Swch FL.10.05.0021
>> enterprises.47196.4.1.1.1.304
>> Aruba JL728A 6200F 48G CL4 4SFP+740W Swch ML.10.05.0021
>> Thank you, to everyone who works to maintain and expand Netdisco. It is a 
>> wonderful piece of software.
>> Sincerely,
>> Michael L.
> 
> 
> 


--- End Message ---
--- Begin Message ---
Hi Jeroen,

If needed I'll be happy to assist as a beta user. 

We have 6300, and 8325 switches in our site.

Regards,
Igal Zuntz
Network Administrator 
IT services
Electrical Engineering Department
Technion – Israel Institute of Technology 

Tel: +972-4-8294634  
E-mail: ig...@technion.ac.il  | vee.technion.ac.il
 
-Original Message-
From: Muris  
Sent: Wednesday, April 7, 2021 4:09 PM
To: Jeroen van Ingen 
Cc: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] (no subject)

Hi Jeroen, is it possible to include Aruba controllers?

I think the controllers only need a slight tweak with snmp to pull arp tables 
and description of interfaces, as at the moment thats not working.


> On 7 Apr 2021, at 16:52, Jeroen van Ingen  
> wrote:
>
> Hi Michael,
>
> Currently I'm working on adding support for Aruba switches in the newer 
> ArubaOS-CX product line. Aruba made some choices in the SNMP support that 
> make it hard for us to add them; I'm trying to find a solution. Will probably 
> take several weeks more before there's a somewhat usable level of support in 
> a development version.
>
>
> Regards,
>
> Jeroen van Ingen, Network Engineer
> University of Twente | Library, ICT Services & Archive (LISA) P.O.Box 
> 217, 7500 AE Enschede, The Netherlands
>
>
>> On 10-03-2021 22:17, Lavin, Michael (ITS) via netdisco-users wrote:
>> Hello,
>> My organization has purchased some new Aruba Wired Switches, 6200 series, 
>> 6300 series.
>> Netdisco lists them as enterprises.47196.1.1.1.xxx It seems to gather 
>> a lot of the other SNMP information just fine.
>> I was wondering if there are any plans underway to add these to 
>> Netdisco, or what the process of loading up the MIBs or other 
>> procedure for getting Netdisco to list them as Aruba switches with an 
>> Aruba OS on them
>> enterprises.47196.4.1.1.1.301
>> Aruba JL725A 6200F 24G CL4 4SFP+370W Swch ML.10.05.0021
>> enterprises.47196.4.1.1.1.100
>> Aruba JL658A 6300M 24SFP+ 4SFP56 Swch FL.10.05.0021
>> enterprises.47196.4.1.1.1.304
>> Aruba JL728A 6200F 48G CL4 4SFP+740W Swch ML.10.05.0021 Thank you, to 
>> everyone who works to maintain and expand Netdisco. It is a wonderful piece 
>> of software.
>> Sincerely,
>> Michael L.
>
>
>


___
Netdisco mailing list
netdisco-users@lists.sourceforge.net

netdisco-users Digest, Vol 177, Issue 9

[netdisco-users-request]

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: compliation errors (Ricardo Stella)
   2. Re: compliation errors (Oliver Gorwits)
--- Begin Message ---
Big Duh... Since I was installing a separate poller I wanted to make sure
both were running the same version of netdisco and in case I needed to
upgrade, I did update the OS.

All good now.

On Wed, Apr 14, 2021 at 12:25 PM Oliver Gorwits  wrote:

> Hi Ricardo
>
> Have you recently upgraded the operating system or similar?
>
> regards
> Oliver.
>
> On Wed, 14 Apr 2021 at 17:23, Ricardo Stella  wrote:
>
>>
>> Hi,
>>
>> Noticed the following errors recently - any ideas as to what could be
>> wrong?
>>
>>
>> "_linear_isa" is not exported by the Moo::_Utils module
>> Can't continue after import errors at
>> /home/netdisco/perl5/lib/perl5/Method/Generate/BuildAll.pm line 8.
>> BEGIN failed--compilation aborted at
>> /home/netdisco/perl5/lib/perl5/Method/Generate/BuildAll.pm line 8,
>> <__ANONIO__> line 1273635.
>> Compilation failed in require at
>> /home/netdisco/perl5/lib/perl5/Method/Generate/Constructor.pm line 61,
>> <__ANONIO__> line 1273635.
>>
>> I believe installation is up to date:
>>
>> App::Netdisco 2.47.5
>> SNMP::Info 3.71
>> DB Schema 64
>> PostgreSQL 9.2.24
>> Perl 5.16.3
>>
>> --
>> °(((=((===°°°(((
>> ___
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
>

-- 
°(((=((===°°°(((
--- End Message ---
--- Begin Message ---
No worries :)

Guess you worked out it’s a simple reinstall of netdisco code (db can
remain).

Oliver.

On Wed, 14 Apr 2021 at 18:07, Ricardo Stella  wrote:

>
> Big Duh... Since I was installing a separate poller I wanted to make sure
> both were running the same version of netdisco and in case I needed to
> upgrade, I did update the OS.
>
> All good now.
>
> On Wed, Apr 14, 2021 at 12:25 PM Oliver Gorwits  wrote:
>
>> Hi Ricardo
>>
>> Have you recently upgraded the operating system or similar?
>>
>> regards
>> Oliver.
>>
>> On Wed, 14 Apr 2021 at 17:23, Ricardo Stella  wrote:
>>
>>>
>>> Hi,
>>>
>>> Noticed the following errors recently - any ideas as to what could be
>>> wrong?
>>>
>>>
>>> "_linear_isa" is not exported by the Moo::_Utils module
>>> Can't continue after import errors at
>>> /home/netdisco/perl5/lib/perl5/Method/Generate/BuildAll.pm line 8.
>>> BEGIN failed--compilation aborted at
>>> /home/netdisco/perl5/lib/perl5/Method/Generate/BuildAll.pm line 8,
>>> <__ANONIO__> line 1273635.
>>> Compilation failed in require at
>>> /home/netdisco/perl5/lib/perl5/Method/Generate/Constructor.pm line 61,
>>> <__ANONIO__> line 1273635.
>>>
>>> I believe installation is up to date:
>>>
>>> App::Netdisco 2.47.5
>>> SNMP::Info 3.71
>>> DB Schema 64
>>> PostgreSQL 9.2.24
>>> Perl 5.16.3
>>>
>>
>>>
>>> --
>>> °(((=((===°°°(((
>>> ___
>>> Netdisco mailing list
>>> 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

netdisco-users Digest, Vol 177, Issue 6

[netdisco-users-request]

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. Login (Tim Polimeni)
   2. Re: Login (Christian Ramseyer)
   3. Re: Login (Christian Ramseyer)
   4. Re: Login (Christian Ramseyer)
   5. remote collector (Ricardo Stella)
   6. Re: remote collector (Christian Ramseyer)
--- Begin Message ---
Hello, I havent messed with my netdisco setup in some time as it was a side
project, I can't recall what I used for a login. Is there any way that I
can reset the UID password to regain access?
--- End Message ---
--- Begin Message ---
Hi Tim


On 09.04.21 19:05, Tim Polimeni wrote:
> Hello, I havent messed with my netdisco setup in some time as it was a
> side project, I can't recall what I used for a login. Is there any way
> that I can reset the UID password to regain access?
>



If you remove the admin flag from all users and run netdisco-deploy
again, it will ask to create a new admin user:


$ netdisco-do psql

netdisco => update users set admin = false;
UPDATE 4 (can be any number depending on table content)

netdisco => \q


$ netdisco-deploy
This is the Netdisco 2 deployment script.



So, is all of the above in place? [y/N]: y

Would you like to deploy the database schema? [y/N]: y
DB schema update complete.
Updating statistics... done.

We need to create a user for initial login. This user will be a full
Administrator.
Afterwards, you can go to Admin -> User Management to manage users.

Username:  : admin2
Password:  : hunter2

Cheers
Christian



-- 
Christian Ramseyer, netnea ag
Network Management. Security. OpenSource.


--- End Message ---
--- Begin Message ---


On 09.04.21 20:06, Tim Polimeni wrote:
> Thanks it looks like I have some challenges as well after I updated to
> the lasted version I get the following as well 
> 
> 
> 
> Before we continue, the following prerequisites must be in place:
>  * Database added to PostgreSQL for Netdisco
>  * User added to PostgreSQL with rights to the Netdisco Database
>  * "~/environments/deployment.yml" file configured with Database
> dsn/user/pass
>  * A full backup of any existing Netdisco database data
>  * Internet access (for OUIs and MIBs)
> 
> If you are upgrading Netdisco 2 read the release notes:
> https://github.com/netdisco/netdisco/wiki/Release-Notes
> 
> There you will find required and incompatible changes
> which are not covered by this script.
> 
> You will be asked to confirm all changes to your system.
> 
> So, is all of the above in place? [y/N]: y
> 
> Would you like to deploy the database schema? [y/N]: y
> DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently
> unversioned. Please call upgrade on your schema to sync the DB. at
> /home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121
> DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed:
> DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI
> connect('dbname=netdisco','netdisco',...) failed: FATAL:  remaining
> connection slots are reserved for non-replication superuser connections
> at /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1639.
> at /home/netdisco/perl5/bin/netdisco-db-deploy line 110 at
> /home/netdisco/perl5/bin/netdisco-db-deploy line 110
> DB schema update complete.
> DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently
> unversioned. Please call upgrade on your schema to sync the DB. at
> /home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121
> DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI
> connect('dbname=netdisco','netdisco',...) failed: FATAL:  remaining
> connection slots are reserved for non-replication superuser connections
> at /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1639.
> at /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Statistics.pm line 37
> Updating statistics... [netdisco@netengsrv01 ~]$ 
> 
> 
> [netdisco@netengsrv01 ~]$ netdisco-do psql
> [3955495] 2021-04-09 18:06:06  info App::Netdisco version 2.047005 loaded.
> [3955495] 2021-04-09 18:06:06  info psql:  started at Fri Apr  9
> 14:06:06 2021
> psql: FATAL:  remaining connection slots are reserved for
> non-replication superuser connections
> [3955495] 2021-04-09 18:06:06  info psql: finished at Fri Apr  9
> 14:06:06 2021
> [3955495] 2021-04-09 18:06:06  info psql: status done: psql session closed.
> [netdisco@netengsrv01 ~]$ 
> 

Yes looks like your database is in some trouble. If this is a local
database just for 

netdisco-users Digest, Vol 177, Issue 8

[netdisco-users-request]

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: remote collector (Ricardo Stella)
   2. compliation errors (Ricardo Stella)
   3. Re: compliation errors (Oliver Gorwits)
--- Begin Message ---
No idea why the deploy option would get stuck, but manually imported the
mibs and after that tried a discover and all went well.

Thanks for your help - Ricardo.

On Tue, Apr 13, 2021 at 6:38 AM Christian Ramseyer 
wrote:

> Hi Ricardo
>
> Yes unfortunately we don't have a full description of the installation
> of a second poller, and as you notice there are some potential questions
> and variants how to do it.
>
> On 13.04.21 06:54, Ricardo Stella wrote:
> > Thanks - I'm having some issues however.
> >
> > Figuring I don't need the postgres server, I did not install that RPM.
> > I then opened up the 5432 port in the main netdisco db server, changed
> > the psql-hba file to allow remote access, and verified connectivity
> > using the psql client. I then configured the deployment.xml and added
> > the host/port entry for the DB.
>
> That's spot on, the postgres server is not needed, just enough Postgres
> packages to successfully connect to the main server. Sounds like that is
> working for you.
>
> >
> > Finally on the remote collector, I tried running netdisco-deploy except
> > I said No to deploy database schema. But it gets stuck after "download
> > and update OUI data".  I also tried doing it by passing ./oui.txt as a
> > parameter (like for non-internet access installations).
>
> I'm not sure why this happens, but the OUI step just copies the file
> into the database, so there is no need to do that a second time and you
> can just skip it.
>
> However I think the mibs should be updated locally and kept in sync with
> the main server. So the "download mibs" step is the only thing that
> should succeed. Or if it doesn't, just copy the mibhome directory
> (https://github.com/netdisco/netdisco/wiki/Configuration#mibhome) from
> the main server.
>
> BTW whether you do the update of the db schema also shouldn't matter,
> the remote poller would just see that it's already up-to-date and not
> change anything.
>
> So once you're  past the mibs step your remote netdisco should be good
> to go.
>
> To test it, the easiest way would be to discover a device from your
> remote network on the command line, e.g.
>
> netdisco-do -D discover -d 192.168.3.99
>
> You should see errors regarding db connection etc. straight away in you
> terminal, an afterwards you should be able to find the device in your
> main Netdisco.
>
> Let us know if you encounter more issues, then we can maybe also put
> them in the Wiki as a guide for future readers.
>
> Cheers
> Christian
>
>

-- 
°(((=((===°°°(((
--- End Message ---
--- Begin Message ---
Hi,

Noticed the following errors recently - any ideas as to what could be
wrong?


"_linear_isa" is not exported by the Moo::_Utils module
Can't continue after import errors at
/home/netdisco/perl5/lib/perl5/Method/Generate/BuildAll.pm line 8.
BEGIN failed--compilation aborted at
/home/netdisco/perl5/lib/perl5/Method/Generate/BuildAll.pm line 8,
<__ANONIO__> line 1273635.
Compilation failed in require at
/home/netdisco/perl5/lib/perl5/Method/Generate/Constructor.pm line 61,
<__ANONIO__> line 1273635.

I believe installation is up to date:

App::Netdisco 2.47.5
SNMP::Info 3.71
DB Schema 64
PostgreSQL 9.2.24
Perl 5.16.3

-- 
°(((=((===°°°(((
--- End Message ---
--- Begin Message ---
Hi Ricardo

Have you recently upgraded the operating system or similar?

regards
Oliver.

On Wed, 14 Apr 2021 at 17:23, Ricardo Stella  wrote:

>
> Hi,
>
> Noticed the following errors recently - any ideas as to what could be
> wrong?
>
>
> "_linear_isa" is not exported by the Moo::_Utils module
> Can't continue after import errors at
> /home/netdisco/perl5/lib/perl5/Method/Generate/BuildAll.pm line 8.
> BEGIN failed--compilation aborted at
> /home/netdisco/perl5/lib/perl5/Method/Generate/BuildAll.pm line 8,
> <__ANONIO__> line 1273635.
> Compilation failed in require at
> /home/netdisco/perl5/lib/perl5/Method/Generate/Constructor.pm line 61,
> <__ANONIO__> line 1273635.
>
> I believe installation is up to date:
>
> App::Netdisco 2.47.5
> SNMP::Info 3.71
> DB Schema 64
> PostgreSQL 9.2.24
> Perl 5.16.3
>
> --
> °(((=((===°°°(((
> 

netdisco-users Digest, Vol 177, Issue 7

[netdisco-users-request]

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: remote collector (Ricardo Stella)
   2. Re: remote collector (Christian Ramseyer)
--- Begin Message ---
Thanks - I'm having some issues however.

Figuring I don't need the postgres server, I did not install that RPM.  I
then opened up the 5432 port in the main netdisco db server, changed the
psql-hba file to allow remote access, and verified connectivity using the
psql client. I then configured the deployment.xml and added the host/port
entry for the DB.

Finally on the remote collector, I tried running netdisco-deploy except I
said No to deploy database schema. But it gets stuck after "download and
update OUI data".  I also tried doing it by passing ./oui.txt as a
parameter (like for non-internet access installations).

Should I do a full install including the postgres DB, then change
deployment.xml and shut down that local DB? Or am I missing something?

TIA.

On Sat, Apr 10, 2021 at 4:55 AM Christian Ramseyer 
wrote:

>
>
> On 09.04.21 22:56, Ricardo Stella wrote:
> >
> > We had a site that was directly connected to us in the past that now it
> > has become a semi separate network and we no longer can directly see
> > it's devices.  I found a thread where Oliver says you could run a remote
> > "netdisco-backend" and have it report to the main DB and web front end.
> >
> > If so, would the process be just do a full install but then have
> > netdisco-backend point to the main system? How would this be done? Am I
> > missing a Wiki entry here?
>
> Hi Ricardo
>
> Yes that is pretty much it, just install a second Netdisco but change
> the database: settings in it to point to the "main" database. Use
> devices_no/devices_only to distribute your networks between the two.
>
> There is a short bit about it in the wiki here:
>
>
> https://github.com/netdisco/netdisco/wiki/Install-Tips#run-multiple-poller-daemons
>
>
> Cheers
> Christian
>


-- 
°(((=((===°°°(((
--- End Message ---
--- Begin Message ---
Hi Ricardo

Yes unfortunately we don't have a full description of the installation
of a second poller, and as you notice there are some potential questions
and variants how to do it.

On 13.04.21 06:54, Ricardo Stella wrote:
> Thanks - I'm having some issues however.
> 
> Figuring I don't need the postgres server, I did not install that RPM. 
> I then opened up the 5432 port in the main netdisco db server, changed
> the psql-hba file to allow remote access, and verified connectivity
> using the psql client. I then configured the deployment.xml and added
> the host/port entry for the DB.

That's spot on, the postgres server is not needed, just enough Postgres
packages to successfully connect to the main server. Sounds like that is
working for you.

> 
> Finally on the remote collector, I tried running netdisco-deploy except
> I said No to deploy database schema. But it gets stuck after "download
> and update OUI data".  I also tried doing it by passing ./oui.txt as a
> parameter (like for non-internet access installations).

I'm not sure why this happens, but the OUI step just copies the file
into the database, so there is no need to do that a second time and you
can just skip it.

However I think the mibs should be updated locally and kept in sync with
the main server. So the "download mibs" step is the only thing that
should succeed. Or if it doesn't, just copy the mibhome directory
(https://github.com/netdisco/netdisco/wiki/Configuration#mibhome) from
the main server.

BTW whether you do the update of the db schema also shouldn't matter,
the remote poller would just see that it's already up-to-date and not
change anything.

So once you're  past the mibs step your remote netdisco should be good
to go.

To test it, the easiest way would be to discover a device from your
remote network on the command line, e.g.

netdisco-do -D discover -d 192.168.3.99

You should see errors regarding db connection etc. straight away in you
terminal, an afterwards you should be able to find the device in your
main Netdisco.

Let us know if you encounter more issues, then we can maybe also put
them in the Wiki as a guide for future readers.

Cheers
Christian



--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 177, Issue 10

[netdisco-users-request]

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. Netdisco behind a Firewall (Christopher Doolan)
--- Begin Message ---
Hi Guys, the issue I am experiencing is that the Netdisco installed behind a 
firewall cannot connect to a test switch using netdisco-do -discover.

info discover: status defer: discover failed: could not SNMP connect to ...

However, the dev netdisco that I use at my desk is able to connect to the test 
switch using netdisco-do -discover.

Info discover: status done: Ended discover for .

This would appear to be a Firewall issue, however the switch has an ACL 
configure to limit what SNMP can connect to it and I am not sure if this is the 
problem even though both IP addresses are in the ACL.

What I would like to do is use snmpget to try and connect to the test switch 
from both Netdiscos, but I found that dev netdisco cannot be connect using 
snmpget, which complicates things.

Here is an example of the snmpget command I have been trying to use on dev 
netdisco.

snmpget -v 2c -c [my community] xxx.xxx.xxx.xxx sysobjectID.0

Shouldn't this work if the community is the same as what is in the Netdisco 
deployment.yml?

Device_auth:

-  tag: 'default_v2_readonly'

community: '[my community]'

read: true

write: false

What am I missing?

Regards
Chris Doolan


__

This email (including any attached files) is confidential and is 

for the intended recipient(s) only. If you received this email by 

mistake, please, as a courtesy, tell the sender, then delete this 

email.

The views and opinions are the originator's and do not necessarily 

reflect those of the University of Southern Queensland. Although 

all reasonable precautions were taken to ensure that this email 

contained no viruses at the time it was sent we accept no 

liability for any losses arising from its receipt.

The University of Southern Queensland is a registered provider 

of education with the Australian Government.

(CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081)
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 177, Issue 11

[netdisco-users-request]

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: Netdisco behind a Firewall (Michael Butash)
   2. Re: Netdisco behind a Firewall (Christopher Doolan)
--- Begin Message ---
No reason for it NOT to work unless the firewall is denying the traffic, or
doesn't have routes back to it (blackhole at worst, async routing at
best).  Perhaps NAT needs involved, or not involved?

I do netdisco and other snmp tools a lot over firewalls, usually remote
when possible, through VPN's and other tunneling mechanisms, so I know it's
possible, seems just incomplete policy, routing, or nat behaviour of your
devices.  Check that you're getting the snmp query first at the endpoint
device via snmp debugging, and then verify you're getting the return
traffic back to your ND server, or identify where in path it's getting
eaten.

-mb


On Mon, Apr 19, 2021 at 11:31 PM Christopher Doolan <
christopher.doo...@usq.edu.au> wrote:

> Hi Guys, the issue I am experiencing is that the Netdisco installed behind
> a firewall cannot connect to a test switch using netdisco-do –discover.
>
>
>
> info discover: status defer: discover failed: could not SNMP connect to …
>
>
>
> However, the dev netdisco that I use at my desk is able to connect to the
> test switch using netdisco-do –discover.
>
>
>
> Info discover: status done: Ended discover for …..
>
>
>
> This would appear to be a Firewall issue, however the switch has an ACL
> configure to limit what SNMP can connect to it and I am not sure if this is
> the problem even though both IP addresses are in the ACL.
>
>
>
> What I would like to do is use snmpget to try and connect to the test
> switch from both Netdiscos, but I found that dev netdisco cannot be connect
> using snmpget, which complicates things.
>
>
>
> Here is an example of the snmpget command I have been trying to use on dev
> netdisco.
>
>
>
> snmpget -v 2c -c [my community] xxx.xxx.xxx.xxx
> sysobjectID.0
>
>
>
> Shouldn’t this work if the community is the same as what is in the
> Netdisco deployment.yml?
>
>
>
> Device_auth:
>
> -  tag: ‘default_v2_readonly’
>
> community: ‘[my community]’
>
> read: true
>
> write: false
>
>
>
> What am I missing?
>
>
>
> Regards
>
> Chris Doolan
>
>
>
>
> __
> This email (including any attached files) is confidential and is
> for the intended recipient(s) only. If you received this email by
> mistake, please, as a courtesy, tell the sender, then delete this
> email.
> The views and opinions are the originator's and do not necessarily
> reflect those of the University of Southern Queensland. Although
> all reasonable precautions were taken to ensure that this email
> contained no viruses at the time it was sent we accept no
> liability for any losses arising from its receipt.
> The University of Southern Queensland is a registered provider
> of education with the Australian Government.
> (CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081)
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
--- End Message ---
--- Begin Message ---
Thanks Michael

Regards

Chris Doolan
From: Michael Butash 
Sent: Wednesday, 21 April 2021 2:01 AM
To: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Netdisco behind a Firewall

No reason for it NOT to work unless the firewall is denying the traffic, or 
doesn't have routes back to it (blackhole at worst, async routing at best).  
Perhaps NAT needs involved, or not involved?

I do netdisco and other snmp tools a lot over firewalls, usually remote when 
possible, through VPN's and other tunneling mechanisms, so I know it's 
possible, seems just incomplete policy, routing, or nat behaviour of your 
devices.  Check that you're getting the snmp query first at the endpoint device 
via snmp debugging, and then verify you're getting the return traffic back to 
your ND server, or identify where in path it's getting eaten.

-mb


On Mon, Apr 19, 2021 at 11:31 PM Christopher Doolan 
mailto:christopher.doo...@usq.edu.au>> wrote:
Hi Guys, the issue I am experiencing is that the Netdisco installed behind a 
firewall cannot connect to a test switch using netdisco-do –discover.

info discover: status defer: discover failed: could not SNMP connect to …

However, the dev netdisco that I use at my desk 

netdisco-users Digest, Vol 175, Issue 6

[netdisco-users-request]

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: Polling failures (Oliver Gorwits)
   2. Re: LLDP phone info extension number (Oliver Gorwits)
--- Begin Message ---
Hi Charlie

It is interesting that the jobs start and never complete. Netdisco should
either timeout on long running jobs (over 10 minutes) or else if the worker
dies abruptly, the job is defined as stale and eventually ignored.

Assuming you have an up to date version of Netdisco running, here are the
config options to try tweaking:

jobs_stale_after - this is a number of seconds and defaults to 50 minutes,
after which these jobs should be repeated. Try an aggressively lower
setting.
workers: retry_after - amount of time after which to ignore failures and
retry connecting to a device.

https://github.com/netdisco/netdisco/wiki/Configuration#workers
and
https://github.com/netdisco/netdisco/wiki/Configuration#jobs_stale_after

I'll have a look at this as well just to see if I can reproduce.

Good luck,

regards
Oliver.

On Fri, 12 Feb 2021 at 15:13, Charlie Butera via netdisco-users <
netdisco-users@lists.sourceforge.net> wrote:

> Hello,
>
> I am having an issue where various jobs (discover, arpnip & macsuck) fail
> on random devices and never complete. This results in a stuck state since
> the device is never polled successfully from that point on (for the
> respective job).
>
> Example Host 10.x.x.x
> Last Discover 2021-02-04 19:04
> Last Arpnip 2021-02-05 16:20
> Last Macsuck 2021-02-04 21:00
>
> Query to view stuck jobs for that host (apologies for display of table, I
> tried sending an image but it didnt send pending "moderator can review it
> for approval")
>
> ~ $ ./bin/netdisco-do psql -e "SELECT * FROM admin WHERE finished IS NULL
> AND device = '10.x.x.x'"
> [459] 2021-02-12 14:53:33  info App::Netdisco version 2.047002 loaded.
> [459] 2021-02-12 14:53:33  info psql:  started at Fri Feb 12 14:53:33 2021
>   job  |  entered   |  started   |
> finished |  device  | port |  action  | subaction |  status
> | username | userip | log | debug | device_key
>
> ---+++--+--+--+--+---+-+--++-+---+
>   3064 | 2021-02-04 20:00:36.570694 | 2021-02-04 20:00:48.60293  |
>  | 10.x.x.x |  | discover |   | queued-netdisco-backend |
>|| |   |
>   6178 | 2021-02-04 21:50:43.342499 | 2021-02-04 21:50:45.729956 |
>  | 10.x.x.x |  | macsuck  |   | queued-netdisco-backend |
>|| |   |
>  10449 | 2021-02-05 17:20:32.251217 | 2021-02-05 17:20:33.91666  |
>  | 10.x.x.x |  | arpnip   |   | queued-netdisco-backend |
>|| |   |
> (3 rows)
>
> [459] 2021-02-12 14:53:33  info psql: finished at Fri Feb 12 14:53:33 2021
> [459] 2021-02-12 14:53:33  info psql: status done: psql session closed.
>
> However when I run a ./bin/netdisco-do manually or trigger the job via the
> web ui it completes successfully.
> ~ $ ./bin/netdisco-do macsuck -d 10.x.x.x
> [17326] 2021-02-12 15:04:57  info App::Netdisco version 2.047002 loaded.
> [17326] 2021-02-12 15:04:57  info macsuck: [10.x.x.x] started at Fri Feb
> 12 15:04:57 2021
> [17326] 2021-02-12 15:04:59  info macsuck: finished at Fri Feb 12 15:04:59
> 2021
> [17326] 2021-02-12 15:04:59  info macsuck: status done: Ended macsuck for
> 10.x.x.x
>
> Software Version
> App::Netdisco 2.47.2
> SNMP::Info 3.71
> DB Schema 64
> PostgreSQL 12.00.2
> Perl 5.30.3
>
> Deployment Info:
> 1 netdisco-backend (docker container)
> 1 netdisco-web (docker container)
> 1 netdisco-postgres (docker container)
>
>
>
>
> *Charles Butera*
>
> *Network Engineer*
>
> cbut...@squarespace.com 
>
> Squarespace
>
> Squarespace.com
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi Ricardo

Does the device_port_properties table of the database contain anything
useful for these ports? This is additional data not always shown in the web
interface.

regards
Oliver

On Tue, 9 Feb 2021 at 17:50, Ricardo Stella  wrote:

> Hi,
>
> Following up on this. Am I missing a package or something?
>
> I would also like to have access points names show up - this info does
> show via lldp.
>
> Thanks - Ricardo.

netdisco-users Digest, Vol 175, Issue 5

[netdisco-users-request]

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. AD authentication - LDAP config (Christopher Doolan)
   2. Re: AD authentication - LDAP config (Oliver Gorwits)
--- Begin Message ---
Hi everyone, here is something I noticed regarding configuration of LDAP.

Using Red Hat Enterprise Linux release 8.3, I tried to use the following ldap 
config.

ldap:
servers:
 - '10.x.x.x'
  user_string: '%USER%@FQDN'
  opts:
  version: 3
   debug: 0

This failed and I kept on getting the error of "Unable to parse the 
configuration file:", with "did not find expected key".

Apparently it did not like the user_string;
user_string: '%USER%@FQDN'
(I try using '%USER%@DOMAIN' which I found worked in my CentOS 
7.8 dev box, but this too failed)

I also tried changing to the following, but the same error appeared;
user_string: 'DOMAIN\%USER%'

After search and reading this mailing list (thank you), I found this and it 
worked;
ldap:
   servers: [10.xx.xx.xx, 10.xx.xx.xy, 10.xx.xx.xz]
   user_string: 'DOMAIN\%USER%'

I hope that this will be of help to someone else having their own issues with 
ldap.

Regards
Chris
__

This email (including any attached files) is confidential and is 

for the intended recipient(s) only. If you received this email by 

mistake, please, as a courtesy, tell the sender, then delete this 

email.

The views and opinions are the originator's and do not necessarily 

reflect those of the University of Southern Queensland. Although 

all reasonable precautions were taken to ensure that this email 

contained no viruses at the time it was sent we accept no 

liability for any losses arising from its receipt.

The University of Southern Queensland is a registered provider 

of education with the Australian Government.

(CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081)
--- End Message ---
--- Begin Message ---
Thanks Chris!

I have added a note to the LDAP config with these examples for 7.x and 8.x

On Tue, 16 Feb 2021 at 06:02, Christopher Doolan <
christopher.doo...@usq.edu.au> wrote:

> Hi everyone, here is something I noticed regarding configuration of LDAP.
>
>
>
> Using Red Hat Enterprise Linux release 8.3, I tried to use the following
> ldap config.
>
>
>
> ldap:
>
> servers:
>
>  - '10.x.x.x'
>
>   user_string: '%USER%@FQDN’
>
>   opts:
>
>   version: 3
>
>debug: 0
>
>
>
> This failed and I kept on getting the error of “Unable to parse the
> configuration file:”, with “did not find expected key”.
>
>
>
> Apparently it did not like the user_string;
>
> user_string: '%USER%@FQDN’
>
> (I try using ‘%USER%@DOMAIN’ which I found worked in my
> CentOS 7.8 dev box, but this too failed)
>
>
>
> I also tried changing to the following, but the same error appeared;
>
> user_string: 'DOMAIN\%USER%’
>
>
>
> After search and reading this mailing list (thank you), I found this and
> it worked;
>
> ldap:
>
>servers: [10.xx.xx.xx, 10.xx.xx.xy, 10.xx.xx.xz]
>
>user_string: 'DOMAIN\%USER%'
>
>
>
> I hope that this will be of help to someone else having their own issues
> with ldap.
>
>
>
> Regards
>
> Chris
> __
> This email (including any attached files) is confidential and is
> for the intended recipient(s) only. If you received this email by
> mistake, please, as a courtesy, tell the sender, then delete this
> email.
> The views and opinions are the originator's and do not necessarily
> reflect those of the University of Southern Queensland. Although
> all reasonable precautions were taken to ensure that this email
> contained no viruses at the time it was sent we accept no
> liability for any losses arising from its receipt.
> The University of Southern Queensland is a registered provider
> of education with the Australian Government.
> (CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081)
> ___
> Netdisco mailing list
> 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

netdisco-users Digest, Vol 175, Issue 7

[netdisco-users-request]

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: Dell N2024 - snmp discovery not working (Oliver Gorwits)
   2. Re: LLDP phone info extension number (Ricardo Stella)
--- Begin Message ---
Hi Paweł

If you add the ND2_SHOW_COMMUNITY=1 environment to the netdisco-do debug,
you can also check Netdisco is using the correct community string.

regards
Oliver

On Thu, 11 Feb 2021 at 09:24, Moszumański Paweł <
pawel.moszuman...@pl.toyota-industries.eu> wrote:

> Hi
>
> Netdisco installed yesterday (current version)  – everything works smooth
> with Cisco switches and some other Dells but Dell N2024 is a problem
>
> Cant connect to it.
>
>
>
>
>
>
>
> netdisco-do discover -DI -d X.X.X.X
>
> [15504] 2021-02-11 09:02:12  info App::Netdisco version 2.047002 loaded.
>
> [15504] 2021-02-11 09:02:14  info discover: [X.X.X.X] started at Thu Feb
> 11 10:02:14 2021
>
> [15504] 2021-02-11 09:02:14 debug discover: running with timeout 600s
>
> [15504] 2021-02-11 09:02:14 debug => running workers for phase: check
>
> [15504] 2021-02-11 09:02:14 debug -> run worker check/_base_/0
>
> [15504] 2021-02-11 09:02:14 debug Discover is able to run.
>
> [15504] 2021-02-11 09:02:14 debug => running workers for phase: early
>
> [15504] 2021-02-11 09:02:14 debug -> run worker early/properties/100
>
> [15504] 2021-02-11 09:02:14 debug snmp reader cache warm: [X.X.X.X]
>
> [15504] 2021-02-11 09:02:14 debug [X.X.X.X:161] try_connect with ver: 2,
> class: SNMP::Info, comm: 
>
> SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
> .1.3.6.1.2.1.1.3.0
>
> SNMP::Info::_global(uptime) Timeout at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Transport/SNMP.pm line 245.
>
> [15504] 2021-02-11 09:02:29 debug [X.X.X.X:161] try_connect with ver: 1,
> class: SNMP::Info, comm: 
>
> SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
> .1.3.6.1.2.1.1.3.0
>
> SNMP::Info::_global(uptime) Timeout at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Transport/SNMP.pm line 245.
>
> [15504] 2021-02-11 09:02:39 debug discover failed: could not SNMP connect
> to X.X.X.X
>
> [15504] 2021-02-11 09:02:39 debug -> run worker early/properties/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker early/properties/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker early/properties/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker early/properties/100
>
> [15504] 2021-02-11 09:02:39 debug => running workers for phase: main
>
> [15504] 2021-02-11 09:02:39 debug -> run worker main/canonicalip/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker main/entities/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker main/neighbors/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker main/neighbors/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker main/neighbors/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker main/portpower/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker main/portproperties/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker main/vlans/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker main/wireless/100
>
> [15504] 2021-02-11 09:02:39 debug -> run worker main/withnodes/0
>
> [15504] 2021-02-11 09:02:39 debug => running workers for phase: late
>
> [15504] 2021-02-11 09:02:39 debug -> run worker late/hooks/0
>
> [15504] 2021-02-11 09:02:39 debug  [X.X.X.X] hooks - 0 queued
>
> [15504] 2021-02-11 09:02:39  info discover: finished at Thu Feb 11
> 10:02:39 2021
>
> [15504] 2021-02-11 09:02:39  info discover: status defer: discover failed:
> could not SNMP connect to X.X.X.X
>
>
>
> But snmpget, smnpwalk and snmstatus works fine
>
> snmpget -v 2c -c ***   X.X.X.X  .1.3.6.1.2.1.1.3.0
>
> iso.3.6.1.2.1.1.3.0 = Timeticks: (948676300) 109 days, 19:12:43.00
>
>
>
> snmpstatus -v 2c -c *** X.X.X.X
>
> [UDP: [X.X.X.X]:161->[0.0.0.0]:32983]=>[Dell Networking N2024, 6.1.2.4,
> Linux 3.6.5-601418a5] Up: 109 days, 19:13:28.00
>
> Interfaces: 158, Recv/Trans packets: -1598118246/-1048259727 | IP:
> 134172974/1771698
>
> 150 interfaces are down!
>
>
>
> Zabbix also works fine with this switch.. only netdisco can’t cope with
> communication
>
>
>
> Tried many options – timeouts, no bulks and no positive result ☹
>
> PM
>
>
>
>
>
> Information classification: Internal
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi 

netdisco-users Digest, Vol 175, Issue 3

[netdisco-users-request]

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. Polling failures (Charlie Butera)
--- Begin Message ---
Hello,

I am having an issue where various jobs (discover, arpnip & macsuck) fail
on random devices and never complete. This results in a stuck state since
the device is never polled successfully from that point on (for the
respective job).

Example Host 10.x.x.x
Last Discover 2021-02-04 19:04
Last Arpnip 2021-02-05 16:20
Last Macsuck 2021-02-04 21:00

Query to view stuck jobs for that host (apologies for display of table, I
tried sending an image but it didnt send pending "moderator can review it
for approval")

~ $ ./bin/netdisco-do psql -e "SELECT * FROM admin WHERE finished IS NULL
AND device = '10.x.x.x'"
[459] 2021-02-12 14:53:33  info App::Netdisco version 2.047002 loaded.
[459] 2021-02-12 14:53:33  info psql:  started at Fri Feb 12 14:53:33 2021
  job  |  entered   |  started   | finished
|  device  | port |  action  | subaction |  status |
username | userip | log | debug | device_key
---+++--+--+--+--+---+-+--++-+---+
  3064 | 2021-02-04 20:00:36.570694 | 2021-02-04 20:00:48.60293  |
 | 10.x.x.x |  | discover |   | queued-netdisco-backend |
   || |   |
  6178 | 2021-02-04 21:50:43.342499 | 2021-02-04 21:50:45.729956 |
 | 10.x.x.x |  | macsuck  |   | queued-netdisco-backend |
   || |   |
 10449 | 2021-02-05 17:20:32.251217 | 2021-02-05 17:20:33.91666  |
 | 10.x.x.x |  | arpnip   |   | queued-netdisco-backend |
   || |   |
(3 rows)

[459] 2021-02-12 14:53:33  info psql: finished at Fri Feb 12 14:53:33 2021
[459] 2021-02-12 14:53:33  info psql: status done: psql session closed.

However when I run a ./bin/netdisco-do manually or trigger the job via the
web ui it completes successfully.
~ $ ./bin/netdisco-do macsuck -d 10.x.x.x
[17326] 2021-02-12 15:04:57  info App::Netdisco version 2.047002 loaded.
[17326] 2021-02-12 15:04:57  info macsuck: [10.x.x.x] started at Fri Feb 12
15:04:57 2021
[17326] 2021-02-12 15:04:59  info macsuck: finished at Fri Feb 12 15:04:59
2021
[17326] 2021-02-12 15:04:59  info macsuck: status done: Ended macsuck for
10.x.x.x

Software Version
App::Netdisco 2.47.2
SNMP::Info 3.71
DB Schema 64
PostgreSQL 12.00.2
Perl 5.30.3

Deployment Info:
1 netdisco-backend (docker container)
1 netdisco-web (docker container)
1 netdisco-postgres (docker container)




*Charles Butera*

*Network Engineer*

cbut...@squarespace.com 

Squarespace

Squarespace.com
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 175, Issue 4

[netdisco-users-request]

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: Netdisco 2.47.2: Perl error when using API
  /api/v1/object/device/ip/port_vlans (Oliver Gorwits)
--- Begin Message ---
Hi Vincent

Thanks for the report, I found the problem and the fix will be in the next
release of Netdisci

regards
oliver

On Mon, 25 Jan 2021 at 08:15, Vincent Feyaerts <
vincent.feyae...@uantwerpen.be> wrote:

> Hi,
>
>
>
> I am using the API on Netdisco 2.47.2, Perl 5.30.0. It’s all working,
> except for the method port_vlans. This gives the following error:
>
>
>
> [406752] 2021-01-25 07:56:18 error request to GET
> /api/v1/object/device/[working public ip, redacted]/port_vlans crashed:
> encountered object
> 'App::Netdisco::DB::Result::DevicePort=HASH(0x55c2e4f0ab30)', but neither
> allow_blessed, convert_blessed nor allow_tags settings are enabled (or
> TO_JSON/FREEZE method missing) at /home/netdisco/perl5/lib/perl5/JSON.pm
> line 173.
>
>
>
> My OS:
>
>
>
> Distributor ID: Ubuntu
>
> Description:Ubuntu 20.04.1 LTS
>
> Release:20.04
>
> Codename:   focal
>
>
>
> Has anybody else encountered this error?
>
>
>
> Thank you
>
> Vincent Feyaerts
>
> Network admin
>
> University of Antwerp
> ___
> Netdisco mailing list
> 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

netdisco-users Digest, Vol 175, Issue 9

[netdisco-users-request]

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: LLDP phone info extension number (Dean, Barry)
--- Begin Message ---
I have discovery of my Mitel phones and Cisco APs off as well, only because 
with discovery on, ND2 queues jobs to discover them via SNMP which it can’t do 
and I end up with thousands of stuck jobs in the queue!

Would be useful to record something though.

Get Outlook for iOS

From: Jethro Binks 
Sent: Wednesday, February 17, 2021 7:14:44 PM
To: netdisco-users@lists.sourceforge.net 
Subject: Re: [Netdisco] LLDP phone info extension number

I'm interested in this too.  Also have Mitel phones that are noticed:

[54561] 2021-02-17 19:04:01 debug  [10.3.6.24] neigh - 10.6.4.164 with ID 
[10.6.4.164] on GigabitEthernet2/0/46
[54561] 2021-02-17 19:04:01 debug is_discoverable: 10.6.4.164 matches 
phone_platforms but discover_phones is not enabled
[54561] 2021-02-17 19:04:01 debug  [10.3.6.24] neigh - skip: 10.6.4.164 of type 
[regDN ,MITEL 5320 IP,h/w rev 0,ASIC rev 1,f/w Boot 05.02.02.01,f/w Main 
05.02.03.01] excluded by discover_* config

but I've looked in the device_port_properties table and while remote_is_phone 
is true, there are no other details stored for it.  Likewise, my phones are 
also set to discover_no.  So are my APs, and I also think it would be useful to 
see my AP names on switch ports in ND, as reported from LLDP.

Web interface just shows "10.6.6.35 - LAN port" (with ip phone and inaccessible 
neighbour icons)

Is this a deficiency in the SNMP::Info modules?  Any clues on where to look to 
see what might need to be done to populate device_port_properties with 
something more useful that doesn't require query of the device itself?

(JvI alert, yes this is H3C in my case, Ricardo's looks more Ciscoish).

Jethro.


.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .

Jethro R Binks, Network Manager,

Information Services Directorate, University Of Strathclyde, Glasgow, UK


The University of Strathclyde is a charitable body, registered in Scotland, 
number SC015263.


From: Ricardo Stella 
Sent: 17 February 2021 18:00
To: Oliver Gorwits 
Cc: netdisco-users@lists.sourceforge.net 
Subject: Re: [Netdisco] LLDP phone info extension number

Hi Oliver,

Thanks for getting back to me. Not sure if it's on the device_port_properties 
table as I'm not sure how to query it.

That said, I ran a discover with debug and this showed:

[14943] 2021-02-17 17:36:31 debug  [10.0.99.220] neigh - skip: 10.200.0.164 of 
type [regDN 2555,MINET_6920,ver: 01.05.03.027,PxE: 6.5,17/02/2021 12:36:06 
+] excluded by discover_* config

And in the environments file I don't have discover_phones true - I guess this 
is why it aint' working? I had this as per the suggestion in order to avoid 
SNMP queries.

Thanks - Ricardo.


On Wed, Feb 17, 2021 at 8:04 AM Oliver Gorwits 
mailto:oli...@cpan.org>> wrote:
Hi Ricardo

Does the device_port_properties table of the database contain anything useful 
for these ports? This is additional data not always shown in the web interface.

regards
Oliver

On Tue, 9 Feb 2021 at 17:50, Ricardo Stella 
mailto:ste...@rider.edu>> wrote:
Hi,

Following up on this. Am I missing a package or something?

I would also like to have access points names show up - this info does show via 
lldp.

Thanks - Ricardo.


On Wed, Jan 13, 2021 at 10:56 AM Ricardo Stella 
mailto:ste...@rider.edu>> wrote:
Hi folks,

We recently deployed a new phone system and noticed that the IP phones are 
giving us the extension number via LLDP on the switches, but not showing up in 
Netdisco.

Here's an example on the switch I get:
sh lldp neighbors
Device ID   Local Intf Hold-time  Capability  Port ID
regDN 1234,MINET_692Gi3/0/18   120B,T 0100.aaa.bbb

"1234" is the extension number assigned to this IP phone.  It is part of the 
"System Name:
System Name: regDN 1234,MINET_6920

But on Netdisco, I only see the following information:
10.1.2.50 - Port 1
(id: SEP080AAA type: MINET_6920 )

Would love to be able to display the extension in netdisco and even better, 
able to search for it.

Any ideas?  Ricardo.


--
°(((=((===°°°(((


--
°(((=((===°°°(((
___
Netdisco mailing list

netdisco-users Digest, Vol 181, Issue 7

[netdisco-users-request]

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: wap_platforms and phone_platforms (Ricardo Stella)
--- Begin Message ---
Ad-block - ugh - what's odd it was the only icon being blocked. Thanks.

Now, how to get LLDP system name?

On Fri, Aug 13, 2021 at 11:24 AM Nick Nauwelaerts <
nick.nauwelae...@aquafin.be> wrote:

> that icon comes from font-awesome which we ship with netdisco. just to be
> sure i doublechecked the woff file.
>
>
>
> if it doesn't show up for you it is most likely a local issue:
>
> * you have an adblocker active which blocks this
>
> * you have tracking protection active in your browser
>
> * you have a local version of font-awesome installed which doesn't include
> this icon
>
> * you've disabled remote fonts in your browser
>
>
>
>
>
> tested on windows in both normal & private browsing mode with:
>
> * firefox 91.0
>
> * chrome 92.0.4515.131
>
> * edge chromium
>
>
>
> does your browser give any errors in web dev mode? (f12 to activate that
> in most browsers)
>
>
>
>
>
> // nick
>
>
>
> *From:* Ricardo Stella 
> *Sent:* Thursday, August 12, 2021 16:10
> *To:* Oliver Gorwits 
> *Cc:* netdisco-users@lists.sourceforge.net
> *Subject:* Re: [Netdisco] wap_platforms and phone_platforms
>
>
>
>
>
> Thanks for this - I don't think they have SNMP access but was curious as
> to why they don't show a wireless access point or wireless client icon.
> Though I just noticed there's no actual icon for wireless access point.
>
>
>
>
>
>
>
> Now, the next issue is there anyway to get the System Name to populate and
> be searchable? The info does show up in LLDP on the switch but doesn't seem
> to be grabbed by Netdisco.  Same goes for phones which do include their
> extension
>
>
>
> System Name: regDN 1234,MINET_6920
>
> System Name: Test_AP
>
>
>
> Thanks - Ricardo.
>
>
>
>
>
> On Thu, Aug 12, 2021 at 6:27 AM Oliver Gorwits  wrote:
>
> Hi,
>
>
>
> You shouldn't need to mess with wap_platforms or wap_capabilities, if the
> APs are fairly modern.
>
>
>
> This is more likely that Netdisco doesn't recognise them as devices or
> they are not responding to SNMP sufficiently. This is why the inaccessible
> icon ... nothing to do with AP and more to do with device discovery.
>
>
>
> Simplest approach is to ignore them and allow the AP clients to appear on
> the upstream switch port:
> https://github.com/netdisco/netdisco/wiki/Configuration#macsuck_unsupported
>
>
>
> regards
>
> Oliver
>
>
>
> On Wed, 4 Aug 2021 at 22:52, Ricardo Stella  wrote:
>
>
>
> Figure I ask before reinventing the wheel.  Our Aruba APs don't seem to be
> recognized as access points.  They only show a device is inaccessible
> icon.  No entries for discover_waps so default of true should be in effect.
>
>
>
> For example, c_platform returns "ArubaOS (MODEL: 315), Version Aruba AP"
>
>
>
> Tried adding the whole string to test to deployment.yml but doesn't seem
> to work:
>
>
>
> wap_platforms:
>  - 'ArubaOS (MODEL: 315), Version Aruba AP'
>
>
>
> Am I missing something? Thanks in advance.
>
>
>
> --
>
> °(((*=*((*===°°°*(((**
>
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
>
>
>
> --
>
> °(((*=*((*===°°°*(((**
>
>
> --
>
>
> *Volg Aquafin op Facebook  | Twitter
>  | YouTube
>  |
> LinkedIN  | Instagram
>  *
>
> 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
> .
>
>   P Denk aan het milieu. Druk deze mail niet onnodig af.
>
> 
>


-- 
°(((=((===°°°(((
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 181, Issue 6

[netdisco-users-request]

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: wap_platforms and phone_platforms (Ricardo Stella)
--- Begin Message ---
Thanks for this - I don't think they have SNMP access but was curious as to
why they don't show a wireless access point or wireless client icon.
Though I just noticed there's no actual icon for wireless access point.


[image: image.png]

Now, the next issue is there anyway to get the System Name to populate and
be searchable? The info does show up in LLDP on the switch but doesn't seem
to be grabbed by Netdisco.  Same goes for phones which do include their
extension

System Name: regDN 1234,MINET_6920
System Name: Test_AP

Thanks - Ricardo.


On Thu, Aug 12, 2021 at 6:27 AM Oliver Gorwits  wrote:

> Hi,
>
> You shouldn't need to mess with wap_platforms or wap_capabilities, if the
> APs are fairly modern.
>
> This is more likely that Netdisco doesn't recognise them as devices or
> they are not responding to SNMP sufficiently. This is why the inaccessible
> icon ... nothing to do with AP and more to do with device discovery.
>
> Simplest approach is to ignore them and allow the AP clients to appear on
> the upstream switch port:
> https://github.com/netdisco/netdisco/wiki/Configuration#macsuck_unsupported
>
> regards
> Oliver
>
> On Wed, 4 Aug 2021 at 22:52, Ricardo Stella  wrote:
>
>>
>> Figure I ask before reinventing the wheel.  Our Aruba APs don't seem to
>> be recognized as access points.  They only show a device is inaccessible
>> icon.  No entries for discover_waps so default of true should be in effect.
>>
>> For example, c_platform returns "ArubaOS (MODEL: 315), Version Aruba AP"
>>
>> Tried adding the whole string to test to deployment.yml but doesn't seem
>> to work:
>>
>> wap_platforms:
>>  - 'ArubaOS (MODEL: 315), Version Aruba AP'
>>
>> Am I missing something? Thanks in advance.
>>
>> --
>> °(((=((===°°°(((
>> ___
>> Netdisco mailing list
>> 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

netdisco-users Digest, Vol 181, Issue 12

[netdisco-users-request]

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. netdisco web interface behind CAS service (Gallavardin Antoine)
--- Begin Message ---

  
  
Hello
I'm using netdisco since a few month, and I'm wondering how I
  survived before  !!
Now I'd like to share netdisco Informations to other by allowing
  them to connect on web interface trough our CAS server
So 

I installed Apache, put mod_cas, redirect all http external
  traffic to localhost on port 5000
I created users inside database and setup netdico in order to
  allow remote user  and  no success
I test several configuration , X_REMOTE_USER REMOTE_USER ... no
  success at all
do you have any clue ?
My config :
deployment.yml :
trust_remote_user: true
validate_remote_user: true
behind_proxy: true
show_errors: true
Apache2

...

    CASCookiePath /var/cache/apache2/mod_auth_cas/
    CASLoginURL https:///cas/login
    CASValidateURL https:///cas/serviceValidate
    
    Authtype CAS
    Require valid-user
    


    ProxyPass   /   http://127.0.0.1:5000/
    ProxyPassReverse    /   http://127.0.0.1:5000/
...



cheers
Antoine



-- 
Antoine Gallavardin
INRAE - SIIR Auvergne Rhone Alpes - DSI-INFRA
French Research Center

  



--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 181, Issue 14

[netdisco-users-request]

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: Custom query help (Juan Romero)
--- Begin Message ---
Haven't done custom reports myself but that looks like a YAML parsing error, 
file syntax.

 
Check spaces/tabs in the reports section of your file. In the wiki page 
(https://github.com/netdisco/netdisco/wiki/Custom-Reports) I see some examples 
in the way the queries are formatted 

 
-

Juan J. Romero

Founder & Director

email: jrom...@auroranetworks.net

m: +61420246579

https://www.auroranetworks.net 

https://logio.auroranetworks.net

Aurora Networks Managed Services

ABN: 50 627 553 619

20-24 Premier Street

Kogarah, NSW 2217

 
  

Follow us on Locals:

https://cybersec.locals.com/

-Original message-
From: Ricardo Stella
Sent: Saturday, August 28 2021, 6:45 am
To: Jethro Binks
Cc: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Custom query help
  Problem is, I get the following errors with the second report.  Line 126 in 
deployment.yml is the second -tag line:
 PS: Anyone willing to help with the report I'm trying to do?
 Unable to parse the configuration file: 
/home/netdisco/environments/deployment.yml: YAML::XS::Load Error: The problem:

    did not find expected key

was found at document: 1, line: 126, column: 2
while parsing a block mapping at line: 13, column: 1
 at /home/netdisco/perl5/lib/perl5/Dancer/Config.pm line 232.
        
Dancer::Config::load_settings_from_yaml('/home/netdisco/environments/deployment.yml',
 'YAML') called at /home/netdisco/perl5/lib/perl5/Dancer/Config.pm line 205
        Dancer::Config::load('Dancer::Config') called at 
/home/netdisco/perl5/lib/perl5/Dancer.pm line 274
        Dancer::import('Dancer', ':script') called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        App::Netdisco::Util::DNS::BEGIN() called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        eval {...} called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        require App/Netdisco/Util/DNS.pm called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4
        App::Netdisco::Util::DeviceAuth::BEGIN() called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        eval {...} called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        require App/Netdisco/Util/DeviceAuth.pm called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Configuration.pm line 4

        App::Netdisco::Configuration::BEGIN() called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        eval {...} called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        require App/Netdisco/Configuration.pm called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco.pm line 8
        App::Netdisco::BEGIN() called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        eval {...} called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        require App/Netdisco.pm called at 
/home/netdisco/perl5/bin/netdisco-backend-fg line 20
        main::BEGIN() called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        eval {...} called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
BEGIN failed--compilation aborted at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5.
Compilation failed in require at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4.
BEGIN failed--compilation aborted at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4.
Compilation failed in require at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Configuration.pm line 4.
BEGIN failed--compilation aborted at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Configuration.pm line 4.
Compilation failed in require at /home/netdisco/perl5/lib/perl5/App/Netdisco.pm 
line 8.
BEGIN failed--compilation aborted at 
/home/netdisco/perl5/lib/perl5/App/Netdisco.pm line 8.
Compilation failed in require at /home/netdisco/perl5/bin/netdisco-backend-fg 
line 20.
BEGIN failed--compilation aborted at 
/home/netdisco/perl5/bin/netdisco-backend-fg line 20.
   On Thu, Aug 26, 2021 at 6:05 PM Jethro Binks  
wrote:
There should only be one
 reports:
 keyword followed by a tag: for each report.  Your second reports: tag is 
overriding the first, just 

netdisco-users Digest, Vol 181, Issue 16

[netdisco-users-request]

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: Custom query help (Juan Romero)
--- Begin Message ---
can u paste the full reports section of your yaml?

 
-

Juan J. Romero

Founder & Director

email: jrom...@auroranetworks.net

m: +61420246579

https://www.auroranetworks.net 

https://logio.auroranetworks.net

Aurora Networks Managed Services

ABN: 50 627 553 619

20-24 Premier Street

Kogarah, NSW 2217

 
  

Follow us on Locals:

https://cybersec.locals.com/

-Original message-
From: Ricardo Stella
Sent: Saturday, August 28 2021, 7:23 am
To: Juan Romero
Cc: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Custom query help
 Each of those reports in the wiki work fine by themselves, but both one after 
another don't 
 On Fri, Aug 27, 2021 at 5:09 PM Juan Romero  wrote:
Haven't done custom reports myself but that looks like a YAML parsing error, 
file syntax.

 
Check spaces/tabs in the reports section of your file. In the wiki page 
(https://github.com/netdisco/netdisco/wiki/Custom-Reports) I see some examples 
in the way the queries are formatted 

 
-

Juan J. Romero

Founder & Director

email: jrom...@auroranetworks.net

m: +61420246579

https://www.auroranetworks.net 

https://logio.auroranetworks.net

Aurora Networks Managed Services

ABN: 50 627 553 619

20-24 Premier Street

Kogarah, NSW 2217

 
  

Follow us on Locals:

https://cybersec.locals.com/

-Original message-
From: Ricardo Stella
Sent: Saturday, August 28 2021, 6:45 am
To: Jethro Binks
Cc: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] Custom query help
  Problem is, I get the following errors with the second report.  Line 126 in 
deployment.yml is the second -tag line:
 PS: Anyone willing to help with the report I'm trying to do?
 Unable to parse the configuration file: 
/home/netdisco/environments/deployment.yml: YAML::XS::Load Error: The problem:

    did not find expected key

was found at document: 1, line: 126, column: 2
while parsing a block mapping at line: 13, column: 1
 at /home/netdisco/perl5/lib/perl5/Dancer/Config.pm line 232.
        
Dancer::Config::load_settings_from_yaml('/home/netdisco/environments/deployment.yml',
 'YAML') called at /home/netdisco/perl5/lib/perl5/Dancer/Config.pm line 205
        Dancer::Config::load('Dancer::Config') called at 
/home/netdisco/perl5/lib/perl5/Dancer.pm line 274
        Dancer::import('Dancer', ':script') called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        App::Netdisco::Util::DNS::BEGIN() called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        eval {...} called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        require App/Netdisco/Util/DNS.pm called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4
        App::Netdisco::Util::DeviceAuth::BEGIN() called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        eval {...} called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        require App/Netdisco/Util/DeviceAuth.pm called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Configuration.pm line 4

        App::Netdisco::Configuration::BEGIN() called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        eval {...} called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        require App/Netdisco/Configuration.pm called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco.pm line 8
        App::Netdisco::BEGIN() called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        eval {...} called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        require App/Netdisco.pm called at 
/home/netdisco/perl5/bin/netdisco-backend-fg line 20
        main::BEGIN() called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
        eval {...} called at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
BEGIN failed--compilation aborted at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5.
Compilation failed in require at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4.
BEGIN failed--compilation aborted at 

netdisco-users Digest, Vol 181, Issue 13

[netdisco-users-request]

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: Custom query help (Ricardo Stella)
--- Begin Message ---
Problem is, I get the following errors with the second report.  Line 126 in
deployment.yml is the second -tag line:

PS: Anyone willing to help with the report I'm trying to do?

Unable to parse the configuration file:
/home/netdisco/environments/deployment.yml: YAML::XS::Load Error: The
problem:

did not find expected key

was found at document: 1, line: 126, column: 2
while parsing a block mapping at line: 13, column: 1
 at /home/netdisco/perl5/lib/perl5/Dancer/Config.pm line 232.

Dancer::Config::load_settings_from_yaml('/home/netdisco/environments/deployment.yml',
'YAML') called at /home/netdisco/perl5/lib/perl5/Dancer/Config.pm line 205
Dancer::Config::load('Dancer::Config') called at
/home/netdisco/perl5/lib/perl5/Dancer.pm line 274
Dancer::import('Dancer', ':script') called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
App::Netdisco::Util::DNS::BEGIN() called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
eval {...} called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
require App/Netdisco/Util/DNS.pm called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4
App::Netdisco::Util::DeviceAuth::BEGIN() called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
eval {...} called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
require App/Netdisco/Util/DeviceAuth.pm called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Configuration.pm line 4
App::Netdisco::Configuration::BEGIN() called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
eval {...} called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
require App/Netdisco/Configuration.pm called at
/home/netdisco/perl5/lib/perl5/App/Netdisco.pm line 8
App::Netdisco::BEGIN() called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
eval {...} called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
require App/Netdisco.pm called at
/home/netdisco/perl5/bin/netdisco-backend-fg line 20
main::BEGIN() called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
eval {...} called at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
BEGIN failed--compilation aborted at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5.
Compilation failed in require at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4.
BEGIN failed--compilation aborted at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4.
Compilation failed in require at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Configuration.pm line 4.
BEGIN failed--compilation aborted at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Configuration.pm line 4.
Compilation failed in require at
/home/netdisco/perl5/lib/perl5/App/Netdisco.pm line 8.
BEGIN failed--compilation aborted at
/home/netdisco/perl5/lib/perl5/App/Netdisco.pm line 8.
Compilation failed in require at
/home/netdisco/perl5/bin/netdisco-backend-fg line 20.
BEGIN failed--compilation aborted at
/home/netdisco/perl5/bin/netdisco-backend-fg line 20.



On Thu, Aug 26, 2021 at 6:05 PM Jethro Binks 
wrote:

> There should only be one
>
> reports:
>
> keyword followed by a tag: for each report.  Your second reports: tag is
> overriding the first, just remove it.
>
> Jethro.
>
> .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
>
> Jethro R Binks, Network Manager,
>
> Information Services Directorate, University Of Strathclyde, Glasgow, UK
>
>
> The University of Strathclyde is a charitable body, registered in Scotland,
> number SC015263.
>
> --
> *From:* Ricardo Stella 
> *Sent:* 25 August 2021 20:52
> *To:* Oliver Gorwits 
> *Cc:* netdisco-users@lists.sourceforge.net <
> netdisco-users@lists.sourceforge.net>
> *Subject:* Re: [Netdisco] Custom query help
>
>
> Thanks - Two questions:
>
> * How can you do multiple reports? It only looks like the last one defined
> is shown.  I have them as follows:
>
> reports:
>  - tag: wap_speed
> ...
> reports:
>  - tag: admin_up_down
> ...
>
> * Also, looks like I'm not sure how to do this one - Syntax seems correct,
> but getting search failed.
>
> reports:
>  - tag: wap_port_speeds

netdisco-users Digest, Vol 181, Issue 15

[netdisco-users-request]

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: Custom query help (Ricardo Stella)
--- Begin Message ---
Each of those reports in the wiki work fine by themselves, but both one
after another don't

On Fri, Aug 27, 2021 at 5:09 PM Juan Romero 
wrote:

> Haven't done custom reports myself but that looks like a YAML parsing
> error, file syntax.
>
>
>
> Check spaces/tabs in the reports section of your file. In the wiki page (
> https://github.com/netdisco/netdisco/wiki/Custom-Reports) I see some
> examples in the way the queries are formatted
>
>
>
> -
>
> Juan J. Romero
>
> Founder & Director
>
> email: *jrom...@auroranetworks.net *
>
> m: *+61420246579*
>
> https://www.auroranetworks.net
>
> https://logio.auroranetworks.net
>
> Aurora Networks Managed Services
>
> ABN: 50 627 553 619
>
> 20-24 Premier Street
>
> Kogarah, NSW 2217
>
>
>
> Follow us on Locals:
>
> https://cybersec.locals.com/
>
> -Original message-
> *From:* Ricardo Stella
> *Sent:* Saturday, August 28 2021, 6:45 am
> *To:* Jethro Binks
> *Cc:* netdisco-users@lists.sourceforge.net
> *Subject:* Re: [Netdisco] Custom query help
>
>
> Problem is, I get the following errors with the second report.  Line 126
> in deployment.yml is the second -tag line:
>
> PS: Anyone willing to help with the report I'm trying to do?
>
> Unable to parse the configuration file:
> /home/netdisco/environments/deployment.yml: YAML::XS::Load Error: The
> problem:
>
> did not find expected key
>
> was found at document: 1, line: 126, column: 2
> while parsing a block mapping at line: 13, column: 1
>  at /home/netdisco/perl5/lib/perl5/Dancer/Config.pm line 232.
>
> Dancer::Config::load_settings_from_yaml('/home/netdisco/environments/deployment.yml',
> 'YAML') called at /home/netdisco/perl5/lib/perl5/Dancer/Config.pm line 205
> Dancer::Config::load('Dancer::Config') called at
> /home/netdisco/perl5/lib/perl5/Dancer.pm line 274
> Dancer::import('Dancer', ':script') called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> App::Netdisco::Util::DNS::BEGIN() called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> eval {...} called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> require App/Netdisco/Util/DNS.pm called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4
> App::Netdisco::Util::DeviceAuth::BEGIN() called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> eval {...} called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> require App/Netdisco/Util/DeviceAuth.pm called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Configuration.pm line 4
> App::Netdisco::Configuration::BEGIN() called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> eval {...} called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> require App/Netdisco/Configuration.pm called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco.pm line 8
> App::Netdisco::BEGIN() called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> eval {...} called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> require App/Netdisco.pm called at
> /home/netdisco/perl5/bin/netdisco-backend-fg line 20
> main::BEGIN() called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> eval {...} called at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5
> BEGIN failed--compilation aborted at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DNS.pm line 5.
> Compilation failed in require at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4.
> BEGIN failed--compilation aborted at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/DeviceAuth.pm line 4.
> Compilation failed in require at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Configuration.pm line 4.
> BEGIN failed--compilation aborted at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Configuration.pm line 4.
> Compilation failed in require at
> /home/netdisco/perl5/lib/perl5/App/Netdisco.pm line 8.
> BEGIN failed--compilation aborted at
> /home/netdisco/perl5/lib/perl5/App/Netdisco.pm line 8.
> Compilation failed in require at
> /home/netdisco/perl5/bin/netdisco-backend-fg line 20.
> BEGIN failed--compilation aborted at
> 

netdisco-users Digest, Vol 181, Issue 17

[netdisco-users-request]

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. 1st device discovery fails (Shravan Hulyalkar)
   2. Re: 1st device discovery fails (Dominik M?ller)
   3. Re: 1st device discovery fails (Shravan Hulyalkar)
--- Begin Message ---
Hello All,

This is my first installation and I am fairly new to this. So please bear
with me.

I have added tried adding v2 and v3 SNMP versions on the switch but it
still didn't work.

I also did a discovery through the bowser but luck there as well.
I ran the following command via the terminal :

*~/bin/netdisco-do discover -D -d 10.125.0.155*

Can anyone help please tell me what I am doing wrong?
































*[1401566] 2021-08-31 17:14:57  info App::Netdisco version 2.049001
loaded.[1401566] 2021-08-31 17:14:58  info discover: [10.125.0.155] started
at Tue Aug 31 10:14:58 2021[1401566] 2021-08-31 17:14:58 debug discover:
running with timeout 600s[1401566] 2021-08-31 17:14:58 debug => running
workers for phase: check[1401566] 2021-08-31 17:14:58 debug -> run worker
check/_base_/0[1401566] 2021-08-31 17:14:58 debug Discover is able to
run.[1401566] 2021-08-31 17:14:58 debug => running workers for phase:
early[1401566] 2021-08-31 17:14:58 debug -> run worker
early/properties/100[1401566] 2021-08-31 17:14:58 debug snmp reader cache
warm: [10.125.0.155][1401566] 2021-08-31 17:14:58 debug [10.125.0.155:161
] try_connect with ver: 2, class: SNMP::Info,
comm: [1401566] 2021-08-31 17:15:02 debug [10.125.0.155:161
] try_connect with ver: 1, class: SNMP::Info,
comm: [1401566] 2021-08-31 17:15:05 debug discover failed: could
not SNMP connect to 10.125.0.155[1401566] 2021-08-31 17:15:05 debug -> run
worker early/properties/100[1401566] 2021-08-31 17:15:05 debug -> run
worker early/properties/100[1401566] 2021-08-31 17:15:05 debug -> run
worker early/properties/100[1401566] 2021-08-31 17:15:05 debug -> run
worker early/properties/100[1401566] 2021-08-31 17:15:05 debug => running
workers for phase: main[1401566] 2021-08-31 17:15:05 debug -> run worker
main/canonicalip/100[1401566] 2021-08-31 17:15:05 debug -> run worker
main/entities/100[1401566] 2021-08-31 17:15:05 debug -> run worker
main/neighbors/100[1401566] 2021-08-31 17:15:05 debug -> run worker
main/neighbors/100[1401566] 2021-08-31 17:15:05 debug -> run worker
main/neighbors/100[1401566] 2021-08-31 17:15:05 debug -> run worker
main/portpower/100[1401566] 2021-08-31 17:15:05 debug -> run worker
main/portproperties/100[1401566] 2021-08-31 17:15:05 debug -> run worker
main/vlans/100[1401566] 2021-08-31 17:15:05 debug -> run worker
main/wireless/100[1401566] 2021-08-31 17:15:05 debug -> run worker
main/withnodes/0[1401566] 2021-08-31 17:15:05 debug => running workers for
phase: late[1401566] 2021-08-31 17:15:05 debug -> run worker
late/hooks/0[1401566] 2021-08-31 17:15:05 debug  [10.125.0.155] hooks - 0
queued[1401566] 2021-08-31 17:15:05  info discover: finished at Tue Aug 31
10:15:05 2021[1401566] 2021-08-31 17:15:05  info discover: status defer:
discover failed: could not SNMP connect to 10.125.0.155*
-- 
Thanks in advance

Regards,
Shravan Hulyalkar
(669)247-9901
--- End Message ---
--- Begin Message ---
Hi,

Seems there is a Problem with the snmp credentials or snmp is disabled on the 
switch.

Could you Post the content of your deployment.yml file? 

BR 

Dominik

Von meinem iPhone gesendet

> Am 31.08.2021 um 19:45 schrieb Dominik Müller :
> Seems there is a Problem with the snmp credentials or snmp is disabled on 
> the switch.
> 
> Could you Post the content of your deployment.yml file? 
> 
> BR 
> 
> Dominik
> 
>> Am 31.08.2021 um 19:32 schrieb Shravan Hulyalkar 
>> :
>> 
>> Hello All, 
>> 
>> This is my first installation and I am fairly new to this. So please bear 
>> with me. 
>> 
>> I have added tried adding v2 and v3 SNMP versions on the switch but it still 
>> didn't work. 
>> 
>> I also did a discovery through the bowser but luck there as well. 
>> I ran the following command via the terminal :
>> 
>> ~/bin/netdisco-do discover -D -d 10.125.0.155
>> 
>> Can anyone help please tell me what I am doing wrong?
>> 
>> [1401566] 2021-08-31 17:14:57  info App::Netdisco version 2.049001 loaded.
>> [1401566] 2021-08-31 17:14:58  info discover: [10.125.0.155] started at Tue 
>> Aug 31 10:14:58 2021
>> [1401566] 2021-08-31 17:14:58 debug discover: running with timeout 600s
>> [1401566] 2021-08-31 17:14:58 debug => running workers for phase: check

netdisco-users Digest, Vol 181, Issue 18

[netdisco-users-request]

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: 1st device discovery fails (Dominik M?ller)
   2. Re: 1st device discovery fails (Shravan Hulyalkar)
--- Begin Message ---
Okay, 

so when i see it right there are no snmp credentials within the yml file.

You have to insert the arista community here:

> device_auth:
>   - tag: 'default_v2_readonly'
> community: 'arista'
> read: true
> write: false

BR

Dominik

> Am 31.08.2021 um 20:03 schrieb Shravan Hulyalkar :
> 
> 
> I also thought the same thing. But i wasnt sure where to put the credentials 
> for snmp. 
> I have the following on the switch right now. 
> snmp-server community arista ro
> 
> 
> Here is the deployment.yml
> #
> # NETDISCO 2 CONFIGURATION FILE
> #
> # Settings in this file override share/config.yml
> #
> # https://github.com/netdisco/netdisco/wiki/Configuration has
> # in depth explanations about each setting.
> 
> # --
> # ESSENTIAL SETTINGS
> # --
> 
> database:
>   name: 'postgres'
>   user: 'netdisco'
>   pass: '*'
>   #host: '10.125.0.155'
> 
> # 
> # RECOMMENDED SETTINGS
> # 
> 
> # Device authentication settings
> # define snmp communities and ssh credentials here
> # 
> device_auth:
>   - tag: 'default_v2_readonly'
> community: 'public'
> read: true
> write: false
> #  - tag: 'default_v2_for_write'
> #community: 'private'
> #read: false
> #write: true
> 
> # will be stripped from fqdn when displayed in the web UI
> # also, do not forget the leading dot.
> # ```
> domain_suffix: ['example.corp']
> 
> 
> # ¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸
> #
> # SOME MORE INTERESTING SETTINGS WHERE THE DEFAULTS ARE PROBABLY OKAY
> #
> # ¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸
> 
> 
> # discover Wireless Access Points, but not IP Phones
> # usually these are visible as device neighbors but don't support
> # SNMP, which just clogs up the job queue.
> # ```
> #discover_waps: true
> #discover_phones: false
> 
> # this is the schedule for automatically keeping netdisco up-to-date;
> # these are good defaults, so only uncomment if needing to change.
> # (or set "schedule: null" if you wish to disable the scheduler)
> # 
> #schedule:
> #  discoverall:
> #when: '5 7 * * *'
> #  macwalk:
> #when:
> #  min: 20
> #  arpwalk:
> #when:
> #  min: 50
> #  nbtwalk:
> #when: '0 8,13,21 * * *'
> #  expire:
> #when: '30 23 * * *'
> #  makerancidconf: null
> 
> # number of SNMP workers to run in parallel (in netdisco-backend).
> # the default is twice the number of CPU cores. increase this if
> # your system has few cores and the schedule is taking too long.
> # ```
> #workers:
> #  tasks: 'AUTO * 2'
> 
> # number of parallel DNS queries for node names
> # `
> #dns:
> #  max_outstanding: 50
> 
> # set to true to globally disable authentication/login.
> # create a user called "guest" if you want to assign port/admin rights.
> # `
> #no_auth: false
> 
> # set to false if you MUST maintain backwards compatibility
> # with Netdisco 1.x web frontend.
> # `
> #safe_password_store: true
> 
>> On Tue, Aug 31, 2021 at 10:46 AM Dominik Müller  wrote:
>> Seems there is a Problem with the snmp credentials or snmp is disabled on 
>> the switch.
>> 
>> Could you Post the content of your deployment.yml file? 
>> 
>> BR 
>> 
>> Dominik
>> 
 Am 31.08.2021 um 19:32 schrieb Shravan Hulyalkar 
 :
 
>>> 
>>> Hello All, 
>>> 
>>> This is my first installation and I am fairly new to this. So please bear 
>>> with me. 
>>> 
>>> I have added tried adding v2 and v3 SNMP versions on the switch but it 
>>> still didn't work. 
>>> 
>>> I also did a discovery through the bowser but luck there as well. 
>>> I ran the following command via the terminal :
>>> 
>>> ~/bin/netdisco-do discover -D -d 10.125.0.155
>>> 
>>> Can anyone help please tell me what I am doing wrong?
>>> 
>>> [1401566] 2021-08-31 17:14:57  info 

netdisco-users Digest, Vol 182, Issue 1

[netdisco-users-request]

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: 1st device discovery fails (Dominik M?ller)
--- Begin Message ---
No Problem,

Glad i could help :)

> Am 31.08.2021 um 20:29 schrieb Shravan Hulyalkar :
> 
> 
> Thank you Dominik. That did work and I was able to discover my first device. 
> 
> Thank you Eric for the snmpwalk command as well. Super helpful :D 
> 
> 
>> On Tue, Aug 31, 2021 at 11:21 AM Dominik Müller  wrote:
>> Okay, 
>> 
>> so when i see it right there are no snmp credentials within the yml file.
>> 
>> You have to insert the arista community here:
>> 
>>> device_auth:
>>>   - tag: 'default_v2_readonly'
>>> community: 'arista'
>>> read: true
>>> write: false
>> 
>> BR
>> 
>> Dominik
>> 
 Am 31.08.2021 um 20:03 schrieb Shravan Hulyalkar 
 :
 
>>> 
>>> I also thought the same thing. But i wasnt sure where to put the 
>>> credentials for snmp. 
>>> I have the following on the switch right now. 
>>> snmp-server community arista ro
>>> 
>>> 
>>> Here is the deployment.yml
>>> #
>>> # NETDISCO 2 CONFIGURATION FILE
>>> #
>>> # Settings in this file override share/config.yml
>>> #
>>> # https://github.com/netdisco/netdisco/wiki/Configuration has
>>> # in depth explanations about each setting.
>>> 
>>> # --
>>> # ESSENTIAL SETTINGS
>>> # --
>>> 
>>> database:
>>>   name: 'postgres'
>>>   user: 'netdisco'
>>>   pass: '*'
>>>   #host: '10.125.0.155'
>>> 
>>> # 
>>> # RECOMMENDED SETTINGS
>>> # 
>>> 
>>> # Device authentication settings
>>> # define snmp communities and ssh credentials here
>>> # 
>>> device_auth:
>>>   - tag: 'default_v2_readonly'
>>> community: 'public'
>>> read: true
>>> write: false
>>> #  - tag: 'default_v2_for_write'
>>> #community: 'private'
>>> #read: false
>>> #write: true
>>> 
>>> # will be stripped from fqdn when displayed in the web UI
>>> # also, do not forget the leading dot.
>>> # ```
>>> domain_suffix: ['example.corp']
>>> 
>>> 
>>> # ¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸
>>> #
>>> # SOME MORE INTERESTING SETTINGS WHERE THE DEFAULTS ARE PROBABLY OKAY
>>> #
>>> # ¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸
>>> 
>>> 
>>> # discover Wireless Access Points, but not IP Phones
>>> # usually these are visible as device neighbors but don't support
>>> # SNMP, which just clogs up the job queue.
>>> # ```
>>> #discover_waps: true
>>> #discover_phones: false
>>> 
>>> # this is the schedule for automatically keeping netdisco up-to-date;
>>> # these are good defaults, so only uncomment if needing to change.
>>> # (or set "schedule: null" if you wish to disable the scheduler)
>>> # 
>>> #schedule:
>>> #  discoverall:
>>> #when: '5 7 * * *'
>>> #  macwalk:
>>> #when:
>>> #  min: 20
>>> #  arpwalk:
>>> #when:
>>> #  min: 50
>>> #  nbtwalk:
>>> #when: '0 8,13,21 * * *'
>>> #  expire:
>>> #when: '30 23 * * *'
>>> #  makerancidconf: null
>>> 
>>> # number of SNMP workers to run in parallel (in netdisco-backend).
>>> # the default is twice the number of CPU cores. increase this if
>>> # your system has few cores and the schedule is taking too long.
>>> # ```
>>> #workers:
>>> #  tasks: 'AUTO * 2'
>>> 
>>> # number of parallel DNS queries for node names
>>> # `
>>> #dns:
>>> #  max_outstanding: 50
>>> 
>>> # set to true to globally disable authentication/login.
>>> # create a user called "guest" if you want to assign port/admin rights.
>>> # `
>>> #no_auth: false
>>> 
>>> # set to false if you MUST maintain backwards compatibility
>>> # with Netdisco 1.x web frontend.
>>> # `
>>> #safe_password_store: true
>>> 
 On Tue, Aug 31, 2021 at 10:46 AM Dominik Müller  wrote:
 Seems there is a Problem with the snmp credentials or snmp is disabled on 
 the switch.
 
 Could you Post the content of your deployment.yml file? 
 
 BR 
 
 Dominik
 
>> Am 31.08.2021 um 19:32 schrieb Shravan 

netdisco-users Digest, Vol 181, Issue 9

[netdisco-users-request]

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. Custom query help (Ricardo Stella)
   2. Re: Custom query help (Juan Romero)
   3. Re: Custom query help (Oliver Gorwits)
--- Begin Message ---
Hi folks, not a DBA nor programmer here so figure I ask if someone has done
something similar.

Trying to do a query or search for say "active access points running at
100mbps", or at least "devices running at less than 1gbps"

Any ideas on how to do this via the GUI or command line?

TIA

-- 
°(((=((===°°°(((
--- End Message ---
--- Begin Message ---
Try sthg like this on the PSQL DB.

Replace:

 
like '%AV%'

 
with a wildcard matching your WAPs hostnames

 
 

 
 
 
 
-

Juan J. Romero

Founder & Director

email: jrom...@auroranetworks.net

m: +61420246579

https://www.auroranetworks.net 

https://logio.auroranetworks.net

Aurora Networks Managed Services

ABN: 50 627 553 619

20-24 Premier Street

Kogarah, NSW 2217

 
  

Follow us on Locals:

https://cybersec.locals.com/

-Original message-
From: Ricardo Stella
Sent: Wednesday, August 25 2021, 7:52 am
To: netdisco-users@lists.sourceforge.net
Subject: [Netdisco] Custom query help
 Hi folks, not a DBA nor programmer here so figure I ask if someone has done 
something similar.
 Trying to do a query or search for say "active access points running at 
100mbps", or at least "devices running at less than 1gbps"
 Any ideas on how to do this via the GUI or command line?
 TIA
 --
°(((=((===°°°(((

 

___

Netdisco mailing list

netdisco-users@lists.sourceforge.net

https://sourceforge.net/p/netdisco/mailman/netdisco-users/

--- End Message ---
--- Begin Message ---
Hi Ricardo and Juan

Yes Juan is right, that's the easiest method if you have consistently named
access points. You can start with the reports here:

https://github.com/netdisco/netdisco/wiki/Custom-Reports

(yes we started a wiki page for helping this)

The first report joins the device and device_port table which is what you
need to do to get both the hostname (device.dns) and speed
(device_port.speed).

Alternatively, to select devices which report themselves as APs, join on
device_port_properties and inspect the remote_is_wap field:

LEFT JOIN device_port_properties ON device_port.ip = device_port_properties.ip
...
WHERE remote_is_wap

Just think about which way round you are doing it: looking for APs with
ports running less than 1Gbps, or switch ports connected to APs running
less than 1Gbps.
It might be easier to do the second because APs have multiple interfaces
and you only want the uplink to the switch after all.

Good luck,

Oliver.



On Wed, 25 Aug 2021 at 04:51, Juan Romero 
wrote:

> Try sthg like this on the PSQL DB.
>
> Replace:
>
>
>
> like '%AV%'
>
>
>
> with a wildcard matching your WAPs hostnames
>
>
>
>
>
>
>
>
>
>
>
>
>
> -
>
> Juan J. Romero
>
> Founder & Director
>
> email: *jrom...@auroranetworks.net *
>
> m: *+61420246579*
>
> https://www.auroranetworks.net
>
> https://logio.auroranetworks.net
>
> Aurora Networks Managed Services
>
> ABN: 50 627 553 619
>
> 20-24 Premier Street
>
> Kogarah, NSW 2217
>
>
>
> Follow us on Locals:
>
> https://cybersec.locals.com/
>
> -Original message-
> *From:* Ricardo Stella
> *Sent:* Wednesday, August 25 2021, 7:52 am
> *To:* netdisco-users@lists.sourceforge.net
> *Subject:* [Netdisco] Custom query help
>
> Hi folks, not a DBA nor programmer here so figure I ask if someone has
> done something similar.
>
> Trying to do a query or search for say "active access points running at
> 100mbps", or at least "devices running at less than 1gbps"
>
> Any ideas on how to do this via the GUI or command line?
>
> TIA
>
> --
> °(((*=*((*===°°°*(((**
>
>
>
> ___
>
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
___
Netdisco mailing 

netdisco-users Digest, Vol 181, Issue 10

[netdisco-users-request]

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: Custom query help (Ricardo Stella)
--- Begin Message ---
Thanks - Two questions:

* How can you do multiple reports? It only looks like the last one defined
is shown.  I have them as follows:

reports:
 - tag: wap_speed
...
reports:
 - tag: admin_up_down
...

* Also, looks like I'm not sure how to do this one - Syntax seems correct,
but getting search failed.

reports:
 - tag: wap_port_speeds
   label: 'WAP Port Speeds'
   columns:
  - { host: Device_name}
  - { ip: ip}
  - { port: Port}
  - { name: Description}
  - { speed: 'Speed'}
   query: |
 SELECT device.name AS host, device_port.ip, device_port.port,
device_port.name
   FROM device_port
   LEFT JOIN device_port_properties ON device_port.ip =
device_port_properties.ip
   WHERE remote_is_wap

Ricardo.

On Wed, Aug 25, 2021 at 3:42 AM Oliver Gorwits  wrote:

> Hi Ricardo and Juan
>
> Yes Juan is right, that's the easiest method if you have consistently
> named access points. You can start with the reports here:
>
> https://github.com/netdisco/netdisco/wiki/Custom-Reports
>
> (yes we started a wiki page for helping this)
>
> The first report joins the device and device_port table which is what you
> need to do to get both the hostname (device.dns) and speed
> (device_port.speed).
>
> Alternatively, to select devices which report themselves as APs, join on
> device_port_properties and inspect the remote_is_wap field:
>
> LEFT JOIN device_port_properties ON device_port.ip = device_port_properties.ip
> ...
> WHERE remote_is_wap
>
> Just think about which way round you are doing it: looking for APs with
> ports running less than 1Gbps, or switch ports connected to APs running
> less than 1Gbps.
> It might be easier to do the second because APs have multiple interfaces
> and you only want the uplink to the switch after all.
>
> Good luck,
>
> Oliver.
>
>
>
> On Wed, 25 Aug 2021 at 04:51, Juan Romero 
> wrote:
>
>> Try sthg like this on the PSQL DB.
>>
>> Replace:
>>
>>
>>
>> like '%AV%'
>>
>>
>>
>> with a wildcard matching your WAPs hostnames
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> -
>>
>> Juan J. Romero
>>
>> Founder & Director
>>
>> email: *jrom...@auroranetworks.net *
>>
>> m: *+61420246579*
>>
>> https://www.auroranetworks.net
>>
>> https://logio.auroranetworks.net
>>
>> Aurora Networks Managed Services
>>
>> ABN: 50 627 553 619
>>
>> 20-24 Premier Street
>>
>> Kogarah, NSW 2217
>>
>>
>>
>> Follow us on Locals:
>>
>> https://cybersec.locals.com/
>>
>> -Original message-
>> *From:* Ricardo Stella
>> *Sent:* Wednesday, August 25 2021, 7:52 am
>> *To:* netdisco-users@lists.sourceforge.net
>> *Subject:* [Netdisco] Custom query help
>>
>> Hi folks, not a DBA nor programmer here so figure I ask if someone has
>> done something similar.
>>
>> Trying to do a query or search for say "active access points running at
>> 100mbps", or at least "devices running at less than 1gbps"
>>
>> Any ideas on how to do this via the GUI or command line?
>>
>> TIA
>>
>> --
>> °(((*=*((*===°°°*(((**
>>
>>
>>
>> ___
>>
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>>
>> ___
>> Netdisco mailing list
>> 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

netdisco-users Digest, Vol 181, Issue 8

[netdisco-users-request]

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: wap_platforms and phone_platforms (Nick Nauwelaerts)
--- Begin Message ---
that icon comes from font-awesome which we ship with netdisco. just to be sure 
i doublechecked the woff file.

if it doesn't show up for you it is most likely a local issue:
* you have an adblocker active which blocks this
* you have tracking protection active in your browser
* you have a local version of font-awesome installed which doesn't include this 
icon
* you've disabled remote fonts in your browser


tested on windows in both normal & private browsing mode with:
* firefox 91.0
* chrome 92.0.4515.131
* edge chromium

does your browser give any errors in web dev mode? (f12 to activate that in 
most browsers)


// nick

From: Ricardo Stella 
Sent: Thursday, August 12, 2021 16:10
To: Oliver Gorwits 
Cc: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] wap_platforms and phone_platforms


Thanks for this - I don't think they have SNMP access but was curious as to why 
they don't show a wireless access point or wireless client icon.  Though I just 
noticed there's no actual icon for wireless access point.


[cid:image001.png@01D79066.BC724BB0]

Now, the next issue is there anyway to get the System Name to populate and be 
searchable? The info does show up in LLDP on the switch but doesn't seem to be 
grabbed by Netdisco.  Same goes for phones which do include their extension

System Name: regDN 1234,MINET_6920
System Name: Test_AP

Thanks - Ricardo.


On Thu, Aug 12, 2021 at 6:27 AM Oliver Gorwits 
mailto:oli...@cpan.org>> wrote:
Hi,

You shouldn't need to mess with wap_platforms or wap_capabilities, if the APs 
are fairly modern.

This is more likely that Netdisco doesn't recognise them as devices or they are 
not responding to SNMP sufficiently. This is why the inaccessible icon ... 
nothing to do with AP and more to do with device discovery.

Simplest approach is to ignore them and allow the AP clients to appear on the 
upstream switch port: 
https://github.com/netdisco/netdisco/wiki/Configuration#macsuck_unsupported

regards
Oliver

On Wed, 4 Aug 2021 at 22:52, Ricardo Stella 
mailto:ste...@rider.edu>> wrote:

Figure I ask before reinventing the wheel.  Our Aruba APs don't seem to be 
recognized as access points.  They only show a device is inaccessible icon.  No 
entries for discover_waps so default of true should be in effect.

For example, c_platform returns "ArubaOS (MODEL: 315), Version Aruba AP"

Tried adding the whole string to test to deployment.yml but doesn't seem to 
work:

wap_platforms:
 - 'ArubaOS (MODEL: 315), Version Aruba AP'

Am I missing something? Thanks in advance.

--
°(((=((===°°°(((
___
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/


--
°(((=((===°°°(((



Volg Aquafin op Facebook | 
Twitter | 
YouTube | 
LinkedIN | 
Instagram

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.

  P Denk aan het milieu. Druk deze mail niet onnodig af.

[https://www.aquafin.be/sites/aquafin/files/styles/paragraph_with_caption/public/2021-04/banner_verhuis%20HK_600x200_blauw_12042021_M.png?itok=ugZqjHed]
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 182, Issue 3

[netdisco-users-request]

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. SSH arpnip error (Muris)
   2. Re: SSH arpnip error (Muris)
   3. Re: SSH arpnip error (Christian Ramseyer)
--- Begin Message ---
Hi Netdisco group,

 

I noticed something is failing with the SSH connector for arpnip in the logs 
recently, perhaps after a system update maybe.

 

Im getting this error

 

[4781] 2021-09-09 10:53:24 debug cli session cache warm: [10.xx.xx.xx]

[4781] 2021-09-09 10:53:24 error  [10.xx.xx.xx] ssh connection error [ctl_dir 
/home/netdisco/.libnet-openssh-perl/ is not secure]

[4781] 2021-09-09 10:53:24 debug arpnip failed: could not SSH connect to 
10.xx.xx.xx

 

How to make It secure ?

 

Thanks

Muris

--- End Message ---
--- Begin Message ---
Thanks, 755 fixed it, appreciate your help.

On 9/9/21, 21:29, "Christian Ramseyer"  wrote:

Hi



On 09.09.21 12:58, Muris wrote:
> 
> I noticed something is failing with the SSH connector for arpnip in the
> logs recently, perhaps after a system update maybe.
> 
>  
> 
> Im getting this error
> 
>  
> 
> [4781] 2021-09-09 10:53:24 debug cli session cache warm: [10.xx.xx.xx]
> 
> [4781] 2021-09-09 10:53:24 error  [10.xx.xx.xx] ssh connection error
> [ctl_dir /home/netdisco/.libnet-openssh-perl/ is not secure]
> 
> [4781] 2021-09-09 10:53:24 debug arpnip failed: could not SSH connect to
> 10.xx.xx.xx
> 

It's most likely the permissions on the netdisco or .libnet-openssh-perl
directories, make sure they are not group or world-writeable.

If in doubt, i'd go with chmod 755 for netdisco and chmod 700 for
.libnet-openssh-perl.

Cheers
Christian




--- End Message ---
--- Begin Message ---
Hi



On 09.09.21 12:58, Muris wrote:
> 
> I noticed something is failing with the SSH connector for arpnip in the
> logs recently, perhaps after a system update maybe.
> 
>  
> 
> Im getting this error
> 
>  
> 
> [4781] 2021-09-09 10:53:24 debug cli session cache warm: [10.xx.xx.xx]
> 
> [4781] 2021-09-09 10:53:24 error  [10.xx.xx.xx] ssh connection error
> [ctl_dir /home/netdisco/.libnet-openssh-perl/ is not secure]
> 
> [4781] 2021-09-09 10:53:24 debug arpnip failed: could not SSH connect to
> 10.xx.xx.xx
> 

It's most likely the permissions on the netdisco or .libnet-openssh-perl
directories, make sure they are not group or world-writeable.

If in doubt, i'd go with chmod 755 for netdisco and chmod 700 for
.libnet-openssh-perl.

Cheers
Christian


--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 182, Issue 4

[netdisco-users-request]

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. nornir inventory (Eric W. Bates)
   2. Re: nornir inventory (Christian Ramseyer)
   3. Re: nornir inventory (Joseph Bernard)
   4. Re: nornir inventory (Michael Butash)
--- Begin Message ---
Has anyone already written a script to generate a nornir hosts/groups 
file from netdisco?


Thank you.

--
Clark 159a, MS 46
508/289-3112



--- End Message ---
--- Begin Message ---


On 09.09.21 16:59, Eric W. Bates wrote:
> Has anyone already written a script to generate a nornir hosts/groups
> file from netdisco?

Hi Eric

Not directly, but I recently discovered this Netdisco to Ansible
inventory tool:


This is also creates a similar YAML file with Netdisco contents, maybe
you can us it to get started.

Cheers
Christian




--- End Message ---
--- Begin Message ---
At the end of July I started a thread "pulling out Inventory via Python for 
automation?" if you look in the mail archives.  I still haven't gotten around 
to getting something tested due to higher priority issues popping up, but the 
answers people gave may help you.

Thanks,
Joseph B.


On 9/9/21, 11:18 AM, "Eric W. Bates"  wrote:

Has anyone already written a script to generate a nornir hosts/groups 
file from netdisco?

Thank you.

-- 
Clark 159a, MS 46
508/289-3112



___
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/

--- End Message ---
--- Begin Message ---
Exporting the data you want, hostname, dns or ip (or all), or anything else
like vendor/model/os is pretty easy with even some very rudimentary pgsql
and sql skill, and I use that term skill loosely at least for myself.  I'm
an old network monkey, not a developer.

Logging into the db with psql (sudo su postgres && psql), entering the
netdisco db (\c netdisco), describing tables (\dt), doing some "select *
from xxx" different tables you learn and shows what you're looking for
where with minimal skill.  Rest is modifying queries of the examples given
in the reporting part of docs to get out what you want, and in what
format.  That I spent a half a day figuring out roughly how sql joins work
via furious googling and examples everyone's done a 1000x times already
decently enough to generate some of my own custom reports from queries.  I
did this a few months ago, I've mostly already forgotten what I did, but
easy enough to pick back up if needed from examples I did of my own.

Using Nornir you should be able to invoke a python dbi to get the data out
easy enough if you learn to query what you want from where within the
netdisco db schema.

HTH!

-mb


On Thu, Sep 9, 2021 at 8:18 AM Eric W. Bates  wrote:

> Has anyone already written a script to generate a nornir hosts/groups
> file from netdisco?
>
> Thank you.
>
> --
> Clark 159a, MS 46
> 508/289-3112
>
>
>
> ___
> Netdisco mailing list
> 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

netdisco-users Digest, Vol 182, Issue 5

[netdisco-users-request]

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. Netdisco search results missing randomly (Muris)
   2. Re: Netdisco search results missing randomly (Muris)
   3. Re: Netdisco search results missing randomly (Muris)
--- Begin Message ---
Hi,

 

Ive noticed sometimes netdisco search results are missing, even if you want to 
enter the specific device it comes up empty

 

I had a look at the backend and im seeing things like this, any ideas what is 
causing this?

 

DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  

SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Arpnip/Subnets.pm 
line 65

 

DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  

SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Node.pm line 182

 

Use of uninitialized value $res{"234"} in string eq at 
/home/netdisco/perl5/lib/perl5/SNMP/Info/CiscoStpExtensions.   pm line 256.

 

 

Thankyou

--- End Message ---
--- Begin Message ---
By the way, to get it working, I have to restart netdisco-web

 

I can’t really see errors in netdisco-web log though

 

From: Muris 
Date: Monday, 13 September 2021 at 13:32
To: "netdisco-users@lists.sourceforge.net" 

Subject: Netdisco search results missing randomly

 

Hi,

 

Ive noticed sometimes netdisco search results are missing, even if you want to 
enter the specific device it comes up empty

 

I had a look at the backend and im seeing things like this, any ideas what is 
causing this?

 

DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  

SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Arpnip/Subnets.pm 
line 65

 

DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  

SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Node.pm line 182

 

Use of uninitialized value $res{"234"} in string eq at 
/home/netdisco/perl5/lib/perl5/SNMP/Info/CiscoStpExtensions.   pm line 256.

 

 

Thankyou

--- End Message ---
--- Begin Message ---
I did a debug on arpnip and shows this, seems it crashes on something 
referenced in related to Subnets.pm ?

 

1037] 2021-09-13 05:51:29 debug  [10.x.x.x] arpnip - found subnet 10.x.x.x/27

[1037] 2021-09-13 05:51:29 debug  [10.x.x.x] arpnip - found subnet 10.x.x.x/30

[1037] 2021-09-13 05:51:29 debug  [10.x.x.x] arpnip - found subnet 10.x.x.0/27

[1037] 2021-09-13 05:51:29 debug  [10.x.x.x] arpnip - found subnet 10.x.x.x/26

DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  
SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Arpnip/Subnets.pm 
line 65

[1037] 2021-09-13 05:51:30 debug -> DBIx::Class::Row::update(): Can't update 
App::Netdisco::DB::Result::Subnet=HASH(0x4e22e70): updated more than one row at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Arpnip/Subnets.pm 
line 65

[1037] 2021-09-13 05:51:30 debug bless( {'msg' => 'DBIx::Class::Row::update(): 
Can\'t update App::Netdisco::DB::Result::Subnet=HASH(0x4e22e70): updated more 
than one row at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Arpnip/Subnets.pm 
line 65

'}, 'DBIx::Class::Exception' )

[1037] 2021-09-13 05:51:30 debug => running workers for phase: store

[1037] 2021-09-13 05:51:30 debug -> run worker store/nodes/0

[1037] 2021-09-13 05:51:31 debug  [10.x.x.x] arpnip - processed 293 ARP Cache 
entries

[1037] 2021-09-13 05:51:31 debug  [10.x.x.x] arpnip - processed 0 IPv6 Neighbor 
Cache entries

 

From: Muris 
Date: Monday, 13 September 2021 at 13:37
To: "netdisco-users@lists.sourceforge.net" 

Subject: Re: Netdisco search results missing randomly

 

By the way, to get it working, I have to restart netdisco-web

 

I can’t really see errors in netdisco-web log though

 

From: Muris 
Date: Monday, 13 September 2021 at 13:32
To: "netdisco-users@lists.sourceforge.net" 

Subject: Netdisco search results missing randomly

 

Hi,

 

Ive noticed sometimes netdisco search results are missing, even if you want to 
enter the specific device it comes up empty

 

I had a look at the backend and im seeing things like this, any ideas what is 

netdisco-users Digest, Vol 182, Issue 6

[netdisco-users-request]

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: Netdisco search results missing randomly (Joseph Bernard)
--- Begin Message ---
I’ve never figured out the cause, but I set up a cronjob to restart 
netdisco-web as a workaround. If I remember correctly, you can actually see the 
results in the source code of the page, but I guess it’s missing the code or 
something to make it display.


Thanks,
Joseph B.

On Sep 13, 2021, at 12:08 AM, Muris  wrote:


By the way, to get it working, I have to restart netdisco-web

I can’t really see errors in netdisco-web log though

From: Muris 
Date: Monday, 13 September 2021 at 13:32
To: "netdisco-users@lists.sourceforge.net" 

Subject: Netdisco search results missing randomly

Hi,

Ive noticed sometimes netdisco search results are missing, even if you want to 
enter the specific device it comes up empty

I had a look at the backend and im seeing things like this, any ideas what is 
causing this?

DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.
SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Arpnip/Subnets.pm 
line 65

DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.
SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Node.pm line 182

Use of uninitialized value $res{"234"} in string eq at 
/home/netdisco/perl5/lib/perl5/SNMP/Info/CiscoStpExtensions.   pm line 256.


Thankyou
___
Netdisco mailing list
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

netdisco-users Digest, Vol 182, Issue 8

[netdisco-users-request]

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. Similar tool to netdisco for servers ? (Shravan Hulyalkar)
--- Begin Message ---
Hello All,

As I have gotten my instance of Netdisco up and running. I have seen how
useful it is to keep a track of switches.
Can anyone help if something similar is available for servers as well? I
was able to discover ESXi in Netdisco using SNMP but it doesn't display the
server model as you can see in the screenshot attached and wasnt able to do
it for linux baremetal yet.

If someone has any pointers would really appreciate it.



-- 

Regards,
Shravan Hulyalkar
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 182, Issue 2

[netdisco-users-request]

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: Netdisco and Aruba Controllers (Muris)
--- Begin Message ---
Hi, just querying this again, is it possible to fix so netdisco can grab snmp 
arp, and description details of the interfaces for aruba controllers?

 

If I issue on the controller “show arp” its all listed, I just need to find a 
way for netdisco to interpret the data via snmp which seems to be broken at the 
moment for controllers.

 

I don’t believe it will be that difficult to tweak, happy to work with someone 
to test/implement, preferably for the L3 Aruba SNMP component that already 
exists

 

Just have about 100+ of these deployed and don’t have any arp data, or grabbing 
the description of interfaces/ cdp/lldp etc

 

Thankyou

 

From: Muris 
Date: Saturday, 13 March 2021 at 18:21
To: 
Subject: Re: [Netdisco] Netdisco and Aruba Controllers

 

Anyone able to make at least some changes to SNMP Info to pickup arp 
tables/description details off interfaces for Aruba controllers?

 

I don’t think its that complex probably just some code adjustments

 

From: Muris 
Date: Tuesday, 19 January 2021 at 23:56
To: 
Subject: Re: [Netdisco] Netdisco and Aruba Controllers

 

Is it possible an update can be made to work with aruba controllers for snmp 
info?

Sent from my iPhone

 

 

On 3 Nov 2020, at 21:21, Muris  wrote:



I think even if the mibs are updated,  snmp info probably needs some tweaking 
also

 

From: Oliver Gorwits 
Date: Tuesday, 3 November 2020 at 19:42
To: Neil Johnson 
Cc: Muris , "netdisco-users@lists.sourceforge.net" 

Subject: Re: [Netdisco] Netdisco and Aruba Controllers

 

Hi Neil

 

Take a look at the procedure here: 
https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs

 

And feel free to open a pull request on Github or ask questions on IRC

 

oliver.

 

On Tue, 3 Nov 2020 at 08:51, Neil Johnson  wrote:

What's involved in updating the Aruba MIBs?

 

The MIBs included in NetDisco are for ArubaOS 8.5.0.2_71711. The latest is 
8.7.1.0.

 

Thanks!

 

 

 

On Mon, Nov 2, 2020 at 7:25 PM Muris  wrote:

Hi All, 

 

Also it seems the arpnip and macsuck doesn’t seem to work.. so if you connect 
downstream switches it cant match the data to the ports mac/ip..

 

Whats the chance of having a fix for the descriptions and arpnip/mac data 
sucking to work.. we are putting lot of these out there and bit hard without 
having the data available.

 

Thanks 

 

From: Oliver Gorwits 
Date: Wednesday, 28 October 2020 at 03:00
To: Muris 
Cc: Jon Gerdes , "netdisco-users@lists.sourceforge.net" 

Subject: Re: [Netdisco] Netdisco and Aruba Controllers

 

Sounds like the age-old challenge of picking from ifDescr, ifName and ifAlias 
and different platforms using them differently

 

An update to SNMP::Info might be required

 

On Tue, 27 Oct 2020 at 12:36, Muris  wrote:

I did give.

 

Basically the descriptions on the physical interfaces netdisco is not getting 
that information.

 

It is just obtaining thr default interface name like ge0/0/0 

It clasifies the controllers correctly and captures info about them so that 
part works fine.

 

 

On 27 Oct 2020, at 20:17, Jon Gerdes  wrote:

 

 

This:  https://github.com/netdisco/netdisco-mibs/blob/master/aruba/aruba.my

 

mentions 7220 and 7030, so they are probably supported.  You don't give us much 
else to go on.

 

 

 

On Tue, 2020-10-27 at 12:53 +1030, Muris wrote:

Hi, I have various aruba controllers such as 7220 and 7030, netdisco picks them 
up, however its not grabbing the descriptions of the interfaces and putting 
them in, or connected devices. Interfaces just stay default GE0/0/0, GE0/0/1, 
etc

 

Do these work yet or some slight adjustments to SNMP info need to be made?

 

Thanks

 

___

Netdisco mailing list

netdisco-users@lists.sourceforge.net

https://sourceforge.net/p/netdisco/mailman/netdisco-users/

 

___
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/

___
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/


 

-- 

Neil Johnson (N0SFH)

--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net

netdisco-users Digest, Vol 182, Issue 9

[netdisco-users-request]

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: Similar tool to netdisco for servers ? (Juan Romero)
--- Begin Message ---
I can suggest Open-Audit for full inventory (not monitoring though).

Zabbix or Telegraf + InfluxDB for monitoring.

 
Regards.

 
-

Juan J. Romero

Founder & Director

email: jrom...@auroranetworks.net

m: +61420246579

https://www.auroranetworks.net 

https://logio.auroranetworks.net

Aurora Networks Managed Services

ABN: 50 627 553 619

20-24 Premier Street

Kogarah, NSW 2217

 
  

Follow us on Locals:

https://cybersec.locals.com/

-Original message-
From: Shravan Hulyalkar
Sent: Thursday, September 16 2021, 4:02 pm
To: netdisco-users@lists.sourceforge.net
Subject: [Netdisco] Similar tool to netdisco for servers ?
 Hello All, 

As I have gotten my instance of Netdisco up and running. I have seen how useful 
it is to keep a track of switches. 
Can anyone help if something similar is available for servers as well? I was 
able to discover ESXi in Netdisco using SNMP but it doesn't display the server 
model as you can see in the screenshot attached and wasnt able to do it for 
linux baremetal yet. 

If someone has any pointers would really appreciate it.
   --
 Regards, 
Shravan Hulyalkar
 
 

___

Netdisco mailing list

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

netdisco-users Digest, Vol 181, Issue 3

[netdisco-users-request]

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: wap_platforms and phone_platforms (Nick Nauwelaerts)
   2. Re: Occasional discovery fail (Nick Nauwelaerts)
--- Begin Message ---
wap_platforms seems to be a regular expression list, so the brackets could be 
causing an issue.

on the top of my head i would change it to something like '(?i:.*Aruba\sAP$)'

other issue could be that the ap is not returning the required cpd/lldp/etc 
info:
https://github.com/netdisco/netdisco/wiki/Configuration#wap_capabilities



// nick

From: Ricardo Stella 
Sent: Wednesday, August 4, 2021 21:56
To: netdisco-users@lists.sourceforge.net
Subject: [Netdisco] wap_platforms and phone_platforms


Figure I ask before reinventing the wheel.  Our Aruba APs don't seem to be 
recognized as access points.  They only show a device is inaccessible icon.  No 
entries for discover_waps so default of true should be in effect.

For example, c_platform returns "ArubaOS (MODEL: 315), Version Aruba AP"

Tried adding the whole string to test to deployment.yml but doesn't seem to 
work:

wap_platforms:
 - 'ArubaOS (MODEL: 315), Version Aruba AP'

Am I missing something? Thanks in advance.

--
°(((=((===°°°(((



Volg Aquafin op Facebook | 
Twitter | 
YouTube | 
LinkedIN | 
Instagram

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.

  P Denk aan het milieu. Druk deze mail niet onnodig af.

[https://www.aquafin.be/sites/aquafin/files/styles/paragraph_with_caption/public/2021-04/banner_verhuis%20HK_600x200_blauw_12042021_M.png?itok=ugZqjHed]
--- End Message ---
--- Begin Message ---
did you have a look at 
https://github.com/netdisco/netdisco/wiki/Vendor-Tips#cisco-2960-and-3750-series-giving-incomplete-results
 ?





// nick



> -Original Message-

> From: Eric W. Bates 

> Sent: Tuesday, August 3, 2021 16:30

> To: netdisco-users 

> Subject: [Netdisco] Occasional discovery fail

>

> discovery is apparently failing occasionally when collecting the module

> inventory on cisco c2960-X.

>

> I recently discovered two machines with a single pseudo chassis entry

> and nothing else. I re-ran discovery:

>

> ~netdisco/bin/netdisco-do discover -d challenger01x01 -D

>

> and it failed again:

>

> [3886973] 2021-08-03 12:01:55 debug [172.26.8.226] modules - removed 1

> chassis modules

> [3886973] 2021-08-03 12:01:55 debug  [172.26.8.226] modules - 0 chassis

> components (added one pseudo for chassis)

>

> re-ran a second time:

>

> Use of uninitialized value in hash element at

> /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Entities.p

> m

> line 103.

> Use of uninitialized value in hash element at

> /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Entities.p

> m

> line 103.

> Use of uninitialized value in hash element at

> /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Entities.p

> m

> line 103.

> [3889556] 2021-08-03 12:15:57 debug  [172.26.8.226] modules - removed 1

> chassis modules

> [3889556] 2021-08-03 12:15:57 debug  [172.26.8.226] modules - added 137

> new chassis modules

>

> And it finds all the modules; but there was a series of errors just

> prior to the log about adding the modules and when displayed, the

> modules appeared on the web page with no hierarchy.

>

> so I re-ran a 3rd time and all is well with the universe:

>

> [3890699] 2021-08-03 12:20:39 debug [172.26.8.226] modules - removed 137

> chassis modules

> [3890699] 2021-08-03 12:20:39 debug  [172.26.8.226] modules - added 137

> new chassis modules

>

> I've not noticed this before. I'm guessing it's a timeout on the switch?

>

> Is this somewhat common? (I haven't cooked up a query to find all

> devices with only a single device_module yet.)

>

> Are there any steps I can take?

>

> --

> Clark 159a, MS 46

> 508/289-3112

>

>

>

> ___

> Netdisco mailing list

> 

netdisco-users Digest, Vol 181, Issue 5

[netdisco-users-request]

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: wap_platforms and phone_platforms (Oliver Gorwits)
--- Begin Message ---
Hi,

You shouldn't need to mess with wap_platforms or wap_capabilities, if the
APs are fairly modern.

This is more likely that Netdisco doesn't recognise them as devices or they
are not responding to SNMP sufficiently. This is why the inaccessible icon
... nothing to do with AP and more to do with device discovery.

Simplest approach is to ignore them and allow the AP clients to appear on
the upstream switch port:
https://github.com/netdisco/netdisco/wiki/Configuration#macsuck_unsupported

regards
Oliver

On Wed, 4 Aug 2021 at 22:52, Ricardo Stella  wrote:

>
> Figure I ask before reinventing the wheel.  Our Aruba APs don't seem to be
> recognized as access points.  They only show a device is inaccessible
> icon.  No entries for discover_waps so default of true should be in effect.
>
> For example, c_platform returns "ArubaOS (MODEL: 315), Version Aruba AP"
>
> Tried adding the whole string to test to deployment.yml but doesn't seem
> to work:
>
> wap_platforms:
>  - 'ArubaOS (MODEL: 315), Version Aruba AP'
>
> Am I missing something? Thanks in advance.
>
> --
> °(((=((===°°°(((
> ___
> Netdisco mailing list
> 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

netdisco-users Digest, Vol 181, Issue 4

[netdisco-users-request]

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: wap_platforms and phone_platforms (Ricardo Stella)
--- Begin Message ---
Thanks for the tip but it didn't seem to work even though the regex seems
ok from what I can tell.

Running a discover in debug mode I get (obfuscated):

[2598] 2021-08-10 16:29:50 debug  [10.0.0.110] neigh - 10.1.0.210 with ID
[aa:bb:cc:dd:ee:ff] on GigabitEthernet1/0/1
SELECT me.ip, me.alias, me.subnet, me.port, me.dns, me.creation
  FROM device_ip me
WHERE me.alias = '10.1.0.210' AND me.ip = '10.1.0.210'
SELECT me.ip, me.alias, me.subnet, me.port, me.dns, me.creation
  FROM device_ip me
WHERE alias = '10.1.0.210'
SELECT me.ip, me.creation, me.dns, me.description, me.uptime, me.contact,
me.name, me.location, me.layers, me.num_ports, me.mac, me.serial, me.model,
me.ps1_type, me.ps2_type, me.ps1_status, me.ps2_status, me.fan, me.slots,
me.vendor, me.os, me.os_ver, me.log, me.snmp_ver, me.snmp_comm,
me.snmp_class, me.snmp_engineid, me.vtp_domain, me.last_discover,
me.last_macsuck, me.last_arpnip, to_char( me.creation, '-MM-DD HH24:MI'
), to_char( me.last_arpnip, '-MM-DD HH24:MI' ), to_char(
me.last_discover, '-MM-DD HH24:MI' ), to_char( me.last_macsuck,
'-MM-DD HH24:MI' ), extract( epoch
  FROM age( now(  ), me.creation ) ), extract( epoch
  FROM age( now(  ), me.last_arpnip ) ), extract( epoch
  FROM age( now(  ), me.last_discover ) ), extract( epoch
  FROM age( now(  ), me.last_macsuck ) ), replace( age( timestamp
'epoch' + me.uptime / 100 * interval '1 second', timestamp '1970-01-01
00:00:00-00' ) ::text, 'mon', 'month' )
  FROM device me
WHERE me.ip = '10.1.0.210'
UPDATE device_port
  SET is_uplink = true, manual_topo = false, remote_id =
'aa:bb:cc:dd:ee:ff', remote_ip = '10.1.0210', remote_port = 'bond0',
remote_type = 'ArubaOS (MODEL: 315), Version Aruba AP'
WHERE ip = '10.0.0.110' AND port = 'GigabitEthernet1/0/1'
SELECT me.ip, me.port, me.creation, me.descr, me.up, me.up_admin, me.type,
me.duplex, me.duplex_admin, me.speed, me.speed_admin, me.name, me.mac,
me.mtu, me.stp, me.remote_ip, me.remote_port, me.remote_type, me.remote_id,
me.is_master, me.slave_of, me.manual_topo, me.is_uplink, me.vlan, me.pvid,
me.lastchange
  FROM device_port me
WHERE me.ip = '10.0.0.110' AND me.port = 'GigabitEthernet1/0/1'

My understanding is that this should show a "matches wap_platforms" message
like I get for phones (which do show the telephone icon).

I think the device is returning the capabilities properly - here's the
output

0.1.313  [
[0] "bridge",
[1] "wlanAccessPoint"
],

c_platforms return:

 0.1.313  "ArubaOS (MODEL: 315), Version Aruba AP",

I added the following to deployments.yml:

wap_platforms:
 - '(?i:.*Aruba\sAP$)'

wap_capabilities:
 - '(?i:wlanAccessPoint)'

More than the icon, I'd love to be able to search by the AP name:  Here's
the LLDP info:

Chassis id: aa:bb:cc:dd:ee:ff
Port id: aa:bb:cc:dd:ee:ff
Port Description: bond0
System Name: Test_AP

System Description:
ArubaOS (MODEL: 315), Version Aruba AP


Thanks in advance - Ricardo.

On Tue, Aug 10, 2021 at 1:40 AM Nick Nauwelaerts <
nick.nauwelae...@aquafin.be> wrote:

> wap_platforms seems to be a regular expression list, so the brackets could
> be causing an issue.
>
>
>
> on the top of my head i would change it to something like
> '(?i:.*Aruba\sAP$)'
>
>
>
> other issue could be that the ap is not returning the required
> cpd/lldp/etc info:
>
> https://github.com/netdisco/netdisco/wiki/Configuration#wap_capabilities
>
>
>
>
>
>
>
> // nick
>
>
>
> *From:* Ricardo Stella 
> *Sent:* Wednesday, August 4, 2021 21:56
> *To:* netdisco-users@lists.sourceforge.net
> *Subject:* [Netdisco] wap_platforms and phone_platforms
>
>
>
>
>
> Figure I ask before reinventing the wheel.  Our Aruba APs don't seem to be
> recognized as access points.  They only show a device is inaccessible
> icon.  No entries for discover_waps so default of true should be in effect.
>
>
>
> For example, c_platform returns "ArubaOS (MODEL: 315), Version Aruba AP"
>
>
>
> Tried adding the whole string to test to deployment.yml but doesn't seem
> to work:
>
>
>
> wap_platforms:
>  - 'ArubaOS (MODEL: 315), Version Aruba AP'
>
>
>
> Am I missing something? Thanks in advance.
>
>
>
> --
>
> °(((*=*((*===°°°*(((**
>
>
> --
>
>
> *Volg Aquafin op Facebook  | Twitter
> 

netdisco-users Digest, Vol 181, Issue 1

[netdisco-users-request]

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. Occasional discovery fail (Eric W. Bates)
--- Begin Message ---
discovery is apparently failing occasionally when collecting the module 
inventory on cisco c2960-X.


I recently discovered two machines with a single pseudo chassis entry 
and nothing else. I re-ran discovery:


~netdisco/bin/netdisco-do discover -d challenger01x01 -D

and it failed again:

[3886973] 2021-08-03 12:01:55 debug [172.26.8.226] modules - removed 1 
chassis modules
[3886973] 2021-08-03 12:01:55 debug  [172.26.8.226] modules - 0 chassis 
components (added one pseudo for chassis)


re-ran a second time:

Use of uninitialized value in hash element at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Entities.pm 
line 103.
Use of uninitialized value in hash element at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Entities.pm 
line 103.
Use of uninitialized value in hash element at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Entities.pm 
line 103.
[3889556] 2021-08-03 12:15:57 debug  [172.26.8.226] modules - removed 1 
chassis modules
[3889556] 2021-08-03 12:15:57 debug  [172.26.8.226] modules - added 137 
new chassis modules


And it finds all the modules; but there was a series of errors just 
prior to the log about adding the modules and when displayed, the 
modules appeared on the web page with no hierarchy.


so I re-ran a 3rd time and all is well with the universe:

[3890699] 2021-08-03 12:20:39 debug [172.26.8.226] modules - removed 137 
chassis modules
[3890699] 2021-08-03 12:20:39 debug  [172.26.8.226] modules - added 137 
new chassis modules


I've not noticed this before. I'm guessing it's a timeout on the switch?

Is this somewhat common? (I haven't cooked up a query to find all 
devices with only a single device_module yet.)


Are there any steps I can take?

--
Clark 159a, MS 46
508/289-3112



--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 181, Issue 2

[netdisco-users-request]

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. wap_platforms and phone_platforms (Ricardo Stella)
--- Begin Message ---
Figure I ask before reinventing the wheel.  Our Aruba APs don't seem to be
recognized as access points.  They only show a device is inaccessible
icon.  No entries for discover_waps so default of true should be in effect.

For example, c_platform returns "ArubaOS (MODEL: 315), Version Aruba AP"

Tried adding the whole string to test to deployment.yml but doesn't seem to
work:

wap_platforms:
 - 'ArubaOS (MODEL: 315), Version Aruba AP'

Am I missing something? Thanks in advance.

-- 
°(((=((===°°°(((
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 182, Issue 12

[netdisco-users-request]

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: [External] Re:  Cisco port err-disabled detection
  (Oliver Gorwits)
--- Begin Message ---
Thanks Neil,

OK so your devices are being classified as Layer3::Cisco which is the basic
Cisco class and it does not support this feature.

I find this a bit weird as we have the Layer3::CiscoSwitch class which is
the same as Layer3::Cisco but with some additional stuff. I don't see why
that's not the default for Cisco (well, there is a philosophical argument
here perhaps, or I have just introduced bugs; we shall see).

So I have changed that, and released SNMP::Info 3.79.

Give it a few hours then run:
~netdisco/bin/localenv cpanm --notest SNMP::Info

Then restart netdisco-backend and rediscover the device, and I hope that
the methods test below now resolves, and the data will be in the tables
(you can poke at the device_port_properties table in the database to check).

regards
Oliver.

On Wed, 22 Sept 2021 at 18:35, Johnson, Neil M 
wrote:

> I get an “unable to resolve method.” Error from SNMP::Info::
>
>
>
> -Neil
>
>
>
>
>
> netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e
> i_err_disable_cause -d itdc-2.switch.uiowa.edu -DI
>
> [3239250] 2021-09-22 17:32:00  info App::Netdisco version 2.047008 loaded.
>
> [3239250] 2021-09-22 17:32:01  info show:
> [172.24.128.13]/i_err_disable_cause started at Wed Sep 22 17:32:01 2021
>
> [3239250] 2021-09-22 17:32:01 debug show: running with timeout 600s
>
> [3239250] 2021-09-22 17:32:01 debug => running workers for phase: check
>
> [3239250] 2021-09-22 17:32:01 debug -> run worker check/_base_/0
>
> [3239250] 2021-09-22 17:32:01 debug Show is able to run
>
> [3239250] 2021-09-22 17:32:01 debug => running workers for phase: main
>
> [3239250] 2021-09-22 17:32:01 debug -> run worker main/_base_/100
>
> [3239250] 2021-09-22 17:32:01 debug snmp reader cache warm: [172.24.128.13]
>
> [3239250] 2021-09-22 17:32:01 debug [172.24.128.13:161] try_connect with
> ver: 2, class: SNMP::Info::Layer3::Cisco, comm: 
>
> SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
> .1.3.6.1.2.1.1.3.0
>
> SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
>
> SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 :
> .1.3.6.1.2.1.1.1.0
>
> SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
>
> SNMP::Info 3.73
>
> SNMP::Info::device_type() layers:0110 id:9 sysDescr:"Cisco IOS
> Software [Amsterdam], Catalyst L3 Switch Software (CAT9K_IOSXE), Version
> 17.3.3, RELEASE SOFTWARE (fc7) Technical Support:
> http://www.cisco.com/techsupport Copyright (c) 1986-2021 by Cisco
> Systems, Inc. Compiled Thu 04-Mar-21 12:32 by mcpre"
>
> SNMP::Info::_validate_autoload_method(i_err_disable_cause) Unable to
> resolve method.
>
> undef
>
> [3239250] 2021-09-22 17:32:01  info show: finished at Wed Sep 22 17:32:01
> 2021
>
> [3239250] 2021-09-22 17:32:01  info show: status done: Showed
> i_err_disable_cause response from 172.24.128.13
>
> netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e
> cErrDisableIfStatusCause -d itdc-2.switch.uiowa.edu -DI
>
> [3239258] 2021-09-22 17:32:47  info App::Netdisco version 2.047008 loaded.
>
> [3239258] 2021-09-22 17:32:47  info show:
> [172.24.128.13]/cErrDisableIfStatusCause started at Wed Sep 22 17:32:47 2021
>
> [3239258] 2021-09-22 17:32:47 debug show: running with timeout 600s
>
> [3239258] 2021-09-22 17:32:47 debug => running workers for phase: check
>
> [3239258] 2021-09-22 17:32:47 debug -> run worker check/_base_/0
>
> [3239258] 2021-09-22 17:32:47 debug Show is able to run
>
> [3239258] 2021-09-22 17:32:47 debug => running workers for phase: main
>
> [3239258] 2021-09-22 17:32:47 debug -> run worker main/_base_/100
>
> [3239258] 2021-09-22 17:32:47 debug snmp reader cache warm: [172.24.128.13]
>
> [3239258] 2021-09-22 17:32:47 debug [172.24.128.13:161] try_connect with
> ver: 2, class: SNMP::Info::Layer3::Cisco, comm: 
>
> SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
> .1.3.6.1.2.1.1.3.0
>
> SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
>
> SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 :
> .1.3.6.1.2.1.1.1.0
>
> SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
>
> SNMP::Info 3.73
>
> SNMP::Info::device_type() layers:0110 id:9 sysDescr:"Cisco IOS
> Software [Amsterdam], Catalyst L3 Switch Software (CAT9K_IOSXE), Version
> 17.3.3, RELEASE 

netdisco-users Digest, Vol 182, Issue 16

[netdisco-users-request]

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: [External] Re:  Cisco port err-disabled detection
  (Oliver Gorwits)
--- Begin Message ---
Awesome 

On Fri, 24 Sep 2021 at 17:32, Johnson, Neil M 
wrote:

>
>
> That did the trick! Thanks so much!
>
>
>
> -Neil
>
>
>
> --
>
> Neil Johnson – University of Iowa
>
>
>
> *From:* Oliver Gorwits 
> *Sent:* Friday, September 24, 2021 10:36 AM
> *To:* Johnson, Neil M 
> *Cc:* netdisco-users@lists.sourceforge.net
> *Subject:* Re: [External] Re: [Netdisco] Cisco port err-disabled detection
>
>
>
> Yes, run discover on the devices again and see if that works. Hope so!
>
>
>
> On Fri, 24 Sep 2021 at 15:56, Johnson, Neil M 
> wrote:
>
> Oliver,
>
>
>
> The commands are working but, now the data is not showing up on the
> Reports->Ports->Error Disabled Ports report, or on the ports page for the
> device.
>
>
>
> Or do I  just need to wait for a day for the data to be polled?
>
>
>
> Thanks!
>
>
>
> -Neil
>
>
>
> --
>
> Neil Johnson – University of Iowa
>
>
>
> *From:* Oliver Gorwits 
> *Sent:* Wednesday, September 22, 2021 4:20 PM
> *To:* Johnson, Neil M 
> *Cc:* netdisco-users@lists.sourceforge.net
> *Subject:* Re: [External] Re: [Netdisco] Cisco port err-disabled detection
>
>
>
> Thanks Neil,
>
>
>
> OK so your devices are being classified as Layer3::Cisco which is the
> basic Cisco class and it does not support this feature.
>
>
>
> I find this a bit weird as we have the Layer3::CiscoSwitch class which is
> the same as Layer3::Cisco but with some additional stuff. I don't see why
> that's not the default for Cisco (well, there is a philosophical argument
> here perhaps, or I have just introduced bugs; we shall see).
>
>
>
> So I have changed that, and released SNMP::Info 3.79.
>
>
>
> Give it a few hours then run:
>
> ~netdisco/bin/localenv cpanm --notest SNMP::Info
>
>
>
> Then restart netdisco-backend and rediscover the device, and I hope that
> the methods test below now resolves, and the data will be in the tables
> (you can poke at the device_port_properties table in the database to check).
>
>
>
> regards
>
> Oliver.
>
>
>
> On Wed, 22 Sept 2021 at 18:35, Johnson, Neil M 
> wrote:
>
> I get an “unable to resolve method.” Error from SNMP::Info::
>
>
>
> -Neil
>
>
>
>
>
> netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e
> i_err_disable_cause -d itdc-2.switch.uiowa.edu -DI
>
> [3239250] 2021-09-22 17:32:00  info App::Netdisco version 2.047008 loaded.
>
> [3239250] 2021-09-22 17:32:01  info show:
> [172.24.128.13]/i_err_disable_cause started at Wed Sep 22 17:32:01 2021
>
> [3239250] 2021-09-22 17:32:01 debug show: running with timeout 600s
>
> [3239250] 2021-09-22 17:32:01 debug => running workers for phase: check
>
> [3239250] 2021-09-22 17:32:01 debug -> run worker check/_base_/0
>
> [3239250] 2021-09-22 17:32:01 debug Show is able to run
>
> [3239250] 2021-09-22 17:32:01 debug => running workers for phase: main
>
> [3239250] 2021-09-22 17:32:01 debug -> run worker main/_base_/100
>
> [3239250] 2021-09-22 17:32:01 debug snmp reader cache warm: [172.24.128.13]
>
> [3239250] 2021-09-22 17:32:01 debug [172.24.128.13:161] try_connect with
> ver: 2, class: SNMP::Info::Layer3::Cisco, comm: 
>
> SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
> .1.3.6.1.2.1.1.3.0
>
> SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
>
> SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 :
> .1.3.6.1.2.1.1.1.0
>
> SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
>
> SNMP::Info 3.73
>
> SNMP::Info::device_type() layers:0110 id:9 sysDescr:"Cisco IOS
> Software [Amsterdam], Catalyst L3 Switch Software (CAT9K_IOSXE), Version
> 17.3.3, RELEASE SOFTWARE (fc7) Technical Support:
> http://www.cisco.com/techsupport Copyright (c) 1986-2021 by Cisco
> Systems, Inc. Compiled Thu 04-Mar-21 12:32 by mcpre"
>
> SNMP::Info::_validate_autoload_method(i_err_disable_cause) Unable to
> resolve method.
>
> undef
>
> [3239250] 2021-09-22 17:32:01  info show: finished at Wed Sep 22 17:32:01
> 2021
>
> [3239250] 2021-09-22 17:32:01  info show: status done: Showed
> i_err_disable_cause response from 172.24.128.13
>
> netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e
> cErrDisableIfStatusCause -d itdc-2.switch.uiowa.edu -DI
>
> [3239258] 2021-09-22 17:32:47  info App::Netdisco version 2.047008 loaded.
>
> [3239258] 2021-09-22 17:32:47  info show:
> [172.24.128.13]/cErrDisableIfStatusCause started at Wed 

netdisco-users Digest, Vol 182, Issue 14

[netdisco-users-request]

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: [External] Re:  Cisco port err-disabled detection
  (Oliver Gorwits)
--- Begin Message ---
Yes, run discover on the devices again and see if that works. Hope so!

On Fri, 24 Sep 2021 at 15:56, Johnson, Neil M 
wrote:

> Oliver,
>
>
>
> The commands are working but, now the data is not showing up on the
> Reports->Ports->Error Disabled Ports report, or on the ports page for the
> device.
>
>
>
> Or do I  just need to wait for a day for the data to be polled?
>
>
>
> Thanks!
>
>
>
> -Neil
>
>
>
> --
>
> Neil Johnson – University of Iowa
>
>
>
> *From:* Oliver Gorwits 
> *Sent:* Wednesday, September 22, 2021 4:20 PM
> *To:* Johnson, Neil M 
> *Cc:* netdisco-users@lists.sourceforge.net
> *Subject:* Re: [External] Re: [Netdisco] Cisco port err-disabled detection
>
>
>
> Thanks Neil,
>
>
>
> OK so your devices are being classified as Layer3::Cisco which is the
> basic Cisco class and it does not support this feature.
>
>
>
> I find this a bit weird as we have the Layer3::CiscoSwitch class which is
> the same as Layer3::Cisco but with some additional stuff. I don't see why
> that's not the default for Cisco (well, there is a philosophical argument
> here perhaps, or I have just introduced bugs; we shall see).
>
>
>
> So I have changed that, and released SNMP::Info 3.79.
>
>
>
> Give it a few hours then run:
>
> ~netdisco/bin/localenv cpanm --notest SNMP::Info
>
>
>
> Then restart netdisco-backend and rediscover the device, and I hope that
> the methods test below now resolves, and the data will be in the tables
> (you can poke at the device_port_properties table in the database to check).
>
>
>
> regards
>
> Oliver.
>
>
>
> On Wed, 22 Sept 2021 at 18:35, Johnson, Neil M 
> wrote:
>
> I get an “unable to resolve method.” Error from SNMP::Info::
>
>
>
> -Neil
>
>
>
>
>
> netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e
> i_err_disable_cause -d itdc-2.switch.uiowa.edu -DI
>
> [3239250] 2021-09-22 17:32:00  info App::Netdisco version 2.047008 loaded.
>
> [3239250] 2021-09-22 17:32:01  info show:
> [172.24.128.13]/i_err_disable_cause started at Wed Sep 22 17:32:01 2021
>
> [3239250] 2021-09-22 17:32:01 debug show: running with timeout 600s
>
> [3239250] 2021-09-22 17:32:01 debug => running workers for phase: check
>
> [3239250] 2021-09-22 17:32:01 debug -> run worker check/_base_/0
>
> [3239250] 2021-09-22 17:32:01 debug Show is able to run
>
> [3239250] 2021-09-22 17:32:01 debug => running workers for phase: main
>
> [3239250] 2021-09-22 17:32:01 debug -> run worker main/_base_/100
>
> [3239250] 2021-09-22 17:32:01 debug snmp reader cache warm: [172.24.128.13]
>
> [3239250] 2021-09-22 17:32:01 debug [172.24.128.13:161] try_connect with
> ver: 2, class: SNMP::Info::Layer3::Cisco, comm: 
>
> SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
> .1.3.6.1.2.1.1.3.0
>
> SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
>
> SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 :
> .1.3.6.1.2.1.1.1.0
>
> SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
>
> SNMP::Info 3.73
>
> SNMP::Info::device_type() layers:0110 id:9 sysDescr:"Cisco IOS
> Software [Amsterdam], Catalyst L3 Switch Software (CAT9K_IOSXE), Version
> 17.3.3, RELEASE SOFTWARE (fc7) Technical Support:
> http://www.cisco.com/techsupport Copyright (c) 1986-2021 by Cisco
> Systems, Inc. Compiled Thu 04-Mar-21 12:32 by mcpre"
>
> SNMP::Info::_validate_autoload_method(i_err_disable_cause) Unable to
> resolve method.
>
> undef
>
> [3239250] 2021-09-22 17:32:01  info show: finished at Wed Sep 22 17:32:01
> 2021
>
> [3239250] 2021-09-22 17:32:01  info show: status done: Showed
> i_err_disable_cause response from 172.24.128.13
>
> netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e
> cErrDisableIfStatusCause -d itdc-2.switch.uiowa.edu -DI
>
> [3239258] 2021-09-22 17:32:47  info App::Netdisco version 2.047008 loaded.
>
> [3239258] 2021-09-22 17:32:47  info show:
> [172.24.128.13]/cErrDisableIfStatusCause started at Wed Sep 22 17:32:47 2021
>
> [3239258] 2021-09-22 17:32:47 debug show: running with timeout 600s
>
> [3239258] 2021-09-22 17:32:47 debug => running workers for phase: check
>
> [3239258] 2021-09-22 17:32:47 debug -> run worker check/_base_/0
>
> [3239258] 2021-09-22 17:32:47 debug Show is able to run
>
> [3239258] 2021-09-22 17:32:47 debug => running workers for phase: main
>
> [3239258] 2021-09-22 17:32:47 debug 

netdisco-users Digest, Vol 182, Issue 15

[netdisco-users-request]

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: [External] Re:  Cisco port err-disabled detection
  (Johnson, Neil M)
--- Begin Message ---

That did the trick! Thanks so much!

-Neil

--
Neil Johnson – University of Iowa

From: Oliver Gorwits 
Sent: Friday, September 24, 2021 10:36 AM
To: Johnson, Neil M 
Cc: netdisco-users@lists.sourceforge.net
Subject: Re: [External] Re: [Netdisco] Cisco port err-disabled detection

Yes, run discover on the devices again and see if that works. Hope so!

On Fri, 24 Sep 2021 at 15:56, Johnson, Neil M 
mailto:neil-john...@uiowa.edu>> wrote:
Oliver,

The commands are working but, now the data is not showing up on the 
Reports->Ports->Error Disabled Ports report, or on the ports page for the 
device.

Or do I  just need to wait for a day for the data to be polled?

Thanks!

-Neil

--
Neil Johnson – University of Iowa

From: Oliver Gorwits mailto:oli...@cpan.org>>
Sent: Wednesday, September 22, 2021 4:20 PM
To: Johnson, Neil M mailto:neil-john...@uiowa.edu>>
Cc: 
netdisco-users@lists.sourceforge.net
Subject: Re: [External] Re: [Netdisco] Cisco port err-disabled detection

Thanks Neil,

OK so your devices are being classified as Layer3::Cisco which is the basic 
Cisco class and it does not support this feature.

I find this a bit weird as we have the Layer3::CiscoSwitch class which is the 
same as Layer3::Cisco but with some additional stuff. I don't see why that's 
not the default for Cisco (well, there is a philosophical argument here 
perhaps, or I have just introduced bugs; we shall see).

So I have changed that, and released SNMP::Info 3.79.

Give it a few hours then run:
~netdisco/bin/localenv cpanm --notest SNMP::Info

Then restart netdisco-backend and rediscover the device, and I hope that the 
methods test below now resolves, and the data will be in the tables (you can 
poke at the device_port_properties table in the database to check).

regards
Oliver.

On Wed, 22 Sept 2021 at 18:35, Johnson, Neil M 
mailto:neil-john...@uiowa.edu>> wrote:
I get an “unable to resolve method.” Error from SNMP::Info::

-Neil


netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e i_err_disable_cause -d 
itdc-2.switch.uiowa.edu -DI
[3239250] 2021-09-22 17:32:00  info App::Netdisco version 2.047008 loaded.
[3239250] 2021-09-22 17:32:01  info show: [172.24.128.13]/i_err_disable_cause 
started at Wed Sep 22 17:32:01 2021
[3239250] 2021-09-22 17:32:01 debug show: running with timeout 600s
[3239250] 2021-09-22 17:32:01 debug => running workers for phase: check
[3239250] 2021-09-22 17:32:01 debug -> run worker check/_base_/0
[3239250] 2021-09-22 17:32:01 debug Show is able to run
[3239250] 2021-09-22 17:32:01 debug => running workers for phase: main
[3239250] 2021-09-22 17:32:01 debug -> run worker main/_base_/100
[3239250] 2021-09-22 17:32:01 debug snmp reader cache warm: [172.24.128.13]
[3239250] 2021-09-22 17:32:01 debug 
[172.24.128.13:161] try_connect with ver: 2, class: 
SNMP::Info::Layer3::Cisco, comm: 
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance : 
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0
SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
SNMP::Info 3.73
SNMP::Info::device_type() layers:0110 id:9 sysDescr:"Cisco IOS Software 
[Amsterdam], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.3.3, RELEASE 
SOFTWARE (fc7) Technical Support: http://www.cisco.com/techsupport Copyright 
(c) 1986-2021 by Cisco Systems, Inc. Compiled Thu 04-Mar-21 12:32 by mcpre"
SNMP::Info::_validate_autoload_method(i_err_disable_cause) Unable to resolve 
method.
undef
[3239250] 2021-09-22 17:32:01  info show: finished at Wed Sep 22 17:32:01 2021
[3239250] 2021-09-22 17:32:01  info show: status done: Showed 
i_err_disable_cause response from 172.24.128.13
netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e cErrDisableIfStatusCause 
-d itdc-2.switch.uiowa.edu -DI
[3239258] 2021-09-22 17:32:47  info App::Netdisco version 2.047008 loaded.
[3239258] 2021-09-22 17:32:47  info show: 
[172.24.128.13]/cErrDisableIfStatusCause started at Wed Sep 22 17:32:47 2021
[3239258] 2021-09-22 17:32:47 debug show: running with timeout 600s
[3239258] 2021-09-22 17:32:47 debug => running workers 

netdisco-users Digest, Vol 182, Issue 13

[netdisco-users-request]

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: [External] Re:  Cisco port err-disabled detection
  (Johnson, Neil M)
--- Begin Message ---
Oliver,

The commands are working but, now the data is not showing up on the 
Reports->Ports->Error Disabled Ports report, or on the ports page for the 
device.

Or do I  just need to wait for a day for the data to be polled?

Thanks!

-Neil

--
Neil Johnson – University of Iowa

From: Oliver Gorwits 
Sent: Wednesday, September 22, 2021 4:20 PM
To: Johnson, Neil M 
Cc: netdisco-users@lists.sourceforge.net
Subject: Re: [External] Re: [Netdisco] Cisco port err-disabled detection

Thanks Neil,

OK so your devices are being classified as Layer3::Cisco which is the basic 
Cisco class and it does not support this feature.

I find this a bit weird as we have the Layer3::CiscoSwitch class which is the 
same as Layer3::Cisco but with some additional stuff. I don't see why that's 
not the default for Cisco (well, there is a philosophical argument here 
perhaps, or I have just introduced bugs; we shall see).

So I have changed that, and released SNMP::Info 3.79.

Give it a few hours then run:
~netdisco/bin/localenv cpanm --notest SNMP::Info

Then restart netdisco-backend and rediscover the device, and I hope that the 
methods test below now resolves, and the data will be in the tables (you can 
poke at the device_port_properties table in the database to check).

regards
Oliver.

On Wed, 22 Sept 2021 at 18:35, Johnson, Neil M 
mailto:neil-john...@uiowa.edu>> wrote:
I get an “unable to resolve method.” Error from SNMP::Info::

-Neil


netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e i_err_disable_cause -d 
itdc-2.switch.uiowa.edu -DI
[3239250] 2021-09-22 17:32:00  info App::Netdisco version 2.047008 loaded.
[3239250] 2021-09-22 17:32:01  info show: [172.24.128.13]/i_err_disable_cause 
started at Wed Sep 22 17:32:01 2021
[3239250] 2021-09-22 17:32:01 debug show: running with timeout 600s
[3239250] 2021-09-22 17:32:01 debug => running workers for phase: check
[3239250] 2021-09-22 17:32:01 debug -> run worker check/_base_/0
[3239250] 2021-09-22 17:32:01 debug Show is able to run
[3239250] 2021-09-22 17:32:01 debug => running workers for phase: main
[3239250] 2021-09-22 17:32:01 debug -> run worker main/_base_/100
[3239250] 2021-09-22 17:32:01 debug snmp reader cache warm: [172.24.128.13]
[3239250] 2021-09-22 17:32:01 debug 
[172.24.128.13:161] try_connect with ver: 2, class: 
SNMP::Info::Layer3::Cisco, comm: 
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance : 
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0
SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
SNMP::Info 3.73
SNMP::Info::device_type() layers:0110 id:9 sysDescr:"Cisco IOS Software 
[Amsterdam], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.3.3, RELEASE 
SOFTWARE (fc7) Technical Support: http://www.cisco.com/techsupport Copyright 
(c) 1986-2021 by Cisco Systems, Inc. Compiled Thu 04-Mar-21 12:32 by mcpre"
SNMP::Info::_validate_autoload_method(i_err_disable_cause) Unable to resolve 
method.
undef
[3239250] 2021-09-22 17:32:01  info show: finished at Wed Sep 22 17:32:01 2021
[3239250] 2021-09-22 17:32:01  info show: status done: Showed 
i_err_disable_cause response from 172.24.128.13
netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e cErrDisableIfStatusCause 
-d itdc-2.switch.uiowa.edu -DI
[3239258] 2021-09-22 17:32:47  info App::Netdisco version 2.047008 loaded.
[3239258] 2021-09-22 17:32:47  info show: 
[172.24.128.13]/cErrDisableIfStatusCause started at Wed Sep 22 17:32:47 2021
[3239258] 2021-09-22 17:32:47 debug show: running with timeout 600s
[3239258] 2021-09-22 17:32:47 debug => running workers for phase: check
[3239258] 2021-09-22 17:32:47 debug -> run worker check/_base_/0
[3239258] 2021-09-22 17:32:47 debug Show is able to run
[3239258] 2021-09-22 17:32:47 debug => running workers for phase: main
[3239258] 2021-09-22 17:32:47 debug -> run worker main/_base_/100
[3239258] 2021-09-22 17:32:47 debug snmp reader cache warm: [172.24.128.13]
[3239258] 2021-09-22 17:32:47 debug 
[172.24.128.13:161] try_connect with ver: 2, class: 
SNMP::Info::Layer3::Cisco, comm: 
SNMP::Info::_global uptime : 

netdisco-users Digest, Vol 182, Issue 17

[netdisco-users-request]

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: Netdisco search results missing randomly (Muris)
   2. Re: Netdisco search results missing randomly (Joseph Bernard)
--- Begin Message ---
This issue is getting so annoying, the search function just becomes broken 
constantly 

 

Even on the latest version shows, when you go in inventory, click the devices 
in the amount of inventory and shows blank results

 

Like im having to restart netdisco-web many times throughout the day

 

From: Muris 
Date: Monday, 13 September 2021 at 23:03
To: Joseph Bernard 
Cc: "netdisco-users@lists.sourceforge.net" 

Subject: Re: [Netdisco] Netdisco search results missing randomly

 

Thanks same i did it also. It should really be fixed its quite an annoying bug.

 

As with the issue and arnip crashing, i truncated the subnets table in pgsql 
database which seems to have fixed it.

 

Theres a few issues id like fixed at moment, but its having a resource who can 
look at it and patch it. 

 




On 13 Sep 2021, at 20:51, Joseph Bernard  wrote:

 I’ve never figured out the cause, but I set up a cronjob to restart 
netdisco-web as a workaround. If I remember correctly, you can actually see the 
results in the source code of the page, but I guess it’s missing the code or 
something to make it display. 

 

 

Thanks,

Joseph B.




On Sep 13, 2021, at 12:08 AM, Muris  wrote:

 

By the way, to get it working, I have to restart netdisco-web

 

I can’t really see errors in netdisco-web log though

 

From: Muris 
Date: Monday, 13 September 2021 at 13:32
To: "netdisco-users@lists.sourceforge.net" 

Subject: Netdisco search results missing randomly

 

Hi,

 

Ive noticed sometimes netdisco search results are missing, even if you want to 
enter the specific device it comes up empty

 

I had a look at the backend and im seeing things like this, any ideas what is 
causing this?

 

DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  

SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Arpnip/Subnets.pm 
line 65

 

DBIx::Class::Storage::DBI::select_single(): Query returned more than one row.  

SQL that returns multiple rows is DEPRECATED for ->find and ->single at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Node.pm line 182

 

Use of uninitialized value $res{"234"} in string eq at 
/home/netdisco/perl5/lib/perl5/SNMP/Info/CiscoStpExtensions.   pm line 256.

 

 

Thankyou

___
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/

--- End Message ---
--- Begin Message ---
I find that refreshing the page over and over will eventually work.  Still 
annoying but it’s something.

Thanks,
Joseph B.

Sent from my iPhone

On Sep 26, 2021, at 10:25 PM, Muris  wrote:


This issue is getting so annoying, the search function just becomes broken 
constantly

Even on the latest version shows, when you go in inventory, click the devices 
in the amount of inventory and shows blank results

Like im having to restart netdisco-web many times throughout the day

From: Muris 
Date: Monday, 13 September 2021 at 23:03
To: Joseph Bernard 
Cc: "netdisco-users@lists.sourceforge.net" 

Subject: Re: [Netdisco] Netdisco search results missing randomly

Thanks same i did it also. It should really be fixed its quite an annoying bug.

As with the issue and arnip crashing, i truncated the subnets table in pgsql 
database which seems to have fixed it.

Theres a few issues id like fixed at moment, but its having a resource who can 
look at it and patch it.



On 13 Sep 2021, at 20:51, Joseph Bernard  wrote:
 I’ve never figured out the cause, but I set up a cronjob to restart 
netdisco-web as a workaround. If I remember correctly, you can actually see the 
results in the source code of the page, but I guess it’s missing the code or 
something to make it display.


Thanks,
Joseph B.


On Sep 13, 2021, at 12:08 AM, Muris  wrote:

By the way, to get it working, I have to restart netdisco-web

I can’t really see errors in netdisco-web log though

From: Muris 
Date: Monday, 13 September 2021 at 13:32
To: "netdisco-users@lists.sourceforge.net" 

Subject: Netdisco search results missing randomly

Hi,

Ive noticed sometimes netdisco search results are missing, even if you want to 
enter the specific device it comes up empty

I had 

netdisco-users Digest, Vol 182, Issue 20

[netdisco-users-request]

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: H3C switch discover - failed to return valid serial (Muris)
--- Begin Message ---
Thanks, I changed it and it seems to work, however a few other things happened..

 

On the discovery process comes up failed to get uptime, but does scan in..

 

When it gets to macsuck.. it says ports have no bp_index.. then 0 macs found.. 
then arp also returns 0 results.

 

The same 5130 switch with a single device or 2-3 in a stack work fine.. seems 
something doesn’t like with 8 of them in a stack.

 

Discover 

 

3815] 2021-09-27 10:06:59 debug -> run worker early/properties/100

[3815] 2021-09-27 10:08:26 error  [10.x.x.x] interfaces - Error! Failed to get 
uptime from device!

[3815] 2021-09-27 10:08:26 debug discover failed: no uptime from device 
10.x.x.x!

[3815] 2021-09-27 10:08:26 debug => running workers for phase: main

[3815] 2021-09-27 10:08:26 debug -> run worker main/canonicalip/100

[3815] 2021-09-27 10:08:26 debug -> run worker main/entities/100

[3815] 2021-09-27 10:08:29 debug  [10.x.x.x] modules - removed 690 chassis 
modules

[3815] 2021-09-27 10:08:29 debug  [10.x.x.x] modules - 0 chassis components 
(added one pseudo for chassis)

[3815] 2021-09-27 10:08:29 debug -> run worker main/neighbors/100

[3815] 2021-09-27 10:08:30 debug  [10.x.x.x] neigh - removed 0 outdated manual 
topology links

[3815] 2021-09-27 10:08:30 debug  [10.x.x.x] neigh - setting manual topology 
links

[3815] 2021-09-27 10:09:09 debug  [10.x.x.x] neigh - processed 0 neighbors

[3815] 2021-09-27 10:09:09 debug -> run worker main/neighbors/100

[3815] 2021-09-27 10:09:21 debug  [10.x.x.x] neigh - no BGP, OSPF, IS-IS, or 
EIGRP peers

[3815] 2021-09-27 10:09:21 debug -> run worker main/neighbors/100

[3815] 2021-09-27 10:09:24 debug  [10.x.x.x] neigh - no modems (probably not a 
DOCSIS device)

[3815] 2021-09-27 10:09:24 debug -> run worker main/portpower/100

[3815] 2021-09-27 10:09:30 debug  [10.x.x.x] power - 0 power modules

[3815] 2021-09-27 10:09:30 debug -> run worker main/portproperties/100

[3815] 2021-09-27 10:09:30 debug  [10.x.x.x] properties/speed - local port 
NULL0 already skipped, ignoring

[3815] 2021-09-27 10:10:00 debug  [10.x.x.x] properties/ifindex - local port 
NULL0 already skipped, ignoring

[3815] 2021-09-27 10:10:00 debug  [10.x.x.x] properties - removed 423 ports 
with properties

[3815] 2021-09-27 10:10:00 debug  [10.x.x.x] properties - added 423 new port 
properties

[3815] 2021-09-27 10:10:00 debug -> run worker main/vlans/100

[3815] 2021-09-27 10:10:27 debug  [10.x.x.x] vlans - removed 177 port VLANs

[3815] 2021-09-27 10:10:27 debug  [10.x.x.x] vlans - added 0 new port VLANs

[3815] 2021-09-27 10:10:27 debug  [10.x.x.x] vlans - removed 10 device VLANs

[3815] 2021-09-27 10:10:27 debug  [10.x.x.x] vlans - added 0 new device VLANs

[3815] 2021-09-27 10:10:27 debug  [10.x.x.x] vlans - discovered for ports and 
device

[3815] 2021-09-27 10:10:27 debug -> run worker main/wireless/100

[3815] 2021-09-27 10:10:27 debug -> run worker main/withnodes/0

 

Macsuck

 

[5672] 2021-09-27 10:14:08 debug => running workers for phase: main

[5672] 2021-09-27 10:14:08 debug -> run worker main/nodes/100

[5672] 2021-09-27 10:14:08 debug snmp reader cache warm: [10.x.x.x]

[5672] 2021-09-27 10:14:08 debug [10.x.x.x:161] try_connect with ver: 2, class: 
SNMP::Info::Layer3::H3C, comm: 

[5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 00:17:c8:a0:7e:55 - port 
156 has no bp_index mapping - skipping.

[5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 00:17:c8:43:2d:57 - port 
351 has no bp_index mapping - skipping.

[5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 6c:4b:90:64:48:d7 - port 
12 has no bp_index mapping - skipping.

[5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 00:17:c8:36:08:7b - port 
97 has no bp_index mapping - skipping.

[5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 6c:4b:90:60:1f:56 - port 
15 has no bp_index mapping - skipping.

[5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 00:17:c8:36:1e:e9 - port 
480 has no bp_index mapping - skipping.

[5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 00:07:4d:aa:c7:cd - port 
202 has no bp_index mapping - skipping.

[5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 00:17:c8:10:6e:ad - port 
152 has no bp_index mapping - skipping.

[5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 6c:4b:90:a2:ed:0f - port 
26 has no bp_index mapping - skipping.

netdisco-users Digest, Vol 182, Issue 21

[netdisco-users-request]

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: H3C switch discover - failed to return valid serial
  (Oliver Gorwits)
--- Begin Message ---
I wonder if this is timeouts, then, as the stack gets bigger?

You could try some command line tests:
~netdisco/bin/netdisco-do show -e uptime -d 1.2.3.4 -DI

You can try changing some of the snmp timeout settings:
https://github.com/netdisco/netdisco/wiki/Configuration#snmptimeout

regards
Oliver

On Mon, 27 Sept 2021 at 11:33, Muris  wrote:

> Thanks, I changed it and it seems to work, however a few other things
> happened..
>
>
>
> On the discovery process comes up failed to get uptime, but does scan in..
>
>
>
> When it gets to macsuck.. it says ports have no bp_index.. then 0 macs
> found.. then arp also returns 0 results.
>
>
>
> The same 5130 switch with a single device or 2-3 in a stack work fine..
> seems something doesn’t like with 8 of them in a stack.
>
>
>
> Discover
>
>
>
> 3815] 2021-09-27 10:06:59 debug -> run worker early/properties/100
>
> *[3815] 2021-09-27 10:08:26 error  [10.x.x.x] interfaces - Error! Failed
> to get uptime from device!*
>
> *[3815] 2021-09-27 10:08:26 debug discover failed: no uptime from device
> 10.x.x.x!*
>
> [3815] 2021-09-27 10:08:26 debug => running workers for phase: main
>
> [3815] 2021-09-27 10:08:26 debug -> run worker main/canonicalip/100
>
> [3815] 2021-09-27 10:08:26 debug -> run worker main/entities/100
>
> [3815] 2021-09-27 10:08:29 debug  [10.x.x.x] modules - removed 690 chassis
> modules
>
> [3815] 2021-09-27 10:08:29 debug  [10.x.x.x] modules - 0 chassis
> components (added one pseudo for chassis)
>
> [3815] 2021-09-27 10:08:29 debug -> run worker main/neighbors/100
>
> [3815] 2021-09-27 10:08:30 debug  [10.x.x.x] neigh - removed 0 outdated
> manual topology links
>
> [3815] 2021-09-27 10:08:30 debug  [10.x.x.x] neigh - setting manual
> topology links
>
> [3815] 2021-09-27 10:09:09 debug  [10.x.x.x] neigh - processed 0 neighbors
>
> [3815] 2021-09-27 10:09:09 debug -> run worker main/neighbors/100
>
> [3815] 2021-09-27 10:09:21 debug  [10.x.x.x] neigh - no BGP, OSPF, IS-IS,
> or EIGRP peers
>
> [3815] 2021-09-27 10:09:21 debug -> run worker main/neighbors/100
>
> [3815] 2021-09-27 10:09:24 debug  [10.x.x.x] neigh - no modems (probably
> not a DOCSIS device)
>
> [3815] 2021-09-27 10:09:24 debug -> run worker main/portpower/100
>
> [3815] 2021-09-27 10:09:30 debug  [10.x.x.x] power - 0 power modules
>
> [3815] 2021-09-27 10:09:30 debug -> run worker main/portproperties/100
>
> [3815] 2021-09-27 10:09:30 debug  [10.x.x.x] properties/speed - local port
> NULL0 already skipped, ignoring
>
> [3815] 2021-09-27 10:10:00 debug  [10.x.x.x] properties/ifindex - local
> port NULL0 already skipped, ignoring
>
> [3815] 2021-09-27 10:10:00 debug  [10.x.x.x] properties - removed 423
> ports with properties
>
> [3815] 2021-09-27 10:10:00 debug  [10.x.x.x] properties - added 423 new
> port properties
>
> [3815] 2021-09-27 10:10:00 debug -> run worker main/vlans/100
>
> [3815] 2021-09-27 10:10:27 debug  [10.x.x.x] vlans - removed 177 port VLANs
>
> [3815] 2021-09-27 10:10:27 debug  [10.x.x.x] vlans - added 0 new port VLANs
>
> [3815] 2021-09-27 10:10:27 debug  [10.x.x.x] vlans - removed 10 device
> VLANs
>
> [3815] 2021-09-27 10:10:27 debug  [10.x.x.x] vlans - added 0 new device
> VLANs
>
> [3815] 2021-09-27 10:10:27 debug  [10.x.x.x] vlans - discovered for ports
> and device
>
> [3815] 2021-09-27 10:10:27 debug -> run worker main/wireless/100
>
> [3815] 2021-09-27 10:10:27 debug -> run worker main/withnodes/0
>
>
>
> Macsuck
>
>
>
> [5672] 2021-09-27 10:14:08 debug => running workers for phase: main
>
> [5672] 2021-09-27 10:14:08 debug -> run worker main/nodes/100
>
> [5672] 2021-09-27 10:14:08 debug snmp reader cache warm: [10.x.x.x]
>
> [5672] 2021-09-27 10:14:08 debug [10.x.x.x:161] try_connect with ver: 2,
> class: SNMP::Info::Layer3::H3C, comm: 
>
> [5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 00:17:c8:a0:7e:55 -
> port 156 has no bp_index mapping - skipping.
>
> [5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 00:17:c8:43:2d:57 -
> port 351 has no bp_index mapping - skipping.
>
> [5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 6c:4b:90:64:48:d7 -
> port 12 has no bp_index mapping - skipping.
>
> [5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 00:17:c8:36:08:7b -
> port 97 has no bp_index mapping - skipping.
>
> [5672] 2021-09-27 10:14:30 debug  [10.x.x.x] macsuck 

netdisco-users Digest, Vol 182, Issue 10

[netdisco-users-request]

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. Cisco port err-disabled detection (Johnson, Neil M)
   2. Re: Cisco port err-disabled detection (Oliver Gorwits)
--- Begin Message ---

We have a cisco network.

Is there something I need enable/configure in order to make the report for err 
disabled ports work?

I have forced a port into error disable state, but netdisco is not detecting it.

If this is an issue what information is needed to help troublshoot the issue.

Thanks!
-Neil

--
Neil Johnson (he/him/his)
Network Architect, Network Engineering Services
S5 Lindquist Center, Iowa City, Iowa 52242
Office: 319-384-0938
uiowa.edu
[The University of Iowa Logo]

--- End Message ---
--- Begin Message ---
Hi Neil

This report relies on the i_err_disable_cause() method in SNMP::Info, so
are you getting anything from:

~netdisco/bin/netdisco-do show -e i_err_disable_cause -d 1.2.3.4 -DI
~netdisco/bin/netdisco-do show -e cErrDisableIfStatusCause -d 1.2.3.4 -DI

I am not sure how widely this method is implemented, for what classes, etc.

regards
Oliver

On Wed, 22 Sept 2021 at 03:15, Johnson, Neil M 
wrote:

>
>
> We have a cisco network.
>
>
>
> Is there something I need enable/configure in order to make the report for
> err disabled ports work?
>
>
>
> I have forced a port into error disable state, but netdisco is not
> detecting it.
>
>
>
> If this is an issue what information is needed to help troublshoot the
> issue.
>
>
>
> Thanks!
>
> -Neil
>
>
>
> *-- *
>
> *Neil Johnson (he/him/his)*
> Network Architect, Network Engineering Services
> S5 Lindquist Center, Iowa City, Iowa 52242
> Office: 319-384-0938
>
> *uiowa.edu *
>
> [image: The University of Iowa Logo]
>
>
> ___
> Netdisco mailing list
> 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

netdisco-users Digest, Vol 182, Issue 11

[netdisco-users-request]

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: [External] Re:  Cisco port err-disabled detection
  (Johnson, Neil M)
--- Begin Message ---
I get an “unable to resolve method.” Error from SNMP::Info::

-Neil


netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e i_err_disable_cause -d 
itdc-2.switch.uiowa.edu -DI
[3239250] 2021-09-22 17:32:00  info App::Netdisco version 2.047008 loaded.
[3239250] 2021-09-22 17:32:01  info show: [172.24.128.13]/i_err_disable_cause 
started at Wed Sep 22 17:32:01 2021
[3239250] 2021-09-22 17:32:01 debug show: running with timeout 600s
[3239250] 2021-09-22 17:32:01 debug => running workers for phase: check
[3239250] 2021-09-22 17:32:01 debug -> run worker check/_base_/0
[3239250] 2021-09-22 17:32:01 debug Show is able to run
[3239250] 2021-09-22 17:32:01 debug => running workers for phase: main
[3239250] 2021-09-22 17:32:01 debug -> run worker main/_base_/100
[3239250] 2021-09-22 17:32:01 debug snmp reader cache warm: [172.24.128.13]
[3239250] 2021-09-22 17:32:01 debug [172.24.128.13:161] try_connect with ver: 
2, class: SNMP::Info::Layer3::Cisco, comm: 
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance : 
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0
SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
SNMP::Info 3.73
SNMP::Info::device_type() layers:0110 id:9 sysDescr:"Cisco IOS Software 
[Amsterdam], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.3.3, RELEASE 
SOFTWARE (fc7) Technical Support: http://www.cisco.com/techsupport Copyright 
(c) 1986-2021 by Cisco Systems, Inc. Compiled Thu 04-Mar-21 12:32 by mcpre"
SNMP::Info::_validate_autoload_method(i_err_disable_cause) Unable to resolve 
method.
undef
[3239250] 2021-09-22 17:32:01  info show: finished at Wed Sep 22 17:32:01 2021
[3239250] 2021-09-22 17:32:01  info show: status done: Showed 
i_err_disable_cause response from 172.24.128.13
netdisco@netdisco:~$ ~netdisco/bin/netdisco-do show -e cErrDisableIfStatusCause 
-d itdc-2.switch.uiowa.edu -DI
[3239258] 2021-09-22 17:32:47  info App::Netdisco version 2.047008 loaded.
[3239258] 2021-09-22 17:32:47  info show: 
[172.24.128.13]/cErrDisableIfStatusCause started at Wed Sep 22 17:32:47 2021
[3239258] 2021-09-22 17:32:47 debug show: running with timeout 600s
[3239258] 2021-09-22 17:32:47 debug => running workers for phase: check
[3239258] 2021-09-22 17:32:47 debug -> run worker check/_base_/0
[3239258] 2021-09-22 17:32:47 debug Show is able to run
[3239258] 2021-09-22 17:32:47 debug => running workers for phase: main
[3239258] 2021-09-22 17:32:47 debug -> run worker main/_base_/100
[3239258] 2021-09-22 17:32:47 debug snmp reader cache warm: [172.24.128.13]
[3239258] 2021-09-22 17:32:47 debug [172.24.128.13:161] try_connect with ver: 
2, class: SNMP::Info::Layer3::Cisco, comm: 
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance : 
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 : .1.3.6.1.2.1.1.1.0
SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
SNMP::Info 3.73
SNMP::Info::device_type() layers:0110 id:9 sysDescr:"Cisco IOS Software 
[Amsterdam], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 17.3.3, RELEASE 
SOFTWARE (fc7) Technical Support: http://www.cisco.com/techsupport Copyright 
(c) 1986-2021 by Cisco Systems, Inc. Compiled Thu 04-Mar-21 12:32 by mcpre"
SNMP::Info::_validate_autoload_method(cErrDisableIfStatusCause) Unable to 
resolve method.
undef
[3239258] 2021-09-22 17:32:47  info show: finished at Wed Sep 22 17:32:47 2021
[3239258] 2021-09-22 17:32:47  info show: status done: Showed 
cErrDisableIfStatusCause response from 172.24.128.13
netdisco@netdisco:~$

--
Neil Johnson – University of Iowa

From: Oliver Gorwits 
Sent: Wednesday, September 22, 2021 6:21 AM
To: Johnson, Neil M 
Cc: netdisco-users@lists.sourceforge.net
Subject: [External] Re: [Netdisco] Cisco port err-disabled detection

Hi Neil

This report relies on the i_err_disable_cause() method in SNMP::Info, so are 
you getting anything from:

~netdisco/bin/netdisco-do show -e i_err_disable_cause -d 1.2.3.4 -DI
~netdisco/bin/netdisco-do show -e cErrDisableIfStatusCause -d 1.2.3.4 -DI

I am not sure how widely this method is implemented, for what classes, etc.

regards

netdisco-users Digest, Vol 183, Issue 1

[netdisco-users-request]

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. Unable to see serial number for Linux devices (Shravan Hulyalkar)
--- Begin Message ---
Hello All,

I was able to add the Linux devices after installing SNMP and adding the
correct SNMP settings to the snmpd.conf file.

I have tried adding the different MIBs which i found online on stack
overflow.

This is the snmpd.conf file.























*# Please see /usr/share/doc/packages/net-snmp/EXAMPLE.conf for a# more
complete example and snmpd.conf(5).## Writing is disabled by default for
security reasons.  If you'd like# to enable it uncomment the rwcommunity
line and change the community# name to something nominally secure (keeping
in mind that this is# transmitted in clear text).# don't use ' < > in
strings for syslocation or syscontact# Note that if you define the
following here you won't be able to change# them with snmpsetsyslocation
Server Roomsyscontact Sysadmin (root@localhost)# These really aren't meant
for production use.  They include all MIBS# and can use considerable
resources.  See snmpd.conf(5) for information# on setting up groups and
limiting MIBS.rocommunity arista 10.125.0.72view systemview included
.1.3.6.1.2.1.1view systemview included .1.3.6.1.2.1.25.1.1view systemview
included .1.3.6.1.4.1# rwcommunity mysecret 127.0.0.1*

As you can see here in netdisco its not able to grab the serial number.


System Name cptdevc01n38
Location Server Room
Contact Sysadmin (root@localhost)
Vendor / Model Net-SNMP

 / linux

OS / Version Linux

 / 4.12.14-95.29-default / Net-SNMP 5.7.3

Serial Number
Chassis ID
Description Linux cptdevc01n38 4.12.14-95.29-default #1 SMP Thu Aug 1
15:34:33 UTC 2019 (47e48a4) x86_64
Administration  SSH  Telnet  Web 
SNMP Class SNMP::Info::Layer3::NetSNMP

Uptime 7 months 19 days 04:10:34
Layers
Last Discover 2021-10-05 07:05
Last Arpnip
Last Macsuck
Hardware Status Fan:
PS1 []:
PS2 []:
MAC Address
VTP Domain
In the module inventory its seen like this

[image: Screen Shot 2021-10-05 at 4.06.58 PM.png]



Can someone please help if there are any pointers I need to follow.

Thanks in advance
-- 

Regards,
Shravan Hulyalkar
(669)247-9901
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 182, Issue 19

[netdisco-users-request]

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: H3C switch discover - failed to return valid serial
  (Oliver Gorwits)
   2. Cisco 1100 series routers (Eg.C1113) dont report connected
  nodes (Muris)
--- Begin Message ---
Hi Muris

A couple of things I can think of. First, for Cisco there is a setting to
control whether the stack is discovered as individual items or one:
https://github.com/netdisco/netdisco/wiki/Vendor-Tips#report-cisco-as-single-device-instead-of-stacked-37xx29xxetc

I wonder if there is the same for H3C. Second, this setting is the one
which is aborting your discovery:
https://github.com/netdisco/netdisco/wiki/Configuration#snmp_field_protection

You can change it to force the job to continue, although lack of Serial is
a bit weird and I would want to dig further.
(for example change to '!group:__ANY__' to suppress the function)

Hope that helps,
Oliver.

On Mon, 27 Sept 2021 at 06:50, Muris  wrote:

> Hi, got another interesting one with H3C/HP switch 5130 stacked with 8
> switches
>
>
>
> Getting discovery error, failed to return valid serial, maybe its confused
> as it’s a stack of 8 switches?
>
>
>
> info discover: [10.x.x.x] started at Mon Sep 27 15:13:25 2021
>
> debug discover: running with timeout 600s
>
> debug => running workers for phase: check
>
> debug -> run worker check/_base_/0
>
> Discover is able to run.
>
> debug => running workers for phase: early
>
> -> run worker early/properties/100
>
> [debug snmp reader cache warm: [10.x.x.x]
>
> debug [10.x.x.x:161] try_connect with ver: 2, class:
> SNMP::Info::Layer3::H3C, comm: 
>
> [debug discover cancelled: 10.x.x.x failed to return valid serial
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
I have an issue where Cisco 1100 series routers are not reporting connected 
mac's/ip addresses on ports, Eg the C1113 version.

I noticed in the debug for macsuck, it says Vlan 1 and 10 are not in use by any 
port skipping, but they are actually in use and configured on the port.. so 
something doesnt seem right. 

Maybe someone else has the same issue? As a comparison ive compared the C1113 
and C897 routers (the previous models) where it works.

debug snmp reader cache warm: [10.x.x.x]
debug [10.x.x.x:161] try_connect with ver: 2, class: 
SNMP::Info::Layer3::CiscoSwitch, comm: 
debug [10.x.x.x] macsuck - VLANs: 1,10,1002,1003,1004,1005
debug [10.x.x.x] macsuck VLAN 1/default - not in use by any port - skipping.
debug [10.x.x.x] macsuck VLAN 10/Data_LAN - not in use by any port - skipping.
debug [10.x.x.x] macsuck VLAN 1002 - skipped by macsuck_no_vlan config
debug [10.x.x.x] macsuck VLAN 1003 - skipped by macsuck_no_vlan config
debug [10.x.x.x] macsuck VLAN 1004 - skipped by macsuck_no_vlan config
debug [10.x.x.x] macsuck VLAN 1005 - skipped by macsuck_no_vlan config
debug [10.x.x.x] reindexing to vlan 0 (ver: 2, class: 
SNMP::Info::Layer3::CiscoSwitch)
debug [10.x.x.x] macsuck - 0 updated forwarding table entries
debug [10.x.x.x] macsuck - removed 0 fwd table entries to archive
debug -> run worker main/wirelessnodes/100
debug => running workers for phase: late
debug -> run worker late/hooks/0
debug [10.x.x.x] hooks - 0 queued

As a comparison a Cisco 897 Router, the previous model works fine

debug macsuck: running with timeout 600s
debug => running workers for phase: check
debug -> run worker check/base/0
debug Macsuck is able to run.
debug => running workers for phase: main
debug -> run worker main/nodes/100
debug snmp reader cache warm: [10.x.x.x]
debug [10.x.x.x:161] try_connect with ver: 2, class: SNMP::Info::Layer3::Cisco, 
comm: 
debug [10.x.x.x:161] try_connect with ver: 2, new class: 
SNMP::Info::Layer3::CiscoSwitch, comm: 
debug [10.x.x.x] macsuck - VLANs: 1,100,1002,1003,1004,1005
debug [10.x.x.x] macsuck VLAN 1002 - skipped by macsuck_no_vlan config
debug [10.x.x.x] macsuck VLAN 1003 - skipped by macsuck_no_vlan config
debug [10.x.x.x] macsuck VLAN 1004 - skipped by macsuck_no_vlan config
debug [10.x.x.x] macsuck VLAN 1005 - skipped by macsuck_no_vlan config
debug [10.x.x.x] reindexing to vlan 1 (ver: 2, class: 
SNMP::Info::Layer3::CiscoSwitch)
debug [10.x.x.x] reindexing to vlan 100 (ver: 2, class: 
SNMP::Info::Layer3::CiscoSwitch)
debug [10.x.x.x] reindexing to vlan 0 (ver: 2, class: 
SNMP::Info::Layer3::CiscoSwitch)
debug 

netdisco-users Digest, Vol 182, Issue 18

[netdisco-users-request]

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. H3C switch discover - failed to return valid serial (Muris)
   2. Re: Netdisco search results missing randomly (Oliver Gorwits)
--- Begin Message ---
Hi, got another interesting one with H3C/HP switch 5130 stacked with 8 switches

 

Getting discovery error, failed to return valid serial, maybe its confused as 
it’s a stack of 8 switches?

 

info discover: [10.x.x.x] started at Mon Sep 27 15:13:25 2021

debug discover: running with timeout 600s

debug => running workers for phase: check

debug -> run worker check/_base_/0

Discover is able to run.

debug => running workers for phase: early

-> run worker early/properties/100

[debug snmp reader cache warm: [10.x.x.x]

debug [10.x.x.x:161] try_connect with ver: 2, class: SNMP::Info::Layer3::H3C, 
comm: 

[debug discover cancelled: 10.x.x.x failed to return valid serial

--- End Message ---
--- Begin Message ---
Hi

The difficulty here is a developer reproducing it.

Is anyone willing and able to share a snapshot of their database? This
would be a good start (and results either way after that would be
informative).

As with each time I’ve done this before, of course data is purged
afterwards.

Feel free to email me direct or message direct on IRC.

Thanks
Oliver.

On Mon, 27 Sep 2021 at 03:26, Muris  wrote:

> This issue is getting so annoying, the search function just becomes broken
> constantly
>
>
>
> Even on the latest version shows, when you go in inventory, click the
> devices in the amount of inventory and shows blank results
>
>
>
> Like im having to restart netdisco-web many times throughout the day
>
>
>
> *From: *Muris 
> *Date: *Monday, 13 September 2021 at 23:03
> *To: *Joseph Bernard 
> *Cc: *"netdisco-users@lists.sourceforge.net" <
> netdisco-users@lists.sourceforge.net>
> *Subject: *Re: [Netdisco] Netdisco search results missing randomly
>
>
>
> Thanks same i did it also. It should really be fixed its quite an annoying
> bug.
>
>
>
> As with the issue and arnip crashing, i truncated the subnets table in
> pgsql database which seems to have fixed it.
>
>
>
> Theres a few issues id like fixed at moment, but its having a resource who
> can look at it and patch it.
>
>
>
>
>
> On 13 Sep 2021, at 20:51, Joseph Bernard  wrote:
>
>  I’ve never figured out the cause, but I set up a cronjob to restart
> netdisco-web as a workaround. If I remember correctly, you can actually see
> the results in the source code of the page, but I guess it’s missing the
> code or something to make it display.
>
>
>
>
>
> Thanks,
>
> Joseph B.
>
>
>
> On Sep 13, 2021, at 12:08 AM, Muris  wrote:
>
> 
>
> By the way, to get it working, I have to restart netdisco-web
>
>
>
> I can’t really see errors in netdisco-web log though
>
>
>
> *From: *Muris 
> *Date: *Monday, 13 September 2021 at 13:32
> *To: *"netdisco-users@lists.sourceforge.net" <
> netdisco-users@lists.sourceforge.net>
> *Subject: *Netdisco search results missing randomly
>
>
>
> Hi,
>
>
>
> Ive noticed sometimes netdisco search results are missing, even if you
> want to enter the specific device it comes up empty
>
>
>
> I had a look at the backend and im seeing things like this, any ideas what
> is causing this?
>
>
>
> DBIx::Class::Storage::DBI::select_single(): Query returned more than one
> row.
>
> SQL that returns multiple rows is DEPRECATED for ->find and ->single at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Arpnip/Subnets.pm
> line 65
>
>
>
> DBIx::Class::Storage::DBI::select_single(): Query returned more than one
> row.
>
> SQL that returns multiple rows is DEPRECATED for ->find and ->single at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Node.pm line 182
>
>
>
> Use of uninitialized value $res{"234"} in string eq at
> /home/netdisco/perl5/lib/perl5/SNMP/Info/CiscoStpExtensions.   pm line 256.
>
>
>
>
>
> Thankyou
>
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
> ___
> Netdisco mailing list
> 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

netdisco-users Digest, Vol 186, Issue 1

[netdisco-users-request]

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. TP-Link tp1600g-52ps not being detected (Aaron W. Bayles)
--- Begin Message ---
Happy New Year all!

In my downtime I installed NetDisco via Docker to query a new (to-me)
switch and it's not being detected accurately. This is an older model of
the switch, v2 but was upgraded to the v3 firmware. It is being detected
using SNMP::Info::Layer 2. I've included a -DIQ debut below. I checked that
the tplink MIBs do have the same vendor ID (tplink.mib: tplink OBJECT
IDENTIFIER ::= { enterprises 11863 }) and specific switch model included
(tplink-products.mib: tplink-t1600g-52ps OBJECT IDENTIFIER ::= {
tplinkProducts 38 }). The switch is detected by NetDisco as "Vendor / Model
/ enterprises.11863.5.38". I did disable bulkwalk as my first attempt with
debugging did show numerous timeouts during discovery. Any help would be
greatly appreciated.

Thanks,
Aaron

~ $ bin/netdisco-do discover -d 10.0.0.4 -DIQ
[14012] 2022-01-03 15:06:47  info App::Netdisco version 2.052000 loaded.
SELECT me.version, me.installed
  FROM dbix_class_schema_versions me
WHERE 1 = 0
SELECT me.version
  FROM dbix_class_schema_versions me
ORDER BY installed DESC
  LIMIT '1'
SELECT me.ip, me.alias, me.subnet, me.port, me.dns, me.creation
  FROM device_ip me
WHERE me.alias = '10.0.0.4' AND me.ip = '10.0.0.4'
SELECT me.ip, me.creation, me.dns, me.description, me.uptime, me.contact,
me.name, me.location, me.layers, me.num_ports, me.mac, me.serial,
me.chassis_id, me.model, me.ps1_type, me.ps2_type, me.ps1_status,
me.ps2_status, me.fan, me.slots, me.vendor, me.os, me.os_ver, me.log,
me.snmp_ver, me.snmp_comm, me.snmp_class, me.snmp_engineid, me.vtp_domain,
me.last_discover, me.last_macsuck, me.last_arpnip, me.is_pseudo, to_char(
me.creation, '-MM-DD HH24:MI' ), to_char( me.last_arpnip, '-MM-DD
HH24:MI' ), to_char( me.last_discover, '-MM-DD HH24:MI' ), to_char(
me.last_macsuck, '-MM-DD HH24:MI' ), extract( epoch
  FROM age( now(  ), me.creation ) ), extract( epoch
  FROM age( now(  ), me.last_arpnip ) ), extract( epoch
  FROM age( now(  ), me.last_discover ) ), extract( epoch
  FROM age( now(  ), me.last_macsuck ) ), replace( age( timestamp
'epoch' + me.uptime / 100 * interval '1 second', timestamp '1970-01-01
00:00:00-00' ) ::text, 'mon', 'month' )
  FROM device me
WHERE me.ip = '10.0.0.4'
[14012] 2022-01-03 15:06:48  info discover: [10.0.0.4] started at Mon Jan
 3 15:06:48 2022
[14012] 2022-01-03 15:06:49 debug discover: running with timeout 600s
[14012] 2022-01-03 15:06:49 debug => running workers for phase: check
[14012] 2022-01-03 15:06:49 debug -> run worker check/_base_/0
[14012] 2022-01-03 15:06:49 debug Discover is able to run.
[14012] 2022-01-03 15:06:49 debug => running workers for phase: early
[14012] 2022-01-03 15:06:49 debug -> run worker early/properties/100
[14012] 2022-01-03 15:06:49 debug snmp reader cache warm: [10.0.0.4]
SELECT me.ip, me.snmp_comm_rw, me.snmp_auth_tag_read,
me.snmp_auth_tag_write
  FROM community me
WHERE me.ip = '10.0.0.4'
UPDATE community
  SET snmp_auth_tag_read = NULL
WHERE ip = '10.0.0.4'
[14012] 2022-01-03 15:06:49 debug [10.0.0.4:161] try_connect with ver: 2,
class: SNMP::Info::Layer2, comm: 
SNMP::Info::_global uptime : DISMAN-EVENT-MIB::sysUpTimeInstance :
.1.3.6.1.2.1.1.3.0
SNMP::Info::_global layers : SNMPv2-MIB::sysServices.0 : .1.3.6.1.2.1.1.7.0
SELECT me.ip, me.snmp_comm_rw, me.snmp_auth_tag_read,
me.snmp_auth_tag_write
  FROM community me
WHERE me.ip = '10.0.0.4'
UPDATE community
  SET snmp_auth_tag_read = 'default_v2_readonly'
WHERE ip = '10.0.0.4'
SNMP::Info::_global description : SNMPv2-MIB::sysDescr.0 :
.1.3.6.1.2.1.1.1.0
SNMP::Info::_global id : SNMPv2-MIB::sysObjectID.0 : .1.3.6.1.2.1.1.2.0
SNMP::Info 3.81
SNMP::Info::device_type() layers:0011 id:11863 sysDescr:"JetStream
48-Port Gigabit Smart PoE Switch with 4 SFP Slots"
SNMP::Info::_validate_autoload_method(vtp_d_name) Unable to resolve method.
SNMP::Info::_global name : SNMPv2-MIB::sysName.0 : .1.3.6.1.2.1.1.5.0
SNMP::Info::_validate_autoload_method(mac) Unable to resolve method.
SNMP::Info::_validate_autoload_method(ps1_type) Unable to resolve method.
SNMP::Info::_validate_autoload_method(ps2_type) Unable to resolve method.
SNMP::Info::_validate_autoload_method(ps1_status) Unable to resolve method.
SNMP::Info::_validate_autoload_method(ps2_status) Unable to resolve method.
SNMP::Info::_validate_autoload_method(fan) Unable to resolve method.

netdisco-users Digest, Vol 185, Issue 2

[netdisco-users-request]

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. ERR_EMPTY_RESPONSE (Basti S.)
   2. Re: ERR_EMPTY_RESPONSE (Christian Ramseyer)
   3. Re: ERR_EMPTY_RESPONSE (Basti S.)
   4. Re: ERR_EMPTY_RESPONSE (Basti S.)
--- Begin Message ---
Hello,

We installed 3 Netdisco instances on 3 separated locations. All was running
well, since last week I got "ERR_EMPTY_RESPONSE" on 2 of them when I enter
the web address.

Today I played a little bit with tcpdump to see if packets are coming in at
the netdisco machine and yes, this is the case on all machines.
Accidentally it started working again on one of the 2 instances where it
was no more working. I don't know why.

On the third I still get ERR_EMPTY_RESPONSE and it doesn't matter which
browser I use.
I also restarted all machines etc.

Do you have any idea?

Thanks in advance!
--- End Message ---
--- Begin Message ---

Hi

I've never seen that error, but I'd try first to see if this also 
happens locally on the server or maybe in transit somewhere 
(WAF/Proxy/shitty DLP, Antimalware etc.).


The first bit of a reply directly on your Netdisco server should look 
like this:


 $ curl -v http://localhost:5000 2>&1 | head -30

 0*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 5000 (#0)
> GET / HTTP/1.1
> Host: localhost:5000
> User-Agent: curl/7.60.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: Perl Dancer 1.3512
< Content-Length: 7586
< Content-Type: text/html; charset=utf-8
< Set-Cookie: 
dancer.session=MSOep-bOuPrs0P9plHrG6iJM4V1h0Ffhm2KwlIiaU6U~~gOwfkIDvT9G3dy8cuFdqZhL8tPKu0IA9xbv09vjgSQwrTezShOMRO2YikJinUTtoJs6HTgbfyX5HWtUPWqSNhw~ouDtAkqq7DrRkuFeG7sL55e_p4mKEXqd1yi-GrRyax8~2; 
path=/; HttpOnly

< X-Powered-By: Perl Dancer 1.3512
< Content-Security-Policy: frame-ancestors none;
< X-Frame-Options: DENY
< Date: Tue, 21 Dec 2021 13:50:28 GMT
< Connection: close
<
{ [7586 bytes data]
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;>
http://www.w3.org/1999/xhtml;>

  
  type="image/x-icon">

  

Given the error, check if Content-Length: is not 0 and there is actually 
html code appearing after the [7586 bytes data].


If you already get the error with curl, 
https://github.com/netdisco/netdisco/wiki/Developing shows how to start 
the webserver in the foreground with some debugging enabled, maybe you 
can see there what's going wrong.


Cheers
Christian



On 21.12.21 14:26, Basti S. wrote:

Hello,

We installed 3 Netdisco instances on 3 separated locations. All was 
running well, since last week I got "ERR_EMPTY_RESPONSE" on 2 of them 
when I enter the web address.


Today I played a little bit with tcpdump to see if packets are coming in 
at the netdisco machine and yes, this is the case on all machines.
Accidentally it started working again on one of the 2 instances where it 
was no more working. I don't know why.


On the third I still get ERR_EMPTY_RESPONSE and it doesn't matter which 
browser I use.

I also restarted all machines etc.

Do you have any idea?

Thanks in advance!



--- End Message ---
--- Begin Message ---
When I stop the netdisco web service and restart it and directly enter the
website, I can see in Fiddler that a few requests are successful, but the
most are not and the server returned 0 bytes.
I got the login screen without any css formatting etc because all the
needed files could not be downloaded.
Malware web scanner and firewall is disabled for testing on my client.

Am Di., 21. Dez. 2021 um 15:14 Uhr schrieb Basti S. :

> Hi Christian,
>
> Yes, that worked without any problems. My output looks very similar to
> yours.
>
> Anything else I can check? Why my other problematic instance started
> working again is still a mystery to me.
>
> Regards,
> Bastian
>
> Am Di., 21. Dez. 2021 um 14:57 Uhr schrieb Christian Ramseyer <
> ramse...@netnea.com>:
>
>> Hi
>>
>> I've never seen that error, but I'd try first to see if this also
>> happens locally on the server or maybe in transit somewhere
>> (WAF/Proxy/shitty DLP, Antimalware etc.).
>>
>> The first bit of a reply directly on your Netdisco server should look
>> like this:
>>
>>   $ curl -v http://localhost:5000 2>&1 | head -30
>>
>>   0*   Trying 127.0.0.1...
>> * TCP_NODELAY set
>> * Connected to localhost (127.0.0.1) port 5000 (#0)
>>  > GET / HTTP/1.1
>>  > Host: localhost:5000
>>  > User-Agent: curl/7.60.0
>>  > Accept: */*
>>  >
>> < HTTP/1.1 200 OK
>> < Server: Perl Dancer 1.3512
>> < Content-Length: 7586
>> < Content-Type: text/html; 

netdisco-users Digest, Vol 184, Issue 17

[netdisco-users-request]

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: SSH Collector Testing? (Jim Araujo)
--- Begin Message ---
Awesome! I've applied the code snippet modification and it now lists 
ONLY the mgmt IP. Is there  way to have it list the IPs listed from the 
database command, since those IPs the BigIP-F5 owns as well?


https://pastecode.io/s/xpthr4qb


On 11/15/2021 6:42 PM, Christian Ramseyer wrote:
From your device_ip dump it looks like the issue is the empty "port" 
column, this is what allows to map the IPs back to the physical 
interface it is configured on.


I found a Big IP in a rarely visited corner of our network (BIG-IP 
vCMP Guest : Linux 2.6x, BIG-IP software release 12.1.4.1).


There, it looks like the F5-BIGIP-SYSTEM-MIB::sysInterfaceName : 
.1.3.6.1.4.1.3375.2.1.2.4.1.2.1.1 is the problem. This data needs to 
be matched with  IP-MIB::ipAdEntIfIndex : .1.3.6.1.2.1.4.20.1.2, but 
the former does not use the ifEntry ifindex, but a decimal ascii 
sequence of the interface names. This can be visualized with 
netdisco-do show:



$ netdisco-do show -I -d 10.0.29.24 -e ip_index
SNMP::Info::_load_attr old_ip_index : IP-MIB::ipAdEntIfIndex : 
.1.3.6.1.2.1.4.20.1.2

{
    10.0.29.24   33,
    10.0.29.25   33,
    169.254.73.9   112
}

$ netdisco-do show -I -d 10.0.29.24 -e interfaces
SNMP::Info::_load_attr i_index : F5-BIGIP-SYSTEM-MIB::sysInterfaceName 
: .1.3.6.1.4.1.3375.2.1.2.4.1.2.1.1

{
    6.49.47.48.46.49.57   "1/0.19" (dualvar: 1),
    6.49.47.48.46.50.48   "1/0.20" (dualvar: 1),
    6.49.47.109.103.109.116   "1/mgmt" (dualvar: 1),
    6.50.47.48.46.49.57   "2/0.19" (dualvar: 2),
    6.50.47.48.46.50.48   "2/0.20" (dualvar: 2),
    6.50.47.109.103.109.116   "2/mgmt" (dualvar: 2)
}


I tried a quick hack in lib/SNMP/Info/Layer3/F5.pm that looks up the 
actual ifIndex and adds this as an additional row to the result:


$ netdisco-do show -I -d 10.0.29.24 -e interfaces
SNMP::Info::_load_attr i_index : F5-BIGIP-SYSTEM-MIB::sysInterfaceName 
: .1.3.6.1.4.1.3375.2.1.2.4.1.2.1.1

{
    33    "1/mgmt" (dualvar: 1),
    34    "2/mgmt" (dualvar: 2),
    177   "1/0.19" (dualvar: 1),
    178   "2/0.19" (dualvar: 2),
    193   "1/0.20" (dualvar: 1),
    194   "2/0.20" (dualvar: 2),
    6.49.47.48.46.49.57   "1/0.19" (dualvar: 1),
    6.49.47.48.46.50.48   "1/0.20" (dualvar: 1),
    6.49.47.109.103.109.116   "1/mgmt" (dualvar: 1),
    6.50.47.48.46.49.57   "2/0.19" (dualvar: 2),
    6.50.47.48.46.50.48   "2/0.20" (dualvar: 2),
    6.50.47.109.103.109.116   "2/mgmt" (dualvar: 2)
}

Unfortunately this Netdisco installation is behind five tunnels and 
VPNs and I can not start the GUI, but I'm pretty confident it would 
now show up in the Adresses tab. You can give it a try, the interfaces 
method in F5.pm would need to look like this:


# Override L3 interfaces
sub interfaces {
    my $f5  = shift;
    my $partial = shift;

    # F5-BIGIP-SYSTEM-MIB::sysInterfaceName uses an ascii
    # string of the interface name as table index,
    # add an additional record with the regular ifIndex
    my $ifnames =  $f5->ifName($partial);
    my %i2ind = reverse %$ifnames;

    my $if = $f5->i_index($partial);
    foreach my $k(keys %$if){
  my $ifindex = $i2ind{$if->{$k}};
  $if->{$ifindex} = $if->{$k};
    }

    return $if;
}

Then run netdisco-do discover again. If it works maybe a resident 
SNMP::Info crack can give us some advice how to make a proper patch 
for this, it would need fixing in some more methods and be implemented 
module-wide somewhere (is there anything Munge-like for indexes?) Also 
I'm not sure if this breaks anything else and if we should keep the 
ascii string indexes around.


I imagine the Palo Alto is something similar but I have no way to try 
currently. Might be a case for the hot new snapshot feature 
(https://github.com/netdisco/netdisco/wiki/Snapshot)


Cheers
Christian


On 15.11.21 14:55, Jim Araujo wrote:

Sure thing Christian.

Both the below Device Types(BigIP * PaloAlto) seem to have similar 
issues with Addresses reporting in the DB, but not the WebGUI.


This pate-code is the -DISQ(first link) and DB commands(second link) 
from a BigIP F5 i2800


https://pastecode.io/s/avkzee1x

https://pastecode.io/s/y3ekxc8r


This Paste-code is the -DISQ(first link) and DB commands(second link) 
from a PaloAlto PA-5220

netdisco-users Digest, Vol 184, Issue 18

[netdisco-users-request]

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: SSH Collector Testing? (Jim Araujo)
--- Begin Message ---
I wanted to also comment on the SNMP vs SSH collector of BigIP F5 
information. We currently also are testing out LibreNMS another 
opensource community project which uses only SNMP. When discovering a 
BigIP F5 with LibreNMS it detects all the IP information include all the 
VirtualIPs. I am not sure how they do it, maybe another MIB or 
something. Just FYI.



On 11/16/2021 8:32 AM, Jim Araujo wrote:
Awesome! I've applied the code snippet modification and it now lists 
ONLY the mgmt IP. Is there  way to have it list the IPs listed from 
the database command, since those IPs the BigIP-F5 owns as well?


https://pastecode.io/s/xpthr4qb


On 11/15/2021 6:42 PM, Christian Ramseyer wrote:
From your device_ip dump it looks like the issue is the empty "port" 
column, this is what allows to map the IPs back to the physical 
interface it is configured on.


I found a Big IP in a rarely visited corner of our network (BIG-IP 
vCMP Guest : Linux 2.6x, BIG-IP software release 12.1.4.1).


There, it looks like the F5-BIGIP-SYSTEM-MIB::sysInterfaceName : 
.1.3.6.1.4.1.3375.2.1.2.4.1.2.1.1 is the problem. This data needs to 
be matched with  IP-MIB::ipAdEntIfIndex : .1.3.6.1.2.1.4.20.1.2, but 
the former does not use the ifEntry ifindex, but a decimal ascii 
sequence of the interface names. This can be visualized with 
netdisco-do show:



$ netdisco-do show -I -d 10.0.29.24 -e ip_index
SNMP::Info::_load_attr old_ip_index : IP-MIB::ipAdEntIfIndex : 
.1.3.6.1.2.1.4.20.1.2

{
    10.0.29.24   33,
    10.0.29.25   33,
    169.254.73.9   112
}

$ netdisco-do show -I -d 10.0.29.24 -e interfaces
SNMP::Info::_load_attr i_index : 
F5-BIGIP-SYSTEM-MIB::sysInterfaceName : 
.1.3.6.1.4.1.3375.2.1.2.4.1.2.1.1

{
    6.49.47.48.46.49.57   "1/0.19" (dualvar: 1),
    6.49.47.48.46.50.48   "1/0.20" (dualvar: 1),
    6.49.47.109.103.109.116   "1/mgmt" (dualvar: 1),
    6.50.47.48.46.49.57   "2/0.19" (dualvar: 2),
    6.50.47.48.46.50.48   "2/0.20" (dualvar: 2),
    6.50.47.109.103.109.116   "2/mgmt" (dualvar: 2)
}


I tried a quick hack in lib/SNMP/Info/Layer3/F5.pm that looks up the 
actual ifIndex and adds this as an additional row to the result:


$ netdisco-do show -I -d 10.0.29.24 -e interfaces
SNMP::Info::_load_attr i_index : 
F5-BIGIP-SYSTEM-MIB::sysInterfaceName : 
.1.3.6.1.4.1.3375.2.1.2.4.1.2.1.1

{
    33    "1/mgmt" (dualvar: 1),
    34    "2/mgmt" (dualvar: 2),
    177   "1/0.19" (dualvar: 1),
    178   "2/0.19" (dualvar: 2),
    193   "1/0.20" (dualvar: 1),
    194   "2/0.20" (dualvar: 2),
    6.49.47.48.46.49.57   "1/0.19" (dualvar: 1),
    6.49.47.48.46.50.48   "1/0.20" (dualvar: 1),
    6.49.47.109.103.109.116   "1/mgmt" (dualvar: 1),
    6.50.47.48.46.49.57   "2/0.19" (dualvar: 2),
    6.50.47.48.46.50.48   "2/0.20" (dualvar: 2),
    6.50.47.109.103.109.116   "2/mgmt" (dualvar: 2)
}

Unfortunately this Netdisco installation is behind five tunnels and 
VPNs and I can not start the GUI, but I'm pretty confident it would 
now show up in the Adresses tab. You can give it a try, the 
interfaces method in F5.pm would need to look like this:


# Override L3 interfaces
sub interfaces {
    my $f5  = shift;
    my $partial = shift;

    # F5-BIGIP-SYSTEM-MIB::sysInterfaceName uses an ascii
    # string of the interface name as table index,
    # add an additional record with the regular ifIndex
    my $ifnames =  $f5->ifName($partial);
    my %i2ind = reverse %$ifnames;

    my $if = $f5->i_index($partial);
    foreach my $k(keys %$if){
  my $ifindex = $i2ind{$if->{$k}};
  $if->{$ifindex} = $if->{$k};
    }

    return $if;
}

Then run netdisco-do discover again. If it works maybe a resident 
SNMP::Info crack can give us some advice how to make a proper patch 
for this, it would need fixing in some more methods and be 
implemented module-wide somewhere (is there anything Munge-like for 
indexes?) Also I'm not sure if this breaks anything else and if we 
should keep the ascii string indexes around.


I imagine the Palo Alto is something similar but I have no way to try 
currently. Might be a case for the hot new snapshot feature 
(https://github.com/netdisco/netdisco/wiki/Snapshot)


Cheers
Christian


On 15.11.21 14:55, Jim Araujo wrote:

Sure 

netdisco-users Digest, Vol 184, Issue 19

[netdisco-users-request]

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: SSH Collector Testing? (Michael Butash)
--- Begin Message ---
I would assume librenms does, as they're enumerating vips, pools, gtm
features, etc, so someone modeled it specifically around F5 mibs there.

Fortigate's are a bit annoying like that too - working for an msp for a
bit, I had a customer I put in big modular chassis firewall, a FGT7060, and
base system and ipmib stats were pretty weak when troubleshooting some of
their code issues.  If I hit the fortigate mibs, I could enumerate each
core/thread and a lot more system/interface statistics than the base mibs
did, and had the guy doing all their nagios integration there build me
custom Fortigate models around those devices.

Luckily I had some clout that I could assign work to a capable dev see it
done, and it was pretty sweet, but definitely requires some dirty hands and
custom investment of developer time with someone that knows the management
software to do so.

I think you said this was a "test" instance that now became "critical" to
the business, so tell them it's time to invest some in it.  I know how that
goes though, they still won't more than likely, it's just that silly
network stuff no one cares about and isn't *that* important...  :D

-mb


On Thu, Nov 18, 2021 at 10:23 AM Jim Araujo  wrote:

> I wanted to also comment on the SNMP vs SSH collector of BigIP F5
> information. We currently also are testing out LibreNMS another opensource
> community project which uses only SNMP. When discovering a BigIP F5 with
> LibreNMS it detects all the IP information include all the VirtualIPs. I am
> not sure how they do it, maybe another MIB or something. Just FYI.
>
>
> On 11/16/2021 8:32 AM, Jim Araujo wrote:
>
> Awesome! I've applied the code snippet modification and it now lists ONLY
> the mgmt IP. Is there  way to have it list the IPs listed from the database
> command, since those IPs the BigIP-F5 owns as well?
>
> https://pastecode.io/s/xpthr4qb
>
>
> On 11/15/2021 6:42 PM, Christian Ramseyer wrote:
>
> From your device_ip dump it looks like the issue is the empty "port"
> column, this is what allows to map the IPs back to the physical interface
> it is configured on.
>
> I found a Big IP in a rarely visited corner of our network (BIG-IP vCMP
> Guest : Linux 2.6x, BIG-IP software release 12.1.4.1).
>
> There, it looks like the F5-BIGIP-SYSTEM-MIB::sysInterfaceName :
> .1.3.6.1.4.1.3375.2.1.2.4.1.2.1.1 is the problem. This data needs to be
> matched with  IP-MIB::ipAdEntIfIndex : .1.3.6.1.2.1.4.20.1.2, but the
> former does not use the ifEntry ifindex, but a decimal ascii sequence of
> the interface names. This can be visualized with netdisco-do show:
>
>
> $ netdisco-do show -I -d 10.0.29.24 -e ip_index
> SNMP::Info::_load_attr old_ip_index : IP-MIB::ipAdEntIfIndex :
> .1.3.6.1.2.1.4.20.1.2
> {
> 10.0.29.24   33,
> 10.0.29.25   33,
> 169.254.73.9   112
> }
>
> $ netdisco-do show -I -d 10.0.29.24 -e interfaces
> SNMP::Info::_load_attr i_index : F5-BIGIP-SYSTEM-MIB::sysInterfaceName :
> .1.3.6.1.4.1.3375.2.1.2.4.1.2.1.1
> {
> 6.49.47.48.46.49.57   "1/0.19" (dualvar: 1),
> 6.49.47.48.46.50.48   "1/0.20" (dualvar: 1),
> 6.49.47.109.103.109.116   "1/mgmt" (dualvar: 1),
> 6.50.47.48.46.49.57   "2/0.19" (dualvar: 2),
> 6.50.47.48.46.50.48   "2/0.20" (dualvar: 2),
> 6.50.47.109.103.109.116   "2/mgmt" (dualvar: 2)
> }
>
>
> I tried a quick hack in lib/SNMP/Info/Layer3/F5.pm that looks up the
> actual ifIndex and adds this as an additional row to the result:
>
> $ netdisco-do show -I -d 10.0.29.24 -e interfaces
> SNMP::Info::_load_attr i_index : F5-BIGIP-SYSTEM-MIB::sysInterfaceName :
> .1.3.6.1.4.1.3375.2.1.2.4.1.2.1.1
> {
> 33"1/mgmt" (dualvar: 1),
> 34"2/mgmt" (dualvar: 2),
> 177   "1/0.19" (dualvar: 1),
> 178   "2/0.19" (dualvar: 2),
> 193   "1/0.20" (dualvar: 1),
> 194   "2/0.20" (dualvar: 2),
> 6.49.47.48.46.49.57   "1/0.19" (dualvar: 1),
> 6.49.47.48.46.50.48   "1/0.20" (dualvar: 1),
> 6.49.47.109.103.109.116   "1/mgmt" (dualvar: 1),
> 6.50.47.48.46.49.57   "2/0.19" (dualvar: 2),
> 6.50.47.48.46.50.48   "2/0.20" (dualvar: 2),
> 6.50.47.109.103.109.116   "2/mgmt" (dualvar: 2)
> }
>
> Unfortunately this Netdisco installation is behind five 

netdisco-users Digest, Vol 184, Issue 9

[netdisco-users-request]

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: SSH Collector Testing? (Christian Ramseyer)
   2. Re: SSH Collector Testing? (Jim Araujo)
   3. Re: SSH Collector Testing? (Christian Ramseyer)
--- Begin Message ---

Hi Jim

The SSH collector only collects ARP tables. There are two more pieces 
that are needed for everything to show up properly in the web interface:


- discovery of the L2 device: netdisco-do -D discover -d 
  this will give the list of interfaces and other hardware
- collection of the mac address tables: netdisco-do -D macsuck -d 
  this will give the interface -> connected MAC addresses

If you see ARP entries collected that later can not be found in the UI, 
most likely one of these is not working properly with your gear.


I usually look into the database using SQL after running 
discover/macsuck/arpnip: netdisco-do psql , then:


select * from device where ip = ;
-- if there's nothing here, discovery or credentials is the problem
-- all your routers and switches involved should show up here

select * from device_port where  ip = ;
-- if there's nothing here, discovery found no ports:
-- shitty SNMP support or switch is not added to netdisco

select * from node where switch = ;
-- here you should see some connected macs on ports, otherwise
-- macsuck issue

select * from node_ip where mac = ;
-- you should find your arp tables here, otherwise arpnip issue or
-- you're not pointing netdisco at the correct L3 devices

Maybe that helps narrowing the issue down a bit.

Cheers
Christian




On 10.11.21 17:58, Jim Araujo wrote:
I believe SSHCollector is getting the ARP entries as when i do a 
'~/bin/netdisco-do arpnip -d 1.2.3.4 -D' shows 'processed 43 ARP cache 
entries.  However nothing is listed in the web gui for this node...Am I 
running into a bug?


https://sourceforge.net/p/netdisco/netdisco2/254/

On 11/10/2021 8:43 AM, Jim Araujo wrote:
Hello netdisco team! First off great work on this app, it is 
incredible. SNMPv3 seems to work correctly, however when I create a 
new stanza for SSH collection for devices like BigIP, PaloAlto, and 
NXOS is there a way to test if they are working? On the web gui these 
particular devices do not show any information under Addresses, nor 
anything under Ports...I am hoping to get this working as we have a 
large F5 environment and would be helpful to be able to search for IPs 
that the F5 or PaloAlto owns.


Thanks again!




--- End Message ---
--- Begin Message ---
Hi Christian, thanks for the troubleshooting steps. I see that the last 
query shows the database has the IPv4 addresses in it, but the Web Gui 
does not. The troubleshooting log is from a Palo alto PA-5220.


https://pastecode.io/s/0i2kdb37


On 11/11/2021 8:08 AM, Christian Ramseyer wrote:

Hi Jim

The SSH collector only collects ARP tables. There are two more pieces 
that are needed for everything to show up properly in the web interface:


- discovery of the L2 device: netdisco-do -D discover -d 
  this will give the list of interfaces and other hardware
- collection of the mac address tables: netdisco-do -D macsuck -d 
  this will give the interface -> connected MAC addresses

If you see ARP entries collected that later can not be found in the 
UI, most likely one of these is not working properly with your gear.


I usually look into the database using SQL after running 
discover/macsuck/arpnip: netdisco-do psql , then:


select * from device where ip = ;
-- if there's nothing here, discovery or credentials is the problem
-- all your routers and switches involved should show up here

select * from device_port where  ip = ;
-- if there's nothing here, discovery found no ports:
-- shitty SNMP support or switch is not added to netdisco

select * from node where switch = ;
-- here you should see some connected macs on ports, otherwise
-- macsuck issue

select * from node_ip where mac = ;
-- you should find your arp tables here, otherwise arpnip issue or
-- you're not pointing netdisco at the correct L3 devices

Maybe that helps narrowing the issue down a bit.

Cheers
Christian




On 10.11.21 17:58, Jim Araujo wrote:
I believe SSHCollector is getting the ARP entries as when i do a 
'~/bin/netdisco-do arpnip -d 1.2.3.4 -D' shows 'processed 43 ARP 
cache entries.  However nothing is listed in the web gui for this 
node...Am I running into a bug?


https://sourceforge.net/p/netdisco/netdisco2/254/

On 11/10/2021 8:43 AM, Jim Araujo wrote:
Hello netdisco team! First off 

netdisco-users Digest, Vol 184, Issue 7

[netdisco-users-request]

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: Deployment not working (Basti S.)
   2. SSH Collector Testing? (Jim Araujo)
   3. Re: SSH Collector Testing? (Oliver Gorwits)
--- Begin Message ---
Hello Christian,

I presumed that this would be a problem - ok, good to know!

I got it working in the meantime.
In the deployment.yml I activated the "host" parameter for the database and
put in 127.0.0.1 here.

What do you think about that?

KR
Bastian

Am Mi., 10. Nov. 2021 um 13:04 Uhr schrieb Christian Ramseyer <
ramse...@netnea.com>:

> Hi
>
> Peer authentication matches the OS username to the database username
> (netdisco), but it seems like your Linux user is called "sa-netdisco" so
> there is not match. You need to replace the peer authentication for the
> netdisco database on local connections to something else, e.g.
> scram-sha-256, md5 or trust. Post your pg_hba.conf if you can't get it to
> work.
>
> Cheers
> Christian
>
> On 10.11.21 08:50, Basti S. wrote:
>
> Hello community,
>
> I want to install a second Netdisco instance and stuck in the Deploy step
> with this error:
>
> Would you like to deploy the database schema? [y/N]: y
>
> DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently
> unversioned. Please call upgrade on your  schema to
> sync the DB. at /home/sa-netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121
>
> DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed:
> DBIx::Class::Storage::DBI::catch {...} ():  DBI
> Connection failed: DBI connect('dbname=netdisco','netdisco',...) failed:
> FATAL:  Peer authentication fa iled for user
> "netdisco" at /home/sa-netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm
> line 1639. at /home/
> sa-netdisco/perl5/bin/netdisco-db-deploy line 110 at
> /home/sa-netdisco/perl5/bin/netdisco-db-deploy line 110
>
> DB schema update complete.
>
> DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently
> unversioned. Please call upgrade on your  schema to
> sync the DB. at /home/sa-netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121
>
> DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI
> connect('dbname=netdisco','netdisco',. ..) failed:
> FATAL:  Peer authentication failed for user "netdisco" at
> /home/sa-netdisco/perl5/lib/perl5/DBIx
> /Class/Storage/DBI.pm line 1639. at
> /home/sa-netdisco/perl5/lib/perl5/App/Netdisco/Util/Statistics.pm line 3
>
>
>
> I tested the connection to the database with psql and the netdisco user
> and password, but it was only working when I also added "-h 127.0.0.1".
>
> Otherwise I get the same error: "failed: FATAL:  Peer authentication
> failed for user..."
>
>
> I have already checked the pg_hba.conf, seems to be correct.
>
>
> What else can I try?
>
>
> Thanks in advance!
>
>
> Regards,
>
> Bastian
>
>
> ___
> Netdisco mailing 
> listnetdisco-users@lists.sourceforge.nethttps://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
>
> --
> Christian Ramseyer, netnea ag
> Network Management. Security. OpenSource.
> Phone: +41 79 644 77 64
> Teams: ramse...@netnea.onmicrosoft.com
>
>
--- End Message ---
--- Begin Message ---
Hello netdisco team! First off great work on this app, it is incredible. 
SNMPv3 seems to work correctly, however when I create a new stanza for 
SSH collection for devices like BigIP, PaloAlto, and NXOS is there a way 
to test if they are working? On the web gui these particular devices do 
not show any information under Addresses, nor anything under Ports...I 
am hoping to get this working as we have a large F5 environment and 
would be helpful to be able to search for IPs that the F5 or PaloAlto owns.


Thanks again!

--
-Jim



--- End Message ---
--- Begin Message ---
Hi Jim

Good question. I think at the command line you can do something like this
to run the SSH ARP collection. It's not so much a test of the connection as
doing the full thing, but will show any failure immediately to you.

~netdisco/bin/netdisco-do arpnip::nodes -d 1.2.3.4 -D

regards,
oliver.

On Wed, 10 Nov 2021 at 13:43, Jim Araujo  wrote:

> Hello netdisco team! First off great work on this app, it is incredible.
> SNMPv3 seems to work correctly, however when I create a new stanza for
> SSH collection for devices like BigIP, PaloAlto, and NXOS is there a way
> to test if they are working? On the web gui 

netdisco-users Digest, Vol 184, Issue 6

[netdisco-users-request]

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. Deployment not working (Basti S.)
   2. Re: Deployment not working (Christian Ramseyer)
   3. Re: Deployment not working (Oliver Gorwits)
--- Begin Message ---
Hello community,

I want to install a second Netdisco instance and stuck in the Deploy step
with this error:

Would you like to deploy the database schema? [y/N]: y

DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently
unversioned. Please call upgrade on your  schema to
sync the DB. at /home/sa-netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121

DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed:
DBIx::Class::Storage::DBI::catch {...} ():  DBI
Connection failed: DBI connect('dbname=netdisco','netdisco',...) failed:
FATAL:  Peer authentication fa iled for user
"netdisco" at /home/sa-netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm
line 1639. at /home/
sa-netdisco/perl5/bin/netdisco-db-deploy line 110 at
/home/sa-netdisco/perl5/bin/netdisco-db-deploy line 110

DB schema update complete.

DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently
unversioned. Please call upgrade on your  schema to
sync the DB. at /home/sa-netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121

DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI
connect('dbname=netdisco','netdisco',. ..) failed:
FATAL:  Peer authentication failed for user "netdisco" at
/home/sa-netdisco/perl5/lib/perl5/DBIx
/Class/Storage/DBI.pm line 1639. at
/home/sa-netdisco/perl5/lib/perl5/App/Netdisco/Util/Statistics.pm line 3



I tested the connection to the database with psql and the netdisco user and
password, but it was only working when I also added "-h 127.0.0.1".

Otherwise I get the same error: "failed: FATAL:  Peer authentication failed
for user..."


I have already checked the pg_hba.conf, seems to be correct.


What else can I try?


Thanks in advance!


Regards,

Bastian
--- End Message ---
--- Begin Message ---

Hi

Peer authentication matches the OS username to the database username 
(netdisco), but it seems like your Linux user is called "sa-netdisco" so 
there is not match. You need to replace the peer authentication for the 
netdisco database on local connections to something else, e.g. 
scram-sha-256, md5 or trust. Post your pg_hba.conf if you can't get it 
to work.


Cheers
Christian

On 10.11.21 08:50, Basti S. wrote:

Hello community,

I want to install a second Netdisco instance and stuck in the Deploy 
step with this error:


Would you like to deploy the database schema? [y/N]: y

DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently 
unversioned. Please call upgrade on your  
schema to sync the DB. at 
/home/sa-netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121


DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: 
DBIx::Class::Storage::DBI::catch {...} ():  
DBI Connection failed: DBI connect('dbname=netdisco','netdisco',...) 
failed: FATAL:  Peer authentication fa iled for user "netdisco" at 
/home/sa-netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1639. 
at /home/ sa-netdisco/perl5/bin/netdisco-db-deploy line 110 at 
/home/sa-netdisco/perl5/bin/netdisco-db-deploy line 110


DB schema update complete.

DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently 
unversioned. Please call upgrade on your  
schema to sync the DB. at 
/home/sa-netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121


DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI 
connect('dbname=netdisco','netdisco',. ..) failed: FATAL:  Peer 
authentication failed for user "netdisco" at 
/home/sa-netdisco/perl5/lib/perl5/DBIx /Class/Storage/DBI.pm line 
1639. at 
/home/sa-netdisco/perl5/lib/perl5/App/Netdisco/Util/Statistics.pm line 3


I tested the connection to the database with psql and the netdisco 
user and password, but it was only working when I also added "-h 
127.0.0.1".


Otherwise I get the same error: "failed: FATAL:  Peer authentication 
failed for user..."



I have already checked the pg_hba.conf, seems to be correct.


What else can I try?


Thanks in advance!


Regards,

Bastian



___
Netdisco mailing list
netdisco-users@lists.sourceforge.net

netdisco-users Digest, Vol 184, Issue 10

[netdisco-users-request]

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: SSH Collector Testing? (Jim Araujo)
   2. Re: SSH Collector Testing? (Michael Butash)
--- Begin Message ---

Hi Christian,

Thanks again for looking into this. Perhaps I am confused. I thought for 
these particular devices SSHCollector performs the task of getting IP 
addresses?


I've setup the stanza for

https://metacpan.org/pod/App::Netdisco::SSHCollector::Platform::PaloAlto

and looking at the code on github, it looks like the SSHCollector 
performs a "set cli scripting-mode on" and then a "show arp all". I 
believe the collector is working as the database command you had me run 
shows the database has the  interface IP addresses. Just the Web GUI is 
blank. If I search for an IP owned by the Palo it shows up under the 
switch it is plugged into, but not for the PaloAlto itself.



On 11/11/2021 6:46 PM, Christian Ramseyer wrote:
Ok in the macsuck part it says that the device does not advertise 
layer 2 functionality in the SNMP attributes, and so no macsuck is 
performed.


I think if you just enter the IP or Mac in the search box on top of 
the UI, you should get an entry similar to the attached image. But 
since there is no L2 mapping from Mac to Port it will not show up in 
the ports of the device, it's just a disconnected ARP entry.


I have no Palo Altos to try, in some cases you can get lucky by just 
enabling layer 2 in the snmp settings, but more likely Palo Alto does 
not support these MIBs and will not give you any useful data. Maybe 
somebody else on the list has experience with this brand.


Cheers
Christian


On 11.11.21 17:29, Jim Araujo wrote:
Hi Christian, thanks for the troubleshooting steps. I see that the 
last query shows the database has the IPv4 addresses in it, but the 
Web Gui does not. The troubleshooting log is from a Palo alto PA-5220.


https://pastecode.io/s/0i2kdb37


On 11/11/2021 8:08 AM, Christian Ramseyer wrote:

Hi Jim

The SSH collector only collects ARP tables. There are two more 
pieces that are needed for everything to show up properly in the web 
interface:


- discovery of the L2 device: netdisco-do -D discover -d 
  this will give the list of interfaces and other hardware
- collection of the mac address tables: netdisco-do -D macsuck -d 
  this will give the interface -> connected MAC addresses

If you see ARP entries collected that later can not be found in the 
UI, most likely one of these is not working properly with your gear.


I usually look into the database using SQL after running 
discover/macsuck/arpnip: netdisco-do psql , then:


select * from device where ip = ;
-- if there's nothing here, discovery or credentials is the problem
-- all your routers and switches involved should show up here

select * from device_port where  ip = ;
-- if there's nothing here, discovery found no ports:
-- shitty SNMP support or switch is not added to netdisco

select * from node where switch = ;
-- here you should see some connected macs on ports, otherwise
-- macsuck issue

select * from node_ip where mac = step>;

-- you should find your arp tables here, otherwise arpnip issue or
-- you're not pointing netdisco at the correct L3 devices

Maybe that helps narrowing the issue down a bit.

Cheers
Christian




On 10.11.21 17:58, Jim Araujo wrote:
I believe SSHCollector is getting the ARP entries as when i do a 
'~/bin/netdisco-do arpnip -d 1.2.3.4 -D' shows 'processed 43 ARP 
cache entries.  However nothing is listed in the web gui for this 
node...Am I running into a bug?


https://sourceforge.net/p/netdisco/netdisco2/254/

On 11/10/2021 8:43 AM, Jim Araujo wrote:
Hello netdisco team! First off great work on this app, it is 
incredible. SNMPv3 seems to work correctly, however when I create 
a new stanza for SSH collection for devices like BigIP, PaloAlto, 
and NXOS is there a way to test if they are working? On the web 
gui these particular devices do not show any information under 
Addresses, nor anything under Ports...I am hoping to get this 
working as we have a large F5 environment and would be helpful to 
be able to search for IPs that the F5 or PaloAlto owns.


Thanks again!


--
-Jim



--- End Message ---
--- Begin Message ---
I would think with snmp in any version working you would get *most* data
back to build a device model, and arp would give you the rest for mac
associations as a router without a cam table would link device interfaces.
Even stupid cisco firewalls that still don't support 

netdisco-users Digest, Vol 184, Issue 15

[netdisco-users-request]

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: SSH Collector Testing? (Jim Araujo)
   2. Re: SSH Collector Testing? (Christian Ramseyer)
--- Begin Message ---

Sure thing Christian.

Both the below Device Types(BigIP * PaloAlto) seem to have similar 
issues with Addresses reporting in the DB, but not the WebGUI.


This pate-code is the -DISQ(first link) and DB commands(second link) 
from a BigIP F5 i2800


https://pastecode.io/s/avkzee1x

https://pastecode.io/s/y3ekxc8r


This Paste-code is the -DISQ(first link) and DB commands(second link) 
from a PaloAlto PA-5220


https://pastecode.io/s/vagnng2z

https://pastecode.io/s/wvsppfdh


On 11/15/2021 7:17 AM, Christian Ramseyer wrote:

Hi Jim

Ok it wasn't quite clear to me earlier in this thread where you're not 
finding the expected IPs. For the addresses tab, the data is collected 
in the discover step, and written into the table device_ip. This is 
most likely empty for your device, you can check with:


db=> select * from device_ip where ip = 'x.x.x.x';

IIRC this uses IP-MIB, but you can see exactly what OIDs are queried, 
and what is returned by running


netdisco-do discover -DISQ -d x.x.x.x

Unfortunately your pastecode snipped expired so I can't tell if there 
were any errors there, but this should point the search in the right 
direction.


Cheers
Christian




On 12.11.21 22:59, Jim Araujo wrote:
Alrighty. I just erased the db from postgres and add a single device 
having the issue. Still occuring only with one device. 
https://pastecode.io/s/tuuc90gy


and the address page




On 11/12/2021 4:34 PM, Michael Butash wrote:
Why I mentioned comparing the databases, though not sure how they 
link to each other, by a device column or some index, or combination 
thereof.  If the ssh collected mac table is using a wrong device to 
link to snmp data, it'll just treat them as two broken sets of 
devices vs. merging and associating them.  Could just be something 
dumb like ip vs. name vs. whatever you used for the sshcollector 
device spec in deployment.yml, but the data sounds just unassociated 
for whatever reason.


I had to learn to nose around the psql tables and basic sql queries 
manually (select * from $table;), but it was helpful to see how 
things associate, and what data was available to build my own custom 
reports.  I'd suggest a crash course in postgres and sql queries in 
your spare time if planning to stick with netdisco over time.  I 
took a day or two over the weekend to do so and actually make a 
custom report or 3, if you know linux decently already it's not bad, 
and learning new stuff is never bad in general.


-mb


On Fri, Nov 12, 2021 at 1:53 PM Jim Araujo  wrote:

    I believe you are on to something with the problem associating an
    asset to the same device or different. The Palo is part of a HA
    pair so the IP and MAC are used by both according to Netdisco. If
    I search the database for a MAC or IP owned by the Palo it shows
    up on both units. Would this explain why searching in the the web
    gui shows two devices listed with the same IP but the unit itself
    says no address found?

    -

    On 11/12/2021 12:42 AM, Michael Butash wrote:

    I would think with snmp in any version working you would get
    *most* data back to build a device model, and arp would give you
    the rest for mac associations as a router without a cam table
    would link device interfaces.  Even stupid cisco firewalls that
    still don't support cdp/lldp or arp mib via polling usually give
    me a proper response enough to build a netdisco device, but not
    enough to associate them properly to a switch link in topology
    without the mac->ip via arp tables polled with ssh as Christian
    mentioned.

    Do you get lldp neighbors show on the pan/f5 and switch both in
    netdisco?  Maybe debug the device discovery to see what it's
    polling and results, or compare the data between the sql tables
    if not matching up?  Seems perhaps something isn't associating
    the same device, snmp vs ssh collector, or conflicting? Should it?

    Good data to probably add to the site for troubleshooting ssh
    features out of this, something I was meaning to try at my last
    project but didn't get to for our pans there.

    -mb


    On Thu, Nov 11, 2021 at 5:04 PM Jim Araujo 
    wrote:

    Hi Christian,

    Thanks again for looking into this. Perhaps I am confused. I
    thought for
    these 

netdisco-users Digest, Vol 184, Issue 16

[netdisco-users-request]

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: LDAPS authentication possible / How to discover all?
  (Basti S.)
   2. Re: LDAPS authentication possible / How to discover all?
  (Oliver Gorwits)
   3. Re: LDAPS authentication possible / How to discover all?
  (Christian Ramseyer)
--- Begin Message ---
It would be very nice if somebody patch this and make LDAPS possible. :-)
In the meantime I would say LDAPS is state of the art and normal LDAP
should no longer be used.

Thanks for the help with the discovery. I will use the loop with a text
file, good idea!

Regards
Bastian


Am Fr., 12. Nov. 2021 um 13:35 Uhr schrieb Christian Ramseyer <
ramse...@netnea.com>:

> Hi Bastian
>
> On 12.11.21 09:26, Basti S. wrote:
> > Hello,
> >
> > In the past we used the LDAP authentication for netdisco, a very nice
> thing.
> > But as far as I know LDAPS is not possible - is there a way to make it
> > possible?
>
> Yes it unsupported according to the doc:
> . I never
> looked into it too closely but Net::LDAP does ldaps just fine, so I
> imagine it couldn't be too hard to patch in. Most likely nobody wanted
> it bad enough to submit a Patch/PR.
>
> >
> > Second question: Should Netdisco find all other connected switches if I
> > just do the discovery for the back bone switch? Or how can I achieve
> > that without do it for every single switch?
>
> Theoretically Netdisco should find your whole network from a single
> switch, but in practice that's not always working. If you have chunks of
> the network missing you can manually discover some IPs in these chunks.
>
> Alternatively you can also discover whole IP ranges, e.g.
>
> netdisco-do discover --enqueue -d 192.168.7.0/24
>
> or discover a list of ip addresses from your inventory with:
>
> for ip in $(< mylist.txt) ; do netdisco-do discover --enqueue -d $ip ; done
>
>
> Cheers
> Christian
>
>
> --
> Christian Ramseyer, netnea ag
> Network Management. Security. OpenSource.
> Phone: +41 79 644 77 64
>
>
--- End Message ---
--- Begin Message ---
Hi Bastian

To clarify:

   - Netdisco _does_ support secure LDAP using TLS, using the
   official StartTLS extension (see the docs...).
   - Netdisco (and Net::LDAP) does not support the non-standard LDAPS

I googled and found this explanation of the two approaches:
https://kb.sos-berlin.com/pages/viewpage.action?pageId=18778435
This is very similar to SMTP where the standard model is also using
StartTLS over the standard SMTP ports. SMTPS is an old and outdated model.

I expect that whatever software you use for LDAP should support StartTLS.

regards
Oliver.

On Tue, 16 Nov 2021 at 10:44, Basti S.  wrote:

> It would be very nice if somebody patch this and make LDAPS possible. :-)
> In the meantime I would say LDAPS is state of the art and normal LDAP
> should no longer be used.
>
> Thanks for the help with the discovery. I will use the loop with a text
> file, good idea!
>
> Regards
> Bastian
>
>
> Am Fr., 12. Nov. 2021 um 13:35 Uhr schrieb Christian Ramseyer <
> ramse...@netnea.com>:
>
>> Hi Bastian
>>
>> On 12.11.21 09:26, Basti S. wrote:
>> > Hello,
>> >
>> > In the past we used the LDAP authentication for netdisco, a very nice
>> thing.
>> > But as far as I know LDAPS is not possible - is there a way to make it
>> > possible?
>>
>> Yes it unsupported according to the doc:
>> . I never
>> looked into it too closely but Net::LDAP does ldaps just fine, so I
>> imagine it couldn't be too hard to patch in. Most likely nobody wanted
>> it bad enough to submit a Patch/PR.
>>
>> >
>> > Second question: Should Netdisco find all other connected switches if I
>> > just do the discovery for the back bone switch? Or how can I achieve
>> > that without do it for every single switch?
>>
>> Theoretically Netdisco should find your whole network from a single
>> switch, but in practice that's not always working. If you have chunks of
>> the network missing you can manually discover some IPs in these chunks.
>>
>> Alternatively you can also discover whole IP ranges, e.g.
>>
>> netdisco-do discover --enqueue -d 192.168.7.0/24
>>
>> or discover a list of ip addresses from your inventory with:
>>
>> for ip in $(< mylist.txt) ; do netdisco-do discover --enqueue -d $ip ;
>> done
>>
>>
>> Cheers
>> Christian
>>
>>
>> --
>> Christian Ramseyer, netnea ag
>> Network Management. Security. OpenSource.

netdisco-users Digest, Vol 184, Issue 11

[netdisco-users-request]

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. LDAPS authentication possible / How to discover all? (Basti S.)
   2. Re: LDAPS authentication possible / How to discover all?
  (Christian Ramseyer)
--- Begin Message ---
Hello,

In the past we used the LDAP authentication for netdisco, a very nice thing.
But as far as I know LDAPS is not possible - is there a way to make it
possible?

Second question: Should Netdisco find all other connected switches if I
just do the discovery for the back bone switch? Or how can I achieve that
without do it for every single switch?

Thanks in advance!

Regards,
Bastian
--- End Message ---
--- Begin Message ---

Hi Bastian

On 12.11.21 09:26, Basti S. wrote:

Hello,

In the past we used the LDAP authentication for netdisco, a very nice thing.
But as far as I know LDAPS is not possible - is there a way to make it 
possible?


Yes it unsupported according to the doc: 
. I never 
looked into it too closely but Net::LDAP does ldaps just fine, so I 
imagine it couldn't be too hard to patch in. Most likely nobody wanted 
it bad enough to submit a Patch/PR.




Second question: Should Netdisco find all other connected switches if I 
just do the discovery for the back bone switch? Or how can I achieve 
that without do it for every single switch?


Theoretically Netdisco should find your whole network from a single 
switch, but in practice that's not always working. If you have chunks of 
the network missing you can manually discover some IPs in these chunks.


Alternatively you can also discover whole IP ranges, e.g.

netdisco-do discover --enqueue -d 192.168.7.0/24

or discover a list of ip addresses from your inventory with:

for ip in $(< mylist.txt) ; do netdisco-do discover --enqueue -d $ip ; done


Cheers
Christian


--
Christian Ramseyer, netnea ag
Network Management. Security. OpenSource.
Phone: +41 79 644 77 64



--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 184, Issue 12

[netdisco-users-request]

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: SSH Collector Testing? (Jim Araujo)
   2. Re: SSH Collector Testing? (Michael Butash)
--- Begin Message ---
I believe you are on to something with the problem associating an asset 
to the same device or different. The Palo is part of a HA pair so the IP 
and MAC are used by both according to Netdisco. If I search the database 
for a MAC or IP owned by the Palo it shows up on both units. Would this 
explain why searching in the the web gui shows two devices listed with 
the same IP but the unit itself says no address found?


-

On 11/12/2021 12:42 AM, Michael Butash wrote:
I would think with snmp in any version working you would get *most* 
data back to build a device model, and arp would give you the rest for 
mac associations as a router without a cam table would link device 
interfaces.  Even stupid cisco firewalls that still don't support 
cdp/lldp or arp mib via polling usually give me a proper response 
enough to build a netdisco device, but not enough to associate them 
properly to a switch link in topology without the mac->ip via arp 
tables polled with ssh as Christian mentioned.


Do you get lldp neighbors show on the pan/f5 and switch both in 
netdisco?  Maybe debug the device discovery to see what it's polling 
and results, or compare the data between the sql tables if not 
matching up?  Seems perhaps something isn't associating the same 
device, snmp vs ssh collector, or conflicting?  Should it?


Good data to probably add to the site for troubleshooting ssh features 
out of this, something I was meaning to try at my last project but 
didn't get to for our pans there.


-mb


On Thu, Nov 11, 2021 at 5:04 PM Jim Araujo  wrote:

Hi Christian,

Thanks again for looking into this. Perhaps I am confused. I
thought for
these particular devices SSHCollector performs the task of getting IP
addresses?

I've setup the stanza for

https://metacpan.org/pod/App::Netdisco::SSHCollector::Platform::PaloAlto

and looking at the code on github, it looks like the SSHCollector
performs a "set cli scripting-mode on" and then a "show arp all". I
believe the collector is working as the database command you had
me run
shows the database has the  interface IP addresses. Just the Web
GUI is
blank. If I search for an IP owned by the Palo it shows up under the
switch it is plugged into, but not for the PaloAlto itself.


On 11/11/2021 6:46 PM, Christian Ramseyer wrote:
> Ok in the macsuck part it says that the device does not advertise
> layer 2 functionality in the SNMP attributes, and so no macsuck is
> performed.
>
> I think if you just enter the IP or Mac in the search box on top of
> the UI, you should get an entry similar to the attached image. But
> since there is no L2 mapping from Mac to Port it will not show
up in
> the ports of the device, it's just a disconnected ARP entry.
>
> I have no Palo Altos to try, in some cases you can get lucky by
just
> enabling layer 2 in the snmp settings, but more likely Palo Alto
does
> not support these MIBs and will not give you any useful data. Maybe
> somebody else on the list has experience with this brand.
>
> Cheers
> Christian
>
>
> On 11.11.21 17:29, Jim Araujo wrote:
>> Hi Christian, thanks for the troubleshooting steps. I see that the
>> last query shows the database has the IPv4 addresses in it, but
the
>> Web Gui does not. The troubleshooting log is from a Palo alto
PA-5220.
>>
>> https://pastecode.io/s/0i2kdb37
>>
>>
>> On 11/11/2021 8:08 AM, Christian Ramseyer wrote:
>>> Hi Jim
>>>
>>> The SSH collector only collects ARP tables. There are two more
>>> pieces that are needed for everything to show up properly in
the web
>>> interface:
>>>
>>> - discovery of the L2 device: netdisco-do -D discover -d 
>>>   this will give the list of interfaces and other hardware
>>> - collection of the mac address tables: netdisco-do -D macsuck
-d 
>>>   this will give the interface -> connected MAC addresses
>>>
>>> If you see ARP entries collected that later can not be found
in the
>>> UI, most likely one of these is not working properly with your
gear.
>>>
>>> I usually look into the database using SQL after running
>>> discover/macsuck/arpnip: 

netdisco-users Digest, Vol 184, Issue 14

[netdisco-users-request]

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: SSH Collector Testing? (Christian Ramseyer)
--- Begin Message ---

Hi Jim

Ok it wasn't quite clear to me earlier in this thread where you're not 
finding the expected IPs. For the addresses tab, the data is collected 
in the discover step, and written into the table device_ip. This is most 
likely empty for your device, you can check with:


db=> select * from device_ip where ip = 'x.x.x.x';

IIRC this uses IP-MIB, but you can see exactly what OIDs are queried, 
and what is returned by running


netdisco-do discover -DISQ -d x.x.x.x

Unfortunately your pastecode snipped expired so I can't tell if there 
were any errors there, but this should point the search in the right 
direction.


Cheers
Christian




On 12.11.21 22:59, Jim Araujo wrote:
Alrighty. I just erased the db from postgres and add a single device 
having the issue. Still occuring only with one device. 
https://pastecode.io/s/tuuc90gy


and the address page




On 11/12/2021 4:34 PM, Michael Butash wrote:
Why I mentioned comparing the databases, though not sure how they link 
to each other, by a device column or some index, or combination 
thereof.  If the ssh collected mac table is using a wrong device to 
link to snmp data, it'll just treat them as two broken sets of devices 
vs. merging and associating them.  Could just be something dumb like 
ip vs. name vs. whatever you used for the sshcollector device spec in 
deployment.yml, but the data sounds just unassociated for whatever reason.


I had to learn to nose around the psql tables and basic sql queries 
manually (select * from $table;), but it was helpful to see how things 
associate, and what data was available to build my own custom 
reports.  I'd suggest a crash course in postgres and sql queries in 
your spare time if planning to stick with netdisco over time.  I took 
a day or two over the weekend to do so and actually make a custom 
report or 3, if you know linux decently already it's not bad, and 
learning new stuff is never bad in general.


-mb


On Fri, Nov 12, 2021 at 1:53 PM Jim Araujo  wrote:

I believe you are on to something with the problem associating an
asset to the same device or different. The Palo is part of a HA
pair so the IP and MAC are used by both according to Netdisco. If
I search the database for a MAC or IP owned by the Palo it shows
up on both units. Would this explain why searching in the the web
gui shows two devices listed with the same IP but the unit itself
says no address found?

-

On 11/12/2021 12:42 AM, Michael Butash wrote:

I would think with snmp in any version working you would get
*most* data back to build a device model, and arp would give you
the rest for mac associations as a router without a cam table
would link device interfaces.  Even stupid cisco firewalls that
still don't support cdp/lldp or arp mib via polling usually give
me a proper response enough to build a netdisco device, but not
enough to associate them properly to a switch link in topology
without the mac->ip via arp tables polled with ssh as Christian
mentioned.

Do you get lldp neighbors show on the pan/f5 and switch both in
netdisco?  Maybe debug the device discovery to see what it's
polling and results, or compare the data between the sql tables
if not matching up?  Seems perhaps something isn't associating
the same device, snmp vs ssh collector, or conflicting?  Should it?

Good data to probably add to the site for troubleshooting ssh
features out of this, something I was meaning to try at my last
project but didn't get to for our pans there.

-mb


On Thu, Nov 11, 2021 at 5:04 PM Jim Araujo 
wrote:

Hi Christian,

Thanks again for looking into this. Perhaps I am confused. I
thought for
these particular devices SSHCollector performs the task of
getting IP
addresses?

I've setup the stanza for

https://metacpan.org/pod/App::Netdisco::SSHCollector::Platform::PaloAlto

and looking at the code on github, it looks like the
SSHCollector
performs a "set cli scripting-mode on" and then a "show arp
all". I
believe the collector is working as the database command you
had me run
shows the database has the  interface IP addresses. Just the
Web GUI is
blank. If I search 

netdisco-users Digest, Vol 184, Issue 8

[netdisco-users-request]

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: SSH Collector Testing? (Jim Araujo)
--- Begin Message ---
I believe SSHCollector is getting the ARP entries as when i do a 
'~/bin/netdisco-do arpnip -d 1.2.3.4 -D' shows 'processed 43 ARP cache 
entries.  However nothing is listed in the web gui for this node...Am I 
running into a bug?


https://sourceforge.net/p/netdisco/netdisco2/254/

On 11/10/2021 8:43 AM, Jim Araujo wrote:
Hello netdisco team! First off great work on this app, it is 
incredible. SNMPv3 seems to work correctly, however when I create a 
new stanza for SSH collection for devices like BigIP, PaloAlto, and 
NXOS is there a way to test if they are working? On the web gui these 
particular devices do not show any information under Addresses, nor 
anything under Ports...I am hoping to get this working as we have a 
large F5 environment and would be helpful to be able to search for IPs 
that the F5 or PaloAlto owns.


Thanks again!


--
-Jim



--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 184, Issue 4

[netdisco-users-request]

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: Issues with netdisco and postgresql (Oliver Gorwits)
--- Begin Message ---
>
> All you can really do is distribute collection, spread out timed jobs


Yes, it's worth looking into the features we have... you can run multiple
backends (restricted to certain device IPs if you wish, or not), you can
spread out the polling by having different arpwalk/etc commands limited to
certain device IPs, and of course simply alter the number of pollers on the
backend.

Similar to Mike I would be interested to hear examples of how people have
used these features (I do know that distributed backends has been helpful
to those running global networks, to have the SNMP happen locally and DB
data sent over the WAN back home) -- and any tips for DB scaling as that
becomes the central bottleneck for it all.

Thanks,

On Sat, 6 Nov 2021 at 07:11, Michael Butash  wrote:

> Do you have a lot of fex or stack switch ports?  With ciscos I always
> notice vss/stack/fex's are terribly slow in returning snmp data and put
> huge delays into them having to remote query cluster devices with enough
> they'll back monitoring up.  I've seen this in bigger environments when
> polling a lot of pseudo-devices like those, particularly remotely a few
> states away over vpn.  I find these often good reasons not to use
> vss/stack/fex's, and seen enough tools conversely also impact (ie crash)
> the devices adversely from over-polling.  Hell, last asr1000 I pointed
> netdisco at began causing 100% cpu, never underestimate vendor
> bugs/stupidity.
>
> All you can really do is distribute collection, spread out timed jobs, or
> squeeze performance out of the app/db themselves debugging the box.  Check
> iotop and db tools for performance bottlenecks too.
>
> I'd be curious what a scale out model of netdisco would look like for
> large/huge environments if distributed layers of collection, database,
> graphic ui's, etc, but never needed to.
>
> -mb
>
>
> On Fri, Nov 5, 2021 at 9:01 PM Muris  wrote:
>
>> Hi Trent, thanks for that.
>>
>>
>>
>> What I found out was, because the environment is so big, the arpnips and
>> macsucks are overlapping, I have them on a hourly basis..so I don’t think
>> they finishing on time... so I have separated them out by 2 – 3 hours now..
>> and it seems to be working a lot better. When arpnips/macsucks are running
>> seems to use 90-100% cpu.. and then web requests can timeout looking up
>> things.
>>
>>
>>
>> Will checkout the vacuum things too.
>>
>>
>>
>> Muris
>>
>>
>>
>> *From: *Trent Curtis 
>> *Date: *Thursday, 4 November 2021 at 22:07
>> *To: *Dominik Müller 
>> *Cc: *
>> *Subject: *Re: [Netdisco] Issues with netdisco and postgresql
>>
>>
>>
>> I would suggest stopping services, restarting postgres, and performing a
>> full database vacuum, and potentially clearing the admin table.
>>
>>
>>
>> 1. Sudo as netdisco and Stop Netdisco-backend and Netdisco-web:
>>
>> ~/bin/netdisco-backend stop
>>
>> ~/bin/netdisco-web stop
>>
>>
>>
>> 2. Restart postgres service per your distro instructions.
>>
>>
>>
>> 3. Sudo as postgres user and execute:
>>
>> psql netdisco
>>
>> set statement_timeout=0;
>>
>> vacuum full;
>>
>>
>>
>> The vacuum will take a while depending on the table sizes.  I'd suggest
>> also making the pgtune tweaks if you have not already. It would also good
>> to take a look at your postgres logs to see if the vacuum is actually
>> running. Another tip would be to clear the admin table all together to
>> clear any schedule backlogs, this could be one of the culprits of the
>> slowness.
>>
>>
>>
>> To clear the admin queue, sudo as netdisco and execute:
>>
>> ~/bin/netdisco-do psql -e "DELETE FROM admin;"
>>
>>
>>
>> Also please share your schedule config from the deployment.yml file.
>> Ultimately you want to avoid any job overlaps to prevent scheduling
>> backlogs.
>>
>>
>>
>> Hope this helps.
>>
>>
>>
>> - Trent
>>
>>
>>
>> On Thu, Nov 4, 2021, 1:21 AM Dominik Müller  wrote:
>>
>> Hi,
>>
>>
>>
>> sounds like there is a constant writing on your db.
>>
>> How often do you discover your Network?
>>
>>
>>
>> BR
>>
>>
>>
>> Dominik
>>
>>
>>
>> Am 04.11.2021 um 04:47 schrieb Kurt Buff :
>>
>> 
>>
>> A pure guess - is the vacuum running?
>>
>> https://www.postgresql.org/docs/9.1/sql-vacuum.html
>>
>>
>>
>> Kurt
>>
>>
>>
>> On Wed, Nov 3, 2021 at 7:55 AM Muris  wrote:
>>
>> Hi All,
>>
>>
>>
>> I have a bit of a problem where netdisco database seems to 

netdisco-users Digest, Vol 184, Issue 3

[netdisco-users-request]

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: Issues with netdisco and postgresql (Muris)
   2. Re: Issues with netdisco and postgresql (Michael Butash)
--- Begin Message ---
Hi Trent, thanks for that.

 

What I found out was, because the environment is so big, the arpnips and 
macsucks are overlapping, I have them on a hourly basis..so I don’t think they 
finishing on time... so I have separated them out by 2 – 3 hours now.. and it 
seems to be working a lot better. When arpnips/macsucks are running seems to 
use 90-100% cpu.. and then web requests can timeout looking up things.

 

Will checkout the vacuum things too.

 

Muris

 

From: Trent Curtis 
Date: Thursday, 4 November 2021 at 22:07
To: Dominik Müller 
Cc: 
Subject: Re: [Netdisco] Issues with netdisco and postgresql

 

I would suggest stopping services, restarting postgres, and performing a full 
database vacuum, and potentially clearing the admin table.

 

1. Sudo as netdisco and Stop Netdisco-backend and Netdisco-web: 

~/bin/netdisco-backend stop

~/bin/netdisco-web stop

 

2. Restart postgres service per your distro instructions.  

 

3. Sudo as postgres user and execute: 

psql netdisco

set statement_timeout=0;

vacuum full; 

 

The vacuum will take a while depending on the table sizes.  I'd suggest also 
making the pgtune tweaks if you have not already. It would also good to take a 
look at your postgres logs to see if the vacuum is actually running. Another 
tip would be to clear the admin table all together to clear any schedule 
backlogs, this could be one of the culprits of the slowness. 

 

To clear the admin queue, sudo as netdisco and execute: 

~/bin/netdisco-do psql -e "DELETE FROM admin;"

 

Also please share your schedule config from the deployment.yml file. Ultimately 
you want to avoid any job overlaps to prevent scheduling backlogs.

 

Hope this helps.

 

- Trent

 

On Thu, Nov 4, 2021, 1:21 AM Dominik Müller  wrote:

Hi,

 

sounds like there is a constant writing on your db.

How often do you discover your Network?

 

BR

 

Dominik




Am 04.11.2021 um 04:47 schrieb Kurt Buff :



A pure guess - is the vacuum running?

https://www.postgresql.org/docs/9.1/sql-vacuum.html

 

Kurt

 

On Wed, Nov 3, 2021 at 7:55 AM Muris  wrote:

Hi All,

 

I have a bit of a problem where netdisco database seems to have stopped working 
and lookups from web interface I have tried to restart postgresql and 
netdisco-web and netdisco-backend helps a bit but then starts happening again

 

The database is very slow to access looking at items through the web interface, 
and looking up a device comes up with “Search failed! Please contact your site 
administrator (server error).”

 

Netdisco-backend and netdisco-log don’t show any errors, so I think its 
something postgresql related that’s not going right…

 

I then stop netdisco-web and netdisco-backend and theres this “postgres : 
checkpointer” that constantly hangs around and takes cpu

 

What can I do to fix it or see whats going on with postgres? 

 

Thanks

Muris

___
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/

___
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/

___
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/

--- End Message ---
--- Begin Message ---
Do you have a lot of fex or stack switch ports?  With ciscos I always
notice vss/stack/fex's are terribly slow in returning snmp data and put
huge delays into them having to remote query cluster devices with enough
they'll back monitoring up.  I've seen this in bigger environments when
polling a lot of pseudo-devices like those, particularly remotely a few
states away over vpn.  I find these often good reasons not to use
vss/stack/fex's, and seen enough tools conversely also impact (ie crash)
the devices adversely from over-polling.  Hell, last asr1000 I pointed
netdisco at began causing 100% cpu, never underestimate vendor
bugs/stupidity.

All you can really do is distribute collection, spread out timed jobs, or
squeeze performance out of the app/db themselves debugging the box.  Check
iotop and db tools for performance bottlenecks too.

I'd be curious what 

netdisco-users Digest, Vol 184, Issue 1

[netdisco-users-request]

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. Issues with netdisco and postgresql (Muris)
   2. Re: Issues with netdisco and postgresql (Kurt Buff)
   3. Re: Issues with netdisco and postgresql (Dominik M?ller)
--- Begin Message ---
Hi All,

 

I have a bit of a problem where netdisco database seems to have stopped working 
and lookups from web interface I have tried to restart postgresql and 
netdisco-web and netdisco-backend helps a bit but then starts happening again

 

The database is very slow to access looking at items through the web interface, 
and looking up a device comes up with “Search failed! Please contact your site 
administrator (server error).”

 

Netdisco-backend and netdisco-log don’t show any errors, so I think its 
something postgresql related that’s not going right…

 

I then stop netdisco-web and netdisco-backend and theres this “postgres : 
checkpointer” that constantly hangs around and takes cpu

 

What can I do to fix it or see whats going on with postgres? 

 

Thanks

Muris

--- End Message ---
--- Begin Message ---
A pure guess - is the vacuum running?
https://www.postgresql.org/docs/9.1/sql-vacuum.html

Kurt

On Wed, Nov 3, 2021 at 7:55 AM Muris  wrote:

> Hi All,
>
>
>
> I have a bit of a problem where netdisco database seems to have stopped
> working and lookups from web interface I have tried to restart postgresql
> and netdisco-web and netdisco-backend helps a bit but then starts happening
> again
>
>
>
> The database is very slow to access looking at items through the web
> interface, and looking up a device comes up with “Search failed! Please
> contact your site administrator (server error).”
>
>
>
> Netdisco-backend and netdisco-log don’t show any errors, so I think its
> something postgresql related that’s not going right…
>
>
>
> I then stop netdisco-web and netdisco-backend and theres this “postgres :
> checkpointer” that constantly hangs around and takes cpu
>
>
>
> What can I do to fix it or see whats going on with postgres?
>
>
>
> Thanks
>
> Muris
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi,

sounds like there is a constant writing on your db.
How often do you discover your Network?

BR

Dominik

> Am 04.11.2021 um 04:47 schrieb Kurt Buff :
> 
> 
> A pure guess - is the vacuum running?
> https://www.postgresql.org/docs/9.1/sql-vacuum.html
> 
> Kurt
> 
> On Wed, Nov 3, 2021 at 7:55 AM Muris  wrote:
>> Hi All,
>> 
>>  
>> 
>> I have a bit of a problem where netdisco database seems to have stopped 
>> working and lookups from web interface I have tried to restart postgresql 
>> and netdisco-web and netdisco-backend helps a bit but then starts happening 
>> again
>> 
>>  
>> 
>> The database is very slow to access looking at items through the web 
>> interface, and looking up a device comes up with “Search failed! Please 
>> contact your site administrator (server error).”
>> 
>>  
>> 
>> Netdisco-backend and netdisco-log don’t show any errors, so I think its 
>> something postgresql related that’s not going right…
>> 
>>  
>> 
>> I then stop netdisco-web and netdisco-backend and theres this “postgres : 
>> checkpointer” that constantly hangs around and takes cpu
>> 
>>  
>> 
>> What can I do to fix it or see whats going on with postgres?
>> 
>>  
>> 
>> Thanks
>> 
>> Muris
>> 
>> ___
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
> ___
> Netdisco mailing list
> 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

netdisco-users Digest, Vol 184, Issue 2

[netdisco-users-request]

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: Issues with netdisco and postgresql (Trent Curtis)
--- Begin Message ---
I would suggest stopping services, restarting postgres, and performing a
full database vacuum, and potentially clearing the admin table.

1. Sudo as netdisco and Stop Netdisco-backend and Netdisco-web:
~/bin/netdisco-backend stop
~/bin/netdisco-web stop

2. Restart postgres service per your distro instructions.

3. Sudo as postgres user and execute:
psql netdisco
set statement_timeout=0;
vacuum full;

The vacuum will take a while depending on the table sizes.  I'd suggest
also making the pgtune tweaks if you have not already. It would also good
to take a look at your postgres logs to see if the vacuum is actually
running. Another tip would be to clear the admin table all together to
clear any schedule backlogs, this could be one of the culprits of the
slowness.

To clear the admin queue, sudo as netdisco and execute:
~/bin/netdisco-do psql -e "DELETE FROM admin;"

Also please share your schedule config from the deployment.yml file.
Ultimately you want to avoid any job overlaps to prevent scheduling
backlogs.

Hope this helps.

- Trent


On Thu, Nov 4, 2021, 1:21 AM Dominik Müller  wrote:

> Hi,
>
> sounds like there is a constant writing on your db.
> How often do you discover your Network?
>
> BR
>
> Dominik
>
> Am 04.11.2021 um 04:47 schrieb Kurt Buff :
>
> 
> A pure guess - is the vacuum running?
> https://www.postgresql.org/docs/9.1/sql-vacuum.html
>
> Kurt
>
> On Wed, Nov 3, 2021 at 7:55 AM Muris  wrote:
>
>> Hi All,
>>
>>
>>
>> I have a bit of a problem where netdisco database seems to have stopped
>> working and lookups from web interface I have tried to restart postgresql
>> and netdisco-web and netdisco-backend helps a bit but then starts happening
>> again
>>
>>
>>
>> The database is very slow to access looking at items through the web
>> interface, and looking up a device comes up with “Search failed! Please
>> contact your site administrator (server error).”
>>
>>
>>
>> Netdisco-backend and netdisco-log don’t show any errors, so I think its
>> something postgresql related that’s not going right…
>>
>>
>>
>> I then stop netdisco-web and netdisco-backend and theres this “postgres :
>> checkpointer” that constantly hangs around and takes cpu
>>
>>
>>
>> What can I do to fix it or see whats going on with postgres?
>>
>>
>>
>> Thanks
>>
>> Muris
>> ___
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
> ___
> Netdisco mailing list
> 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

netdisco-users Digest, Vol 184, Issue 5

[netdisco-users-request]

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: Issues with netdisco and postgresql (Christian Ramseyer)
   2. Re: Issues with netdisco and postgresql (Michael Butash)
--- Begin Message ---
We did a lot of experimenting and tuning over the years, but in the end 
macsucking through a large Cisco network is just very slow due to the 
community based indexing. It effectively turns a linear problem into a 
quadratish one, and a DC-style switch with a bunch of FEX and a large 
amount of VLANS can clog up a poller for ten minutes easily.


I was thinking lately about trying non-SNMP variants of macsuck, e.g. by 
leveraging ntc-templates for the parsing of all "show mac-address table" 
IOS/NXOS variants and then writing the results back via the API. I'm 
pretty sure that would speed up things a lot. In the meantime, we just 
throw CPUs and workers: at the problem until we finish in the desired 
cycle time :)



Cheers
Christian


On 06.11.21 08:42, Oliver Gorwits wrote:

All you can really do is distribute collection, spread out timed jobs


Yes, it's worth looking into the features we have... you can run 
multiple backends (restricted to certain device IPs if you wish, or 
not), you can spread out the polling by having different arpwalk/etc 
commands limited to certain device IPs, and of course simply alter the 
number of pollers on the backend.


Similar to Mike I would be interested to hear examples of how people 
have used these features (I do know that distributed backends has been 
helpful to those running global networks, to have the SNMP happen 
locally and DB data sent over the WAN back home) -- and any tips for DB 
scaling as that becomes the central bottleneck for it all.


Thanks,

On Sat, 6 Nov 2021 at 07:11, Michael Butash > wrote:


Do you have a lot of fex or stack switch ports?  With ciscos I
always notice vss/stack/fex's are terribly slow in returning snmp
data and put huge delays into them having to remote query cluster
devices with enough they'll back monitoring up.  I've seen this in
bigger environments when polling a lot of pseudo-devices like those,
particularly remotely a few states away over vpn.  I find these
often good reasons not to use vss/stack/fex's, and seen enough tools
conversely also impact (ie crash) the devices adversely from
over-polling.  Hell, last asr1000 I pointed netdisco at began
causing 100% cpu, never underestimate vendor bugs/stupidity.

All you can really do is distribute collection, spread out timed
jobs, or squeeze performance out of the app/db themselves debugging
the box.  Check iotop and db tools for performance bottlenecks too.

I'd be curious what a scale out model of netdisco would look like
for large/huge environments if distributed layers of collection,
database, graphic ui's, etc, but never needed to.

-mb


On Fri, Nov 5, 2021 at 9:01 PM Muris mailto:alcat...@gmail.com>> wrote:

Hi Trent, thanks for that.

__ __

What I found out was, because the environment is so big, the
arpnips and macsucks are overlapping, I have them on a hourly
basis..so I don’t think they finishing on time... so I have
separated them out by 2 – 3 hours now.. and it seems to be
working a lot better. When arpnips/macsucks are running seems to
use 90-100% cpu.. and then web requests can timeout looking up
things.

__ __

Will checkout the vacuum things too.

__ __

Muris

__ __

*From: *Trent Curtis mailto:trent.cur...@gmail.com>>
*Date: *Thursday, 4 November 2021 at 22:07
*To: *Dominik Müller mailto:mue...@t-online.de>>
*Cc: *mailto:netdisco-users@lists.sourceforge.net>>
*Subject: *Re: [Netdisco] Issues with netdisco and postgresql

__ __

I would suggest stopping services, restarting postgres, and
performing a full database vacuum, and potentially clearing the
admin table.

__ __

1. Sudo as netdisco and Stop Netdisco-backend and Netdisco-web: 

~/bin/netdisco-backend stop

~/bin/netdisco-web stop

__ __

2. Restart postgres service per your distro instructions. 

__ __

3. Sudo as postgres user and execute: 

psql netdisco

set statement_timeout=0;

  

netdisco-users Digest, Vol 185, Issue 1

[netdisco-users-request]

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. CVE-2021-44228, log4j, Dancer, Apache2 (o...@leferguson.com)
   2. Re: CVE-2021-44228, log4j, Dancer, Apache2 (Christian Ramseyer)
   3. Re: CVE-2021-44228, log4j, Dancer, Apache2 (o...@leferguson.com)
--- Begin Message ---
I have been running Netdisco for ages under apache, but I honestly do not know 
if dancer is still under the covers somewhere or how to check.

Is there any info on ensuring that Netdisco (+/- dancer) either does not have 
this vulnerability or has been mitigated (and how/what-version)?

Linwood

--- End Message ---
--- Begin Message ---
Hi Linwood

Netdisco and Dancer is pure Perl only and does not use Log4j, so nothing
to worry about.

You might see the log4j-inspired Log4Perl library as a dependency in
some places, but it is not so closely related as that it would share the
vulnerability.

Cheers
Christian

On 12.12.21 15:46, o...@leferguson.com wrote:
> I have been running Netdisco for ages under apache, but I honestly do
> not know if dancer is still under the covers somewhere or how to check.
> 
>  
> 
> Is there any info on ensuring that Netdisco (+/- dancer) either does not
> have this vulnerability or has been mitigated (and how/what-version)?
> 
>  


--- End Message ---
--- Begin Message ---
One less to worry about.  Thank you.


-Original Message-
From: Christian Ramseyer  
Sent: Sunday, December 12, 2021 1:19 PM
To: o...@leferguson.com; netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] CVE-2021-44228, log4j, Dancer, Apache2

Hi Linwood

Netdisco and Dancer is pure Perl only and does not use Log4j, so nothing to 
worry about.

You might see the log4j-inspired Log4Perl library as a dependency in some 
places, but it is not so closely related as that it would share the 
vulnerability.

Cheers
Christian

On 12.12.21 15:46, o...@leferguson.com wrote:
> I have been running Netdisco for ages under apache, but I honestly do 
> not know if dancer is still under the covers somewhere or how to check.
> 
>  
> 
> Is there any info on ensuring that Netdisco (+/- dancer) either does 
> not have this vulnerability or has been mitigated (and how/what-version)?
> 
>  


--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 180, Issue 6

[netdisco-users-request]

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: pulling out Inventory via Python for automation?
  (Michael Butash)
--- Begin Message ---
I put this together as a different inventory view I was looking for, look
at the SELECT sql query, you'll see where you pull data out of what
tables.  Add this to your deploy.yml and you can see what you get from your
query, then call the data directly using the query via python dbi call to
the db to get what you need.

I finally just dropped into a psql shell and poked around until I figured
out the tables and what data went where.  Some notes below for non-native
sql speakers to do some initial exploration.

## add to $netdisco-install-directory/environments/deploy.yml
reports:
  - tag: device-show-all-inventory
label: 'Custom - Device Show All Inventory'
category: Device
columns:
- { name: Device_Name}
- { ip: IP}
- { dns: FQDN}
- { vendor: Vendor}
- { os: Operating_System}
- { model: Model}
- { os_ver: OS_Version}
- { serial: Serial_Number}
- { last_discover: Last_Discovery}
query: |
  SELECT name AS name, ip AS ip, dns AS dns, vendor AS vendor, os AS
os, os_ver AS os_ver, model AS model, serial AS serial, last_discover AS
last_discover
FROM device
  ORDER BY name

## note query select from above, drop full query into sql below to test

## you can download the report directly as csv then even using the tag name
http://netmon-1:5000/ajax/content/report/device-show-all-inventory?

## jump into postgres account for god mode
root@netmon-1:~# su postgres

## launch the psql client for postgres
postgres@netmon-1:~$ psql
psql (12.7 (Ubuntu 12.7-0ubuntu0.20.04.1))
Type "help" for help.

## switch to netdisco db
postgres=# \c netdisco
You are now connected to database "netdisco" as user "postgres".

## describe tables, each contain device relations to each other.
netdisco=# \dt
   List of relations
 Schema |Name| Type  |  Owner
++---+--
 public | admin  | table | netdisco
 public | community  | table | netdisco
 public | dbix_class_schema_versions | table | netdisco
 public | device | table | netdisco
 public | device_ip  | table | netdisco
 public | device_module  | table | netdisco
 public | device_port| table | netdisco
 public | device_port_log| table | netdisco
 public | device_port_power  | table | netdisco
 public | device_port_properties | table | netdisco
 public | device_port_ssid   | table | netdisco
 public | device_port_vlan   | table | netdisco
 public | device_port_wireless   | table | netdisco
 public | device_power   | table | netdisco
 public | device_skip| table | netdisco
 public | device_vlan| table | netdisco
 public | log| table | netdisco
 public | netmap_positions   | table | netdisco
 public | node   | table | netdisco
 public | node_ip| table | netdisco
 public | node_monitor   | table | netdisco
 public | node_nbt   | table | netdisco
 public | node_wireless  | table | netdisco
 public | oui| table | netdisco
 public | process| table | netdisco
 public | sessions   | table | netdisco
 public | statistics | table | netdisco
 public | subnets| table | netdisco
 public | topology   | table | netdisco
 public | user_log   | table | netdisco
 public | users  | table | netdisco
(31 rows)

## look at all data in any table to see format for each row of device.
This looks at "device" table.
netdisco=# select * from device;

## test query above
netdisco=# SELECT name AS name, ip AS ip, dns AS dns, vendor AS vendor, os
AS os, os_ver AS os_ver, model AS model, serial AS serial, last_discover AS
last_discover FROM device ORDER BY name

Saw this the other day to learn some quickie sql to assemble your own
queries, I learned a bit more roundabout.  https://sqlbolt.com/

-mb


On Mon, Jul 19, 2021 at 12:26 PM Joseph Bernard  wrote:

> I did find this:
>
>
>
> https://github.com/adambaumeister/netdisco_ansible_inventory
>
>
>
> Which also uses the 

netdisco-users Digest, Vol 180, Issue 7

[netdisco-users-request]

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. Error after update to 2.47.007 (C?cile Hamy)
   2. Re: Error after update to 2.47.007 (Oliver Gorwits)
   3. Re: Error after update to 2.47.007 (C?cile Hamy)
   4. Re: Error after update to 2.47.007 (C?cile Hamy)
--- Begin Message ---

Hi,

Following an update from version 2.47.005 to 2.47.007, I encounter an 
error when I run the command :


bin/netdisco-do discover -d [IP or name] -D

 Undefined subroutine & 
App::Netdisco::Util::Permission::hostname_from_ip called at 
/home/netdisco2/perl5/lib/perl5/App/Netdisco/Util/Permission.pm line 128.



Do you have an idea?

Thank you

Best regards

Cécile



--- End Message ---
--- Begin Message ---
Hi Cécile,
I am very sorry about that bug. I have just released version 2.047008 to
CPAN which should work properly.
regards
Oliver.

On Wed, 21 Jul 2021 at 08:18, Cécile Hamy  wrote:

> Hi,
>
> Following an update from version 2.47.005 to 2.47.007, I encounter an
> error when I run the command :
>
> bin/netdisco-do discover -d [IP or name] -D
>
>   Undefined subroutine &
> App::Netdisco::Util::Permission::hostname_from_ip called at
> /home/netdisco2/perl5/lib/perl5/App/Netdisco/Util/Permission.pm line 128.
>
>
> Do you have an idea?
>
> Thank you
>
> Best regards
>
> Cécile
>
>
>
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---

Thank's :)

And good luck

Best regards,

Cécile

On 21/07/2021 10:57, Oliver Gorwits wrote:

Hi Cécile,
I am very sorry about that bug. I have just released version 2.047008 
to CPAN which should work properly.

regards
Oliver.

On Wed, 21 Jul 2021 at 08:18, Cécile Hamy > wrote:


Hi,

Following an update from version 2.47.005 to 2.47.007, I encounter an
error when I run the command :

bin/netdisco-do discover -d [IP or name] -D

  Undefined subroutine &
App::Netdisco::Util::Permission::hostname_from_ip called at
/home/netdisco2/perl5/lib/perl5/App/Netdisco/Util/Permission.pm
line 128.


Do you have an idea?

Thank you

Best regards

Cécile



___
Netdisco mailing list
netdisco-users@lists.sourceforge.net

https://sourceforge.net/p/netdisco/mailman/netdisco-users/



--
Cécile Hamy
/Observatoire de Paris
Direction Informatique de l'Observatoire
Calcul, Stockage, Réseau et Système (CASTORS)
Pool of Awesome Network Devices Administrators (PANDA)/
--- End Message ---
--- Begin Message ---

Just for information

it's Ok after update.

regards,

Cécile

On 21/07/2021 11:44, Cécile Hamy wrote:


Thank's :)

And good luck

Best regards,

Cécile

On 21/07/2021 10:57, Oliver Gorwits wrote:

Hi Cécile,
I am very sorry about that bug. I have just released version 2.047008 
to CPAN which should work properly.

regards
Oliver.

On Wed, 21 Jul 2021 at 08:18, Cécile Hamy > wrote:


Hi,

Following an update from version 2.47.005 to 2.47.007, I
encounter an
error when I run the command :

bin/netdisco-do discover -d [IP or name] -D

  Undefined subroutine &
App::Netdisco::Util::Permission::hostname_from_ip called at
/home/netdisco2/perl5/lib/perl5/App/Netdisco/Util/Permission.pm
line 128.


Do you have an idea?

Thank you

Best regards

Cécile



___
Netdisco mailing list
netdisco-users@lists.sourceforge.net

https://sourceforge.net/p/netdisco/mailman/netdisco-users/



--
Cécile Hamy
/Observatoire de Paris
Direction Informatique de l'Observatoire
Calcul, Stockage, Réseau et Système (CASTORS)
Pool of Awesome Network Devices Administrators (PANDA)/


___
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/

--
Cécile Hamy
/Observatoire de Paris
Direction Informatique de l'Observatoire
Calcul, Stockage, Réseau et Système (CASTORS)
Pool of Awesome Network Devices Administrators (PANDA)/
--- End Message ---

netdisco-users Digest, Vol 180, Issue 4

[netdisco-users-request]

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. pulling out Inventory via Python for automation? (Joseph Bernard)
--- Begin Message ---
Has anyone done or found Python code that can pull out switch information from 
Netidsco for use with things like Nornir, Netmiko, or NAPALM?  Just wanted to 
check so I don’t reinvent the wheel.

Thanks,
Joseph Bernard
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 180, Issue 5

[netdisco-users-request]

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: pulling out Inventory via Python for automation?
  (Michael Butash)
   2. Re: pulling out Inventory via Python for automation?
  (Jimmy Taylor)
   3. Re: pulling out Inventory via Python for automation?
  (Joseph Bernard)
--- Begin Message ---
I too am curious about this.

I have been working on creating a few custom reports in ND for my own
purposes, and learning where to find data across its sql tables (as well as
learning sql queries) is probably the main thing, still automation data is
my end goal too.  ND is a wealth of information to reuse if you can get all
the bits formatted and exported into expected sql columns/rows if nothing
else.

I am not a dev or sql dba, but lots of googling plus examples previously
posted got me some decent custom report output beyond what ND does.
Probably just need to dip directly into pgsql with a dbi to get what you
want, and work off that, at least my plan.

Biggest issue I'm having is trying to figure out how to combine/recognize
things like relations between port channels + physical ports, and just
figuring out what is an uplink with lack of cdp/lldp vs. endpoint ports,
that sometimes ala vm hosts have many macs learned as well.  These are just
challenges with any automation in general around making sense of snmp data
between vendors I suppose, and why devops is so hard with networking, at
least for my non-developer self.

There is the API as well, but not sure how better it might be to work with
that vs. raw sql queries for your needs.

HTH!

-mb


On Mon, Jul 19, 2021 at 8:25 AM Joseph Bernard  wrote:

> Has anyone done or found Python code that can pull out switch information
> from Netidsco for use with things like Nornir, Netmiko, or NAPALM?  Just
> wanted to check so I don’t reinvent the wheel.
>
>
>
> Thanks,
>
> Joseph Bernard
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
I have done this in the past with Netmiko using the Psycopg library.

https://www.psycopg.org/docs/index.html

Like Michael was noting, the key is to get your Psql queries so you can get
the data back in a dictionary that you can work with. I used PgAdmin to
refine my queries:

https://www.pgadmin.org/

Some example queries I've done (use at your own risk):

https://gist.github.com/consentfactory/3990cfc6c1b75eb65fcfe1fdccf013ff

All this said, Netdisco has since implemented the Swagger-UI, which I might
prefer to use at times.

On Mon, Jul 19, 2021 at 11:56 AM Michael Butash  wrote:

> I too am curious about this.
>
> I have been working on creating a few custom reports in ND for my own
> purposes, and learning where to find data across its sql tables (as well as
> learning sql queries) is probably the main thing, still automation data is
> my end goal too.  ND is a wealth of information to reuse if you can get all
> the bits formatted and exported into expected sql columns/rows if nothing
> else.
>
> I am not a dev or sql dba, but lots of googling plus examples previously
> posted got me some decent custom report output beyond what ND does.
> Probably just need to dip directly into pgsql with a dbi to get what you
> want, and work off that, at least my plan.
>
> Biggest issue I'm having is trying to figure out how to combine/recognize
> things like relations between port channels + physical ports, and just
> figuring out what is an uplink with lack of cdp/lldp vs. endpoint ports,
> that sometimes ala vm hosts have many macs learned as well.  These are just
> challenges with any automation in general around making sense of snmp data
> between vendors I suppose, and why devops is so hard with networking, at
> least for my non-developer self.
>
> There is the API as well, but not sure how better it might be to work with
> that vs. raw sql queries for your needs.
>
> HTH!
>
> -mb
>
>
> On Mon, Jul 19, 2021 at 8:25 AM Joseph Bernard  wrote:
>
>> Has anyone done or found Python code that can pull out switch information
>> from Netidsco for use with things like Nornir, Netmiko, or NAPALM?  Just
>> wanted to check so I don’t reinvent the wheel.
>>
>>
>>
>> Thanks,
>>
>> Joseph Bernard
>> ___
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> 

netdisco-users Digest, Vol 180, Issue 8

[netdisco-users-request]

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: Firefox auto-logout (Joseph Bernard)
--- Begin Message ---
So it turns out my install of Firefox was really messed up.  I had to delete it 
and start over.  Now everything works as expected.  No idea if it was a bad 
extension (even when disabled) and/or upgrading so many times.  Might help to 
try if all else fails.

Thanks,
Joseph B.

On 6/9/21, 11:42 AM, "Joseph Bernard"  wrote:

I have seen this as well on Firefox 88.0.1 on macOS.

Thanks,
Joseph Bernard


On 6/9/21, 9:50 AM, "Nick Nauwelaerts"  wrote:

i've seen this only when connecting to different netdisco instances. i 
have a prod & dev setup running on the same server but different ports & 
accounts. whenever i change between them i get logged out. could also be 
firefox tracking protection that's active.


// nick



> -Original Message-
> From: Andy Ruhl 
> Sent: Tuesday, June 8, 2021 22:33
> To: netdisco-users@lists.sourceforge.net
> Subject: [Netdisco] Firefox auto-logout
>
> Externe mail Stop – Denk - Kijk en klik niet zomaar!
>
> I know this probably isn't a Netdisco specific thing, but I figured I
> would ask anyway.
>
> In the last month or so I'm being logged out of Netdisco very
> frequently, as if it's an auto-logout. I'm using Firefox. I tested
> this on Safari and it doesn't behave the same. I remain logged in.
>
> I'm trying to search on why this is but I'm getting inundated with
> results that are irrelevant.
>
> Does anyone know what causes this in Firefox?
>
> Thanks.
>
> Andy
>
>
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/



Volg Aquafin op Facebook | 
Twitter | 
YouTube | 
LinkedIN | 
Instagram

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.

  P Denk aan het milieu. Druk deze mail niet onnodig af.

[www.aquafin.be] 

___
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/


___
Netdisco mailing list
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

netdisco-users Digest, Vol 186, Issue 2

[netdisco-users-request]

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. Can we add custom tags? Trying to get phone extensions mapped
  (Ricardo Stella)
--- Begin Message ---
I've asked before back in March on how to get phone extensions via LLDP but
it seems that you would need discover_phones enabled, and iour phones do
not have SNMP enabled.

In any case, the information is getting pulled as part of the "remote_type"
- Is there a way to map the contents (and ideally a substring) into a
custom field that can be displayed and/or searched for?

Doing a discover -DIQ you can see remote_type includes the necessary
information: "reqDN 1177" whereas 1177 is the phone's extension. If we can
do this, we could map the model number of the phone as well "MINET_6920"
whereas 6920 is the model.

[17616] 2022-01-03 18:27:52 debug  [10.1.1.118] neigh - 10.10.7.142 with ID
[10.10.7.142] on GigabitEthernet1/0/13
SELECT me.ip, me.alias, me.subnet, me.port, me.dns, me.creation
  FROM device_ip me
WHERE me.alias = '10.10.7.142' AND me.ip = '10.10.7.142'
SELECT me.ip, me.alias, me.subnet, me.port, me.dns, me.creation
  FROM device_ip me
WHERE alias = '10.10.7.142'
SELECT me.ip, me.creation, me.dns, me.description, me.uptime, me.contact,
me.name, me.location, me.layers, me.num_ports, me.mac, me.serial,
me.chassis_id, me.model, me.ps1_type, me.ps2_type, me.ps1_status,
me.ps2_status, me.fan, me.slots, me.vendor, me.os, me.os_ver, me.log,
me.snmp_ver, me.snmp_comm, me.snmp_class, me.snmp_engineid, me.vtp_domain,
me.last_discover, me.last_macsuck, me.last_arpnip, to_char( me.creation,
'-MM-DD HH24:MI' ), to_char( me.last_arpnip, '-MM-DD HH24:MI' ),
to_char( me.last_discover, '-MM-DD HH24:MI' ), to_char(
me.last_macsuck, '-MM-DD HH24:MI' ), extract( epoch
  FROM age( now(  ), me.creation ) ), extract( epoch
  FROM age( now(  ), me.last_arpnip ) ), extract( epoch
  FROM age( now(  ), me.last_discover ) ), extract( epoch
  FROM age( now(  ), me.last_macsuck ) ), replace( age( timestamp
'epoch' + me.uptime / 100 * interval '1 second', timestamp '1970-01-01
00:00:00-00' ) ::text, 'mon', 'month' )
  FROM device me
WHERE me.ip = '10.10.7.142'
[17616] 2022-01-03 18:27:52 debug is_discoverable: 10.10.7.142 matches
phone_platforms but discover_phones is not enabled
[17616] 2022-01-03 18:27:52 debug  [10.1.1.118] neigh - skip: 10.10.7.142
of type [regDN 1177,MINET_6920,ver: 01.05.03.027,PxE: 6.5,03/01/2022
13:27:23 +] excluded by discover_* config
UPDATE device_port
  SET is_uplink = true, manual_topo = false, remote_id = '10.10.7.142',
remote_ip = '10.10.7.142', remote_port = 'LAN port', remote_type = 'regDN
1177,MINET_6920,ver: 01.05.03.027,PxE: 6.5,03/01/2022 13:27:23 +'
WHERE ip = '10.1.1.118' AND port = 'GigabitEthernet1/0/13'
SELECT me.ip, me.port, me.creation, me.descr, me.up, me.up_admin, me.type,
me.duplex, me.duplex_admin, me.speed, me.speed_admin, me.name, me.mac,
me.mtu, me.stp, me.remote_ip, me.remote_port, me.remote_type, me.remote_id,
me.is_master, me.slave_of, me.manual_topo, me.is_uplink, me.vlan, me.pvid,
me.lastchange
  FROM device_port me
WHERE me.ip = '10.1.1.118' AND me.port = 'GigabitEthernet1/0/13'

Thanks in advance - Ricardo.

-- 
°(((=((===°°°(((
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 186, Issue 3

[netdisco-users-request]

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: Can we add custom tags? Trying to get phone extensions
  mapped (Christian Ramseyer)
--- Begin Message ---

Hi Ricardo

I don't think there is any support for custom extension fields 
currently. What you could do with existing stuff in Netdisco is a 
discover hook that takes the remote_type and tacks it onto an existing 
field like the interface description. This is of course not the pinnacle 
of the third normal form of database design, but it should be in reach 
of a couple lines of Perl/SQL :)


General hook documentation:
https://github.com/netdisco/netdisco/wiki/Hooks

I've already made a hook once that does some twiddling in device_port 
post-discovery, might be a starting point:

https://github.com/rc9000/netdisco_discover_hook


Cheers
Christian

On 03.01.22 19:49, Ricardo Stella wrote:


I've asked before back in March on how to get phone extensions via LLDP 
but it seems that you would need discover_phones enabled, and iour 
phones do not have SNMP enabled.


In any case, the information is getting pulled as part of the 
"remote_type" - Is there a way to map the contents (and ideally a 
substring) into a custom field that can be displayed and/or searched for?


Doing a discover -DIQ you can see remote_type includes the necessary 
information: "reqDN 1177" whereas 1177 is the phone's extension. If we 
can do this, we could map the model number of the phone as well 
"MINET_6920" whereas 6920 is the model.





--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 187, Issue 6

[netdisco-users-request]

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. App::NetdiscoX::Web::Plugin::Observium in  Docker
  (Massimo Del Sarto)
   2. Re: App::NetdiscoX::Web::Plugin::Observium in  Docker
  (Massimo Del Sarto)
--- Begin Message ---



I need to load App::NetdiscoX::Web::Plugin::Observium plugin in a Docker 
installation. 


I copyed the file Observium.pm in 
nd-site-local/lib/App/NetdiscoX/Web/Plugin/Observium.pm 
I commented out 
#use File::ShareDir 'dist_dir'; 
#register_template_path( 
# dist_dir( 'App-NetdiscoX-Web-Plugin-Observium' )); 


But I'm not shure where to put the files device_port_column.tt , observium.css, 
observium.js 
I think I have to put in nd-site-local/share but I don't know which is the righ 
path 


Can help me? 


 
Ing. Massimo Del Sarto .. 
Centro Tecnologie Informatiche, Telematiche ed Elaborazione Dati 
IRCCS Fondazione Stella Maris http://www.fsm.unipi.it 
Tel. +39 050 886 204 / 268 Fax. +39 050 886202 
 


--

Metti il tuo 5x1000 sotto una buona Stella
Destinalo per sostenere la ricerca della Fondazione Stella Maris
Istituto Scientifico per la Neuropsichiatria dell'Infanzia e dell'Adolescenza.
Non ti costera' nulla ed e' molto semplice.

Codice Fiscale Fondazione Stella Maris:   00126240506   < < < 

--
Avvertenze ai sensi del Regolamento Generale UE 679/2016 (Regolamento Privacy)
Il presente messaggio, corredato dei relativi allegati, potrebbe contenere
informazioni strettamente riservate o confidenziali ed e' riferito
esclusivamente al destinatario sopra indicato. Quest'ultimo e' l'unico
autorizzato ad usarlo, copiarlo e, sotto la propria responsabilita' a
diffonderlo. Chiunque ricevesse questo messaggio per errore o lo leggesse
senza esserne legittimato e' avvisato che trattenerlo, copiarlo,
divulgarlo, distribuirlo a persone diverse dal destinatario e' severamente
proibito ed e' pregato di rinviarlo immediatamente al mittente
distruggendo l'originale. Grazie.

This message, together with its annexes, may contain information strictly
confidential or privileged and is intended only for the addressee(s)
identified above, who only may use, copy and, under his/their
responsibility, further disseminate it. If you are not the intended
recipient or have read it without entitlement, please be aware that
keeping, copying, disseminating or distributing this message to persons
other than the addressee(s) is strictly forbidden and transmit it
immediately back to the sender, deleting the original message received.
Thank you. --- End Message ---
--- Begin Message ---
Update. 

I can fix my problem and now works fine. 

this is the correct strutcture: 

nd-site-local/ 
nd-site-local/lib 
nd-site-local/lib/App 
nd-site-local/lib/App/NetdiscoX 
nd-site-local/lib/App/NetdiscoX/Web 
nd-site-local/lib/App/NetdiscoX/Web/Plugin 
nd-site-local/lib/App/NetdiscoX/Web/Plugin/Observium.pm 
nd-site-local/share 
nd-site-local/share/views 
nd-site-local/share/views/plugin 
nd-site-local/share/views/plugin/observium 
nd-site-local/share/views/plugin/observium/device_port_column.tt 
nd-site-local/share/views/plugin/observium/observium.css 
nd-site-local/share/views/plugin/observium/observium.js 

remeber to change the owenership (sudo chown -R 901:901 nd-site-local) 

Massimo 
- Messaggio originale -

> Da: "Massimo Del Sarto" 
> A: netdisco-users@lists.sourceforge.net
> Inviato: Giovedì, 17 febbraio 2022 18:02:33
> Oggetto: App::NetdiscoX::Web::Plugin::Observium in Docker

> I need to load App::NetdiscoX::Web::Plugin::Observium plugin in a
> Docker installation.

> I copyed the file Observium.pm in
> nd-site-local/lib/App/NetdiscoX/Web/Plugin/Observium.pm
> I commented out
> #use File::ShareDir 'dist_dir';
> #register_template_path(
> # dist_dir( 'App-NetdiscoX-Web-Plugin-Observium' ));

> But I'm not shure where to put the files device_port_column.tt ,
> observium.css, observium.js
> I think I have to put in nd-site-local/share but I don't know which
> is the righ path

> Can help me?

> 
> Ing. Massimo Del Sarto ..
> Centro Tecnologie Informatiche, Telematiche ed Elaborazione Dati
> IRCCS Fondazione Stella Maris http://www.fsm.unipi.it
> Tel. +39 050 886 204 / 268 Fax. +39 050 886202
> 

--

netdisco-users Digest, Vol 187, Issue 7

[netdisco-users-request]

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. No results in API searching for a MAC address (Sebastien BEAUDLOT)
--- Begin Message ---
Hi, 

I am playing with Netdisco's API and it seems that it does not give me a 
response when asking /port searching for a specific MAC address. 

Eg : curl -k -s -X GET \ 
-H "Accept: application/json" \ 
-H "Authorization: " \ 
"https://localhost/api/v1/search/port?q=d8%3A9e%3Af3%3A3e%3A8a%3A01; 

Tried with and without escaping semicolons. Searching for a partial MAC 
address, eg : /port?q=d8* is working and giving results. 

Netdisco's is up to date 
App::Netdisco 2.52.1 
SNMP::Info 3.81 
DB Schema 70 
PostgreSQL 11.00.14 
Perl 5.20.2 

Bigger picture, in case i took it wrong : i want to get all ports for a room, 
as nodes hostnames contain the room name. So i do search/node?q=room24* to get 
all MACs for this room, then search/port?q=mac for each MAC to get the ports 
list. 

What am i doing wrong ? :-) 

Regards. 

--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 188, Issue 1

[netdisco-users-request]

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. Question on discover_waps (Roberto Martinez)
--- Begin Message ---
Hi,

I have a question related to the discover_waps feature. In our installation
we have set discover_waps=False as we do not want the APs to be discovered.
We also have set up the wap_platforms with a regex matching the waps (all
cisco AIR, so the default regex included as example works), and we have
checked that the regex matches the ap string (the wireless icon is shown on
the device).
However, we're seeing a Discover job started (but not finished) on all
these devices, job that stays in "queued" status. "netdisco-do dumpconfig"
also shows that the settings have been correctly taken into account
(discover_waps and wap_platforms), but "netdisco-do show -d  -e
c_platform" says "Don't know device: " (which I guess is ok because
after all, we told NetDisco not to discover them)

The question is: should NetDisco start these jobs and let them in queued
status, or should NetDisco NOT start these jobs as they are not supposed to
run?

Thanks
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 188, Issue 2

[netdisco-users-request]

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: Question on discover_waps (Oliver Gorwits)
   2. Netdisco db timezone on shared instance (Roberto Martinez)
--- Begin Message ---
Hi Roberto

Good question! OK so the "queued" status jobs are not started -- they are
just entries in the queue in the database.

Netdisco has a process to select the jobs to run, and the backend will
ignore entries in the queue which it is not permitted to run for any reason.

The subtlety here is that you can have multiple different backend daemons
with different config running. For example, it's possible some users want
some backends to discover the WAPs and others not.

So Netdisco is written to allow the jobs to be queued, they are quite
harmless to sit there (and they are removed after a while by the Expiry job
I think, but would be re-added of course).

Your single backend daemon with this config will ignore the jobs in, I
hope, a fairly efficient way (it should not keep trying to run them, they
are ignored).

Hope that helps!

regards,
oliver.

On Mon, 21 Mar 2022 at 09:33, Roberto Martinez  wrote:

> Hi,
>
> I have a question related to the discover_waps feature. In our
> installation we have set discover_waps=False as we do not want the APs to
> be discovered. We also have set up the wap_platforms with a regex matching
> the waps (all cisco AIR, so the default regex included as example works),
> and we have checked that the regex matches the ap string (the wireless icon
> is shown on the device).
> However, we're seeing a Discover job started (but not finished) on all
> these devices, job that stays in "queued" status. "netdisco-do dumpconfig"
> also shows that the settings have been correctly taken into account
> (discover_waps and wap_platforms), but "netdisco-do show -d  -e
> c_platform" says "Don't know device: " (which I guess is ok because
> after all, we told NetDisco not to discover them)
>
> The question is: should NetDisco start these jobs and let them in queued
> status, or should NetDisco NOT start these jobs as they are not supposed to
> run?
>
> Thanks
> ___
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
--- Begin Message ---
Hi,

We have setup a Netdisco installation using a shared postgresql instance.
We would like to set the timezone specifically for the Netdisco DB and not
all the databases of the instance, so it looks like the only way to do this
is to issue a "SET TIMEZONE='' upon the connection to the
database. AFAIK there's no setting in the deployment.yaml file to specify
"sql commands to run when netdisco connects", and the way to externally set
the timezone would be touching postgresql.conf and restart the instance,
which affects all the databases on the instance and not only that of
Netdisco.

Do you have any hints on how this could be done?

Thanks in advance
Roberto
--- End Message ---
___
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users

netdisco-users Digest, Vol 187, Issue 2

[netdisco-users-request]

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: Netdisco auto discovery tasks suddenly stopped working
  (alcatron)
--- Begin Message ---
Thanks, I did a autovacuum and I reduced the DB size back down, and saved 15gig.

How do you execute reindex concurrently correctly on the db?


From: Christian Ramseyer 
Date: Monday, 31 January 2022 at 11:44 pm
To: alcatron , netdisco-users@lists.sourceforge.net 
, Jethro Binks 
Subject: Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped working
For us, the autovacuum works fine, so I never do vacuum full. But you
can do it if you're totally out of space and need to reclaim some from
Postgres.

The only thing that needs additional intervention is the indexes, we do
a REINDEX CONCURRENTLY once a week, as described here:
https://www.postgresql.org/docs/current/routine-reindex.html

Apparently this "index bloat" should be less of an issue in Postgres 14
but I haven't gotten around to try it yet.



On 31.01.22 13:38, alcatron wrote:
> Thanks, would I ever have to do a “vacuum full” to the db by any chance
> or should it be automatic process?
>
> Auto Vacuum is set to on
>
> *From: *Christian Ramseyer 
> *Date: *Monday, 31 January 2022 at 10:34 pm
> *To: *alcatron ,
> netdisco-users@lists.sourceforge.net
> , Jethro Binks
> 
> *Subject: *Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped
> working
>
>
>
> On 31.01.22 12:56, alcatron wrote:
>> Thanks Christian, those commands you mentioned is that just at the psql
>> command line?
>>
>
> Yes exactly. You can start the command line interface with "netdisco-do
> psql".
>
>
>> For some reason ever since I cleaned this device_skip table the netdisco
>> postgresql folder has grown dramatically in size by an extra 15gig
>> within 2 weeks.
>>
>> I see this directory taking up the space -
>> /var/lib/pgsql/12/data/base/16386 and lot of other files in there.
>>
>> I had a look at the netdisco tables and I cant see any table that big in
>> size, so im not really sure why the psql has dramatically keeps
>> increasing in disk size ?
>
>
> You should see what uses the space with the first query from here:
> https://wiki.postgresql.org/wiki/Disk_Usage
> 
>
> This will include indexes and TOAST tables, the space is probably used
> there instead of the actual table object.
>
> Cheers
> Christian
>
>
>
>
>>
>> Schema |Name| Type  |  Owner   |Size|
>> Description
>>
>> ++---+--++-
>>
>> public | admin  | table | netdisco | 173 MB |
>>
>>   public | community  | table | netdisco | 224 kB |
>>
>>   public | dbix_class_schema_versions | table | netdisco | 40 kB  |
>>
>>   public | device | table | netdisco | 3312 kB|
>>
>>   public | device_ip  | table | netdisco | 34 MB  |
>>
>>   public | device_module  | table | netdisco | 895 MB |
>>
>>   public | device_port| table | netdisco | 1656 MB|
>>
>>   public | device_port_log| table | netdisco | 48 kB  |
>>
>>   public | device_port_power  | table | netdisco | 124 MB |
>>
>>   public | device_port_properties | table | netdisco | 354 MB |
>>
>>   public | device_port_ssid   | table | netdisco | 17 MB  |
>>
>>   public | device_port_vlan   | table | netdisco | 1084 MB|
>>
>>   public | device_port_wireless   | table | netdisco | 6776 kB|
>>
>>   public | device_power   | table | netdisco | 1760 kB|
>>
>>   public | device_skip| table | netdisco | 5544 kB|
>>
>>   public | device_vlan| table | netdisco | 67 MB  |
>>
>>   public | log| table | netdisco | 8192 bytes |
>>
>>   public | netmap_positions   | table | netdisco | 288 kB |
>>
>>   public | node   | table | netdisco | 317 MB |
>>
>>   public | node_ip| table | netdisco | 2084 MB|
>>
>>   public | node_monitor   | table | netdisco | 8192 bytes |
>>
>>   public | node_nbt   | table | netdisco | 4328 kB|
>>
>>   public | node_wireless  | table | netdisco | 16 MB  |
>>
>>   public | oui| table | netdisco | 2160 kB|
>>
>>   public | process   

netdisco-users Digest, Vol 186, Issue 9

[netdisco-users-request]

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: NXOS CLI collection (Johnson, Neil M)
--- Begin Message ---
Here is the out put of the CLI commands executed by netdisco:

rtr-core-lc# show ip arp vrf all | inc :
Flags: * - Adjacencies learnt on non-active FHRP router
Total number of entries: 29105
172.17.64.1000:06:16  001a.1e04.2240  Vlan1221
172.17.64.1100:06:16  001a.1e04.2148  Vlan1221
172.17.64.1200:06:16  001a.1e04.83c8  Vlan1221
172.17.64.1300:06:16  001a.1e04.84f0  Vlan1221
172.17.64.1400:06:16  001a.1e04.8720  Vlan1221
172.17.64.1500:06:16  001a.1e04.3928  Vlan1221
172.17.64.1600:06:16  001a.1e04.85c0  Vlan1221
172.17.64.1700:06:16  001a.1e04.84d8  Vlan1221
172.17.64.1800:06:16  001a.1e04.8338  Vlan1221
172.17.64.1900:06:16  001a.1e04.8598  Vlan1221
.
.
.
128.255.211.66  00:00:10  INCOMPLETE  port-channel450.133
128.255.211.68  00:00:10  INCOMPLETE  port-channel450.133
128.255.211.70  00:00:24  INCOMPLETE  port-channel450.133
128.255.211.76  00:00:12  INCOMPLETE  port-channel450.133
128.255.211.77  00:00:13  INCOMPLETE  port-channel450.133
128.255.211.80  00:00:09  INCOMPLETE  port-channel450.133
128.255.211.82  00:00:19  INCOMPLETE  port-channel450.133
128.255.211.83  00:00:02  INCOMPLETE  port-channel450.133
128.255.211.84  00:00:17  INCOMPLETE  port-channel450.133
128.255.211.85  00:00:02  INCOMPLETE  port-channel450.133
128.255.211.86  00:00:03  INCOMPLETE  port-channel450.133
128.255.211.88  00:00:16  INCOMPLETE  port-channel450.133
128.255.211.91  00:00:13  INCOMPLETE  port-channel450.133
128.255.211.92  00:00:09  INCOMPLETE  port-channel450.133
128.255.211.94  00:00:25  INCOMPLETE  port-channel450.133
128.255.190.2   00:08:09  a24e.2000.000c  port-channel450.142
128.255.190.4   00:00:21  INCOMPLETE  port-channel450.142
rtr-core-lc#

rtr-core-lc# show ipv6 neighbor vrf all | exclude Flags:

   G - Adjacencies of vPC peer with G/W bit
   R - Adjacencies learnt remotely

IPv6 Adjacency Table for all VRFs
Total number of entries: 75215
Address Age   MAC Address Pref Source Interface
2620:0:e50:1401::2
   44w0d  001a.1e04.2240  50   icmpv6 Vlan1221
2620:0:e50:1401::3
,
,
,

rtr-core-lc#

--
Neil Johnson - University of Iowa

From: Johnson, Neil M
Sent: Friday, January 28, 2022 11:03 AM
To: netdisco-users@lists.sourceforge.net
Subject: NXOS CLI collection


How do I force netdisco to use CLI collection for a device:

It seems to allows us SNMP.

This is what I have for a config:

test_routers:
# rtr-core-lc
- 192.168.204.68
.
.
.
device_auth:
.
.
.
  - tag: 'NXOS CLI'
driver: 'cli'
platform: 'NXOS'
only: 'group:test_routers'
username: 'netdisco'
password: 'SECRET'
ssh_master_opts:
  - "-o"
  - "StrictHostKeyChecking=no"
.
.
.

I've verified that I can SSH into the router with the credentials.

Here is the output from the command line:

netdisco@netdisco:~$ ~/bin/netdisco-do arpnip -d 192.168.204.68 -DIS
[1482194] 2022-01-28 16:55:12  info App::Netdisco version 2.052000 loaded.
[1482194] 2022-01-28 16:55:12  info arpnip: [192.168.204.68] started at Fri Jan 
28 16:55:12 2022
[1482194] 2022-01-28 16:55:12 debug => running workers for phase: check
[1482194] 2022-01-28 16:55:12 debug -> run worker check/_base_/0
[1482194] 2022-01-28 16:55:12 debug arpnip is able to run
[1482194] 2022-01-28 16:55:12 debug => running workers for phase: main
[1482194] 2022-01-28 16:55:12 debug -> run worker main/nodes/200
[1482194] 2022-01-28 16:55:12 debug cli session cache warm: [192.168.204.68]
[1482194] 2022-01-28 16:55:16 debug 192.168.204.68 1482194 arpnip()
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:14] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:dc] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:dd] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:de] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:df] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:e0] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:e1] - skipping
[1482194] 

netdisco-users Digest, Vol 186, Issue 10

[netdisco-users-request]

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. NXOS CLI collection (Johnson, Neil M)
--- Begin Message ---

How do I force netdisco to use CLI collection for a device:

It seems to allows us SNMP.

This is what I have for a config:

test_routers:
# rtr-core-lc
- 192.168.204.68
.
.
.
device_auth:
.
.
.
  - tag: 'NXOS CLI'
driver: 'cli'
platform: 'NXOS'
only: 'group:test_routers'
username: 'netdisco'
password: 'SECRET'
ssh_master_opts:
  - "-o"
  - "StrictHostKeyChecking=no"
.
.
.

I've verified that I can SSH into the router with the credentials.

Here is the output from the command line:

netdisco@netdisco:~$ ~/bin/netdisco-do arpnip -d 192.168.204.68 -DIS
[1482194] 2022-01-28 16:55:12  info App::Netdisco version 2.052000 loaded.
[1482194] 2022-01-28 16:55:12  info arpnip: [192.168.204.68] started at Fri Jan 
28 16:55:12 2022
[1482194] 2022-01-28 16:55:12 debug => running workers for phase: check
[1482194] 2022-01-28 16:55:12 debug -> run worker check/_base_/0
[1482194] 2022-01-28 16:55:12 debug arpnip is able to run
[1482194] 2022-01-28 16:55:12 debug => running workers for phase: main
[1482194] 2022-01-28 16:55:12 debug -> run worker main/nodes/200
[1482194] 2022-01-28 16:55:12 debug cli session cache warm: [192.168.204.68]
[1482194] 2022-01-28 16:55:16 debug 192.168.204.68 1482194 arpnip()
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:14] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:dc] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:dd] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:de] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:df] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:e0] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:e1] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:0a] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:0f] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:dc] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:dd] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:de] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:df] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:e0] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:e1] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:0a] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:14] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:0a] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:89] - skipping
[1482194] 2022-01-28 16:55:23 debug  [192.168.204.68] check_mac - VRRP mac 
[00:00:5e:00:01:89] - skipping
[1482194] 2022-01-28 16:55:24 debug  resolving 99110 ARP entries with max 50 
outstanding requests
[1482194] 2022-01-28 16:56:05 debug -> Can't call method "bits" on an undefined 
value at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Arpnip/Nodes.pm line 
97.
[1482194] 2022-01-28 16:56:05 debug Can't call method "bits" on an undefined 
value at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Arpnip/Nodes.pm line 
97.
[1482194] 2022-01-28 16:56:05 debug -> run worker main/nodes/100
[1482194] 2022-01-28 16:56:05 debug snmp reader cache warm: [192.168.204.68]
[1482194] 2022-01-28 16:56:05 debug [192.168.204.68:161] try_connect with ver: 
2, class: SNMP::Info::Layer3::Nexus, comm: 
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/3com
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/adtran
snmp_add_mib_dir: Added mib dir /home/netdisco/netdisco-mibs/aerohive
snmp_add_mib_dir: Added mib dir 

netdisco-users Digest, Vol 187, Issue 1

[netdisco-users-request]

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: Netdisco auto discovery tasks suddenly stopped working
  (Christian Ramseyer)
--- Begin Message ---
For us, the autovacuum works fine, so I never do vacuum full. But you 
can do it if you're totally out of space and need to reclaim some from 
Postgres.


The only thing that needs additional intervention is the indexes, we do 
a REINDEX CONCURRENTLY once a week, as described here: 
https://www.postgresql.org/docs/current/routine-reindex.html


Apparently this "index bloat" should be less of an issue in Postgres 14 
but I haven't gotten around to try it yet.




On 31.01.22 13:38, alcatron wrote:
Thanks, would I ever have to do a “vacuum full” to the db by any chance 
or should it be automatic process?


Auto Vacuum is set to on

*From: *Christian Ramseyer 
*Date: *Monday, 31 January 2022 at 10:34 pm
*To: *alcatron , 
netdisco-users@lists.sourceforge.net 
, Jethro Binks 

*Subject: *Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped 
working




On 31.01.22 12:56, alcatron wrote:
Thanks Christian, those commands you mentioned is that just at the psql 
command line?




Yes exactly. You can start the command line interface with "netdisco-do
psql".


For some reason ever since I cleaned this device_skip table the netdisco 
postgresql folder has grown dramatically in size by an extra 15gig 
within 2 weeks.


I see this directory taking up the space - 
/var/lib/pgsql/12/data/base/16386 and lot of other files in there.


I had a look at the netdisco tables and I cant see any table that big in 
size, so im not really sure why the psql has dramatically keeps 
increasing in disk size ?



You should see what uses the space with the first query from here:
https://wiki.postgresql.org/wiki/Disk_Usage 



This will include indexes and TOAST tables, the space is probably used
there instead of the actual table object.

Cheers
Christian






Schema |    Name    | Type  |  Owner   |    Size    | 
Description


++---+--++-

public | admin  | table | netdisco | 173 MB |

   public | community  | table | netdisco | 224 kB |

   public | dbix_class_schema_versions | table | netdisco | 40 kB  |

   public | device | table | netdisco | 3312 kB    |

   public | device_ip  | table | netdisco | 34 MB  |

   public | device_module  | table | netdisco | 895 MB     |

   public | device_port    | table | netdisco | 1656 MB    |

   public | device_port_log    | table | netdisco | 48 kB  |

   public | device_port_power  | table | netdisco | 124 MB |

   public | device_port_properties     | table | netdisco | 354 MB |

   public | device_port_ssid   | table | netdisco | 17 MB  |

   public | device_port_vlan   | table | netdisco | 1084 MB    |

   public | device_port_wireless   | table | netdisco | 6776 kB    |

   public | device_power   | table | netdisco | 1760 kB    |

   public | device_skip    | table | netdisco | 5544 kB    |

   public | device_vlan    | table | netdisco | 67 MB  |

   public | log    | table | netdisco | 8192 bytes |

   public | netmap_positions   | table | netdisco | 288 kB |

   public | node   | table | netdisco | 317 MB |

   public | node_ip    | table | netdisco | 2084 MB    |

   public | node_monitor   | table | netdisco | 8192 bytes |

   public | node_nbt   | table | netdisco | 4328 kB    |

   public | node_wireless  | table | netdisco | 16 MB  |

   public | oui    | table | netdisco | 2160 kB    |

   public | process    | table | netdisco | 8192 bytes |

   public | sessions   | table | netdisco | 48 kB  |

   public | statistics | table | netdisco | 200 kB |

   public | subnets    | table | netdisco | 1296 kB    |

   public | topology   | table | netdisco | 48 kB  |

   public | user_log   | table | netdisco | 600 kB |

   public | users  | table | netdisco | 48 kB  |

*From: *Christian Ramseyer 
*Date: 

netdisco-users Digest, Vol 186, Issue 11

[netdisco-users-request]

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: Netdisco auto discovery tasks suddenly stopped working
  (alcatron)
--- Begin Message ---
Thanks Christian, those commands you mentioned is that just at the psql command 
line?

For some reason ever since I cleaned this device_skip table the netdisco 
postgresql folder has grown dramatically in size by an extra 15gig within 2 
weeks.

I see this directory taking up the space - /var/lib/pgsql/12/data/base/16386 
and lot of other files in there.

I had a look at the netdisco tables and I cant see any table that big in size, 
so im not really sure why the psql has dramatically keeps increasing in disk 
size ?

Schema |Name| Type  |  Owner   |Size| 
Description
++---+--++-
public | admin  | table | netdisco | 173 MB |
 public | community  | table | netdisco | 224 kB |
 public | dbix_class_schema_versions | table | netdisco | 40 kB  |
 public | device | table | netdisco | 3312 kB|
 public | device_ip  | table | netdisco | 34 MB  |
 public | device_module  | table | netdisco | 895 MB |
 public | device_port| table | netdisco | 1656 MB|
 public | device_port_log| table | netdisco | 48 kB  |
 public | device_port_power  | table | netdisco | 124 MB |
 public | device_port_properties | table | netdisco | 354 MB |
 public | device_port_ssid   | table | netdisco | 17 MB  |
 public | device_port_vlan   | table | netdisco | 1084 MB|
 public | device_port_wireless   | table | netdisco | 6776 kB|
 public | device_power   | table | netdisco | 1760 kB|
 public | device_skip| table | netdisco | 5544 kB|
 public | device_vlan| table | netdisco | 67 MB  |
 public | log| table | netdisco | 8192 bytes |
 public | netmap_positions   | table | netdisco | 288 kB |
 public | node   | table | netdisco | 317 MB |
 public | node_ip| table | netdisco | 2084 MB|
 public | node_monitor   | table | netdisco | 8192 bytes |
 public | node_nbt   | table | netdisco | 4328 kB|
 public | node_wireless  | table | netdisco | 16 MB  |
 public | oui| table | netdisco | 2160 kB|
 public | process| table | netdisco | 8192 bytes |
 public | sessions   | table | netdisco | 48 kB  |
 public | statistics | table | netdisco | 200 kB |
 public | subnets| table | netdisco | 1296 kB|
 public | topology   | table | netdisco | 48 kB  |
 public | user_log   | table | netdisco | 600 kB |
 public | users  | table | netdisco | 48 kB  |

From: Christian Ramseyer 
Date: Thursday, 20 January 2022 at 12:45 am
To: alcatron , netdisco-users@lists.sourceforge.net 
, Jethro Binks 
Subject: Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped working


On 19.01.22 14:00, alcatron wrote:
> As for picking up on the error, I saw this in the netdisco-backend log.
> I believe the device_skip table was getting so big it was running out of
> memory processing it, the device skip table was like 162MB
>
> Im sure this will happen again in the next 2-3 months when the
> device_skip table builds up. Perhaps its some kind of bug it can only
> handle a device_skip table of a certain size?

It's weird how it would get that big, as IIRC it keeps only one record
per device in your DB at most. Is this including indexes? They might
become quite big, since Postgres can create some "bloat" under our
insert/delete pattern.

device_skip is just used to not poll unreachable devices over and over
again, there is no important data in there. So if in doubt,

delete from device_skip;
vacuum analyze device_skip;
reindex table device skip;

should allow for a fresh start.

There are also the max_deferrals and retry_after options to control the
skip behaviour. I don't think it will affect the table size much though.
https://github.com/netdisco/netdisco/wiki/Configuration#workers

If you're getting these issues regularly I'd definitely experiment with
the Postgres memory 

netdisco-users Digest, Vol 186, Issue 12

[netdisco-users-request]

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: Netdisco auto discovery tasks suddenly stopped working
  (Christian Ramseyer)
--- Begin Message ---



On 31.01.22 12:56, alcatron wrote:
Thanks Christian, those commands you mentioned is that just at the psql 
command line?




Yes exactly. You can start the command line interface with "netdisco-do 
psql".



For some reason ever since I cleaned this device_skip table the netdisco 
postgresql folder has grown dramatically in size by an extra 15gig 
within 2 weeks.


I see this directory taking up the space - 
/var/lib/pgsql/12/data/base/16386 and lot of other files in there.


I had a look at the netdisco tables and I cant see any table that big in 
size, so im not really sure why the psql has dramatically keeps 
increasing in disk size ?



You should see what uses the space with the first query from here:
https://wiki.postgresql.org/wiki/Disk_Usage

This will include indexes and TOAST tables, the space is probably used 
there instead of the actual table object.


Cheers
Christian






Schema |    Name    | Type  |  Owner   |    Size    | 
Description


++---+--++-

public | admin  | table | netdisco | 173 MB |

  public | community  | table | netdisco | 224 kB |

  public | dbix_class_schema_versions | table | netdisco | 40 kB  |

  public | device | table | netdisco | 3312 kB    |

  public | device_ip  | table | netdisco | 34 MB  |

  public | device_module  | table | netdisco | 895 MB     |

  public | device_port    | table | netdisco | 1656 MB    |

  public | device_port_log    | table | netdisco | 48 kB  |

  public | device_port_power  | table | netdisco | 124 MB |

  public | device_port_properties     | table | netdisco | 354 MB |

  public | device_port_ssid   | table | netdisco | 17 MB  |

  public | device_port_vlan   | table | netdisco | 1084 MB    |

  public | device_port_wireless   | table | netdisco | 6776 kB    |

  public | device_power   | table | netdisco | 1760 kB    |

  public | device_skip    | table | netdisco | 5544 kB    |

  public | device_vlan    | table | netdisco | 67 MB  |

  public | log    | table | netdisco | 8192 bytes |

  public | netmap_positions   | table | netdisco | 288 kB |

  public | node   | table | netdisco | 317 MB |

  public | node_ip    | table | netdisco | 2084 MB    |

  public | node_monitor   | table | netdisco | 8192 bytes |

  public | node_nbt   | table | netdisco | 4328 kB    |

  public | node_wireless  | table | netdisco | 16 MB  |

  public | oui    | table | netdisco | 2160 kB    |

  public | process    | table | netdisco | 8192 bytes |

  public | sessions   | table | netdisco | 48 kB  |

  public | statistics | table | netdisco | 200 kB |

  public | subnets    | table | netdisco | 1296 kB    |

  public | topology   | table | netdisco | 48 kB  |

  public | user_log   | table | netdisco | 600 kB |

  public | users  | table | netdisco | 48 kB  |

*From: *Christian Ramseyer 
*Date: *Thursday, 20 January 2022 at 12:45 am
*To: *alcatron , 
netdisco-users@lists.sourceforge.net 
, Jethro Binks 

*Subject: *Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped 
working




On 19.01.22 14:00, alcatron wrote:
As for picking up on the error, I saw this in the netdisco-backend log. 
I believe the device_skip table was getting so big it was running out of 
memory processing it, the device skip table was like 162MB


Im sure this will happen again in the next 2-3 months when the 
device_skip table builds up. Perhaps its some kind of bug it can only 
handle a device_skip table of a certain size?


It's weird how it would get that big, as IIRC it keeps only one record
per device in your DB at most. Is this including indexes? They might
become quite big, since Postgres can create some "bloat" under our
insert/delete pattern.

device_skip is just used to not poll unreachable devices over and over
again, there is no 

netdisco-users Digest, Vol 186, Issue 13

[netdisco-users-request]

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: Netdisco auto discovery tasks suddenly stopped working
  (alcatron)
--- Begin Message ---
Thanks, would I ever have to do a “vacuum full” to the db by any chance or 
should it be automatic process?

Auto Vacuum is set to on

From: Christian Ramseyer 
Date: Monday, 31 January 2022 at 10:34 pm
To: alcatron , netdisco-users@lists.sourceforge.net 
, Jethro Binks 
Subject: Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped working


On 31.01.22 12:56, alcatron wrote:
> Thanks Christian, those commands you mentioned is that just at the psql
> command line?
>

Yes exactly. You can start the command line interface with "netdisco-do
psql".


> For some reason ever since I cleaned this device_skip table the netdisco
> postgresql folder has grown dramatically in size by an extra 15gig
> within 2 weeks.
>
> I see this directory taking up the space -
> /var/lib/pgsql/12/data/base/16386 and lot of other files in there.
>
> I had a look at the netdisco tables and I cant see any table that big in
> size, so im not really sure why the psql has dramatically keeps
> increasing in disk size ?


You should see what uses the space with the first query from here:
https://wiki.postgresql.org/wiki/Disk_Usage

This will include indexes and TOAST tables, the space is probably used
there instead of the actual table object.

Cheers
Christian




>
> Schema |Name| Type  |  Owner   |Size|
> Description
>
> ++---+--++-
>
> public | admin  | table | netdisco | 173 MB |
>
>   public | community  | table | netdisco | 224 kB |
>
>   public | dbix_class_schema_versions | table | netdisco | 40 kB  |
>
>   public | device | table | netdisco | 3312 kB|
>
>   public | device_ip  | table | netdisco | 34 MB  |
>
>   public | device_module  | table | netdisco | 895 MB |
>
>   public | device_port| table | netdisco | 1656 MB|
>
>   public | device_port_log| table | netdisco | 48 kB  |
>
>   public | device_port_power  | table | netdisco | 124 MB |
>
>   public | device_port_properties | table | netdisco | 354 MB |
>
>   public | device_port_ssid   | table | netdisco | 17 MB  |
>
>   public | device_port_vlan   | table | netdisco | 1084 MB|
>
>   public | device_port_wireless   | table | netdisco | 6776 kB|
>
>   public | device_power   | table | netdisco | 1760 kB|
>
>   public | device_skip| table | netdisco | 5544 kB|
>
>   public | device_vlan| table | netdisco | 67 MB  |
>
>   public | log| table | netdisco | 8192 bytes |
>
>   public | netmap_positions   | table | netdisco | 288 kB |
>
>   public | node   | table | netdisco | 317 MB |
>
>   public | node_ip| table | netdisco | 2084 MB|
>
>   public | node_monitor   | table | netdisco | 8192 bytes |
>
>   public | node_nbt   | table | netdisco | 4328 kB|
>
>   public | node_wireless  | table | netdisco | 16 MB  |
>
>   public | oui| table | netdisco | 2160 kB|
>
>   public | process| table | netdisco | 8192 bytes |
>
>   public | sessions   | table | netdisco | 48 kB  |
>
>   public | statistics | table | netdisco | 200 kB |
>
>   public | subnets| table | netdisco | 1296 kB|
>
>   public | topology   | table | netdisco | 48 kB  |
>
>   public | user_log   | table | netdisco | 600 kB |
>
>   public | users  | table | netdisco | 48 kB  |
>
> *From: *Christian Ramseyer 
> *Date: *Thursday, 20 January 2022 at 12:45 am
> *To: *alcatron ,
> netdisco-users@lists.sourceforge.net
> , Jethro Binks
> 
> *Subject: *Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped
> working
>
>
>
> On 19.01.22 14:00, alcatron wrote:
>> As for picking up on the error, I saw this in the netdisco-backend log.
>> I believe the device_skip table was getting so big it was running out of
>> memory processing it, the device skip table was like 162MB
>>
>> Im sure this will happen again in 

netdisco-users Digest, Vol 187, Issue 5

[netdisco-users-request]

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: Netdisco auto discovery tasks suddenly stopped working (Muris)
--- Begin Message ---
Excellent, thanks for that, the wiki is a good write up

 

From: Christian Ramseyer 
Date: Thursday, 10 February 2022 at 18:13
To: Muris , "netdisco-users@lists.sourceforge.net" 
, Jethro Binks 
Subject: Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped working

 

In the meantime, we've made a wiki paragraph describing it:

https://github.com/netdisco/netdisco/wiki/Database-Tips#unreasonable-database-size-index-bloat

in short, either

reindex table concurrently $tablename;

or

reindex database concurrently netdisco;

to do the whole db at once.

Cheers
Christian

On 10.02.22 03:16, Muris wrote:

I meant to say in my previous email I did a Vacuum Full, which fixed the issue 
with size and dB and everything is back to being responsive. 

 

Christian, can you tell me how to perform the Reindex Concurrently? What 
command do you exactly issue?

 

I tried to execute but not sure if im doing It right.

 

Cheers

 

From: alcatron 
Date: Wednesday, 2 February 2022 at 19:51
To: Christian Ramseyer , 
"netdisco-users@lists.sourceforge.net" , 
Jethro Binks 
Subject: Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped working

 

Thanks, I did a autovacuum and I reduced the DB size back down, and saved 15gig.

 

How do you execute reindex concurrently correctly on the db?

 

 

From: Christian Ramseyer 
Date: Monday, 31 January 2022 at 11:44 pm
To: alcatron , netdisco-users@lists.sourceforge.net 
, Jethro Binks 
Subject: Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped working

For us, the autovacuum works fine, so I never do vacuum full. But you 
can do it if you're totally out of space and need to reclaim some from 
Postgres.

The only thing that needs additional intervention is the indexes, we do 
a REINDEX CONCURRENTLY once a week, as described here: 
https://www.postgresql.org/docs/current/routine-reindex.html

Apparently this "index bloat" should be less of an issue in Postgres 14 
but I haven't gotten around to try it yet.



On 31.01.22 13:38, alcatron wrote:
> Thanks, would I ever have to do a “vacuum full” to the db by any chance 
> or should it be automatic process?
> 
> Auto Vacuum is set to on
> 
> *From: *Christian Ramseyer 
> *Date: *Monday, 31 January 2022 at 10:34 pm
> *To: *alcatron , 
> netdisco-users@lists.sourceforge.net 
> , Jethro Binks 
> 
> *Subject: *Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped 
> working
> 
> 
> 
> On 31.01.22 12:56, alcatron wrote:
>> Thanks Christian, those commands you mentioned is that just at the psql 
>> command line?
>> 
> 
> Yes exactly. You can start the command line interface with "netdisco-do
> psql".
> 
> 
>> For some reason ever since I cleaned this device_skip table the netdisco 
>> postgresql folder has grown dramatically in size by an extra 15gig 
>> within 2 weeks.
>> 
>> I see this directory taking up the space - 
>> /var/lib/pgsql/12/data/base/16386 and lot of other files in there.
>> 
>> I had a look at the netdisco tables and I cant see any table that big in 
>> size, so im not really sure why the psql has dramatically keeps 
>> increasing in disk size ?
> 
> 
> You should see what uses the space with the first query from here:
> https://wiki.postgresql.org/wiki/Disk_Usage 
> 
> 
> This will include indexes and TOAST tables, the space is probably used
> there instead of the actual table object.
> 
> Cheers
> Christian
> 
> 
> 
> 
>> 
>> Schema |Name| Type  |  Owner   |Size| 
>> Description
>> 
>> ++---+--++-
>> 
>> public | admin  | table | netdisco | 173 MB |
>> 
>>   public | community  | table | netdisco | 224 kB |
>> 
>>   public | dbix_class_schema_versions | table | netdisco | 40 kB  |
>> 
>>   public | device | table | netdisco | 3312 kB|
>> 
>>   public | device_ip  | table | netdisco | 34 MB  |
>> 
>>   public | device_module  | table | netdisco | 895 MB |
>> 
>>   public | device_port| table | netdisco | 1656 MB|
>> 
>>   public | device_port_log| table | netdisco | 48 kB  |
>> 
>>   public | device_port_power  | table | netdisco | 124 MB   

netdisco-users Digest, Vol 187, Issue 3

[netdisco-users-request]

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: Netdisco auto discovery tasks suddenly stopped working (Muris)
--- Begin Message ---
I meant to say in my previous email I did a Vacuum Full, which fixed the issue 
with size and dB and everything is back to being responsive. 

 

Christian, can you tell me how to perform the Reindex Concurrently? What 
command do you exactly issue?

 

I tried to execute but not sure if im doing It right.

 

Cheers

 

From: alcatron 
Date: Wednesday, 2 February 2022 at 19:51
To: Christian Ramseyer , 
"netdisco-users@lists.sourceforge.net" , 
Jethro Binks 
Subject: Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped working

 

Thanks, I did a autovacuum and I reduced the DB size back down, and saved 15gig.

 

How do you execute reindex concurrently correctly on the db?

 

 

From: Christian Ramseyer 
Date: Monday, 31 January 2022 at 11:44 pm
To: alcatron , netdisco-users@lists.sourceforge.net 
, Jethro Binks 
Subject: Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped working

For us, the autovacuum works fine, so I never do vacuum full. But you 
can do it if you're totally out of space and need to reclaim some from 
Postgres.

The only thing that needs additional intervention is the indexes, we do 
a REINDEX CONCURRENTLY once a week, as described here: 
https://www.postgresql.org/docs/current/routine-reindex.html

Apparently this "index bloat" should be less of an issue in Postgres 14 
but I haven't gotten around to try it yet.



On 31.01.22 13:38, alcatron wrote:
> Thanks, would I ever have to do a “vacuum full” to the db by any chance 
> or should it be automatic process?
> 
> Auto Vacuum is set to on
> 
> *From: *Christian Ramseyer 
> *Date: *Monday, 31 January 2022 at 10:34 pm
> *To: *alcatron , 
> netdisco-users@lists.sourceforge.net 
> , Jethro Binks 
> 
> *Subject: *Re: [Netdisco] Netdisco auto discovery tasks suddenly stopped 
> working
> 
> 
> 
> On 31.01.22 12:56, alcatron wrote:
>> Thanks Christian, those commands you mentioned is that just at the psql 
>> command line?
>> 
> 
> Yes exactly. You can start the command line interface with "netdisco-do
> psql".
> 
> 
>> For some reason ever since I cleaned this device_skip table the netdisco 
>> postgresql folder has grown dramatically in size by an extra 15gig 
>> within 2 weeks.
>> 
>> I see this directory taking up the space - 
>> /var/lib/pgsql/12/data/base/16386 and lot of other files in there.
>> 
>> I had a look at the netdisco tables and I cant see any table that big in 
>> size, so im not really sure why the psql has dramatically keeps 
>> increasing in disk size ?
> 
> 
> You should see what uses the space with the first query from here:
> https://wiki.postgresql.org/wiki/Disk_Usage 
> 
> 
> This will include indexes and TOAST tables, the space is probably used
> there instead of the actual table object.
> 
> Cheers
> Christian
> 
> 
> 
> 
>> 
>> Schema |Name| Type  |  Owner   |Size| 
>> Description
>> 
>> ++---+--++-
>> 
>> public | admin  | table | netdisco | 173 MB |
>> 
>>   public | community  | table | netdisco | 224 kB |
>> 
>>   public | dbix_class_schema_versions | table | netdisco | 40 kB  |
>> 
>>   public | device | table | netdisco | 3312 kB|
>> 
>>   public | device_ip  | table | netdisco | 34 MB  |
>> 
>>   public | device_module  | table | netdisco | 895 MB |
>> 
>>   public | device_port| table | netdisco | 1656 MB|
>> 
>>   public | device_port_log| table | netdisco | 48 kB  |
>> 
>>   public | device_port_power  | table | netdisco | 124 MB |
>> 
>>   public | device_port_properties | table | netdisco | 354 MB |
>> 
>>   public | device_port_ssid   | table | netdisco | 17 MB  |
>> 
>>   public | device_port_vlan   | table | netdisco | 1084 MB|
>> 
>>   public | device_port_wireless   | table | netdisco | 6776 kB|
>> 
>>   public | device_power   | table | netdisco | 1760 kB|
>> 
>>   public | device_skip| table | netdisco | 5544 kB|
>> 
>>   public | device_vlan| table | netdisco | 67 MB  |
>> 
>>   public | log| table | 

netdisco-users Digest, Vol 187, Issue 4

[netdisco-users-request]

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: Netdisco auto discovery tasks suddenly stopped working
  (Christian Ramseyer)
--- Begin Message ---

||In the meantime, we've made a wiki paragraph describing it:

https://github.com/netdisco/netdisco/wiki/Database-Tips#unreasonable-database-size-index-bloat

in short, either

reindex table concurrently $tablename;

or

reindex database concurrently netdisco;

to do the whole db at once.

Cheers
Christian

||
On 10.02.22 03:16, Muris wrote:


I meant to say in my previous email I did a Vacuum Full, which fixed 
the issue with size and dB and everything is back to being responsive.


Christian, can you tell me how to perform the Reindex Concurrently? 
What command do you exactly issue?


I tried to execute but not sure if im doing It right.

Cheers

*From: *alcatron 
*Date: *Wednesday, 2 February 2022 at 19:51
*To: *Christian Ramseyer , 
"netdisco-users@lists.sourceforge.net" 
, Jethro Binks 

*Subject: *Re: [Netdisco] Netdisco auto discovery tasks suddenly 
stopped working


Thanks, I did a autovacuum and I reduced the DB size back down, and 
saved 15gig.


How do you execute reindex concurrently correctly on the db?

*From: *Christian Ramseyer 
*Date: *Monday, 31 January 2022 at 11:44 pm
*To: *alcatron , 
netdisco-users@lists.sourceforge.net 
, Jethro Binks 

*Subject: *Re: [Netdisco] Netdisco auto discovery tasks suddenly 
stopped working


For us, the autovacuum works fine, so I never do vacuum full. But you
can do it if you're totally out of space and need to reclaim some from
Postgres.

The only thing that needs additional intervention is the indexes, we do
a REINDEX CONCURRENTLY once a week, as described here:
https://www.postgresql.org/docs/current/routine-reindex.html

Apparently this "index bloat" should be less of an issue in Postgres 14
but I haven't gotten around to try it yet.



On 31.01.22 13:38, alcatron wrote:
> Thanks, would I ever have to do a “vacuum full” to the db by any chance
> or should it be automatic process?
>
> Auto Vacuum is set to on
>
> *From: *Christian Ramseyer 
> *Date: *Monday, 31 January 2022 at 10:34 pm
> *To: *alcatron ,
> netdisco-users@lists.sourceforge.net
> , Jethro Binks
> 
> *Subject: *Re: [Netdisco] Netdisco auto discovery tasks suddenly 
stopped

> working
>
>
>
> On 31.01.22 12:56, alcatron wrote:
>> Thanks Christian, those commands you mentioned is that just at the 
psql

>> command line?
>>
>
> Yes exactly. You can start the command line interface with "netdisco-do
> psql".
>
>
>> For some reason ever since I cleaned this device_skip table the 
netdisco

>> postgresql folder has grown dramatically in size by an extra 15gig
>> within 2 weeks.
>>
>> I see this directory taking up the space -
>> /var/lib/pgsql/12/data/base/16386 and lot of other files in there.
>>
>> I had a look at the netdisco tables and I cant see any table that 
big in

>> size, so im not really sure why the psql has dramatically keeps
>> increasing in disk size ?
>
>
> You should see what uses the space with the first query from here:
> https://wiki.postgresql.org/wiki/Disk_Usage
> 
>
> This will include indexes and TOAST tables, the space is probably used
> there instead of the actual table object.
>
> Cheers
> Christian
>
>
>
>
>>
>> Schema |    Name    | Type  | Owner   |    Size    |
>> Description
>>
>> 
++---+--++-

>>
>> public | admin  | table | netdisco | 173 MB |
>>
>>   public | community  | table | netdisco | 224 kB |
>>
>>   public | dbix_class_schema_versions | table | netdisco | 40 kB  |
>>
>>   public | device | table | netdisco | 3312 kB    |
>>
>>   public | device_ip  | table | netdisco | 34 MB  |
>>
>>   public | device_module  | table | netdisco | 895 MB     |
>>
>>   public | device_port    | table | netdisco | 1656 MB    |
>>
>>   public | device_port_log    | table | netdisco | 48 kB  |
>>
>>   public | device_port_power  | table | netdisco | 124 MB |
>>
>>   public | device_port_properties     | table | netdisco | 354 MB |
>>
>>   public | device_port_ssid   | table | netdisco | 17 MB  |
>>
>>   public | device_port_vlan   | table | netdisco | 1084 MB    |
>>
>>   public | device_port_wireless   | table 

netdisco-users Digest, Vol 186, Issue 4

[netdisco-users-request]

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. Netdisco auto discovery tasks suddenly stopped working (alcatron)
   2. Re: Netdisco auto discovery tasks suddenly stopped working
  (Christian Ramseyer)
--- Begin Message ---
Hi all, just wanting to ask your thoughts on what could be causing netdisco to 
suddenly stop performing auto discovery tasks.

Seems only arpnip is working via scheduled tasks, but discovery/macsuck has 
halted to auto perform. If I go manually to the device on web interface and 
trigger the auto discovery/arpnip/macsuck it works fine on the device.

Nothing has changed on system, running for a few months now, and suddenly the 
auto discovery is broken partly.

If I go to the backend log I see error like this below. The server is running 
and operational as I can still perform the manual to get discovery etc

The server is not out of memory as it has like 16GB and still plenty unused not 
what the messages are indicating..

Thanks for any assistance 

DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently 
unversioned. Please call upgrade on your schema to sync the DB. at 
/home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121
DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI 
connect('dbname=netdisco','netdisco',...) failed: could not connect to server: 
No such file or directory
Is the server running locally and accepting
connections on Unix domain socket 
"/var/run/postgresql/.s.PGSQL.5432"? at 
/home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1639. at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/JobQueue/PostgreSQL.pm line 50

[25756] error bless( {'msg' => 'DBIx::Class::Storage::DBI::_dbh_execute(): DBI 
Exception: DBD::Pg::st execute failed: ERROR:  out of memory
DETAIL:  Failed on request of size 16 in memory context "MessageContext". [for 
Statement "SELECT me.job, me.entered, me.started, me.finished, me.device, 
me.port, me.action, me.subaction, me.status, me.username, me.userip, me.log, 
me.debug, me.device_key FROM admin me WHERE ( me.job = ? ) FOR UPDATE" with 
ParamValues: 1=\'186421742\'] at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/JobQueue/PostgreSQL.pm line 267
'}, 'DBIx::Class::Exception' )
[25781] 2022-01-11 01:33:53 error bless( {'msg' => 
'DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute 
failed: ERROR:  out of memory
DETAIL:  Failed on request of size 16 in memory context "MessageContext". [for 
Statement "SELECT me.job, me.entered, me.started, me.finished, me.device, 
me.port, me.action, me.subaction, me.status, me.username, me.userip, me.log, 
me.debug, me.device_key FROM admin me WHERE ( me.job = ? ) FOR UPDATE" with 
ParamValues: 1=\'186420514\'] at 
/home/netdisco/perl5/lib/perl5/App/Netdisco/JobQueue/PostgreSQL.pm line 267
--- End Message ---
--- Begin Message ---

Hi

>  could not connect to
> server: No such file or directory/

This would be very concerning, meaning that Postgres is not running at 
all. But since you seem to have the web frontend running that is 
probably not the case currently, so I wouldn't worry too much. Might be 
an old log entry.



> Failed on request of size 16 in memory context
> "MessageContext".

That on the other hand might be the issue. Postgres uses all kinds of 
memory parameters, if one of them is too small the total GB of RAM 
sticks in the server don't matter much.


I had various issues with huge and clogged up discovery queues over the 
years, as a first measure I'd try to:


stop netdisco-backend
restart Postgres, connect to the database with "netdisco-do psql" and in 
there run a "delete from admin;".

for good measure, also run "reindex table admin;"
restart netdisco-backend

This sounds dangerous but admin is in fact just the queue of actions to 
be done, so no important data will be lost.


Also a "select count(*) from admin" first might be interesting, to see 
how many rows are in there. If it's an absurdly high number (millions) 
you can run e.g. "create table admin_backup as select * from admin;" for 
analysis later.


If you're still getting the memory errors afterwards and it still 
doesn't work, I'd try to configure the memory parameters with this 
assistant, using the "online transaction processing" db type. 
https://pgtune.leopard.in.ua/#/about



Cheers
Christian



On 17.01.22 22:03, alcatron wrote:
Hi all, just wanting to ask your thoughts on what could be causing 
netdisco to