Ethernet Automatic Protection Switching: Difference between revisions
No edit summary |
m unpiped links using script |
||
| (29 intermediate revisions by 23 users not shown) | |||
| Line 1: | Line 1: | ||
{{Short description|Ethernet fault-tolerance technique}} |
|||
'''Ethernet Automatic Protection Switching''' ('''EAPS''') is used to create a fault tolerant [[network topology|topology]] by configuring a primary and secondary path for each [[ |
'''Ethernet Automatic Protection Switching''' ('''EAPS''') is used to create a fault tolerant [[network topology|topology]] by configuring a primary and secondary path for each [[VLAN]]. |
||
Invented by [[Extreme Networks]] and submitted to IETF as RFC3619. The idea is to provide highly available Ethernet switched rings (commonly used in [[Metro Ethernet]]) to replace legacy TDM based transport protection fiber rings. Other implementations include '''Ethernet Protection Switching Ring''' ('''EPSR''')<ref>{{Cite web |url=http://alliedtelesis.com/media/fount/how_to_note_alliedware_plus/howto_aw_plus__config_epsr1.pdf |title=How to configure EPSR |access-date=2013-09-10 |archive-url=https://web.archive.org/web/20130624211315/http://www.alliedtelesis.com/media/fount/how_to_note_alliedware_plus/howto_aw_plus__config_epsr1.pdf |archive-date=2013-06-24 |url-status=dead }}</ref> by [[Allied Telesis]] which enhanced EAPS to provide full protected transport of IP Triple Play services (voice, video and internet traffic) for xDSL/FTTx deployments. EAPS/EPSR is the most widely deployed Ethernet protection switching solution deployed with major multi-vendor inter-operability support. The EAPS/EPSR are the basis of the ITU G.8032 Ethernet Protection recommendation. |
|||
== Operation == |
== Operation == |
||
A ring is formed by configuring a Domain. Each domain has a single "master node" and many "transit nodes". Each node will have a primary port and a secondary port, both known to be able to send control traffic to the master node. Under normal operation |
A ring is formed by configuring a Domain. Each domain has a single "master node" and many "transit nodes". Each node will have a primary port and a secondary port, both known to be able to send control traffic to the master node. Under normal operation, the secondary port on the master is blocked for all protected vlans. |
||
When there is a link down situation, the devices that detect the failure send a control message to the master, and the master will then unblock the secondary port and instruct the transits to flush their databases. The next packets sent by the network can then be flooded and learned out of the (now enabled) secondary port without any network disruption. |
When there is a link down situation, the devices that detect the failure send a control message to the master, and the master will then unblock the secondary port and instruct the transits to flush their forwarding databases. The next packets sent by the network can then be flooded and learned out of the (now enabled) secondary port without any network disruption. |
||
Fail-over times are demonstrably in the region of 50ms. |
Fail-over times are demonstrably in the region of 50ms. |
||
| Line 14: | Line 15: | ||
== EAPS v2 == |
== EAPS v2 == |
||
EAPSv2 is configured and enabled to avoid the potential of super-loops in environments where multiple EAPS domains share a common link. EAPSv2 works using the concept of a controller and partner mechanism. Shared port status is verified using health |
EAPSv2 is configured and enabled to avoid the potential of super-loops in environments where multiple EAPS domains share a common link. EAPSv2 works using the concept of a controller and partner mechanism. Shared port status is verified using health [[protocol data unit|PDU]]s exchanged by controller and partner. When a shared link goes down, the configured Controller will open only one segment port for each of the protected VLANs, keeping all other segment ports in a blocking state. This state is maintained as long as the Controller fails to receive the health PDUs over the (broken) shared link. |
||
Although not supported by Extreme Networks, it is possible to complete this shared link with non-EAPS (but tag-aware) switches between the Controller and Partner. |
Although not supported by Extreme Networks, it is possible to complete this shared link with non-EAPS (but tag-aware) switches between the Controller and Partner. |
||
| Line 22: | Line 23: | ||
== See also == |
== See also == |
||
* [[Rapid Spanning Tree Protocol]] |
* [[Rapid Spanning Tree Protocol]] |
||
* [[ |
* [[Ethernet Ring Protection Switching]] |
||
== References == |
== References == |
||
{{reflist}} |
{{reflist}} |
||
| ⚫ | * [http://etrij.etri.re.kr/Cyber/servlet/BrowseAbstract?vol=31&num=5&pg=631 Kwang-Koog Lee, Jeong-dong Ryoo, and Seungwook Min, "An Ethernet Ring Protection Method to Minimize Transient Traffic by Selective FDB Advertisement," ETRI Journal, vol.31, no.5, Oct. 2009, pp.631-633] |
||
== Further reading == |
|||
| ⚫ | |||
| ⚫ | * [http://etrij.etri.re.kr/Cyber/servlet/BrowseAbstract?vol=31&num=5&pg=631 Kwang-Koog Lee, Jeong-dong Ryoo, and Seungwook Min, "An Ethernet Ring Protection Method to Minimize Transient Traffic by Selective FDB Advertisement," ETRI Journal, vol.31, no.5, Oct. 2009, pp.631-633] {{Webarchive|url=https://web.archive.org/web/20110721003043/http://etrij.etri.re.kr/Cyber/servlet/BrowseAbstract?vol=31&num=5&pg=631 |date=2011-07-21 }} |
||
| ⚫ | * [https://web.archive.org/web/20100601084448/http://etrij.etri.re.kr/Cyber/Download/PublishedPaper/3202/etrij.apr2010.0184.pdf Kwang-Koog Lee, and Jeong-dong Ryoo, "Flush Optimizations to Guarantee Less Transient Traffic in Ethernet Ring Protection," ETRI Journal, vol.32, no.2, Apr. 2010, pp.184-194] |
||
== External links == |
== External links == |
||
* RFC 3619 (EAPS) |
* RFC 3619 (EAPS) |
||
* [http://www.itu.int/rec/T-REC-G.8031 |
* [http://www.itu.int/rec/T-REC-G.8031/en ITU-T G.8031/Y.1342] |
||
* [http://www.alliedtelesis.com/documents/epsr-feature-overview-and-configuration-guide EPSR Feature Overview and Configuration Guide] |
|||
[[Category:Ethernet]] |
[[Category:Ethernet|Automatic Protection Switching]] |
||
[[Category:Network protocols]] |
[[Category:Network protocols]] |
||
{{computer-stub}} |
|||
[[pt:Ethernet Automatic Protection Switching]] |
|||
Latest revision as of 14:59, 8 August 2024
Ethernet Automatic Protection Switching (EAPS) is used to create a fault tolerant topology by configuring a primary and secondary path for each VLAN.
Invented by Extreme Networks and submitted to IETF as RFC3619. The idea is to provide highly available Ethernet switched rings (commonly used in Metro Ethernet) to replace legacy TDM based transport protection fiber rings. Other implementations include Ethernet Protection Switching Ring (EPSR)[1] by Allied Telesis which enhanced EAPS to provide full protected transport of IP Triple Play services (voice, video and internet traffic) for xDSL/FTTx deployments. EAPS/EPSR is the most widely deployed Ethernet protection switching solution deployed with major multi-vendor inter-operability support. The EAPS/EPSR are the basis of the ITU G.8032 Ethernet Protection recommendation.
Operation
[edit]A ring is formed by configuring a Domain. Each domain has a single "master node" and many "transit nodes". Each node will have a primary port and a secondary port, both known to be able to send control traffic to the master node. Under normal operation, the secondary port on the master is blocked for all protected vlans.
When there is a link down situation, the devices that detect the failure send a control message to the master, and the master will then unblock the secondary port and instruct the transits to flush their forwarding databases. The next packets sent by the network can then be flooded and learned out of the (now enabled) secondary port without any network disruption.
Fail-over times are demonstrably in the region of 50ms.
The same switch can belong to multiple domains and thus multiple rings. However, these act as independent entities and can be controlled individually.
EAPS v2
[edit]EAPSv2 is configured and enabled to avoid the potential of super-loops in environments where multiple EAPS domains share a common link. EAPSv2 works using the concept of a controller and partner mechanism. Shared port status is verified using health PDUs exchanged by controller and partner. When a shared link goes down, the configured Controller will open only one segment port for each of the protected VLANs, keeping all other segment ports in a blocking state. This state is maintained as long as the Controller fails to receive the health PDUs over the (broken) shared link.
Although not supported by Extreme Networks, it is possible to complete this shared link with non-EAPS (but tag-aware) switches between the Controller and Partner.
When the shared link is restored, the Controller can then unblock its ports, the masters will see their hello packets, and the rings will be protected by their respective masters.
See also
[edit]References
[edit]- ^ "How to configure EPSR" (PDF). Archived from the original (PDF) on 2013-06-24. Retrieved 2013-09-10.
Further reading
[edit]- Kwang-Koog Lee, Jeong-dong Ryoo, and Seungwook Min, "An Ethernet Ring Protection Method to Minimize Transient Traffic by Selective FDB Advertisement," ETRI Journal, vol.31, no.5, Oct. 2009, pp.631-633 Archived 2011-07-21 at the Wayback Machine
- Kwang-Koog Lee, and Jeong-dong Ryoo, "Flush Optimizations to Guarantee Less Transient Traffic in Ethernet Ring Protection," ETRI Journal, vol.32, no.2, Apr. 2010, pp.184-194
External links
[edit]- RFC 3619 (EAPS)
- ITU-T G.8031/Y.1342