Eaps design
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-30-2017 07:18 AM
Hi
In your opinion, how many nodes can I use in single domain, about 20 still will be ok? I knoiw that in theory eaps doesn't have limnitations.
Regards
In your opinion, how many nodes can I use in single domain, about 20 still will be ok? I knoiw that in theory eaps doesn't have limnitations.
Regards
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎09-04-2017 09:36 AM
Hi Pawel,
Here is one interesting discussing about EAPS design.
https://community.extremenetworks.com/extreme/topics/need-some-help-witch-eaps-rings-design
Best regards,
Bin
Here is one interesting discussing about EAPS design.
https://community.extremenetworks.com/extreme/topics/need-some-help-witch-eaps-rings-design
Best regards,
Bin
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-31-2017 08:10 PM
We try to keep ours to ten or less for reason number one... Our core which is 12 switches is the exception because several of the nodes are a pair of 8900's setting side by side... At 80 to 90 k mac tables with about 2500 active tag ids on 25 or 30 EAPS rings in the core we still get sub 150ms fail over... flaps hurt though
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎08-30-2017 05:14 PM
Pawel, EAPS does not impose a limitation in the number of nodes in a ring, but there are two factors that you should bear in mind:
- EAPS, being a ring topology, will survive to ONE failure. If a second failure occurs, you will lose connectivity. The larger the number of nodes (and links), the higher the probability of having two or more failures.
- When a failure is detected (or cleared) the Master switch will send a "Flush-FDB" message through the control vlan. When a Transit node receives this message it flushes its MAC table to relearn the new topology, and retransmits the message to the next switch in the ring. If you have a lot of switches in the ring, the time it takes for the ring to re-converge (that is, the time it takes for all the switches to flush their FDB and re-learn the topology) grows.
