cancel
Showing results for 
Search instead for 
Did you mean: 

EXOS X440G2-48p-10G4 ELRP Loop on restart

EXOS X440G2-48p-10G4 ELRP Loop on restart

derrm
New Contributor

Hello,

I have a Switch which does detect a ELRP Loop on different VLANs. 
it happens on every reboot, strangely enough after i enable the Ports manually it works like a charm.
Its a L2 LAG on P45 and P46. Both ports are taken down. 

ELRP detects a loop on P45 on several VLANs.
I used Advanced IP Scanner to detect multiple Mac adresses on those VLANs i didnt find any.

Well since it works now it cant be a loop. ELRP would have taken them down again after i enabled them i think.

But well i dont know why it always detects one after a restart.

Are there any procedures to detect loops as fast as possible?

Thanks in advance

 

 

1 ACCEPTED SOLUTION

albert64chase
New Contributor

This behavior typically occurs during boot-up because ELRP transmits test packets before the L2 LAG (P45/P46) and spanning tree protocols have fully converged across both links, causing the switch to mistake its own transient, uncoordinated frame propagation for a loop. To prevent these false positives while keeping fast detection active, configure a boot-up delay or hold-timer for ELRP or the affected ports so that loop monitoring only initializes after the LAG links are fully up and stable.

View solution in original post

3 REPLIES 3

larson096vikky
New Contributor

Hello, I think this could be a startup timing issue with the LAG. I’d check the LAG configuration on both ends, VLAN membership, and ELRP settings, and review the switch logs around reboot time.

albert64chase
New Contributor

This behavior typically occurs during boot-up because ELRP transmits test packets before the L2 LAG (P45/P46) and spanning tree protocols have fully converged across both links, causing the switch to mistake its own transient, uncoordinated frame propagation for a loop. To prevent these false positives while keeping fast detection active, configure a boot-up delay or hold-timer for ELRP or the affected ports so that loop monitoring only initializes after the LAG links are fully up and stable.

That was the problem.

Thank you.

GTM-P2G8KFN