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: IOS static Ports (Jeroen van Ingen)
2. Change of git repository locations (SourceForge -> GitHub)
(Oliver Gorwits)
3. Not showing connected nodes (Nicol?s Matsunaga)
4. Re: Change of git repository locations (SourceForge ->
GitHub) (Oliver Gorwits)
5. Re: Change of git repository locations (SourceForge ->
GitHub) (Sanjeev Gupta)
--- Begin Message ---
Hi Oliver,
I understand your point, you expect Netdisco to show "dynamic" for VLAN
type on 802.1X controlled ports.
However, what Netdisco reports here is the exact value of an SNMP object
from the switch; there's no logic applied to this value. The switch
itself says "static" for the 802.1X ports and not "dynamic".
There's probably an inconsistency between CatOS & IOS-XE 3.6.x vs
"classic" IOS 12.x & 15.x in what they report.
You can verify what the switches report by running this on the command line:
netdisco-do show -d <device_ip_or_dns> -e vmVlanType
netdisco-do show -d <device_ip_or_dns> -e ifName
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 12/19/2016 11:26 AM, Oliver Bührig wrote:
Hi all,
I running Netdisco Version 2.033006 and discovered a problem with Cisco
IOS 12.x and 15.x with 802.1x config on the switch ports. All ports with
802.1x config will be stored as 'static' in the Netdisco database. The
IOS switches with VMPS config is able to separate between static and
dynamic via SNMP.
CATOS and ios-xe / 03.06.03.E show the correct settings for vlantype in
the netdisco DB. If there is a change to get the right setting from
those devices with Netdisco ?
All C6500, C3750, C3750x, C3560 are affected, C3850 and C4500 run
without any problems.
Regards,
Oliver Buehrig
--- End Message ---
--- Begin Message ---
Hi all,
First, a very happy [Gregorian calendar] new year to you, and thanks for
continuing to use our software!
Following agreement in the dev team, the new home for Netdisco and
SNMP-Info is: https://github.com/netdisco
Please update your git repository URLs as in the example below:
$ git remote -v
origin ssh://[email protected]/p/snmp-info/code (fetch)
origin ssh://[email protected]/p/snmp-info/code (push)
$ git remote set-url origin [email protected]:netdisco/snmp-info.git
The full list of from/to URL changes (pay close attention!):
ssh://[email protected]/p/snmp-info/code
[email protected]:netdisco/snmp-info.git
ssh://[email protected]/p/netdisco/mibs
[email protected]:netdisco/netdisco-mibs.git
ssh://[email protected]/p/netdisco/misc
[email protected]:netdisco/netdisco-misc.git
ssh://[email protected]/p/netdisco/code
[email protected]:netdisco/netdisco-legacy.git
ssh://[email protected]/p/netdisco/netdisco-ng
[email protected]:netdisco/netdisco.git
See this page if you get stuck with the URL or authenticating:
https://help.github.com/articles/which-remote-url-should-i-use/
I am going to have a look at migrating the tickets, but it may be lossy
in metadata (ticket requestor) so, we'll see. Going forward we would
like the GitHub issues to be used to report bugs and request features,
although of course these mail lists are always preferred for initial
contact and discussion (and will remain at SourceForge).
Any questions, please let me know on or off list,
regards,
oliver.
--- End Message ---
--- Begin Message ---
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 2017-01-05 19:08, Sanjeev Gupta wrote:
On Thu, Jan 5, 2017 at 3:40 AM, Oliver Gorwits <[email protected]>
wrote:
ssh://[email protected]/p/netdisco/netdisco-ng [1]
[email protected]:netdisco/netdisco.git
I have update Openhub with the new code location for netdisco, and the
update job is running.
Thank you!
regards,
oliver.
--
Sanjeev Gupta
+65 98551208 http://sg.linkedin.com/in/ghane [2]
Links:
------
[1] http://[email protected]/p/netdisco/netdisco-ng
[2] http://sg.linkedin.com/in/ghane
--- End Message ---
--- Begin Message ---
On Thu, Jan 5, 2017 at 3:40 AM, Oliver Gorwits <[email protected]> wrote:
>
>
> ssh://[email protected]/p/netdisco/netdisco-ng
> [email protected]:netdisco/netdisco.git
I have update Openhub with the new code location for netdisco, and the
update job is running.
--
Sanjeev Gupta
+65 98551208 http://sg.linkedin.com/in/ghane
--- 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
