S-MLT painful, same i-sids on both members reqd

jeronimo — Thu, 21 Aug 2025 09:41:57 GMT

I am aware of documents like
https://extreme-networks.my.site.com/ExtrArticleDetail?an=000083230

which says: "All VLANs, with an I-SID assigned, must be configured on both the local and the remote vIST peer"

Turns out however that i-sid declaration on both members must be the same even if you use ELAN and Flex-Unis.

But I wonder why this configuration cannot simply be synchronized between members?

I.e. if I declare i-sid X on member 1, if member 2 is its partner, and it requires the i-sid to be declared in order for forwarding to work, then why doesn't the control protocol just instruct it to do so?
Instead of me meticulously comparing tables each time...

Is there a scenario in which you would not declare the i-sid on both peers?

Just a thought...

Re: S-MLT painful, same i-sids on both members reqd

RobertD1 — Fri, 22 Aug 2025 09:59:59 GMT

Point to Point connections or brouter ports would not require an I-SID.

topic S-MLT painful, same i-sids on both members reqd in ExtremeSwitching (VSP/Fabric Engine)

S-MLT painful, same i-sids on both members reqd

Re: S-MLT painful, same i-sids on both members reqd