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: Not showing connected nodes (Sebastian R?sch)
2. Re: Netdisco 2 Neighbors Map - How to Add in hostname
(Alexander R)
3. Re: Discover problem (Matthew Seymour)
--- Begin Message ---
Hi,
we also faced problems after migration to snmpv3 with Cisco 29xx/37xx/45xx, due
to a missing configuration line. We had either missing mac addresses or simply
no mac addresses at all, that netdisco discovered.
Instead of using configuring a context for each vlan (context vlan-xyz) I would
recommend to use this command syntax:
snmp-server group xxx v3 auth context vlan- match prefix
There are 2 advantages using this command:
1.) Only 1 configuration line is necessary
2.) if you configure new vlans, you don´t have to change the snmp config on all
your switches
BR,
Sebastian
-----Ursprüngliche Nachricht-----
Von: Jeroen van Ingen [mailto:j.vaningensche...@utwente.nl]
Gesendet: Freitag, 6. Januar 2017 11:13
An: netdisco-users@lists.sourceforge.net
Betreff: Re: [Netdisco] Not showing connected nodes
Hi,
This sounds familiar, there have been a few similar threads about macsuck &
SNMPv3 on Cisco switches in the past.
I believe a few bugs in Netdisco have been fixed since then, but perhaps the
comment that Bill Fenner made about SNMPv3 context configuration on Cisco
switches is still relevant: could you check out
https://sourceforge.net/p/netdisco/mailman/message/29871772/ and verify the
"snmp-server group xxx v3 auth" config on your switch? Please let us know
whether there are "context vlan-xyz" present for your VLANs, and if not,
whether adding those lines makes a difference.
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 01/05/2017 06:49 PM, Nicolás Matsunaga wrote:
> Hi,
>
> I have recently updated from version 2.033002 to 2.034001 by advice
> of Oliver because I was hunting down a bug.
> I did a workaround to work with multiple SNMPv3 configurations.
> It seemed all was up and running but I recently discovered that
> Connected Nodes is empty on every device (cisco switches).
> With version SNMP v2 and DB version 40, this was working. When I did
> the upgrade I executed "~/bin/netdisco-deploy".
> I am not sure if this is another SNMP v3 issue or a DB schema version issue.
> I put this last reason on the table because if I rerun
> "~/bin/netdisco-deploy" (as shown below), it still says my DB version is 40.
>
> Can someone help me?
>
> Regards, Nicolás
>
> *INFO 1:*
>
> I did force a macsuck on one switch A.B.160.51 (IP is masqueraded for
> security reasons)
>
> $ ~/bin/netdisco-do macsuck -D -d A.B.160.51 [18154] 2017-01-05
> 17:13:20 info App::Netdisco version 2.034001 loaded.
> [18154] 2017-01-05 17:13:20 info macsuck: started at Thu Jan 5
> 14:13:20 2017
> [18154] 2017-01-05 17:13:20 debug [A.B.160.51] try_connect with ver:
> 3,
> class: SNMP::Info::Layer3::C3550, comm: XXXXX [18154] 2017-01-05
> 17:13:22 debug [A.B.160.51] macsuck 00:1e:bd:7f:2b:1c - port
> GigabitEthernet0/1 has neighbor A.B.160.130 - skipping.
> [18154] 2017-01-05 17:13:22 debug [A.B.160.51] macsuck
> 04:da:d2:64:4f:01 - port GigabitEthernet0/3 has neighbor A.B.160.52 -
> skipping.
> [18154] 2017-01-05 17:13:24 debug [A.B.160.51] macsuck - VLANs:
> 1,1002,1003,1004,1005,160,161,162,163,164,165,166,167,168,169,170,171,
> 172,173,174,175,263,264,5,500,501,503,555,77,9
> [18154] 2017-01-05 17:13:24 debug [A.B.160.51] macsuck VLAN 1002 -
> skipped by macsuck_no_vlan config [18154] 2017-01-05 17:13:24 debug
> [A.B.160.51] macsuck VLAN 1003 - skipped by macsuck_no_vlan config
> [18154] 2017-01-05 17:13:24 debug [A.B.160.51] macsuck VLAN 1004 -
> skipped by macsuck_no_vlan config [18154] 2017-01-05 17:13:24 debug
> [A.B.160.51] macsuck VLAN 1005 - skipped by macsuck_no_vlan config
> [18154] 2017-01-05 17:13:24 debug [A.B.160.51] reindexing to "vlan-1"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-160"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-161"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-162"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-163"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-164"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-165"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-166"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-167"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-168"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-169"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-170"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-171"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:24
> debug [A.B.160.51] reindexing to "vlan-172"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-173"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-174"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-175"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-263"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-264"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-5"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-500"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-501"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-503"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-555"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-77"
> (ver: 3, class: SNMP::Info::Layer3::C3550) [18154] 2017-01-05 17:13:25
> debug [A.B.160.51] reindexing to "vlan-9"
> (ver: 3, class: SNMP::Info::Layer3::C3550) *[18154] 2017-01-05
> 17:13:25 debug [A.B.160.51] macsuck - 0 updated forwarding table
> entries** **[18154] 2017-01-05 17:13:25 debug [A.B.160.51] macsuck -
> removed 0 fwd table entries to archive** *[18154] 2017-01-05 17:13:25
> info macsuck: finished at Thu Jan 5
> 14:13:25 2017
> [18154] 2017-01-05 17:13:25 info macsuck: status done: Ended macsuck
> for A.B.160.51
>
>
> *INFO 2:*
>
> [netdisco@server ~]$ ~/bin/netdisco-deploy [18282] 2017-01-05
> 17:27:05 info App::Netdisco 2.034001 loaded.
> This is the Netdisco II deployment script.
>
> Before we continue, the following prerequisites must be in place:
> * Database added to PostgreSQL for Netdisco
> * User added to PostgreSQL with rights to the Netdisco Database
> * "~/environments/deployment.yml" file configured with Database
> dsn/user/pass
> * A full backup of any existing Netdisco database data
> * Internet access (for OUIs and MIBs)
>
> You will be asked to confirm all changes to your system.
>
> So, is all the above in place? [y/N]: y
>
> Would you like to deploy the database schema? [y/N]: y
> DBIx::Class::Schema::Versioned::_on_connect(): Versions out of sync.
> This is 41, your database contains version 40, please call upgrade on
> your Schema. at /home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 85
> DBIx::Class::Schema::Versioned::upgrade_single_step(): DB version (40)
> is lower than the schema version (41). Attempting upgrade.
> DB schema update complete.
> DBIx::Class::Schema::Versioned::_on_connect(): Versions out of sync.
> This is 41, your database contains version 40, please call upgrade on
> your Schema. at /home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 85
>
> Download and update vendor MAC prefixes (OUI data)? [y/N]: n
>
> Download and update MIB files? [y/N]: n
>
>
>
--- End Message ---
--- Begin Message ---
>On 2016-11-18 02:27, Muris wrote:
> I been using Netdisco 2 and ive found it to be great, i wanted to know
> on a device for the "Neighbors" Map it has the circles with the IP
> address, is there anyway of adding in the hostname above the IP, or
> below the IP of the device. This way i have full visibility of
> adjacent networks with an IP and hostname.
> If a hostname can be added on along with the IP, it would be most
> useful either above or below the IP.
> Also make sure domain_suffix is set in your config.
> regards,
> oliver.
Hostnames in "Neighbors" will be very useful, and even more - manageable
tooltips (like Muris wants): Sysname with IP or with DNS name.
For example: I'm as a network admin, manage customer network in datacenter,
that does not have DNS for network devices (I can't change this situation),
as a result, on "Neighbors" I see IPs, but I accustomed to see hostname in
device console. Yes I can remember IP and find device in ND2, but ... it's
not handy
I think, If ND2 will have option how to show devices names in topology (by
IP, DNS//etc/hosts, SNMP Sysname) it will be very good.
At other side, without DNS record for devices, when I select
"Inventory->Vendor-Cisco", ND2 show me table and first column has device
names (yes we're reading from left to right side) not IP and there it's OK
- user friendly.
For example, CA Spectrum has options "Model naming order": 1. Sysname, 2.
IP addr, 3. Name service. So we can select, what naming order we need while
network discovery
--- End Message ---
--- Begin Message ---
Well, this is embarrassing... turns out we had made a config error in a
template that had been replicated around our new switches. Fixed that and
Netdisco scheduler is happily discovering everything now.
On 20 November 2016 at 17:54, Oliver Gorwits <oli...@cpan.org> wrote:
> Hi Matthew,
>
> On 2016-11-07 12:53, Matthew Seymour wrote:
> > One example switch that it found early in the discovery process has an
> > error against it saying it can't make an snmp connection.
> >
> > I've attemped a manual discover of that switch
> > with: ~/bin/netdisco-do -D discover -d <ip address>
> >
> > That works just fine, no errors and now it's in the database. However
> > if I attempt a discover through the web interface it errors.
>
> The web interface isn't running the Discover job, it just puts the job
> in the queue for the scheduler to run sometime in the future (usually
> immediately if it's not busy).
>
> So this is interesting that the scheduler cannot make the connection,
> but the command line can?
>
> Are you running the command line on the same host, as the same user,
> with the same config, as the backend daemon was started on?
>
> Otherwise, if this is reproducible, it would be very interesting to dig
> deeper and help us understand what's happening.
>
> regards,
> oliver.
>
>
> > What have I missed?
> >
> > --
> >
> > Matthew Seymour
> > Network Technician
> > IT Services
> >
> > INFORMATION SERVICES | UNIVERSITY OF
> > YORK | HESLINGTON | YORK | YO10 5DD
> > TEL: 01904 323858 | SCHEDULED WORK [1] | FACEBOOK [2] | twitter
> > [3]
> >
> >
> >
> > Email disclaimer: http://www.york.ac.uk/docs/disclaimer/email.htm [4]
> >
> >
> > Links:
> > ------
> > [1] http://www.york.ac.uk/it-services/news/work/
> > [2] https://www.facebook.com/UoYITServices
> > [3] http://twitter.com/UoYITServices
> > [4] http://www.york.ac.uk/docs/disclaimer/email.htm
> >
> > ------------------------------------------------------------
> ------------------
> > Developer Access Program for Intel Xeon Phi Processors
> > Access to Intel Xeon Phi processor-based developer platforms.
> > With one year of Intel Parallel Studio XE.
> > Training and support from Colfax.
> > Order your platform today. http://sdm.link/xeonphi
> >
> > _______________________________________________
> > Netdisco mailing list
> > netdisco-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
> ------------------------------------------------------------
> ------------------
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
--
Matthew Seymour
Network Technician
IT Services
*Information Services | University of York* | *Heslington* | *York* | *YO10
5DD*
*tel: 01904 323858* | *scheduled work*
<http://www.york.ac.uk/it-services/news/work/> | *facebook*
<https://www.facebook.com/UoYITServices> |
*twitter <http://twitter.com/UoYITServices>*
Email disclaimer: http://www.york.ac.uk/docs/disclaimer/email.htm
--- End Message ---
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
