• Japanese
  • Korean
  • Chinese
Cover Image

Ethernet OAM Market Trends & Case Studies

As carrier Ethernet has become an increasingly primary, business-class global data service defined by service-level agreements (SLAs) and offering differentiated classes of service (CoS), tools to monitor and measure service quality have become increasingly crucial. The last few years have seen increased and improved global interconnection with CoS and development of service operations, administration and maintenance (OAM) protocols and tools with the concomitant associated potential for speeding service provisioning, improving network and service management, facilitating fault detection and resolution, and improving visibility into Ethernet service performance end-to-end across networks.

While there are varying definitions of the specific borders of the Ethernet OAM (EOAM) domain, it broadly refers to protocols and related tools and messages by which Ethernet service problems, or "faults," can be monitored and resolved, and by which performance parameters such as packet delay, jitter, loss and throughput can be systematically measured.

The rapid growth of carrier Ethernet services - and particularly Ethernet's increasingly dominant role in wireless backhaul - have greatly intensified requirements for, and widespread interest in, Ethernet OAM.

‘Ethernet OAM Market Trends & Case Studies’ examines the major protocols driving EOAM and their place in the current market environment. It analyzes the current status of EOAM including obstacles to its fuller deployment, and projects its future role in the delivery of carrier Ethernet services. The report also offers seven case studies of carrier Ethernet service providers in their efforts to deploy EOAM, providing insight into how network operators are dealing with EOAM.

Heavy Reading conducted in-depth interviews with senior executives and marketing and network professionals from 12 major market players, including vendors that sell OAM capabilities and carriers that purchase and deploy them. In several cases, we conducted multiple interviews with these firms, in most cases speaking with two, three or more expert informants per company. Based on these discussions, the report incorporates seven detailed case studies tracing service provider implementation of EOAM and related capabilities worldwide.

The ITU-T's Y.1731 protocol is the most advanced and comprehensive of the three major EOAM protocols, with the greatest future promise and importance, as well as the lowest level of deployment thus far. Y.1731's biggest distinctive contribution is that of performance management, facilitating measurement of Ethernet frame loss, latency, jitter and other parameters. The excerpt below schematically illustrates performance management.

Excerpt 1: Performance Management

Source: Metro Ethernet Forum

Ethernet Local Management Interface (E-LMI) is another protocol that has not yet experienced very wide deployment. It is analogous to LMI in Frame Relay and enables customer equipment to request and receive information about service status and other Ethernet service attributes from carrier devices, enabling the customer equipment to configure itself properly to access those services. The excerpt below schematically illustrates the E-LMI protocol.

Excerpt 2: Ethernet Local Management Interface

Source: Metro Ethernet Forum

Report Scope & Structure

‘Ethernet OAM Market Trends & Case Studies’ is structured as follows:

Section I is an introduction to the report, with complete report key findings.

Section II provides background on EOAM and its major protocols, including Link OAM 802.3ah, traffic generation protocols such as RFC 2544 and Y.1564, and Service OAM including 802.1ag and Y.1731, incorporating CFM and performance monitoring functionalities.

Section III discusses current and emerging trends and issues within the EOAM environment, including the status of OAM deployment, strategic carrier considerations, variations in EOAM deployment by protocol and service provider category, issues regarding standards vs. proprietary vendor-specific capabilities, information overload and data usefulness as issues and differentiators, hurdles to fuller EOAM realization and the future outlook for EOAM.

Section IV provides detailed case studies of EOAM deployment undertaken by seven different network operators worldwide.

‘Ethernet OAM Market Trends & Case Studies’ is published in PDF format.

Table of Contents

LIST OF FIGURES

I. INTRODUCTION & KEY FINDINGS

  • 1.1. Key Findings
  • 1.2. Report Scope & Structure

II. ETHERNET OAM: THE ROAD TO DEPLOYMENT

  • 2.1. Backdrop: Evolution of Contemporary Carrier Ethernet
  • 2.2. EOAM as Competitive Enabler, Restoring Sonet-Like Reliability
  • 2.3. EOAM Protocols Gain Momentum
  • 2.4. Mobile Backhaul as EOAM Driver
  • 2.5. EOAM Functions & Benefits
  • 2.6. 802.3ah: Link CAM
  • 2.7. 802.lag: Connectivity Fault Management
  • 2.8. Y.1731 & Performance Management
  • 2.9. Traffic Generation Protocols

III. EOAM MARKET TRENDS & ISSUES

  • 3.1. Overview: Part of the Way With EOAM
  • 3.2. EOAM as Carrier Strategic Response
  • 3.3. Winning, Keeping Customers: Tangible CAM Results
  • 3.4. EOAM Protocols in Operation
  • 3.5. EOAM in Context: Other Key Elements
  • 3.6. Web Portals & Information Transparency
  • 3.7. Breadth of Coverage
  • 3.8. Visibility (or Not) Between Carriers
  • 3.9. Carriers & Vendors: Interoperability, Standards & Proprietary Capabilities
  • 3.10. CAM Variability Across the Carrier Range
  • 3.11. Retail Customers & EOAM
  • 3.12. EOAM Complexity & Simplicity
  • 3.13. Information Overload &the Drive for Analytics
  • 3.14. What Else Customers Want
  • 3.15. Key Hurdles to Fuller EOAM Realization
  • 3.16. The EOAM Outlook

IV. ETHERNET OAM: SELECTED CASE STUDIES

  • 4.1. Case Study 1: Colt Technology Services
  • 4.2. Case Study 2: Eastern European Incumbent
  • 4.3. Case Study 3: Asia/Pacific Incumbent Operator
  • 4.4. Case Study 4: European Mobile Operator
  • 4.5. Case Study 5: Eastern European Retail Provider
  • 4.6. Case Study 6: North American Tier 1 Operator
  • 4.7. Case Study 7: European CLEC

APPENDIX A: ABOUT THE AUTHOR

APPENDIX B: LEGAL DISCLAIMER

LIST OF FIGURES

SECTION - I

SECTION - II

  • Figure 2.1: Localized Fault Management Under Link CAM
  • Figure 2.2: Pillars of MEF Service CAM
  • Figure 2.3: Connectivity Check Messages
  • Figure 2.4: Link Trace in Action
  • Figure 2.5: Performance Management
  • Figure 2.6: Ethernet Local Management Interface

SECTION - III

SECTION - IV

Show More
Pricing