netdisco-users Digest, Vol 127, Issue 2

Mon, 09 Jan 2017 08:04:50 -0800 

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: Change of git repository locations (SourceForge ->
      GitHub) (Sanjeev Gupta)
   2. Re: Not showing connected nodes (Jeroen van Ingen)
   3. NBTstat: MAC>IP Lookup not working (Wegjan)
   4. Re: Discover problem (Matthew Seymour)
--- Begin Message --- 
On Thu, Jan 5, 2017 at 3:40 AM, Oliver Gorwits <[email protected]> wrote:

> [email protected]:netdisco/snmp-info.git
>

I have updated OpenHub.  You can see statistics on contributions, and the
code base, at:

https://www.openhub.net/p/snmp-info
https://www.openhub.net/p/netdisco


-- 
Sanjeev Gupta
+65 98551208   http://sg.linkedin.com/in/ghane

--- End Message ---
--- Begin Message --- 
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 --- 
Hello,

my Netdisco Setup is working properly except the Mac>IP Lookup. I have tried 
everything i could but Netdisco is only showing the Mac of a Node and not the 
IP or DNS Name. To check if my Installation is correct i have set up a new 
Linux System (Ubuntu 16.04) and did a fresh Install of Netdisco with the same 
result.

Can anyone Help me?

Regards,

Bjoern

--- End Message ---
--- Begin Message --- 
Is there anything I can do to help get to the bottom of this issue? It's
making Netdisco fairly unusable for us unfortunately. Very happy to help in
any way I can.

Best
Matthew

On 20 November 2016 at 17:54, Oliver Gorwits <[email protected]> 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
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
> ------------------------------------------------------------
> ------------------
> _______________________________________________
> Netdisco mailing list
> [email protected]
> 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 ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to