Eaps blocking secondary port on common link unwanted

[42_101010]

Hey everyone,

We are stuck with a nasty problem after our shared link got down by a fiber cut. Over this shared link are going multiple eaps rings. And after the fiber cut we try to enable the link again but the port on the transit switch of the shared link keeps the vlans on this port blocked.

The shared link is between sw1 via port 57 connected to port 57 on sw2

Sw1 Master switches for most rings except 1 Port 57 is the primary port for the rings link but has partner mode for shared link

Sw2 Transit switch Port 57 is secondary port for the rings and is controller for this shared link and when enable keeps blocking the vlans on this port.

Looks like Enable log debug-mode doesn’t give enough hints.

Tips how to further troubleshooting this or ideas what can be the cause are more than welcome at this moment.

Thnx!

[42_101010]

Thanks for your reply, Stachal! I didn't test it outside our production equipment. But there were no errors on the link and checking fdb on port 57 showed mac addresses of the eaps control vlans. Also, I was able to test it with an extra vlan outside eaps. So without eaps, the connection works fine. 

[Stachal · Accepted solution]

Have you tested the newly repaired link outside of your production equipment?  Possible the repaired splice is bad or cross spliced and you have physical layer issues. How do the counters look on both links? Any CRC errors?