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 & Dell Switches (Sanjeev Gupta)
2. R: Re: netdisco2 migration (meniche...@libero.it)
3. Re: R: Re: netdisco2 migration (Oliver Gorwits)
4. Re: IBM BNT switches - no os version (Oliver Gorwits)
5. Netdisco 2 - lots of queued jobs (Andy Ruhl)
6. Re: Netdisco 2 - lots of queued jobs (Scott Harrison)
7. Re: Netdisco 2 - lots of queued jobs (Andy Ruhl)
8. Re: Netdisco 2 - lots of queued jobs (Mike Gray)
--- Begin Message ---
On Fri, Nov 7, 2014 at 10:56 PM, Keith Shannon <kshan...@ffn.com> wrote:
> Netdisco is seeing all the Cisco switches without any issues, however,
> it’s not even detecting the Dell switches. I did a manual discovery & it
> will show the switch, but again won’t show anything connected.
>
Can you confirm the Dell has SNMP switched on?
>From the Netdisco machine, try a
snmpstatus -v 2c -c <community> <DellSwitchIP>
If this does not work, check the Dell. If it does, issue more likely on
Netdisco side.
--
Sanjeev Gupta
+65 98551208 http://sg.linkedin.com/in/ghane
--- End Message ---
--- Begin Message ---
thank you Oliver for your answer.
Now I can't work on this issue.
Incidentally, is there a way to select devices by age in ND2? something like
in inventory ND1
Regards
Marco
>----Messaggio originale----
>Da: oli...@cpan.org
>Data: 03/11/2014 21.05
>A: <netdisco-users@lists.sourceforge.net>
>Ogg: Re: [Netdisco] netdisco2 migration
>
>Hi Marco,
>
>The "netdisco-deploy" script will upgrade the ND1 database to support
>ND2.
>
>So you can either make your new Netdisco 2 system point at the old
>database, or dump and restore it to a new database.
>
>Then run the "netdisco-deploy" as shown in the installation
>instructions.
>
>regards,
>oliver.
>
>On 2014-10-30 15:28, meniche...@libero.it wrote:
>> hello
>> i'm looking for best practice to migrate version and host.
>> i have a running netdisco 1 on a Debian Squeeze (~3 years up &
>> running)
>> i wish to migrate to netdisco 2 on a Debian Wheezy virtual machine
>>
>> a ND2 on a virtual Wheezy is now running for testing everything seems
>> to be fine.
>>
>> i wish to have the old db (ND1) on a brand new ND2?
>>
>> thank you
>>
>> Marco
>
>
>------------------------------------------------------------------------------
>_______________________________________________
>Netdisco mailing list
>netdisco-users@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
--- End Message ---
--- Begin Message ---
Hi Marco,
On 2014-11-08 08:21, meniche...@libero.it wrote:
Incidentally, is there a way to select devices by age in ND2?
something like
in inventory ND1
There's an inventory in ND2 by location, vendor and model. I don't
think we have any report showing devices by age (you mean the last time
they were polled, or uptime?). It would be easy to do - please create a
tracker item if you'd like this report.
http://sourceforge.net/p/netdisco/netdisco2/
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi Andy,
On 2014-10-28 20:51, Andy Ruhl wrote:
I've noticed that on IBM BNT switches, only model 8124 devices have
the os_ver column populated in the device table in postgres.
Can someone help me find out why the other devices (8052, 8264) are
not populating the os_ver column?
The OS version is [usually] extracted from the description (sysDescr.0)
of the device, so (a) has to be coded for and (b) might not work if the
description format changes. Another reason is that the device isn't
being classified correctly.
Can you send us (or me directly if you wish) the output of:
~netdisco/bin/netdisco-do show -d <IP-or-name-of-device> -e description
-D
This will show the SNMP::Info device class being used, and also the
content of sysDescr.0 on the device.
Many thanks,
regards,
oliver.
--- End Message ---
--- Begin Message ---
If I go to Admin -> Job Queue
All I see are queued jobs.
I looked at the database and I see this (don't know if it's relevant):
netdisco=> select count(*) from admin where status='queued';
count
-------
1049
By looking at the "connected nodes" column in the "ports" link for a
device, I'm sure that data is at least a few days old.
What can I do?
I probably don't need to be doing macwalk and arpwalk every hour.
Thanks!
Andy
--- End Message ---
--- Begin Message ---
I also see this happen to the job queue periodically (2-5 weeks) along with the
following messages in /var/log/messages:
Nov 8 11:00:29 netdisco01 kernel: Out of memory: Kill process 2032
(netdisco-daemon) score 34 or sacrifice child
Nov 8 11:00:29 netdisco01 kernel: Killed process 2032, UID 500,
(netdisco-daemon) total-vm:464084kB, anon-rss:166872kB, file-rss:2144kB
I haven't had time to troubleshoot, but a reboot cures.
Running 2.029012 on Centos 6.
--- End Message ---
--- Begin Message ---
On Sat, Nov 8, 2014 at 2:53 PM, Scott Harrison <scott.harri...@asd20.org> wrote:
> I also see this happen to the job queue periodically (2-5 weeks) along with
> the following messages in /var/log/messages:
>
> Nov 8 11:00:29 netdisco01 kernel: Out of memory: Kill process 2032
> (netdisco-daemon) score 34 or sacrifice child
> Nov 8 11:00:29 netdisco01 kernel: Killed process 2032, UID 500,
> (netdisco-daemon) total-vm:464084kB, anon-rss:166872kB, file-rss:2144kB
>
> I haven't had time to troubleshoot, but a reboot cures.
>
> Running 2.029012 on Centos 6.
Rebooting seems to not help. I don't get those messages though.
I noticed this in deployment.yml:
# number of SNMP workers to run in parallel (in netdisco-daemon).
# 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'
tasks: 'AUTO * 3'
My machine has 8 cores. I don't really understand what "few cores"
means but my job queue is stacked up so I increased it.
There are more netdisco processes now, the load average is high (about
4 to 5) and the web gui never comes up. I'll let it run a while and
see what happens.
Andy
--- End Message ---
--- Begin Message ---
Check the daemons make sure they are all up. Generally when I saw this in
the past the jobs will run via cli but not through the gui. In that case if
the daemons are all running make sure the permissions are set. I had to set
all the permissions to completely open on one if nt instances in the past.
If you have any questions you can email me Monday when I am back in the
office and have all my notes in front of me from when I encountered this
issue.
On Nov 8, 2014 8:32 AM, "Andy Ruhl" <acr...@gmail.com> wrote:
> If I go to Admin -> Job Queue
>
> All I see are queued jobs.
>
> I looked at the database and I see this (don't know if it's relevant):
>
> netdisco=> select count(*) from admin where status='queued';
> count
> -------
> 1049
>
> By looking at the "connected nodes" column in the "ports" link for a
> device, I'm sure that data is at least a few days old.
>
> What can I do?
>
> I probably don't need to be doing macwalk and arpwalk every hour.
>
> Thanks!
>
> Andy
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
--- End Message ---
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
