1 / 26

Ethernet OAM Maintenance Entities in ITU-T Q.3/13

Ethernet OAM Maintenance Entities in ITU-T Q.3/13. Dinesh Mohan Paul Bottorff. Nortel Networks. OAM Layering . Ethernet Layer. Ethernet OAM Layering. Customer. Service Provider. Customer. Eth Access. MPLS Core. MPLS Access. Device View. CE. U-PE. B. B. N-PE. P. P. P. N-PE.

diella
Download Presentation

Ethernet OAM Maintenance Entities in ITU-T Q.3/13

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. Ethernet OAM Maintenance Entities in ITU-T Q.3/13 Dinesh Mohan Paul Bottorff Nortel Networks

  2. OAM Layering

  3. Ethernet Layer Ethernet OAM Layering Customer Service Provider Customer Eth Access MPLS Core MPLS Access Device View CE U-PE B B N-PE P P P N-PE P U-PE CE • An example to highlight network/service involving Ethernet and other technologies • The Ethernet Layer implies the visibility to Ethernet frames

  4. OAM Domain – Service/Network Customer Service Provider Customer Eth Access MPLS Core MPLS Access Customer Domain Provider Domain Operator Domain Operator Domain Operator Domain • Domains concept is necessary to contain OAM flows & bound OAM responsibilities

  5. Maintenance Entity Point Maintenance Intermediate Point Maintenance Entity Points (MEP) & Maintenance Intermediate Points (MIP) Customer Service Provider Customer Eth Access MPLS Core MPLS Access Customer Domain Service OAM Provider Domain Operator Domain Operator Domain Operator Domain Network OAM PW/MPLS OAM MPLS Domain MPLS Domain • Location of MEPs and MIPs is dependent on Business Models & Deployment Scenarios

  6. Services Service OAM Network Network OAM Transport Links Ethernet link OAM PW/MPLS OAM EoSONET OAM Other OAM Service/Network OAM – How does it come together? • OAM Interworking possible to utilize OAM across Layers • However, each layer must support OAM capabilities independently

  7. Q.3/13Maintenance Entity Points (MEP) & Maintenance Intermediate Points (MIP)

  8. CustomerEquipment Operator ABridges Operator BBridges CustomerEquipment ETH or SRV Networks using MEPs & MIPs 1 2 3 4 5 6 7 8 9 ETH Maintenance Entity Point Maintenance Intermediate Point • MEPs and MIPs used to identify Maintenance Entities (MEs) • MEs identifies what need to be managed

  9. Dual Relay Model as Single Integrated Provider Device

  10. CustomerEquipment Operator ABridges Operator BBridges CustomerEquipment 1 2a 2b 3 4 5 6b 6a 7 ETH MEP, MIP, TCP for Dual-Relay Model:Single Integrated Provider Device • 2a and 6a allow for peering of L2CP + multiplexing of user flows • Additional MEs may need to be managed

  11. Higher Layer Entities LLC LLC LLC LLC LLC LLC Relay 802.1Q Tagging “Y” 802.1Q Tagging “Y” 802.1ag Up CM Shim 802.1ag Up CM Shim 802.1ag Down CM Shim 802.1ag Down CM Shim MEP Customer Bridge 1Example without ETH link ME

  12. Relay Provider Bridge 2aExample without ETH link ME Higher Layer Entities LLC LLC LLC LLC LLC LLC 802.1Q Tagging “Y” 802.1Q Tagging “Y” 802.1ag Up CM Shim 802.1ag Up CM Shim 802.1ag Down CM Shim 802.1ag Down CM Shim MEP MIP MIP MEP

  13. Relay Provider Bridge 2bExample without ETH link ME Higher Layer Entities LLC LLC LLC LLC LLC LLC MEP 802.1Q Tagging “Y” 802.1Q Tagging “Y” 802.1ag Up CM Shim 802.1ag Up CM Shim 802.1ag Down CM Shim 802.1ag Down CM Shim MEP MIP MIP

  14. Dual Relay Model with Single Relay as Provider Device

  15. CustomerEquipment Operator ABridges Operator BBridges CustomerEquipment 1 2b 3 4 5 6b 7 MEP, MIP, TCP for Dual-Relay Model:Single Relay as Provider Device • 2b and 6b do not allow for peering of L2CP + single service per customer link • Additional MEs may be needed at Customer side

  16. Relay Customer Bridge 1Example without ETH link ME Higher Layer Entities LLC LLC LLC LLC LLC LLC 802.1Q Tagging “Y” 802.1Q Tagging “Y” 802.1ag Up CM Shim 802.1ag Up CM Shim 802.1ag Down CM Shim 802.1ag Down CM Shim MEP

  17. Relay Provider Bridge 2bExample without ETH link ME Higher Layer Entities LLC LLC LLC LLC LLC LLC MEP 802.1Q Tagging “Y” 802.1Q Tagging “Y” 802.1ag Up CM Shim 802.1ag Up CM Shim 802.1ag Down CM Shim 802.1ag Down CM Shim MEP MIP MIP

  18. Dual Relay Model with Bundling for Single Integrated Provider Device

  19. CustomerEquipment Operator ABridges Operator BBridges CustomerEquipment 1 2a 2b 3 4 5 6b 6a 7 11 12 21 22 11 12 C-Tag 21 22 ETH Untagged 10 S-Tag 20 MEP, MIP, TCP for Dual-Relay Model:Bundling - Single Integrated Provider Device C-Tag

  20. Relay MEP MEP MEP MEP Customer Bridge 1Example without ETH link ME - TBD Higher Layer Entities LLC LLC LLC LLC LLC LLC 802.1Q Tagging “Y” 802.1Q Tagging “Y” 802.1ag Up CM Shim 802.1ag Up CM Shim 802.1ag Down CM Shim 802.1ag Down CM Shim

  21. Relay Provider Bridge 2aExample without ETH link ME - TBD Higher Layer Entities LLC LLC LLC LLC LLC LLC 802.1Q Tagging “Y” 802.1Q Tagging “Y” 802.1ag Up CM Shim 802.1ag Up CM Shim 802.1ag Down CM Shim 802.1ag Down CM Shim MEP MEP MEP MEP MIP MIP MIP MIP

  22. Relay MIP Provider Bridge 2bExample without ETH link ME - TBD Higher Layer Entities LLC LLC LLC LLC LLC LLC 802.1Q Tagging “Y” 802.1Q Tagging “Y” MEP MEP 802.1ag Up CM Shim 802.1ag Up CM Shim 802.1ag Down CM Shim 802.1ag Down CM Shim MEP MEP MIP

  23. Dual Relay Model with Bundling for Single Relay as Provider Device

  24. CustomerEquipment Operator ABridges Operator BBridges CustomerEquipment 1 2b 3 4 5 6b 7 11 12 21 22 Untagged 10 S-Tag 20 ETH MEP, MIP, TCP for Dual-Relay Model:Bundling - Single Relay as Provider Device C-Tag

  25. Dual Relay Model with All-to-One Bundling for Single Relay as Provider Device

  26. CustomerEquipment Operator ABridges Operator BBridges CustomerEquipment 1 2b 3 4 5 6b 7 11 12 21 22 Untagged 10 S-Tag ETH MEP, MIP, TCP for Dual-Relay Model:All-to-One Bundling C-Tag

More Related