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: Update: Beginner Problems with Job Queue (Oliver Gorwits)
2. Re: Inventory models sum (Jakub Holecek)
3. Re: Inventory models sum (Ivan Brunello)
--- Begin Message ---
On 2015-01-29 12:33, Stephan Grund wrote:
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.
Great, many thanks for letting us know.
regards,
oliver.
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
netdisco-users@lists.sourceforge.net
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
netdisco-users@lists.sourceforge.net
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
netdisco-users@lists.sourceforge.net
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
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Thanks Oliver,
using discover_no for some ip addressses, deleting and re-discovering works
quite good, now I see just 2 N7k in Inventory.
Admin VDC does not hold any ports, so it is ok not to see this in our topology.
(Although I cannot see where management port is connected now.)
Yes, we have two VDC's on both N7K boxes, so I understand, that virtually I
should see 4 virtual switches (
if Inventory should not show only real boxes).
Implementing VRF support would be pretty for us ;)
Normally, if switch (f.e. cisco 3750) holds more IP addresses responding to
snmp, netdisco can indentify it as one box ?
Regards, Jakub
> Dňa 28.1.2015 22:46 používateľ "Oliver Gorwits" <oli...@cpan.org
> [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
>> >
>> >
>> >
--- End Message ---
--- Begin Message ---
Hi Jakub,
if device has several routed interface (i.e. interface vlan, or routed
port) netdisco usually identifies correctly as a single node.
implementing VRF is not that simple because of a design flaw in VRFs
- VRF name has local scope (you can define different name for same VRF on
different devices)
- rd is also local. usually you set the same rd across all infrastructure
to identify same VRF, but it is not mandatory, and some design (e.g. PIC
EDGE) ask rd to be differentiated on nodes
- rt make sense in MPLS design when BGP is used to its fullest, but it
could be even NOT configured in e.g. VRF-lite implementation.
in short, you don't have a deterministic way of discrimininating whether L3
interfaces on two different, adjacent, devices belong to same vrf.
My two cents.
Ivan
On Thu, Jan 29, 2015 at 4:51 PM, Jakub Holecek <troo...@troolix.cz> wrote:
> Thanks Oliver,
>
> using discover_no for some ip addressses, deleting and re-discovering
> works quite good, now I see just 2 N7k in Inventory.
> Admin VDC does not hold any ports, so it is ok not to see this in our
> topology. (Although I cannot see where management port is connected now.)
>
>
> Yes, we have two VDC's on both N7K boxes, so I understand, that virtually
> I should see 4 virtual switches (
> if Inventory should not show only real boxes).
>
> Implementing VRF support would be pretty for us ;)
>
> Normally, if switch (f.e. cisco 3750) holds more IP addresses responding
> to snmp, netdisco can indentify it as one box ?
>
>
> Regards, Jakub
>
>
> > Dňa 28.1.2015 22:46 používateľ "Oliver Gorwits" <oli...@cpan.org
> > [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/
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> 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
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
