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: Best way to discover Cisco Nexus N5K (Sebastian R?sch)
2. Re: Best way to discover Cisco Nexus N5K (Christian Ramseyer)
3. discovery of Cisco 6500 : duplicate key value (De Bruyne Karel)
4. Search failed! Please contact your site administrator
(netdisco2) (Daniel Bird)
--- Begin Message ---
Hello Jeroen,
exactly, currently I have different snmp communites for each vrf.
My favorite way would be to fetch the addresses with the ssh collector, because
you there is a command in nexus for showing all vrf´s content: "show ip arp vrf
all". That would be great... because I could remove all the additional devices
I´ve just added for arpnipping the different vrf´s.
But so far I wasn´t able to add another device type as described here, I´m not
very familiar with all that perl stuff.....
http://search.cpan.org/~oliver/App-Netdisco/bin/netdisco-sshcollector
What do I need to do for this?
######
Additional device classes can be easily integrated just by adding and additonal
class to the App::Netdisco::SSHCollector::Platform namespace.
######
But this could be the solution to this problem.
Thanks & Best Regards
Sebastian
-----Ursprüngliche Nachricht-----
Von: Jeroen van Ingen [mailto:j.vaningensche...@utwente.nl]
Gesendet: Dienstag, 24. November 2015 11:36
An: Sebastian Rösch <roe...@alcera.de>; netdisco-users@lists.sourceforge.net
Betreff: Re: AW: [Netdisco] Best way to discover Cisco Nexus N5K
Hi Sebastian,
Okay, thanks for the info. That translates to:
CISCO-CONTEXT-MAPPING-MIB::cContextMappingVrfName."netdisco_dmz" =
STRING: "DMZ"
CISCO-CONTEXT-MAPPING-MIB::cContextMappingVrfName."netdisco_wan" =
STRING: "WAN"
CISCO-CONTEXT-MAPPING-MIB::cContextMappingVrfName."Server_Prod_neu" = ""
CISCO-CONTEXT-MAPPING-MIB::cContextMappingVrfName."netdisco_server_prod_neu"
= STRING: "Server_Prod_neu"
...so the SNMP context names are visible here.
So in your case, to get all the ARP tables, would Netdisco need to connect with
communities "netdisco_wan", "netdisco_dmz" and "netdisco_server_prod_neu" ?
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 10/28/2015 04:36 PM, Sebastian Rösch wrote:
> Hello Jeroen,
>
> Today I tried to get the vrf´s via snmp. And yes, It is possible. This will
> list the vrf´s :
>
> snmpwalk -v2c -c com 192.168.0.1 1.3.6.1.4.1.9.9.468.1.1.1.2
>
>
> The OID is on the cisco website, you can search the snmp object navigator for
> it.
> http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate
> =Translate&objectInput=1.3.6.1.4.1.9.9.468.1.1.1.2
>
>
> It looks like that in my case:
>
> iso.3.6.1.4.1.9.9.468.1.1.1.2.12.110.101.116.100.105.115.99.111.95.100.109.122
> = STRING: "DMZ"
> iso.3.6.1.4.1.9.9.468.1.1.1.2.12.110.101.116.100.105.115.99.111.95.119.97.110
> = STRING: "WAN"
> iso.3.6.1.4.1.9.9.468.1.1.1.2.15.83.101.114.118.101.114.95.80.114.111.100.95.110.101.117
> = ""
> iso.3.6.1.4.1.9.9.468.1.1.1.2.24.110.101.116.100.105.115.99.111.95.115.101.114.118.101.114.95.112.114.111.100.95.110.101.117
> = STRING: "Server_Prod_neu"
>
>
> Thanks,
> Sebastian
>
>
> -----Ursprüngliche Nachricht-----
> Von: Jeroen van Ingen [mailto:j.vaningensche...@utwente.nl]
> Gesendet: Freitag, 2. Oktober 2015 09:22
> An: netdisco-users@lists.sourceforge.net
> Betreff: Re: [Netdisco] Best way to discover Cisco Nexus N5K
>
> Hi Sebastian,
>
> The base design for Netdisco didn't include support for VRFs; I don't expect
> any real VRF support coming to 2.x releases either, it's more likely to be
> added when a lot of the code is redesigned for Netdisco 3.
>
> In the mean time, I guess you've already found the options: live without the
> ARP entries in different VRFs, treat every VRF on a box as an extra box in
> the network, or hack around with custom data collection.
>
> Do you happen to know if you can at least list the VRFs that are present via
> SNMP? If so, that would open up possibilities to extend SNMP::Info to collect
> the data you need.
>
>
> Regards,
>
> Jeroen van Ingen
> ICT Service Centre
> University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
>
>
> On 10/01/2015 05:59 PM, Sebastian Rösch wrote:
>> Hi,
>>
>> I would like to know, if somebody uses netdisco to discover Cisco
>> Nexus stuff? We have 4x Nexus 5000 and the problem is, that we´re
>> using multiple vrf´s. To get the ARP entries from all the different
>> vrfs, I cannot use the management address, I have to use IP-Adresses
>> from every vrf. The same management address is present in all
>> discovered nexus devices/instances.
>>
>> Therefore I created different snmp communities, mapped to the
>> different vrfs.
>>
>> Looks like this:
>>
>> snmp-server context netdisco_wan vrf WAN
>>
>> snmp-server context netdisco_dmz vrf DMZ
>>
>> snmp-server context netdisco_server_prod_neu vrf Server_Prod_neu
>>
>> snmp-server community netdisco_wan
>>
>> snmp-server community netdisco_dmz
>>
>> snmp-server community netdisco_server_prod_neu
>>
>> snmp-server mib community-map netdisco_wan context netdisco_wan
>>
>> snmp-server mib community-map netdisco_dmz context netdisco_dmz
>>
>> snmp-server mib community-map netdisco_server_prod_neu context
>> netdisco_server_prod_neu
>>
>> I needed to force netdisco to use snmpv2, v3 wasn´t working.
>>
>> But now, netdisco shows several different entries for the same
>> system, because it treats it as different devices. Isn´t there a way
>> to improve that?
>>
>> I also tried to use ssh-collector, with a little modified Cisco
>> IOS-XR Script. The command line needs to be "show ip arp vrf all".
>> But I didn´t work. I think there also other dependencies, that needs
>> to be modified, I don´t know about.
>>
>> Did somebody found a better way to include nexus devices with vrf?
>>
>> Best Regards
>>
>> Sebastian
>>
>>
>>
>> ---------------------------------------------------------------------
>> -
>> --------
>>
>>
>>
>> _______________________________________________
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>>
>
>
>
--- End Message ---
--- Begin Message ---
On 08/12/15 13:42, Sebastian Rösch wrote:
> exactly, currently I have different snmp communites for each vrf.
> My favorite way would be to fetch the addresses with the ssh collector,
> because you there is a command in nexus for showing all vrf´s content:
> "show ip arp vrf all". That would be great... because I could remove all the
> additional devices I´ve just added for arpnipping the different vrf´s.
> But so far I wasn´t able to add another device type as described here, I´m
> not very familiar with all that perl stuff.....
> http://search.cpan.org/~oliver/App-Netdisco/bin/netdisco-sshcollector
>
> What do I need to do for this?
Hi Sebastian & List
Here is a module that I just made and tested on a N5kC5596Up. You must
store the file in lib/perl5/App/Netdisco/SSHCollector/Platform/NXOS.pm
(there's already all the other platform-specific .pm files there), then
reference it in deployment.yml like this:
sshcollector:
- hostname: 'n5.example.com'
user: whatever
password: topsecret
platform: NXOS
Maybe Olvier or another Netdisco dev can add it to the distro for future
releases.
Hope that helps
Christian
NXOS.pm
Description: Perl program
--- End Message ---
--- Begin Message ---
I've got a rather big network (>500 Cisco switches).
A few weeks ago I discovered Netdisco, and I really like it.
A lot of the tools we wrote ourselves can be replaced by it.
I've got a small problem : the discovery of my network isn't complete...
I always get errors when discovering two of our main routers (Cisco 6500
series):
error running job: DBIx::Class::Storage::DBI::_dbh_execute_for_fetch():
execute_for_fetch() aborted with 'ERROR: duplicate key value violates unique
constraint "device_port_vlan_pkey"
DETAIL: Key (ip, port, vlan, native)=(143.129.xxx.yyy, GigabitEthernet2/16, 1,
t) already exists.' at populate slice:
{
ip => "143.129.xxx.yyy",
last_discover => \"now()",
native => "t",
port => "GigabitEthernet2/16",
vlan => 1,
vlantype => "static"
} at /home/netdisco/perl5/lib/perl5/App/Netdisco/Core/Discover.pm line 487
Even when I delete these devices and re-discover it, I still get these error.
How could I solve this?
Kind Regards,
Karel De Bruyne
University of Antwerp
--- End Message ---
--- Begin Message ---
Hi All,
We started to encounter the same issue as listed in the link below about 10
days ago.
https://sourceforge.net/p/netdisco/mailman/message/34564497/
Again, this a 6509, with a fair few modules and ports (382).
The only time I can get it to display any port information is if I remove
almost all the display items, and especially "Connected Nodes".
I see there was a mention of it being a memory consumption issue, and it being
looked in to. I wondered if there any progress on this?
We're running the latest version
[netdisco2@netmanage ~]$ ~/bin/localenv cpanm --notest App::Netdisco
App::Netdisco is up to date. (2.033004)
And all the other devices we have seem to list their ports fine, although we
don't have any other kit with anywhere near as many ports as the 6509
Cheers
Dan
--- End Message ---
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
