XMC with 3rd Party Switched not showing LLDP on MAP

[Andre_Brits_Kan]

Hi Community

I am in the process of adding 3rd party switched (ALU) to XMC.
XMC is not drawing the links between the 3rd party switches.

However if I connect the 3rd party switches to an x440 then I do see the links auto discovered.
When I connect the 3rd party switches directly I do not see the links.

My lab looks as follows:

Switch "test6460" (IP 10.76.131.22) connects to "test6860" (IP 10.76.130.15) on port 1/47
Switch "test6860 (IP 10.76.130.15) connects to "test6460" (IP 10.76.131.22) on port 1/1/48


I have gather the following info:

1. LLDP Flex view for the 3rd Party devices - show the LLDP neighbors with all the info

2. I have also done the XMC link diag :

The output from the diag looks as follows:

VERIFY INPUT:

First Device: found by IP address
First Device: DeviceEntityData - 10.76.130.15 [60 Ports] [3 Children]
First Port: found by ifName
First Port: [10.76.130.15] Port 1/1/48
----------------------------------------
Second Device: found by IP address
Second Device: DeviceEntityData - 10.76.131.22 [53 Ports] [3 Children]
Second Port: found by ifName
Second Port: [10.76.131.22] Port 1/47
-- SUCCESS --

EXISTING LINK DATA:

Link not found
Summary: The system has no information about links on the specified ports.

EXISTING NEIGHBOR DATA:

First Port current neighbor information: {--, --, --, --, --, --, --}
First Port last known neighbor information: {--, --, --, --, --, --, --}
First Port: No current neighbor information, using last known neighbor.
First Port: no discovery protocol noted for neighbor information
First Port: No last known neighbor device information, cannot resolve any link.
----------------------------------------
Second Port current neighbor information: {--, --, --, --, --, --, --}
Second Port last known neighbor information: {--, --, --, --, --, --, --}
Second Port: No current neighbor information, using last known neighbor.
Second Port: no discovery protocol noted for neighbor information
Second Port: No last known neighbor information, cannot resolve any link.
Summary: there is not sufficient neighbor information to resolve the link

LLDP INFORMATION RETRIEVED FROM DEVICES:

First Device: SNMP retrieved lldpStatsRemTablesLastChangeTime: 0:1:50:39.00
First Device: LLDP is supported
First Device: SNMP retrieved LLDP data for 4 ports
19> 1019 [local] --> 8C:EC:4B:07:38:12 [macAddress] : 8c??4b:07:38:12 [macAddress], capabilities='00'
23> 1023 [local] --> 8C:EC:4B:07:38:12 [macAddress] : 8c??4b:07:38:12 [macAddress], capabilities='00'
47> 1047 [local] --> 00:04:96:A2:04:84 [macAddress] : 22 [interfaceName], capabilities='20'
48> 1048 [local] --> 2C:FA:A2:CF:E0:BA [macAddress] : 1047 [local], capabilities='28', description='Alcatel-Lucent Enterprise 1/47'
First Device: no LLDP data found for First Port.
Summary: the absence of LLDP information is reflected in the neighbor data for First Port.
----------------------------------------
Second Device: SNMP retrieved lldpStatsRemTablesLastChangeTime: 0:0:18:11.73
Second Device: LLDP is supported
Second Device: SNMP retrieved LLDP data for 1 ports
47> 1047 [local] --> 2c:fa:a2:d1:90:bd [macAddress] : 1048 [local], capabilities='28', description='Alcatel-Lucent OS6860 GNI 1/1/48'
Second Device: no LLDP data found for Second Port.
Summary: the absence of LLDP information is reflected in the neighbor data for Second Port.

So reading the above correctly XMC does see the link.

Any comments??

[Zdeněk_Pala · Accepted solution]

Hi,

the map can draw your link if:

• the link is discovered correctly from both ends
• the link is discovered correctly from one end and other end does not support discovery

The map will not draw your link if:

• none of devices support correctly LLDPmib, EDP, SONMP, CDP (Cabletron Discovery Protocol)
• one device does report the link and the other does report conflict

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

Regards