Send netdisco-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: Beginner Problems with Job Queue (Andy Ruhl)
2. Inventory models sum (Jakub Holecek)
3. Update: Beginner Problems with Job Queue (Stephan Grund)
4. Re: Inventory models sum (Oliver Gorwits)
5. Re: Update: Beginner Problems with Job Queue (Oliver Gorwits)
6. Re: Inventory models sum (Pavel Skovajsa)
--- Begin Message ---
On Fri, Jan 23, 2015 at 7:20 AM, Stephan Grund <
[email protected]> wrote:
> Hi!
>
> Am 23.01.2015 um 15:02 schrieb Andy Ruhl:
> > On Fri, Jan 23, 2015 at 1:18 AM, Stephan Grund <
> > [email protected]> wrote:
> [...]
> >>
> >> On the CLI netdisco-do -D discover -d <IP> works like a charm.
> >> But on the Web, the job queue grows larger and no job gets
> >> executed.
> >>
> >> When I search an IP, it gets the information of the first CLI run.
> >>
> >> Daemon is running.
> >>
> >> Can You give me some hints, what I've overseen?
> >>
> >
> > Does it look like jobs are being run at the times shown in the scheduling
> > part of the deployment.yml file? Did you edit the schedule section?
>
> I have edit the schedule section:
>
> $ cat environments/deployment.yml
> [...]
> # this is the schedule for automatically keeping netdisco up-to-date
> # ``````````````````````````````````````````````````````````````````
> schedule:
> discoverall:
> when: '5 7 * * *'
> macwalk:
> when:
> min: 20
> arpwalk:
> when:
> min: 50
> nbtwalk:
> when: '0 8,13,21 * * *'
> expire:
> when: '20 23 * * *'
>
> [...]
>
> The times shown in the job list are matching this times
> (taken from the webpage <netdisco>:5000/admin/jobqueue):
>
> Entered Action Status
> 2015-01-23 14:20 Macwalk Queued
> 2015-01-23 13:50 Arpwalk Queued
> 2015-01-23 13:20 Macwalk Queued
> 2015-01-23 13:00 Nbtwalk Queued
> 2015-01-23 12:50 Arpwalk Queued
> 2015-01-23 12:20 Macwalk Queued
> 2015-01-23 11:50 Arpwalk Queued
> 2015-01-23 11:20 Macwalk Queued
> 2015-01-23 10:50 Arpwalk Queued
> 2015-01-23 10:20 Macwalk Queued
> 2015-01-23 09:50 Arpwalk Queued
> 2015-01-23 09:20 Macwalk Queued
> 2015-01-23 08:50 Arpwalk Queued
> 2015-01-23 08:20 Macwalk Queued
> 2015-01-23 08:00 Nbtwalk Queued
> 2015-01-23 07:50 Arpwalk Queued
> 2015-01-23 07:20 Macwalk Queued
> 2015-01-23 07:05 Discoverall Queued
> 2015-01-23 06:50 Arpwalk Queued
> 2015-01-23 06:20 Macwalk Queued
> 2015-01-23 05:50 Arpwalk Queued
> 2015-01-23 05:20 Macwalk Queued
> 2015-01-23 04:50 Arpwalk Queued
> 2015-01-23 04:20 Macwalk Queued
>
>
> Daemon is running:
>
> $ bin/netdisco-daemon status
> Netdisco Daemon [Running]
>
There was a problem a while back where you needed to restart the daemon to
get jobs finished, have you done this? Just netdisco-daemon restart. This
problem should have been fixed though.
Andy
--- End Message ---
--- Begin Message ---
Hi everybody,
I started with netdisco yesterday.
In the Inventory tab I see N7Kc7010 count number 5, reality is we have two N7K
boxes.
I see this in Devices:
------------------------------------
Device Contact Location System Name Model OS Version
Management IP Serial Last Discovered
n7k-a n7k-a-fp N7Kc7010 6.2(10)
IP#1 SERIAL#1 2015-01-28 08:21
n7k-admin-a n7k-a N7Kc7010 6.2(10)
IP#2 SERIAL#1 2015-01-27 15:06
n7k-admin-b n7k-b N7Kc7010 6.2(10)
IP#3 SERIAL#2 2015-01-27 15:06
n7k-b-fp n7k-b-fp N7Kc7010 6.2(10)
IP#4 SERIAL#2 2015-01-28 08:22
n7k-b n7k-b-fp N7Kc7010 6.2(10)
IP#5 SERIAL#2 2015-01-28 08:20
(I have anonymized real serial numbers and IP addressses))
Netdisco counts as many boxes as ip addresses on N7K boxes it discovers.
Is there way how to summarize models in Inventory by serial numbers ?
Netdisco system information:
PostgreSQL PostgreSQL 9.1.14 on x86_64-unknown-linux-gnu, compiled by
gcc-4.7.real (Debian 4.7.2-5) 4.7.2, 64-bit.
DBI 1.633, DBD::Pg 2.19.2
SNMP::Info 3.23
Perl 5.014002
Built using Open Source
Software Version
App::Netdisco 2.030000
DB Schema v39
Dancer 1.3132
Bootstrap 2.3.1
PostgreSQL PostgreSQL 9.1.14 on x86_64-unknown-linux-gnu, compiled by
gcc-4.7.real (Debian 4.7.2-5) 4.7.2, 64-bit. DBI 1.633, DBD::Pg 2.19.2
SNMP::Info 3.23
Perl 5.014002
Thanks, Jakub
--- End Message ---
--- Begin Message ---
Hi!
First, thanks to Andy for trying to help me.
I've take a second try:
- clean CentOS 6 install
- clean netdisco2 install
The first time I've done a 'netdisco-do -D discover -d <IP>'
Now I skipped this and do the first discover over the web-GUI
At first it looks better. But now the job queue is growing again.
Some jobs are being executed, so the growth isn't as much, as the fist
try, but it doesn't look right for me.
Has anyone some hints for me?
TIA,
Stephan
Am 23.01.2015 um 09:18 schrieb Stephan Grund:
> Hi!
>
> I've made a fresh install of netdisco 2 after the instructions
> on https://metacpan.org/pod/App::Netdisco
>
> On the CLI netdisco-do -D discover -d <IP> works like a charm.
> But on the Web, the job queue grows larger and no job gets
> executed.
>
> When I search an IP, it gets the information of the first CLI run.
>
> Daemon is running.
>
> Can You give me some hints, what I've overseen?
>
> Regards,
> Stephan
>
--- End Message ---
--- Begin Message ---
Hi Jakub,
This is interesting, and not something I've seen before, so I can't
offer a perfect solution. However some workarounds...
The simplest thing would be to use the discover_only config setting to
limit Netdisco to discovering only the device IPs you wish:
discover_only:
- 'IP#1'
- 'IP#5'
It also accepts IP prefixes, and there's discover_no if you prefer an
exclusion model rather than inclusion.
Following that, you can navigate to the device details page and use the
red delete button to make Netdisco forget about the other entries.
It's also interesting to note the last discovered timestamp in the
final column. If you run Netdisco discover once a day, it may be that
Netdisco has already given up on two of the five, for some reason. You
could try deleting them.
And finally to for understanding, Netdisco uses the given IPs of a
device to determine "same"-ness. So if these are VRFs or similar it may
be that they're genuinely reporting as separate devices even though you
know them to be the same. Sadly Netdisco isn't very VRF aware (yet). For
the debug-curious:
$ ~netdisco/bin/netdisco-do discover -d 1.2.3.4 -DI
regards,
oliver.
On 2015-01-28 08:53, Jakub Holecek wrote:
Hi everybody,
I started with netdisco yesterday.
In the Inventory tab I see N7Kc7010 count number 5, reality is we
have two N7K boxes.
I see this in Devices:
------------------------------------
Device Contact Location System Name Model OS Version
Management
IP Serial Last Discovered
n7k-a n7k-a-fp N7Kc7010 6.2(10) IP#1 SERIAL#1 2015-01-28
08:21
n7k-admin-a n7k-a N7Kc7010 6.2(10) IP#2 SERIAL#1 2015-01-27
15:06
n7k-admin-b n7k-b N7Kc7010 6.2(10) IP#3 SERIAL#2 2015-01-27
15:06
n7k-b-fp n7k-b-fp N7Kc7010 6.2(10) IP#4 SERIAL#2 2015-01-28
08:22
n7k-b n7k-b-fp N7Kc7010 6.2(10) IP#5 SERIAL#2 2015-01-28
08:20
(I have anonymized real serial numbers and IP addressses))
Netdisco counts as many boxes as ip addresses on N7K boxes it
discovers.
Is there way how to summarize models in Inventory by serial numbers ?
Netdisco system information:
PostgreSQL PostgreSQL 9.1.14 on x86_64-unknown-linux-gnu, compiled by
gcc-4.7.real (Debian 4.7.2-5) 4.7.2, 64-bit.
DBI 1.633, DBD::Pg 2.19.2
SNMP::Info 3.23
Perl 5.014002
Built using Open Source
Software Version
App::Netdisco 2.030000
DB Schema v39
Dancer 1.3132
Bootstrap 2.3.1
PostgreSQL PostgreSQL 9.1.14 on x86_64-unknown-linux-gnu, compiled by
gcc-4.7.real (Debian 4.7.2-5) 4.7.2, 64-bit. DBI 1.633, DBD::Pg
2.19.2
SNMP::Info 3.23
Perl 5.014002
Thanks, Jakub
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media,
is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more.
Take a
look and join the conversation now.
http://goparallel.sourceforge.net/
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Stephan,
How many CPU cores on the Netdisco system, and how many devices
(switches, routers) on your network?
regards,
oliver.
On 2015-01-28 08:54, Stephan Grund wrote:
Hi!
First, thanks to Andy for trying to help me.
I've take a second try:
- clean CentOS 6 install
- clean netdisco2 install
The first time I've done a 'netdisco-do -D discover -d <IP>'
Now I skipped this and do the first discover over the web-GUI
At first it looks better. But now the job queue is growing again.
Some jobs are being executed, so the growth isn't as much, as the
fist
try, but it doesn't look right for me.
Has anyone some hints for me?
TIA,
Stephan
Am 23.01.2015 um 09:18 schrieb Stephan Grund:
Hi!
I've made a fresh install of netdisco 2 after the instructions
on https://metacpan.org/pod/App::Netdisco
On the CLI netdisco-do -D discover -d <IP> works like a charm.
But on the Web, the job queue grows larger and no job gets
executed.
When I search an IP, it gets the information of the first CLI run.
Daemon is running.
Can You give me some hints, what I've overseen?
Regards,
Stephan
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media,
is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more.
Take a
look and join the conversation now.
http://goparallel.sourceforge.net/
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Jakub
I guess you have separate virtual device contexts on the N7Ks right. In
that case i would consider this 'normal' behavior since it really acts up
as separate entity.
-pavel
Dňa 28.1.2015 22:46 používateľ "Oliver Gorwits" <[email protected]> napísal:
> Hi Jakub,
>
> This is interesting, and not something I've seen before, so I can't
> offer a perfect solution. However some workarounds...
>
> The simplest thing would be to use the discover_only config setting to
> limit Netdisco to discovering only the device IPs you wish:
>
> discover_only:
> - 'IP#1'
> - 'IP#5'
>
> It also accepts IP prefixes, and there's discover_no if you prefer an
> exclusion model rather than inclusion.
>
> Following that, you can navigate to the device details page and use the
> red delete button to make Netdisco forget about the other entries.
>
> It's also interesting to note the last discovered timestamp in the
> final column. If you run Netdisco discover once a day, it may be that
> Netdisco has already given up on two of the five, for some reason. You
> could try deleting them.
>
> And finally to for understanding, Netdisco uses the given IPs of a
> device to determine "same"-ness. So if these are VRFs or similar it may
> be that they're genuinely reporting as separate devices even though you
> know them to be the same. Sadly Netdisco isn't very VRF aware (yet). For
> the debug-curious:
>
> $ ~netdisco/bin/netdisco-do discover -d 1.2.3.4 -DI
>
> regards,
> oliver.
>
> On 2015-01-28 08:53, Jakub Holecek wrote:
> > Hi everybody,
> >
> > I started with netdisco yesterday.
> > In the Inventory tab I see N7Kc7010 count number 5, reality is we
> > have two N7K boxes.
> >
> > I see this in Devices:
> >
> > ------------------------------------
> > Device Contact Location System Name Model OS
> Version Management
> > IP Serial Last Discovered
> > n7k-a n7k-a-fp N7Kc7010 6.2(10)
> IP#1 SERIAL#1 2015-01-28
> > 08:21
> > n7k-admin-a n7k-a N7Kc7010 6.2(10)
> IP#2 SERIAL#1 2015-01-27
> > 15:06
> > n7k-admin-b n7k-b N7Kc7010 6.2(10)
> IP#3 SERIAL#2 2015-01-27
> > 15:06
> > n7k-b-fp n7k-b-fp N7Kc7010 6.2(10)
> IP#4 SERIAL#2 2015-01-28
> > 08:22
> > n7k-b n7k-b-fp N7Kc7010 6.2(10)
> IP#5 SERIAL#2 2015-01-28
> > 08:20
> >
> > (I have anonymized real serial numbers and IP addressses))
> >
> >
> > Netdisco counts as many boxes as ip addresses on N7K boxes it
> > discovers.
> > Is there way how to summarize models in Inventory by serial numbers ?
> >
> >
> >
> > Netdisco system information:
> > PostgreSQL PostgreSQL 9.1.14 on x86_64-unknown-linux-gnu, compiled by
> > gcc-4.7.real (Debian 4.7.2-5) 4.7.2, 64-bit.
> > DBI 1.633, DBD::Pg 2.19.2
> > SNMP::Info 3.23
> > Perl 5.014002
> > Built using Open Source
> >
> > Software Version
> > App::Netdisco 2.030000
> > DB Schema v39
> > Dancer 1.3132
> > Bootstrap 2.3.1
> > PostgreSQL PostgreSQL 9.1.14 on x86_64-unknown-linux-gnu, compiled by
> > gcc-4.7.real (Debian 4.7.2-5) 4.7.2, 64-bit. DBI 1.633, DBD::Pg
> > 2.19.2
> > SNMP::Info 3.23
> > Perl 5.014002
> >
> >
> >
> > Thanks, Jakub
> >
> >
> >
> ------------------------------------------------------------------------------
> > Dive into the World of Parallel Programming. The Go Parallel Website,
> > sponsored by Intel and developed in partnership with Slashdot Media,
> > is your
> > hub for all things parallel software development, from weekly thought
> > leadership blogs to news, videos, case studies, tutorials and more.
> > Take a
> > look and join the conversation now.
> > http://goparallel.sourceforge.net/
> > _______________________________________________
> > Netdisco mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
--- End Message ---
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
