<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: XMC with 3rd Party Switched not showing LLDP on MAP in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/xmc-with-3rd-party-switched-not-showing-lldp-on-map/m-p/82887#M9111</link>
    <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
the map can draw your link if:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;the link is discovered correctly from both ends 
&lt;/LI&gt;&lt;LI&gt;the link is discovered correctly from one end and other end does not support discovery 
&lt;/LI&gt;&lt;/UL&gt;
The map will not draw your link if:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;none of devices support correctly LLDPmib, EDP, SONMP, CDP (Cabletron Discovery Protocol) 
&lt;/LI&gt;&lt;LI&gt;one device does report the link and the other does report conflict 
&lt;/LI&gt;&lt;/UL&gt;
The fact the switch does support LLDP does not mean the switch does support LLDPmib. My experience with ALU: ALU switches does not support LLDPmib as of May 2019&lt;BR /&gt;
&lt;BR /&gt;
Regards</description>
    <pubDate>Fri, 31 May 2019 04:35:29 GMT</pubDate>
    <dc:creator>Zdeněk_Pala</dc:creator>
    <dc:date>2019-05-31T04:35:29Z</dc:date>
    <item>
      <title>XMC with 3rd Party Switched not showing LLDP on MAP</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/xmc-with-3rd-party-switched-not-showing-lldp-on-map/m-p/82886#M9110</link>
      <description>Hi Community&lt;BR /&gt;
&lt;BR /&gt;
I am in the process of adding 3rd party switched (ALU) to XMC.&lt;BR /&gt;
XMC is not drawing the links between the 3rd party switches.&lt;BR /&gt;
&lt;BR /&gt;
However if I connect the 3rd party switches to an x440 then I do see the links auto discovered.&lt;BR /&gt;
When I connect the 3rd party switches directly I do not see the links.&lt;BR /&gt;
&lt;BR /&gt;
My lab looks as follows:&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="1d6f5c2e41e446508cd28d3f77731bcd_a7b5ae37-24a4-4fdc-bf32-88d4decabc05.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/2926i56743F272ED2644C/image-size/large?v=v2&amp;amp;px=999" role="button" title="1d6f5c2e41e446508cd28d3f77731bcd_a7b5ae37-24a4-4fdc-bf32-88d4decabc05.png" alt="1d6f5c2e41e446508cd28d3f77731bcd_a7b5ae37-24a4-4fdc-bf32-88d4decabc05.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
Switch "test6460" (IP 10.76.131.22) connects to "test6860" (IP 10.76.130.15) on port 1/47&lt;BR /&gt;
Switch "test6860 (IP 10.76.130.15) connects to "test6460" (IP 10.76.131.22) on port 1/1/48&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
I have gather the following info:&lt;BR /&gt;
&lt;BR /&gt;
&lt;OL&gt; 
&lt;LI&gt;LLDP Flex view for the 3rd Party devices - show the LLDP neighbors with all the info 
&lt;/LI&gt;&lt;/OL&gt;&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="1d6f5c2e41e446508cd28d3f77731bcd_1bdc5f25-382f-4bc4-85fa-31dd0757d124.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/4117i1A628004CE233C70/image-size/large?v=v2&amp;amp;px=999" role="button" title="1d6f5c2e41e446508cd28d3f77731bcd_1bdc5f25-382f-4bc4-85fa-31dd0757d124.png" alt="1d6f5c2e41e446508cd28d3f77731bcd_1bdc5f25-382f-4bc4-85fa-31dd0757d124.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
2.	 I have also done the XMC link diag :&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="1d6f5c2e41e446508cd28d3f77731bcd_4c8f8837-9f83-43db-a449-4d5df206cf06.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/823i8D34FC9B6C90B9B2/image-size/large?v=v2&amp;amp;px=999" role="button" title="1d6f5c2e41e446508cd28d3f77731bcd_4c8f8837-9f83-43db-a449-4d5df206cf06.png" alt="1d6f5c2e41e446508cd28d3f77731bcd_4c8f8837-9f83-43db-a449-4d5df206cf06.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
The output from the diag looks as follows:&lt;BR /&gt;
&lt;BR /&gt;
VERIFY INPUT:&lt;BR /&gt;
&lt;BR /&gt;
First Device: found by IP address&lt;BR /&gt;
First Device: DeviceEntityData - 10.76.130.15 [60 Ports] [3 Children]&lt;BR /&gt;
First Port: found by ifName&lt;BR /&gt;
First Port: [10.76.130.15] Port 1/1/48&lt;BR /&gt;
----------------------------------------&lt;BR /&gt;
Second Device: found by IP address&lt;BR /&gt;
Second Device: DeviceEntityData - 10.76.131.22 [53 Ports] [3 Children]&lt;BR /&gt;
Second Port: found by ifName&lt;BR /&gt;
Second Port: [10.76.131.22] Port 1/47&lt;BR /&gt;
-- SUCCESS --&lt;BR /&gt;
&lt;BR /&gt;
EXISTING LINK DATA:&lt;BR /&gt;
&lt;BR /&gt;
Link not found &lt;BR /&gt;
Summary: The system has no information about links on the specified ports.&lt;BR /&gt;
&lt;BR /&gt;
EXISTING NEIGHBOR DATA:&lt;BR /&gt;
&lt;BR /&gt;
First Port current neighbor information: {--, --, --, --, --, --, --}&lt;BR /&gt;
First Port last known neighbor information: {--, --, --, --, --, --, --}&lt;BR /&gt;
First Port: No current neighbor information, using last known neighbor.&lt;BR /&gt;
First Port: no discovery protocol noted for neighbor information&lt;BR /&gt;
First Port: No last known neighbor device information, cannot resolve any link.&lt;BR /&gt;
----------------------------------------&lt;BR /&gt;
Second Port current neighbor information: {--, --, --, --, --, --, --}&lt;BR /&gt;
Second Port last known neighbor information: {--, --, --, --, --, --, --}&lt;BR /&gt;
Second Port: No current neighbor information, using last known neighbor.&lt;BR /&gt;
Second Port: no discovery protocol noted for neighbor information&lt;BR /&gt;
Second Port: No last known neighbor information, cannot resolve any link.&lt;BR /&gt;
Summary: there is not sufficient neighbor information to resolve the link&lt;BR /&gt;
&lt;BR /&gt;
LLDP INFORMATION RETRIEVED FROM DEVICES:&lt;BR /&gt;
&lt;BR /&gt;
First Device: SNMP retrieved lldpStatsRemTablesLastChangeTime: 0:1:50:39.00&lt;BR /&gt;
First Device: LLDP is supported&lt;BR /&gt;
First Device: SNMP retrieved LLDP data for 4 ports&lt;BR /&gt;
  19&amp;gt; 1019 [local] --&amp;gt; 8C:EC:4B:07:38:12 [macAddress] : 8c??4b:07:38:12 [macAddress], capabilities='00'&lt;BR /&gt;
  23&amp;gt; 1023 [local] --&amp;gt; 8C:EC:4B:07:38:12 [macAddress] : 8c??4b:07:38:12 [macAddress], capabilities='00'&lt;BR /&gt;
  47&amp;gt; 1047 [local] --&amp;gt; 00:04:96:A2:04:84 [macAddress] : 22 [interfaceName], capabilities='20'&lt;BR /&gt;
  48&amp;gt; 1048 [local] --&amp;gt; 2C:FA:A2:CF:E0:BA [macAddress] : 1047 [local], capabilities='28', description='Alcatel-Lucent Enterprise 1/47'&lt;BR /&gt;
First Device: no LLDP data found for First Port.&lt;BR /&gt;
Summary: the absence of LLDP information is reflected in the neighbor data for First Port.&lt;BR /&gt;
----------------------------------------&lt;BR /&gt;
Second Device: SNMP retrieved lldpStatsRemTablesLastChangeTime: 0:0:18:11.73&lt;BR /&gt;
Second Device: LLDP is supported&lt;BR /&gt;
Second Device: SNMP retrieved LLDP data for 1 ports&lt;BR /&gt;
  47&amp;gt; 1047 [local] --&amp;gt; 2c:fa:a2:d1:90:bd [macAddress] : 1048 [local], capabilities='28', description='Alcatel-Lucent OS6860 GNI 1/1/48'&lt;BR /&gt;
Second Device: no LLDP data found for Second Port.&lt;BR /&gt;
Summary: the absence of LLDP information is reflected in the neighbor data for Second Port.&lt;BR /&gt;
&lt;BR /&gt;
So reading the above correctly XMC does see the link.&lt;BR /&gt;
&lt;BR /&gt;
Any comments??</description>
      <pubDate>Mon, 25 Mar 2019 18:08:32 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/xmc-with-3rd-party-switched-not-showing-lldp-on-map/m-p/82886#M9110</guid>
      <dc:creator>Andre_Brits_Kan</dc:creator>
      <dc:date>2019-03-25T18:08:32Z</dc:date>
    </item>
    <item>
      <title>Re: XMC with 3rd Party Switched not showing LLDP on MAP</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/xmc-with-3rd-party-switched-not-showing-lldp-on-map/m-p/82887#M9111</link>
      <description>Hi,&lt;BR /&gt;
&lt;BR /&gt;
the map can draw your link if:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;the link is discovered correctly from both ends 
&lt;/LI&gt;&lt;LI&gt;the link is discovered correctly from one end and other end does not support discovery 
&lt;/LI&gt;&lt;/UL&gt;
The map will not draw your link if:&lt;BR /&gt;
&lt;UL&gt; 
&lt;LI&gt;none of devices support correctly LLDPmib, EDP, SONMP, CDP (Cabletron Discovery Protocol) 
&lt;/LI&gt;&lt;LI&gt;one device does report the link and the other does report conflict 
&lt;/LI&gt;&lt;/UL&gt;
The fact the switch does support LLDP does not mean the switch does support LLDPmib. My experience with ALU: ALU switches does not support LLDPmib as of May 2019&lt;BR /&gt;
&lt;BR /&gt;
Regards</description>
      <pubDate>Fri, 31 May 2019 04:35:29 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/xmc-with-3rd-party-switched-not-showing-lldp-on-map/m-p/82887#M9111</guid>
      <dc:creator>Zdeněk_Pala</dc:creator>
      <dc:date>2019-05-31T04:35:29Z</dc:date>
    </item>
  </channel>
</rss>

