cancel
Showing results for 
Search instead for 
Did you mean: 

Manage L1 ring topology in FABRIC/EXOS STACK/Third party LAN

Manage L1 ring topology in FABRIC/EXOS STACK/Third party LAN

SebBinet
New Contributor

Hello,

We're currently migrating a customer with a network based on many little ring topology (2 or 3 switches ringed to an HP IRF square core)

The new design is based an four FABRIC engine device (5520) in square topology as core with some SMLT attached 4220 stacks where are ''ringed'' the other switches then going back to the FABRIC.

Here is a quick diagram:

[FABRIC]--->SMLT--->[EXOS STACK]<--->[OLD HPE STACK]<--->[FABRIC]

Usually in ring topology, I was using STP in mixed constructor environnement or ERLP on full EXOS, but in this case, I cannot use STP, because SMLT doesn't support it, nor ERLP because 4220 doesn't support it.

The only remaining feature I can think of is SLPP, but SLPP isn't ''designed'' to managed ring topology but accidental loop occurring. SLPP GUARD can disable a port but at the end of the timer a loop occurs again with packet loss before SLPP Guard detect the loop again. Permanently disable the port with (or without) SLPP Guard isn't an option because the customer loose the ''benefit'' of the ring for resiliency.

So I'm kind of stuck to find a solution here.

I was hoping running full fabric network with 4220 in Fabric Engine, but it seems they don't support it.

Is anyone have a solution to this problem ?

Thanks, Regards

1 REPLY 1

SebBinet
New Contributor

Added a diagram with the different ring topology for this customer (sorry for the french commentary on the diagram)
I can't find a solution with the two first diagrams and can deal with the third with STP as mentioned in the first post.

GTM-P2G8KFN