Wrong topology: inexistent LAG connection displayed

[fbessone]

Hi all,

I have an issue with CBD 2.9: i have some cbs 350 stacks with an fiber optic Alcatel switch which delivers the LAG connections to the stacks.

The topology displays all the switches, however it displays also an inexistent LAG connection as you can see from the picture i attach: it existed months ago as a temporar connection.

I see the LLDP neighbors correcly and CDP, between the 2 CBS350-48FP-4X, is corrrecly empty, since they are only connected through the Alcatel switch.

I tried a rediscovery through a Scheduled Profile in the switch subnet with no success: how can i reset the wrong displayed connection?

Thanks

 

[Flavio Miranda]

@fbessone 

 Did you remove the device and then rediscovered?

[fbessone]

Not yet, I hoped there was a way to make it read the info again. Removing one device should not be enoguh, i'd probably have to remove/rejoin both of them from/to the CBD

[Flavio Miranda]

That´s something I would try.

[fbessone]

Well i have disconnected/reconnected both of them with no success; also tried the "reset connection" button

[clarkwa]

Cloud you show the CDP table of this two CBS350-48FP-4X for me?

[fbessone]

Hi,

thanks for reaching out

First switch:

TO-ArmB#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater, P - VoIP Phone
M - Remotely-Managed Device, C - CAST Phone Port,
W - Two-Port MAC Relay

Device ID Local Adv Time To Capability Platform Port ID
Interface Ver. Live
------------------ ----------- ---- ------- ---------- ------------ -----------

TO-ArmB#

Second switch:

TO-ArmE#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater, P - VoIP Phone
M - Remotely-Managed Device, C - CAST Phone Port,
W - Two-Port MAC Relay

Device ID Local Adv Time To Capability Platform Port ID
Interface Ver. Live
------------------ ----------- ---- ------- ---------- ------------ -----------

TO-ArmE#

[Mark Fang]

It seems that the issue you're experiencing is likely a bug in CBD's handling of neighbor data for third-party devices. I've reported this problem to the CBD production team for further investigation. Will keep you updated once we receive any feedback or a resolution from them.

[Mark Fang · Accepted solution]

Please update your CBD server to version 2.9.1. This latest release includes improvements in topology discovery, which may resolve the problem. After updating, please allow up to 20 minutes for the system to refresh and remove any stale links.

[fbessone]

Hi Mark,

yes, I confirm!!

Thanks