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: Inventory models sum (Oliver Gorwits)
2. Re: Update: Beginner Problems with Job Queue (Oliver Gorwits)
3. Re: Update: Beginner Problems with Job Queue (Natxo Asenjo)
4. Re: Update: Beginner Problems with Job Queue (Stephan Grund)
5. Re: Update: Beginner Problems with Job Queue (Stephan Grund)
--- Begin Message ---
On 2015-01-29 08:56, Pavel Skovajsa wrote:
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.
Many thanks Pavel.
For my own interest, is there any feature which does relate the virtual
device contexts?
For example it could be that they all report the same chassis/hardware
serial numbers, or even the Vendor's device context MIB reporting this.
I also don't know whether there's a "parent" and "child" relation in the
contexts or whether they're all equivalent.
regards,
oliver.
-pavel
Dňa 28.1.2015 22:46 používateľ "Oliver Gorwits" <[email protected]
[7]> 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/ [1]
> _______________________________________________
> Netdisco mailing list
> [email protected] [2]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users [3]
------------------------------------------------------------------------------
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/ [4]
_______________________________________________
Netdisco mailing list
[email protected] [5]
https://lists.sourceforge.net/lists/listinfo/netdisco-users [6]
Links:
------
[1] http://goparallel.sourceforge.net/
[2] mailto:[email protected]
[3] https://lists.sourceforge.net/lists/listinfo/netdisco-users
[4] http://goparallel.sourceforge.net/
[5] mailto:[email protected]
[6] https://lists.sourceforge.net/lists/listinfo/netdisco-users
[7] mailto:[email protected]
--- End Message ---
--- Begin Message ---
On 2015-01-29 07:01, Stephan Grund wrote:
Am 28.01.2015 um 22:47 schrieb Oliver Gorwits:
Hi Stephan,
How many CPU cores on the Netdisco system, and how many devices
(switches, routers) on your network?
netdisco runs on a vm with 1 CPU/Core
we have about 60+ devices in our network
I have tried to increase the number of SNMP workers
(tasks: 'AUTO * 4') with no effect.
I would definitely add more cores if you can (total of four would be
good).
Also check the Slowest Devices report (Admin menu) to see how long
these jobs are taking. It could be that the vendor's SNMP is just slow,
or that Netdisco's having problems with SNMP BULKWALK (we saw that
recently on this list).
I assume, as you've not mentioned it, that there aren't any errors in
the job queue?
regards,
oliver.
Stephan
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
------------------------------------------------------------------------------
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 ---
On Thu, Jan 29, 2015 at 10:05 AM, Oliver Gorwits <[email protected]> wrote:
> On 2015-01-29 07:01, Stephan Grund wrote:
> > Am 28.01.2015 um 22:47 schrieb Oliver Gorwits:
> >> Hi Stephan,
> >>
> >> How many CPU cores on the Netdisco system, and how many devices
> >> (switches, routers) on your network?
> >
> > netdisco runs on a vm with 1 CPU/Core
> > we have about 60+ devices in our network
> > I have tried to increase the number of SNMP workers
> > (tasks: 'AUTO * 4') with no effect.
>
> I would definitely add more cores if you can (total of four would be
> good).
>
fwiw, we are monitoring 202 devices now with a 2vcpu 4Gb ram centos 6
vmware vm.
No sweat. This vm also handles netflow info through nfsen and keeps a
backup of the devices configs using rancid.
--
regards,
Natxo
--- End Message ---
--- Begin Message ---
Hi!
Thanks for the quick response.
Am 29.01.2015 um 10:05 schrieb Oliver Gorwits:
> On 2015-01-29 07:01, Stephan Grund wrote:
>> Am 28.01.2015 um 22:47 schrieb Oliver Gorwits:
>>> Hi Stephan,
>>>
>>> How many CPU cores on the Netdisco system, and how many devices
>>> (switches, routers) on your network?
>>
>> netdisco runs on a vm with 1 CPU/Core
>> we have about 60+ devices in our network
>> I have tried to increase the number of SNMP workers
>> (tasks: 'AUTO * 4') with no effect.
>
> I would definitely add more cores if you can (total of four would be
> good).
OK, I will try with more CPU/Cores
>
> Also check the Slowest Devices report (Admin menu) to see how long
> these jobs are taking. It could be that the vendor's SNMP is just slow,
> or that Netdisco's having problems with SNMP BULKWALK (we saw that
> recently on this list).
the slowest device shown under 'time elapsed' 1:22 Didn't look bad for
me.
>
> I assume, as you've not mentioned it, that there aren't any errors in
> the job queue?
No, no erros in queue or daemon-log.
As written, I will try with more CPU.
Stephan
>
> regards,
> oliver.
>
>
>>
>> Stephan
>>
>>
>>>
>>> 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
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>
--
Stephan Grund, Fraunhofer-Institut für Offene Kommunikationssysteme FOKUS
IT-Management, Technischer Mitarbeiter
Kaiserin-Augusta-Allee 31, 10589 Berlin, Germany
Telefon: +49 (0) 30 / 3463 - 7636
Telefax: +49 (0) 30 / 3463 - 99 7636
mailto:[email protected]
http://www.fokus.fraunhofer.de
--- End Message ---
--- Begin Message ---
Hi!
It works! The netdisco vm now has 2 CPUs/ 4 Cores and 4G RAM.
The Jobqueue ist down from ~400 items to 140 in the last 30 minutes.
Thanks for the support,
Stephan
Am 29.01.2015 um 11:50 schrieb Stephan Grund:
> Hi!
>
> Thanks for the quick response.
>
> Am 29.01.2015 um 10:05 schrieb Oliver Gorwits:
>> On 2015-01-29 07:01, Stephan Grund wrote:
>>> Am 28.01.2015 um 22:47 schrieb Oliver Gorwits:
>>>> Hi Stephan,
>>>>
>>>> How many CPU cores on the Netdisco system, and how many devices
>>>> (switches, routers) on your network?
>>>
>>> netdisco runs on a vm with 1 CPU/Core
>>> we have about 60+ devices in our network
>>> I have tried to increase the number of SNMP workers
>>> (tasks: 'AUTO * 4') with no effect.
>>
>> I would definitely add more cores if you can (total of four would be
>> good).
>
> OK, I will try with more CPU/Cores
>
>>
>> Also check the Slowest Devices report (Admin menu) to see how long
>> these jobs are taking. It could be that the vendor's SNMP is just slow,
>> or that Netdisco's having problems with SNMP BULKWALK (we saw that
>> recently on this list).
>
> the slowest device shown under 'time elapsed' 1:22 Didn't look bad for
> me.
>
>>
>> I assume, as you've not mentioned it, that there aren't any errors in
>> the job queue?
>
> No, no erros in queue or daemon-log.
>
> As written, I will try with more CPU.
>
> Stephan
>
>>
>> regards,
>> oliver.
>>
>>
>>>
>>> Stephan
>>>
>>>
>>>>
>>>> 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
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> 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
