Extreme Networks

Anonymous · 2 weeks ago

Hello community,

I would like to check if my understanding of Fabric Connect Scaling is correct.

Am I right with the following statements from the datasheets?

Fabric Connect Scaling
- Fabric Adjacencies per switch: Maximum number of directly connected fabric nodes
- BEB Nodes per VSN (I-SID): Maximum number of fabric nodes within a VSN
- L2 VSNs: Maximum number of L2 VSNs on the node
- L3 VSNs: Maximum number of L3 VSNs on the node

Furthermore, is it correct that the values of the smallest fabric node count?

1. Assuming there are only fabric nodes with 2000 BEB nodes per VSN and then a fabric node with a maximum of 500 BEB nodes per VSN is added. Then there can only be 500 nodes in this VSN, right?

2. If there is a fabric with nodes that can have 4000 L2 VSNs and a fabric node with a maximum of 512 L2 VSNs is added. Does this affect the other nodes which can have a maximum of 4000 L2 VSNs? Does this also fundamentally reduce them to 512 L2-VSNs or only to the specific L2-VSN as in point 1.?

Many thanks and best regards
Jan

Shaja · 2 weeks ago

Hi Jan

You probably need to reach your country SE they can explained that much better then I...

🙂

Let say we have a very big Enterprise or a ISP with 1000 sites or POPs.

In the local site you have some LAN switches with VLAN (100 200 300 400 500) and 2 fabric nodes.

You can use the same L2VNS but I think it will be much more elegant to mach L2VNS to the site ID.

Like that

Site 1 is Isid 1001 with vlan 100 200 300 400 500

Site 2 is Isid 1002 with vlan 100 200 300 400 500

ISPs

Every client could a Isid or every POP service like Internet Voip IPTV..

POP 1 ISID 1001 Internet

POP 1 ISID 1002 Voip

POP 1 ISID 1003 IPTv

Those ISID or services can run as E-TREE that great for security 🙂

View solution in original post

Phil_ · a week ago

Hi Jan,

1. Yes you are right, the weakest switch does limit the maximum number of nodes you can have. But you can solve this problem with the multi-area feature, which results in each area having a separate limit based on the weakest node in that specific area.

2. This is kinda tricky question, I would assume that it's not, I think that specific node would just stop detecting the i-sid or starts reporting a warning that the table is getting too big. But there is also the multi-area feature that can solve this problem.

Best regards,

Phil

Shaja · 2 weeks ago