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: The connected device information is incorrect on
Netdisco. (Oliver Gorwits)
2. Re: Macsuck not possible on Cisco 2918 Switch (Jeroen van Ingen)
3. Re: Mac Suck Problem with Netdisco2 (Jeroen van Ingen)
4. Re: Best way to discover Cisco Nexus N5K (Jeroen van Ingen)
5. ??: The connected device information is incorrect on
Netdisco. (Zhangyuanyuan (D))
--- Begin Message ---
Hi Jacy,
On 2015-11-17 08:44, Chenjie (Jacy, Enterprise Romania GTAC) wrote:
Please be informed that we tried to contact support from Netdisco but
nobody reply us, I am wondering if you have any other ways to contact
them since we are not familiar with this Netdisco company.
I already replied to you with the following request:
Thank you for reporting this issue. To help us work out where the cause
may be, please could you provide the output of the following commands:
~netdisco/bin/netdisco-do show -d huawei_1 -e c_ip
~netdisco/bin/netdisco-do show -d huawei_1 -e c_if
~netdisco/bin/netdisco-do show -d huawei_1 -e c_port
Many thanks,
regards,
oliver.
Many thanks！
Best regards,
Jacy,
FROM: Zhangyuanyuan (D)
SENT: Wednesday, November 11, 2015 9:46 AM
TO: [email protected]
CC: Chenjie (Jacy, Enterprise Romania GTAC); Zhaoshaoqi; Zoujing
(Jingo Zou, DCLMT); Wuwei (Bryan)
SUBJECT: The connected device information is incorrect on Netdisco.
Hi, all
I met a problem with Netdisco, I had sent a email last week. But
there
was no response.
Could you help us analyze this issue. I will be deeply appreciated if
this issue can be solved.
The problem is that:
when the network is consisted of Huawei Cloudengine Switches, the
connected device information is incorrect on Netdisco, It’s
inconsistent with the Topology.
We have checked the packets that Huawei Switch sends to Netdisco, The
SNMP packets were correct, the LLDP information in SNMP packet was
consistent with the Topology. But, Netdisco showed wrong port
connection.
Here is the detail for this issue:
The LLDP information on Huawei Cloudengine is as follows:
<huawei_1>display lldp neighbor brief
Local Interface Exptime(s) Neighbor Interface Neighbor Device
-------------------------------------------------------------------------------------------
40GE2/0/2 103 40GE1/0/2 huawei_2
GE2/0/19 114 GE2/0/31 huawei_1
GE2/0/31 114 GE2/0/19 huawei_1
We can see that, GE2/0/19 is connected to GE2/0/31. GE2/0/31 is
another port on this device.
But, on Netdisco, we can see that GE2/0/19 is connected to itself.
1. The implementation of LLDP on Huawei device is according to the
protocol “802.1AB-2005”, The LLDP MIB description is as follows:
2. Huawei device use MIB node
“lldpRemoteSystemsData(1.0.8802.1.1.2.1.4)” for LLDP, In this node
“lldpRemPortId(1.0.8802.1.1.2.1.4.1.1.7)” is port’s neighbor
information；
3. According to protocol, “lldpRemPortId” is the remote port that
this device connects to.
“lldpRemPortId” is string type:
4. In the SNMP packet that Huawei Switch sents, the value of the
“lldpRemPortId” is correct.
Take port GE2/0/19 for example, The value of “lldpRemPortId” is as
bellow:
lldpRemPortId.169046155.80.1 = 47.45.32.2f.30.2f.33.31
//”169046155.80.1“ represents GE2/0/19 ” ,and
“47.45.32.2f.30.2f.33.31” represents G.E.2./.0./.31
lldpRemPortId.169046155.92.1 = 47.45.32.2f.30.2f.31.39 //”
169046155.92.1” represents GE2/0/19 “, and
“47.45.32.2f.30.2f.31.39” represents G.E.2./.0./.19.
lldpRemPortId.169046155.115.1 = 34.30.47.45.31.2f.30.2f.32
--- End Message ---
--- Begin Message ---
Sebastian,
I have a problem to macsuck addresses from a Cisco 2918 Switch (Cisco
IOS Software, C2918 Software (C2918-LANLITEK9-M), Version
12.2(44)SE6,
RELEASE SOFTWARE (fc1) ) They won´t be fetched.
When I do a simple snmpwalk the data isn´t also being fetched. What
should I do now? Do I need a special MIB?
If the data isn't appearing with snmpwalk then it could be an SNMP
"view" restriction (ACL)?
You might need to configure the device to permit access to the table
via SNMP. Sadly I can't lay my hands on the command right now but maybe
someone else can help?
Could you paste the SNMP related configuration from that switch? For
example, "show run | inc snmp" ? You may want to find/replace the actual
SNMP community values with something bogus.
This bit of config will show if any SNMP view restrictions are in place,
hiding the objects that we need.
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
--- End Message ---
--- Begin Message ---
Hi Oliver,
Going through the list mails, I saw that nobody had replied to your
question yet.
Netdisco 2.0 does macsuck in the same way that Netdisco 1.x does: it
asks the SNMP::Info class whether or not to do the macsuck per VLAN and
then collects all the forwarding table entries.
Can you share with us what version of SNMP::Info is running on the ND1
system and what version is installed on the ND2 system? Maybe we can
find some way to fix this for you.
Regards,
Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
On 09/25/2015 09:47 AM, Oliver Bührig wrote:
Hi all,
I running Netdisco Version 1.0 and want migrate to Netdisco2. With a
test system I ran into Problems with Catos Switches and MacSuck. Same
Problem as described in a post from Drik Troendle some time ago.
*[Netdisco] Netdisco2 Macsuck CPU Utilization on Cisco Catalyst 6500
<http://sourceforge.net/p/netdisco/mailman/message/33520728/>*
From: Troendle, Dirk (SCC) <dirk.troendle@pa...> - 2015-03-02 15:54:47
It takes about 2-3 hours, depending from the device type, to read all
mac address assignment from the switch. The CPU get up to 100 %. With
Netdisco Version 1.0 I had no problems. The MacSuck run took max. 1.5
minutes. Cisco Nexus and IOS and some other vendor did not run into
problems with Version 2.
Netdisco Version1.0 runs MacSuck in a different way as Version 2.0 do,
right ?
Version 2 request mac address assignments per Vlan and Catalyst with
CatOS spend a lot of time (CPU) to send snmp answers. Version 1.0 seems
to get the mac addresses from the bridgetable.
'Saw : 1440 forwarding table entries. Took 82 seconds.'
Any ideas to get that kind of request in Netdisco Version 2 ?
Regards,
Oliver Buehrig
------------------------------------------------------------------------------
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
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:[email protected]]
Gesendet: Freitag, 2. Oktober 2015 09:22
An: [email protected]
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi oliver,
We have two device: "192.168.1.247" and "192.168.1.246". Here is the output of
the related commands. It seems that all informations are correct.
--------------------------------------------------------------------------------------------------------------------------------------------------
192.168.1.247
netdisco@dc-lmt:~$ ~netdisco/bin/netdisco-do show -d 192.168.1.247 -e c_id
[6870] 2015-11-24 17:43:12 info show: started at Tue Nov 24 12:43:12 2015
\ {
169046155.80.1 "e4:68:a3:f9:17:81",
169046155.92.1 "e4:68:a3:f9:17:81",
169046155.115.1 "00:6d:88:34:87:01"
}
[6870] 2015-11-24 17:43:12 info show: finished at Tue Nov 24 12:43:12 2015
[6870] 2015-11-24 17:43:12 info show: status done: Showed c_id response from
192.168.1.247.
netdisco@dc-lmt:~$ ~netdisco/bin/netdisco-do show -d 192.168.1.247 -e c_ip
[6876] 2015-11-24 17:43:32 info show: started at Tue Nov 24 12:43:32 2015
\ {
169046155.80.1 "3.3.3.3",
169046155.92.1 "3.3.3.3",
169046155.115.1 "2.2.2.2"
}
[6876] 2015-11-24 17:43:33 info show: finished at Tue Nov 24 12:43:33 2015
[6876] 2015-11-24 17:43:33 info show: status done: Showed c_ip response from
192.168.1.247.
netdisco@dc-lmt:~$ ~netdisco/bin/netdisco-do show -d 192.168.1.247 -e c_if
[6895] 2015-11-24 17:44:17 info show: started at Tue Nov 24 12:44:17 2015
\ {
169046155.80.1 80,
169046155.92.1 92,
169046155.115.1 115
}
[6895] 2015-11-24 17:44:18 info show: finished at Tue Nov 24 12:44:18 2015
[6895] 2015-11-24 17:44:18 info show: status done: Showed c_if response from
192.168.1.247.
netdisco@dc-lmt:~$ ~netdisco/bin/netdisco-do show -d 192.168.1.247 -e c_port
[6897] 2015-11-24 17:44:24 info show: started at Tue Nov 24 12:44:24 2015
\ {
169046155.80.1 "GE2/0/31",
169046155.92.1 "GE2/0/19",
169046155.115.1 "40GE1/0/2"
}
[6897] 2015-11-24 17:44:25 info show: finished at Tue Nov 24 12:44:25 2015
[6897] 2015-11-24 17:44:25 info show: status done: Showed c_port response from
192.168.1.247.
--------------------------------------------------------------------------------------------------------------------------------------------------
192.168.1.246
netdisco@dc-lmt:~$ ~netdisco/bin/netdisco-do show -d 192.168.1.246 -e c_id
[6872] 2015-11-24 17:43:19 info show: started at Tue Nov 24 12:43:19 2015
\ {
241393620.172.1 "e4:68:a3:f9:17:81"
}
[6872] 2015-11-24 17:43:20 info show: finished at Tue Nov 24 12:43:20 2015
[6872] 2015-11-24 17:43:20 info show: status done: Showed c_id response from
192.168.1.246.
netdisco@dc-lmt:~$ ~netdisco/bin/netdisco-do show -d 192.168.1.246 -e c_ip
[6874] 2015-11-24 17:43:25 info show: started at Tue Nov 24 12:43:25 2015
\ {
241393620.172.1 "3.3.3.3"
}
[6874] 2015-11-24 17:43:26 info show: finished at Tue Nov 24 12:43:26 2015
netdisco@dc-lmt:~$ ~netdisco/bin/netdisco-do show -d 192.168.1.246 -e c_if
[6893] 2015-11-24 17:44:11 info show: started at Tue Nov 24 12:44:11 2015
\ {
241393620.172.1 172
}
[6893] 2015-11-24 17:44:12 info show: finished at Tue Nov 24 12:44:12 2015
[6893] 2015-11-24 17:44:12 info show: status done: Showed c_if response from
192.168.1.246.
netdisco@dc-lmt:~$ ~netdisco/bin/netdisco-do show -d 192.168.1.246 -e c_port
[6899] 2015-11-24 17:44:32 info show: started at Tue Nov 24 12:44:32 2015
\ {
241393620.172.1 "40GE2/0/2"
}
[6899] 2015-11-24 17:44:33 info show: finished at Tue Nov 24 12:44:33 2015
[6899] 2015-11-24 17:44:33 info show: status done: Showed c_port response from
192.168.1.246.
netdisco@dc-lmt:~$
Best regards.
-----邮件原件-----
发件人: Oliver Gorwits [mailto:[email protected]]
发送时间: 2015年11月23日 17:10
收件人: Chenjie (Jacy, Enterprise Romania GTAC);
[email protected]
抄送: Zoujing (Jingo Zou, DCLMT); Zhangyuanyuan (D); Wuwei (Bryan); Zhaoshaoqi
主题: Re: [Netdisco] The connected device information is incorrect on Netdisco.
Hi Jacy,
On 2015-11-17 08:44, Chenjie (Jacy, Enterprise Romania GTAC) wrote:
> Please be informed that we tried to contact support from Netdisco but
> nobody reply us, I am wondering if you have any other ways to contact
> them since we are not familiar with this Netdisco company.
I already replied to you with the following request:
Thank you for reporting this issue. To help us work out where the cause may be,
please could you provide the output of the following commands:
~netdisco/bin/netdisco-do show -d huawei_1 -e c_ip ~netdisco/bin/netdisco-do
show -d huawei_1 -e c_if ~netdisco/bin/netdisco-do show -d huawei_1 -e c_port
Many thanks,
regards,
oliver.
>
> Many thanks！
>
> Best regards,
>
> Jacy,
>
> FROM: Zhangyuanyuan (D)
> SENT: Wednesday, November 11, 2015 9:46 AM
> TO: [email protected]
> CC: Chenjie (Jacy, Enterprise Romania GTAC); Zhaoshaoqi; Zoujing
> (Jingo Zou, DCLMT); Wuwei (Bryan)
> SUBJECT: The connected device information is incorrect on Netdisco.
>
> Hi, all
>
> I met a problem with Netdisco, I had sent a email last week. But there
> was no response.
>
> Could you help us analyze this issue. I will be deeply appreciated if
> this issue can be solved.
>
> The problem is that:
>
> when the network is consisted of Huawei Cloudengine Switches, the
> connected device information is incorrect on Netdisco, It’s
> inconsistent with the Topology.
>
> We have checked the packets that Huawei Switch sends to Netdisco, The
> SNMP packets were correct, the LLDP information in SNMP packet was
> consistent with the Topology. But, Netdisco showed wrong port
> connection.
>
> Here is the detail for this issue:
>
> The LLDP information on Huawei Cloudengine is as follows:
>
> <huawei_1>display lldp neighbor brief
>
> Local Interface Exptime(s) Neighbor Interface Neighbor Device
>
>
> ----------------------------------------------------------------------
> ---------------------
>
>
> 40GE2/0/2 103 40GE1/0/2 huawei_2
>
> GE2/0/19 114 GE2/0/31 huawei_1
>
> GE2/0/31 114 GE2/0/19 huawei_1
>
> We can see that, GE2/0/19 is connected to GE2/0/31. GE2/0/31 is
> another port on this device.
>
> But, on Netdisco, we can see that GE2/0/19 is connected to itself.
>
> 1. The implementation of LLDP on Huawei device is according to the
> protocol “802.1AB-2005”, The LLDP MIB description is as follows:
>
> 2. Huawei device use MIB node
> “lldpRemoteSystemsData(1.0.8802.1.1.2.1.4)” for LLDP, In this node
> “lldpRemPortId(1.0.8802.1.1.2.1.4.1.1.7)” is port’s neighbor
> information；
>
> 3. According to protocol, “lldpRemPortId” is the remote port that
> this device connects to.
>
> “lldpRemPortId” is string type:
>
> 4. In the SNMP packet that Huawei Switch sents, the value of the
> “lldpRemPortId” is correct.
>
> Take port GE2/0/19 for example, The value of “lldpRemPortId” is as
> bellow:
>
> lldpRemPortId.169046155.80.1 = 47.45.32.2f.30.2f.33.31
> //”169046155.80.1“ represents GE2/0/19 ” ,and
> “47.45.32.2f.30.2f.33.31” represents G.E.2./.0./.31
>
> lldpRemPortId.169046155.92.1 = 47.45.32.2f.30.2f.31.39 //”
> 169046155.92.1” represents GE2/0/19 “, and “47.45.32.2f.30.2f.31.39”
> represents G.E.2./.0./.19.
>
> lldpRemPortId.169046155.115.1 = 34.30.47.45.31.2f.30.2f.32
--- End Message ---
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
