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. SNMP Poll failure (Bavo Seesink)
2. Re: question about serial numbers and the 'snmp-server
chassis' command (Eric Miller)
3. Beginner Problems with Job Queue (Stephan Grund)
4. Re: Beginner Problems with Job Queue (Andy Ruhl)
5. Re: question about serial numbers and the 'snmp-server
chassis' command (Sckolnick, Gary)
6. Re: Beginner Problems with Job Queue (Stephan Grund)
--- Begin Message ---
Hi Oliver,
I`m Gona install the files first thing in the morning.
I`f installed Netdisco 2.0 also on a other server according. this installation
had the same problems.
No netdisco-mibs directory. And i`m sure there is an internet connection.
I let you know the results.
Thanks for helping
Greeting
Bavo
--- End Message ---
--- Begin Message ---
On the ND2 install please check the device module tab and see if the
serial numbers are captured for the individual switch unit(s).
Serial numbers are also available under Reports->Device->Module
Inventory. Using _% (underscore percent sign) in the Module Serial
search box will limit return results to those with a serial number.
This report is exportable as CSV.
There were changes to SNMP::Info between 3.13 and 3.23 that would
account for the difference in the results. The serial number being
returned for the chassis should be from
CISCO-STACK-MIB::chassisSerialNumber.0 or
CISCO-STACK-MIB::chassisSerialNumberString.0. It is Cisco designed
behaviour to return the what is set via the snmp-server chassis-id
command over the default serial number. Some older switches required
entering the chassis serial number via this command as it is not machine
readable otherwise. I'm hoping you can verify the individual switch
serial numbers in the module inventory are correct as those are obtained
from the ENTITY-MIB.
Thanks,
Eric
On 2015-01-21 10:53, Sckolnick, Gary wrote:
Sorry, I meant to include the exact versions of ND. Here are all the
details:
ND1
Netdisco Version: 1.0
SNMP::Info 3.13
Perl Version: 5.8.9 (5.008009)
Postgres Version: PostgreSQL 8.3.7 on i386-portbld-freebsd7.2,
compiled by GCC cc (GCC) 4.2.1 20070719 [FreeBSD]
DBI 1.607 DBD::Pg 2.12.0
Apache Info: Apache/1.3.41 (Unix) mod_perl/1.31
mod_perl Version: 1.31
Mason: Powered by Mason Version 1.42
ZGRViewer: Verison 0.8.2 Interactive GraphViz .svg Viewer used for
Network Map. Author: Emmanuel Pietriga
ND2
Software Version
App::Netdisco 2.030000
DB Schema v39
Dancer 1.3132
Bootstrap 2.3.1
PostgreSQL PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu, compiled by
GCC gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4), 64-bit.
DBI 1.631, DBD::Pg 2.15.1
SNMP::Info 3.23
Perl 5.010001
Switch models where we see this difference between Netdisco/SNMP::Info
versions:
296024TT
296048TCS
3550-48
ciscoSm3k16GePoe
cat3560x24P
cat3560x48P
37xxStack
37xxStack
The majority of our switches do not have 'snmp-server chassis <asset
tag>' configured and, therefore, report their actual serial numbers.
Thanks,
~Gary
-----Original Message-----
From: Eric Miller [mailto:[email protected]]
Sent: Tuesday, January 20, 2015 21:49
To: Sckolnick, Gary
Cc: [email protected]
Subject: Re: [Netdisco] question about serial numbers and the
'snmp-server chassis' command
What model / os version of switch?
What version of SNMP::Info is in use on the ND1 and ND2 installs?
Thanks,
Eric
This message and any attachments may contain information that is
confidential, privileged and/or protected from disclosure under state
and federal laws. If you received this message in error or through
inappropriate means, please reply to this message to notify the Sender
that the message was received by you in error, and then permanently
delete this message from all storage media, without forwarding or
retaining a copy.
--- End Message ---
--- Begin Message ---
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 ---
On Fri, Jan 23, 2015 at 1:18 AM, Stephan Grund <
[email protected]> wrote:
> 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?
>
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?
Andy
--- End Message ---
--- Begin Message ---
Confirmed. Correct serial numbers are captured in ND2 both in the device
module tab as well as under Reports->Device->Module Inventory for the affected
switches. Thank you for your response and explanation for this observed
difference between ND1 and ND2 (or really SNMP::Info 3.13 and 3.23).
Regards,
~Gary
-----Original Message-----
From: Eric Miller [mailto:[email protected]]
Sent: Thursday, January 22, 2015 21:52
To: Sckolnick, Gary
Cc: [email protected]
Subject: RE: [Netdisco] question about serial numbers and the 'snmp-server
chassis' command
On the ND2 install please check the device module tab and see if the serial
numbers are captured for the individual switch unit(s).
Serial numbers are also available under Reports->Device->Module Inventory.
Using _% (underscore percent sign) in the Module Serial search box will limit
return results to those with a serial number.
This report is exportable as CSV.
There were changes to SNMP::Info between 3.13 and 3.23 that would account for
the difference in the results. The serial number being returned for the
chassis should be from
CISCO-STACK-MIB::chassisSerialNumber.0 or
CISCO-STACK-MIB::chassisSerialNumberString.0. It is Cisco designed behaviour
to return the what is set via the snmp-server chassis-id command over the
default serial number. Some older switches required entering the chassis
serial number via this command as it is not machine readable otherwise. I'm
hoping you can verify the individual switch serial numbers in the module
inventory are correct as those are obtained from the ENTITY-MIB.
Thanks,
Eric
On 2015-01-21 10:53, Sckolnick, Gary wrote:
> Sorry, I meant to include the exact versions of ND. Here are all the
> details:
>
> ND1
> Netdisco Version: 1.0
> SNMP::Info 3.13
> Perl Version: 5.8.9 (5.008009)
> Postgres Version: PostgreSQL 8.3.7 on i386-portbld-freebsd7.2,
> compiled by GCC cc (GCC) 4.2.1 20070719 [FreeBSD] DBI 1.607 DBD::Pg
> 2.12.0
> Apache Info: Apache/1.3.41 (Unix) mod_perl/1.31
> mod_perl Version: 1.31
> Mason: Powered by Mason Version 1.42
> ZGRViewer: Verison 0.8.2 Interactive GraphViz .svg Viewer used for
> Network Map. Author: Emmanuel Pietriga
>
>
> ND2
> Software Version
> App::Netdisco 2.030000
> DB Schema v39
> Dancer 1.3132
> Bootstrap 2.3.1
> PostgreSQL PostgreSQL 8.4.20 on x86_64-redhat-linux-gnu, compiled by
> GCC gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4), 64-bit.
> DBI 1.631, DBD::Pg 2.15.1
> SNMP::Info 3.23
> Perl 5.010001
>
> Switch models where we see this difference between Netdisco/SNMP::Info
> versions:
> 296024TT
> 296048TCS
> 3550-48
> ciscoSm3k16GePoe
> cat3560x24P
> cat3560x48P
> 37xxStack
> 37xxStack
>
> The majority of our switches do not have 'snmp-server chassis <asset
> tag>' configured and, therefore, report their actual serial numbers.
>
>
> Thanks,
> ~Gary
>
> -----Original Message-----
> From: Eric Miller [mailto:[email protected]]
> Sent: Tuesday, January 20, 2015 21:49
> To: Sckolnick, Gary
> Cc: [email protected]
> Subject: Re: [Netdisco] question about serial numbers and the
> 'snmp-server chassis' command
>
> What model / os version of switch?
>
> What version of SNMP::Info is in use on the ND1 and ND2 installs?
>
> Thanks,
> Eric
>
> This message and any attachments may contain information that is
> confidential, privileged and/or protected from disclosure under state
> and federal laws. If you received this message in error or through
> inappropriate means, please reply to this message to notify the Sender
> that the message was received by you in error, and then permanently
> delete this message from all storage media, without forwarding or
> retaining a copy.
This message and any attachments may contain information that is confidential,
privileged and/or protected from disclosure under state and federal laws. If
you received this message in error or through inappropriate means, please reply
to this message to notify the Sender that the message was received by you in
error, and then permanently delete this message from all storage media, without
forwarding or retaining a copy.
--- End Message ---
--- Begin Message ---
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]
Stephan
--- End Message ---
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
