Extreme Fabric Connect Multiple Links

[Andre_Brits_Kan]

Hi Community

I am playing with some Fabric kit in my lab.
Below is the diagram of my fabric:

The question I have is regarding the redundant links (Indicated in Red).

My initial thought was that these links would become active and the backbone vlans would load balance odd and event i-sids across them.

I see that the ISIS adj is not formed across these links.

Is MLT required, or should these links become active paths for the fabric without requiring MLT?

Thx

[Ed_Uhler]

MLT if you desire to have traffic load-balance between these two nodes. Otherwise, one NNI link is active the other standby until the first link drops out.

[Tomasz]

Hi Andre,

What is the version of VOSS you have?
From what I remember, recently there should've been added support for redundant adjacencies that are established but kept dormant until needed.
MLT would be a good approach here, you would be able to fully benefit those links.

Oh, here: https://documentation.extremenetworks.com/release_notes/VOSS/9035336_ReleaseNoteVOSS_7.0_RN.pdf
"IS-IS parallel adjacencies between two nodes
This release supports multiple parallel adjacencies between the two nodes to provide link
redundancy. The switch selects the adjacency with the shortest path as the active adjacency.
Note:
IS-IS parallel adjacency support is enabled by default, and it cannot be disabled.
For more information, see Configuring Fabric Basics and Layer 2 Services"
If I'm not wrong, you could be satisfied with that. Personally I would go to MLT though.

Hope that helps,
Tomasz