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: Macsuck not possible on Cisco 2918 Switch (Sebastian R?sch)
2. Re: The connected device information is incorrect on
Netdisco. (Alan Brown)
3. Re: The connected device information is incorrect on
Netdisco. (Chenjie (Jacy, Enterprise Romania GTAC))
--- Begin Message ---
Hello Jeroen,
sure, here is the output:
snmp-server community xyz RO 10
snmp-server community zyx RW 10
snmp-server contact xxx
snmp-server enable traps snmp authentication coldstart warmstart
snmp-server enable traps config
snmp-server enable traps syslog
snmp-server host xyz bla
But I can´t see any restrctions here.... it´s a pretty simple config?!
Best Regards
Sebastian Rösch
-----Ursprüngliche Nachricht-----
Von: Jeroen van Ingen [mailto:[email protected]]
Gesendet: Montag, 23. November 2015 12:16
An: [email protected]
Betreff: Re: [Netdisco] Macsuck not possible on Cisco 2918 Switch
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 ---
On 17/11/15 08:44, Chenjie (Jacy, Enterprise Romania GTAC) wrote:
> Hello Alan,
>
> Please be informed that we tried to contact support from Netdisco but
> nobody reply us,
Did you sign into the mailing list before trying to send a message to
it? https://lists.sourceforge.net/lists/listinfo/netdisco-users
Your message was posted to the list by the amdinistrator after it hit
his reject mailbox as a non-member posting.
I have seen at least one reply to your message, requesting more
information.
If you do not join the list you will not see any followups.
> I am wondering if you have any other ways to contact
> them since we are not familiar with this Netdisco company.
Netdisco is not a company.
The software is produced and maintained by volunteers.
> 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.
>
> cid:[email protected]
>
> 1.The implementation of LLDP on Huawei device is according to the
> protocol “802.1AB-2005”, The LLDP MIB description is as follows:
>
> cid:[email protected]
>
> cid:[email protected]
>
> 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；
>
> cid:[email protected]
>
> 3.According to protocol, “lldpRemPortId” is the remote port that this
> device connects to.
>
> “lldpRemPortId” is string type:
>
> cid:[email protected]
>
> 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” representsGE2/0/19 “, and “47.45.32.2f.30.2f.31.39”
> representsG.E.2./.0./.19.
>
> lldpRemPortId.169046155.115.1 = 34.30.47.45.31.2f.30.2f.32
>
--- End Message ---
--- Begin Message ---
Hello Alan,
Fortunately , we received their reply yesterday and they asked us to provide
more information for analysis. And we have sent them the required information
to them today, hope we can receive their analysis result soon.
Best regards,
陈 杰 Jacy
EU Support Center
HUAWEI European Enterprise Business Group
E-mail: [email protected]<mailto:[email protected]>
Tel: +80 03 38 88 888 (for West Europe)
+80 07 77 78 899 (for Poland/Norway/Sweden)
+40 31 22 61 900 / +40 31 22 61 907 / +40 31 22 61 909 /
+40 31 22 91 238 (for all EU countries)
Address: The Lake View 301-311 Barbu Vacarescu Boulevard,
2nd district, 020276 Bucharest Romania
enterprise.huawei.com<https://email-uk.huawei.com/owa/UrlBlockedError.aspx>
[cid:[email protected]]<https://email-uk.huawei.com/owa/UrlBlockedError.aspx>
[cid:[email protected]] <http://www.weibo.com/hwenterprise>
[cid:[email protected]]
<http://www.linkedin.com/groups/Huawei-Enterprise-4070523>
[cid:[email protected]]
<https://email-uk.huawei.com/owa/UrlBlockedError.aspx>
[cid:[email protected]]
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive this
e-mail in error, please notify the sender by phone or email immediately and
delete it!
-----Original Message-----
From: Alan Brown [mailto:[email protected]]
Sent: 2015年11月24日 18:13
To: Chenjie (Jacy, Enterprise Romania GTAC)
Cc: Zhaoshaoqi; Zoujing (Jingo Zou, DCLMT); Wuwei (Bryan); Zhangyuanyuan (D);
[email protected]
Subject: Re: The connected device information is incorrect on Netdisco.
On 17/11/15 08:44, Chenjie (Jacy, Enterprise Romania GTAC) wrote:
> Hello Alan,
>
> Please be informed that we tried to contact support from Netdisco but
> nobody reply us,
Did you sign into the mailing list before trying to send a message to it?
https://lists.sourceforge.net/lists/listinfo/netdisco-users
Your message was posted to the list by the amdinistrator after it hit his
reject mailbox as a non-member posting.
I have seen at least one reply to your message, requesting more information.
If you do not join the list you will not see any followups.
> I am wondering if you have any other ways to contact them since we are
> not familiar with this Netdisco company.
Netdisco is not a company.
The software is produced and maintained by volunteers.
> Many thanks！
>
> Best regards,
>
> Jacy,
>
> *From:*Zhangyuanyuan (D)
> *Sent:* Wednesday, November 11, 2015 9:46 AM
> *To:*
> [email protected]<mailto:[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.
>
> cid:[email protected]
>
> 1.The implementation of LLDP on Huawei device is according to the
> protocol “802.1AB-2005”, The LLDP MIB description is as follows:
>
> cid:[email protected]
>
> cid:[email protected]
>
> 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；
>
> cid:[email protected]
>
> 3.According to protocol, “lldpRemPortId” is the remote port that this
> device connects to.
>
> “lldpRemPortId” is string type:
>
> cid:[email protected]
>
> 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” representsGE2/0/19 “, and “47.45.32.2f.30.2f.31.39”
> representsG.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
