1 / 25

Interconnect In-depth, Part 2: OAM Implementation

placido
Download Presentation

Interconnect In-depth, Part 2: OAM Implementation

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. Interconnect In-depth, Part 2: OAM Implementation/Standards overview and Impact on Interconnect

    2. Driving Demand for Service OAM: Reliability A Heavy Report survey of Enterprise customers who were potential buyers of Carrier Ethernet services were asked the importance of a variety of attributes and features. The #1 Essential need was Service Reliability. Reliability/Up-time (Reach TDM’s 99.999%) For the service provider: Quality = customer satisfaction and retention – maintain revenue A Heavy Report survey of Enterprise customers who were potential buyers of Carrier Ethernet services were asked the importance of a variety of attributes and features. The #1 Essential need was Service Reliability. Reliability/Up-time (Reach TDM’s 99.999%) For the service provider: Quality = customer satisfaction and retention – maintain revenue

    3. Driving Demand for Service OAM: SLAs SLAs are an essential element of Carrier Ethernet Frame Relay, Private Line, ATM all have them Subscribers want SLAs and proof of compliance Management and reporting are a key element of the solution Global Interconnect complicates SLAs Need tools to determine fault locations across multiple operators What is driving demand for Service OAM? Light Reading asked Service Providers, “What is holding service providers back from deploying Ethernet more aggressively?” 16% said…, >> 18% said… >> and 66% said the lack of performance monitoring and SLA support.What is driving demand for Service OAM? Light Reading asked Service Providers, “What is holding service providers back from deploying Ethernet more aggressively?” 16% said…, >> 18% said… >> and 66% said the lack of performance monitoring and SLA support.

    4. Driving Demand for Service OAM: OPEX This bar diagram compares the OPEX (in purple) and CAPEX (in blue) of TDM Legacy Services, Best Effort Ethernet (caveman) and Carrier Ethernet with Service OAM and Global Interconnect (modern man). Legacy TDM equipment is expensive, but the extensive and robust OAM tools keep operating costs low. Best Effort Ethernet equipment is very inexpensive, but the lack of OAM tools keeps operating costs high. Carrier Ethernet combines the best of both worlds with low cost equipment and the low operating costs of TDM. Bottom line: Efficient operation keeps costs down and allows carriers to be competitive and profitableThis bar diagram compares the OPEX (in purple) and CAPEX (in blue) of TDM Legacy Services, Best Effort Ethernet (caveman) and Carrier Ethernet with Service OAM and Global Interconnect (modern man). Legacy TDM equipment is expensive, but the extensive and robust OAM tools keep operating costs low. Best Effort Ethernet equipment is very inexpensive, but the lack of OAM tools keeps operating costs high. Carrier Ethernet combines the best of both worlds with low cost equipment and the low operating costs of TDM. Bottom line: Efficient operation keeps costs down and allows carriers to be competitive and profitable

    5. Driving Demand for Service OAM: Area Traditional Private Lease Line and Private Virtual Connection (PVC) are provided through T1/T3 or SONET/SHD access loops. They are complicated, costly, somewhat slow and not very scalable. They do offer very consistent and reliable performances, and have built-in OAM for fault detection and management. Interject how “Interconnect” is effected by these challenges Traditional Private Lease Line and Private Virtual Connection (PVC) are provided through T1/T3 or SONET/SHD access loops. They are complicated, costly, somewhat slow and not very scalable. They do offer very consistent and reliable performances, and have built-in OAM for fault detection and management. Interject how “Interconnect” is effected by these challenges

    6. Key Ethernet OAM Standards There are a variety of standards organizations involved, working on a long list of different standards. The ones I want to focus on today are some of the standards focused on Ethernet OAM, starting with IETF’s RFC-2544 specification for Ethernet testing and RFC-2819 for remote monitoring. These were early standards that were included in many Ethernet products, but weren’t really optimized for delivering Ethernet services. In the recent past, we’ve completed IEEE 802.3ah Ethernet in the first mile, which was the first standard that included remote monitoring and testing of an Ethernet service. Following right behind it was IEEE 802.1ag connectivity fault management which provided a more generalized method for monitoring the health of an Ethernet service as well as partitioning the network into tiers to define management responsibilities of different stakeholders. ITU Y.1731 built upon 802.1ag to add performance management capabilities and enabled the monitoring of Ethernet SLAs for the first time. At the same time, the MEF created MEF-13, 16 & 20 which defined an Ethernet user network interface (UNI) for handing off services. In addition there is MEF work on-going to create an Network to Network Interface or NNI and to define a NID device or function to go at these key service handoff points.There are a variety of standards organizations involved, working on a long list of different standards. The ones I want to focus on today are some of the standards focused on Ethernet OAM, starting with IETF’s RFC-2544 specification for Ethernet testing and RFC-2819 for remote monitoring. These were early standards that were included in many Ethernet products, but weren’t really optimized for delivering Ethernet services. In the recent past, we’ve completed IEEE 802.3ah Ethernet in the first mile, which was the first standard that included remote monitoring and testing of an Ethernet service. Following right behind it was IEEE 802.1ag connectivity fault management which provided a more generalized method for monitoring the health of an Ethernet service as well as partitioning the network into tiers to define management responsibilities of different stakeholders. ITU Y.1731 built upon 802.1ag to add performance management capabilities and enabled the monitoring of Ethernet SLAs for the first time. At the same time, the MEF created MEF-13, 16 & 20 which defined an Ethernet user network interface (UNI) for handing off services. In addition there is MEF work on-going to create an Network to Network Interface or NNI and to define a NID device or function to go at these key service handoff points.

    8. Response to Demand New Protocol Solutions End-to-End Service Connectivity Fault OAM (802.1ag) End-to-End Service Performance Monitoring (Y.1731) Link OAM (802.1ah) Enable quick turn-up – Acct acquisition/revenue Increase reliability/up-time – Acct retention/revenue Enables SLA commitments – Keep revenue Enable efficient service operation / maintenance (man/machine/time/energy) – reduce OPEX Interject how “Interconnect” is effected by these challengesInterject how “Interconnect” is effected by these challenges

    9. Ethernet OAM Jurisdictions From an OAM perspective there are several standards that work together in a layered fashion to provide Ethernet OAM. IEEE 802.3ah was the first and provides link level OAM. With more of an end to end focus, 802.1ag provides a connectivity fault management layer for identifying network faults, while ITU Y.1731 adds a performance management which enables SLAs to be monitored. These layers are implemented in a network interface device or NID which can be a standalone device or integrated into other equipment. There is a great deal of commonality between these standards, especially between 802.1ag and Y.1731.From an OAM perspective there are several standards that work together in a layered fashion to provide Ethernet OAM. IEEE 802.3ah was the first and provides link level OAM. With more of an end to end focus, 802.1ag provides a connectivity fault management layer for identifying network faults, while ITU Y.1731 adds a performance management which enables SLAs to be monitored. These layers are implemented in a network interface device or NID which can be a standalone device or integrated into other equipment. There is a great deal of commonality between these standards, especially between 802.1ag and Y.1731.

    10. Link OAM IEEE 802.3ah - Ethernet in the First Mile (EFM) First Ethernet OAM standard completed (2004) Supports: Remote loopback Remote failure indication (dying gasp, link fault and critical event) Link monitoring Loopback Control Discovery Focused on point to point Ethernet link OAM Does not propagate beyond a single link or hop Maintenance OAM, not service

    11. Link OAM From an OAM perspective there are several standards that work together in a layered fashion to provide Ethernet OAM. IEEE 802.3ah was the first and provides link level OAM. With more of an end to end focus, 802.1ag provides a connectivity fault management layer for identifying network faults, while ITU Y.1731 adds a performance management which enables SLAs to be monitored. These layers are implemented in a network interface device or NID which can be a standalone device or integrated into other equipment. There is a great deal of commonality between these standards, especially between 802.1ag and Y.1731.From an OAM perspective there are several standards that work together in a layered fashion to provide Ethernet OAM. IEEE 802.3ah was the first and provides link level OAM. With more of an end to end focus, 802.1ag provides a connectivity fault management layer for identifying network faults, while ITU Y.1731 adds a performance management which enables SLAs to be monitored. These layers are implemented in a network interface device or NID which can be a standalone device or integrated into other equipment. There is a great deal of commonality between these standards, especially between 802.1ag and Y.1731.

    12. End-to-End Service OAM What is Service OAM? Enables fault detection and performance monitoring of the Ethernet Service (EVC) from End-to-End Uses synthetic traffic Supports multiple layers of OAM and maintenance regions Supports multiple networks and operators Includes: IEEE 802.1ag provides Connectivity Fault Management ITU-T Y.1731 provides Performance Monitoring

    13. End-to-End Service OAM What is End-to-End? The entire span of the Ethernet service between customer locations (UNI to UNI) UNI is the User to Network Interface Defines an Ethernet service demarcation point (physical port) between customer and service provider Defines Service Attributes Traffic Classification, Bandwidth Profiles, Tagging, etc. OAM Intelligence at the Demarcation Point The Network Interface Device provides the UNI The NID provides the OAM Intelligence that is required at the CP for End-to-End Service OAM

    14. Service OAM Framework - Domains This example shows Maintenance Associations (MAs) between Maintenance End Points (MEPs) at three levels within a Maintenance Domain (MD). Maintenance Intermediate Points (MIPs) can be associated per MD or per MA which depends on the visibility the administer has configured. This example shows Maintenance Associations (MAs) between Maintenance End Points (MEPs) at three levels within a Maintenance Domain (MD). Maintenance Intermediate Points (MIPs) can be associated per MD or per MA which depends on the visibility the administer has configured.

    16. 802.1ag Connectivity Fault Management 802.1ag CFM Defines the Framework for Service OAM Provides mechanisms to detect, verify, isolate and report end-to-end Ethernet connectivity faults Continuity Check Message Loopback Linktrace Scalable to provide connectivity checking and fault detection across multiple networks and multiple domains Partitions the network into Domains to define responsibilities of different stakeholders. Supports up to 8 Maintenance Domains

    17. Ethernet Service Continuity Check

    18. Ethernet Link Trace

    19. ITU-T Y.1731 Performance Monitoring ITU-T Y.1731 Mechanisms that provide fault and performance monitoring for point-to-point Ethernet services Builds on 802.1ag functionality and adds: Introduces performance measurements for SLA monitoring Delay Measurement (DM) Delay Variation Measurement (DVM) Loss Measurement (LM) Expands on fault notification and isolation Automatic Protection Switching (APS) G.8031 Ethernet Alarm Indication Signal function: Y.1731 ETH-AIS Ethernet Test Signal function: Y.1731 ETH-TEST Technically aligned with 802.1ag Uses slightly different terminology (Eg. MEG = MA in IEEE 802.1ag) 802.1ag specifies the FRAME FORMAT used by Y.1731 802.1ag and Y.1731 bodies worked closely together; hence, the standards provide extremely similar functionality Differences in recommendations exist as the work in IEEE was not completed when SG13 commenced its work on Y.1731 ETH-CC, ETH-LB, ETH-LT ETH-TEST Used to perform one-way on-demand in-service or out-of-service diagnostics tests. This includes verifying bandwidth throughput, frame loss, bit errors, etc. Technically aligned with 802.1ag Uses slightly different terminology (Eg. MEG = MA in IEEE 802.1ag) 802.1ag specifies the FRAME FORMAT used by Y.1731 802.1ag and Y.1731 bodies worked closely together; hence, the standards provide extremely similar functionality Differences in recommendations exist as the work in IEEE was not completed when SG13 commenced its work on Y.1731 ETH-CC, ETH-LB, ETH-LT ETH-TEST Used to perform one-way on-demand in-service or out-of-service diagnostics tests. This includes verifying bandwidth throughput, frame loss, bit errors, etc.

    20. Service Performance Management Key Metrics for Performance Monitoring Frame/Packet Delay – Latency (e.g. UNI/UNI 30ms@99.9%@15min) Frame/Packet Delay Variation – Jitter (e.g. 10ms@99.9%@15min) Frame/Packet Loss Ratio (e.g. CIR FL=1%@15min) Service Availability (e.g. 99.99%@30days) ITU-T has defined measurement metrics for items 1-3 Packet-based measurements (granularity to Class of Service) ITU-T Y.1731 defines how to use 802.1ag to measure performance MEF has defined measurement framework for items 1-4 Ethernet Frame-based measurements MEF 10.1 defines formulae for metrics calculation

    21. Slide is a duplicate of slide 9, but need a top-level concept layout. This clearly shows link vs. service OAM.Slide is a duplicate of slide 9, but need a top-level concept layout. This clearly shows link vs. service OAM.

    22. Service OAM – Enabling CAPEX ROI Service providers spent $17 billion on Carrier Ethernet equipment in 2008 This will increase every year over the next 5 years, and defy the economic downturn. Infonetics Research – April 2009 Worldwide Business Ethernet Services Market Rises to $38.9 Billion by 2013 Carriers continue to expand their Ethernet  footprints and revenue from the global market Vertical Systems Group – March, 2009

    23. Global Interconnect Acceleration

    24. Summary Challenges for Carrier Ethernet Interconnect Increase reliability/up-time – Acct retention/revenue Enables SLA commitments – Keep revenue Enable efficient service operation / maintenance (man/machine/time/energy) – reduce OPEX OAM Protocol Solutions Point-to-Point Link OAM (802.3ah) End-to-End Service OAM Connectivity Fault (802.1ag) End-to-End Service OAM Performance Monitoring (Y.1731) Enables the Global Interconnect

    25. Thank You

More Related