1 / 11

ENNI Protection

M Vinod Kumar Tejas Networks Ltd. ENNI Protection. Agenda. E xample Requirements Possible solutions. Some ENNI Topologies. O. =. |8|. 8. Topology. Op#1 L2 Service Customer. Op#1 L2 Service Customer. ENNI. Operator 1 L2 Network. Operator 2 L2 Leased Line. Work. C1. C2.

nigel
Download Presentation

ENNI Protection

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. M Vinod Kumar Tejas Networks Ltd ENNI Protection

  2. Agenda • Example • Requirements • Possible solutions

  3. Some ENNI Topologies O = |8| 8

  4. Topology Op#1 L2 Service Customer Op#1 L2 Service Customer ENNI Operator 1 L2 Network Operator 2 L2 Leased Line Work C1 C2 Carrier Ethernet/ EoSDH Carrier Ethernet/ EoSDH Protect Rail-Tel Op#1 wants p2p L2VPN from C1 to C2 Op#1leases L2 service from Op#2 ENNI Protection issue

  5. Requirement 1 Op#1 L2 Service Customer Op#1 L2 Service Customer ENNI Operator 1 L2 Network Operator 2 L2 Leased Line Work C1 C2 Carrier Ethernet/ EoSDH Carrier Ethernet/ EoSDH Protect Fault Notification • Working-ENNI fails  traffic switches to protection-ENNI • Protection-ENNI could be defined over the 4 topologies mentioned

  6. Requirement 2 Op#1 L2 Service Customer Op#1 L2 Service Customer ENNI Operator 1 L2 Network Operator 2 L2 Leased Line Work C1 C2 Carrier Ethernet/ EoSDH Carrier Ethernet/ EoSDH Protect Fault Notification Fault within the operator cloud may lead to ENNI protection

  7. Requirement 3 Op#1 L2 Service Customer Op#1 L2 Service Customer ENNI Operator 1 L2 Network Operator 2 L2 Leased Line C1 C2 Work Carrier Ethernet/ EoSDH Carrier Ethernet/ EoSDH Protect Carrier Frames No change to the customer frames Customer Frames

  8. Requirements • If working-ENNI fails then traffic be switched to the protection-ENNI • Protection-ENNI may share zero, one or two terminal bridges with working-ENNI • Fault notification may be sent to one or both operators • Fault within the operator cloud may lead to traffic movement from working-ENNI to protection-ENNI • Example: when the node bridging MTNL and working-ENNI fails • Fault notification be sent towards ENNI or the peering operator • No change to the customer frames • Provider identifiers like S-VLAN, B-VLAN, TESI-ID, etc. may change at the ENNI from provider to provider

  9. Possible solutions • Enhancing PBB-TE with • Open-jaw • Alarm Indication Signal (AIS) in CFM • SPB • Load sharing using ECT at ENNI (works for specific topology ‘8’ of ENNI) • New idea if and only if we cannot enhance the existing technology

  10. Closing • Request for bringing a new PAR

  11. Thank You

More Related