Ethernet OAM - Technical Overview and Deployment Scenarios BRKNMS-2202 Jaroslaw Grabowski Consultant System Engineer Agenda • Introduction • Fault Management • Performance Management • Use cases and configuration Snippets • Platform Support • Summary BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 3 Ethernet OAM Overview & High Level Maps Short History of Ethernet 400G?/Flex? 10M IEEE 802. 100M 1G 10G 100G 1974 1983 1994 1995 1999 2002 2007 2010 Today 2015 IEEE 802.*** Not mandatory Only L3 tools additions Robert Metcalfe First massive Ethernet Ethernet patent deployments in OAM Service Providers Era Networks OAM is needed! BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 5 Historical Map Link Management IEEE 802.3ah (subset of Ethernet First Mile 2004, 2008) CFM (Connectivity Fault IEEE 802.1ag (2007) Management) Architecture + Performance Management Full OAM architecture ITU-T Y.1731 / G.8013 (2008, 2011, 2013 published) Y.xxxx IP and next-generation networks G.xxxx Transmission systems Metro Ethernet Forum E-LMI (2006) Adoption of 802.1ag & Y1731 in MetroEth Service Activation Cisco IP SLA Ethernet OAM Extensions, common CLI, NMS BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 6 Classical ISO/OSI Management Model FCAPS Fault Configuration Accounting Performance Security Management Management Management Management Management Fault Detection Service ... Frame Loss … Fault Verification Provisioning Measurement Fault Isolation Delay E-LMI Measurement Fault Recovery Delay Variation Fault Notification Measurement Availability Link OAM Measurement CFM (Connectivity Fault Management) Performance Management (Y.1731) BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 7 Protocols Positioning Map CFM (Connectivity Fault Management) End-to-End or Domain Management Performance Management (Y.1731) E-LMI Backbone Backbone Bridges Bridges Provider Provider Bridges Bridges Customer Customer MPLS Link OAM MPLS OAM BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 8 Protocol Overview - Link OAM IEEE 802.3-2008 (Clause 57) For your Link OAM (IEEE 802.3ah, Clause 57) reference • Provides mechanisms useful for Reserved Remote Stable Remote Local Stable Local Critical Event Dying Gasp Link Fault “monitoring point-to-point link operation”, Evaluating Evaluating such as: – Link Monitoring DMAC SMAC Type – Remote Failure Indication Dest Address Src Address type subtype flags code datacode CRC 0180c20002 8809 03 – Remote Loopback Control code local info remote info … 00 TLV TLV • Defines an optional OAM sublayer Information OAMPDU code seq link event … 01 # TLV Event Notification OAMPDU • Uses “Slow Protocol”1) frames called code var descriptor … OAMPDUs which are never forwarded by Var Request OAMPDU 02 (branch & leaf) MAC clients (specific multicast Destination code var container … (0180.c200.0002) and Ether-Type (8809) ) Var Response OAMPDU 03 (branch, leaf, width, value) code loopback Loopback Control OAMPDU 04 command • Standardized: IEEE 802.3ah, clause 57 Vendor-Specific OAMPDU code 24-bit OUI … (now in IEEE 802.3-2008) FE (1) No more than 10 Frames Transmitted in Any One-Second Period BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 10 For your Link OAM. Use Case reference Link monitoring and discovery • Discovery process – OAMPDU are sent periodically and carrying platform capabilities and identity OUI (organization unique Provider identifier) Bridges Customer • Link monitoring process Link – Event notification: error rate exceeded a threshold. OAM switch#show ethernet oam summ Symbols: * - Master Loopback State, # - Slave Loopback State Capability codes: L - Link Monitor, R - Remote Loopback interface ….. U - Unidirection, V - Variable Retrieval no ip address ethernet oam Local Remote Interface MAC Address OUI Mode Capability Gi3/2 0014.6a7c.c451 00000C active L R Gi3/48 0015.6282.25a7 00000C passive L BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 11 For your Link OAM. reference DTE Types Link OAM Capability Active DTE Passive DTE Initiates OAM Discovery process Yes No Reacts to OAM Discovery process initiation Yes Yes Required to send Information OAMPDUs Yes Yes Permitted to send Event Notification OAMPDUs Yes Yes Permitted to send Variable Request OAMPDUs Yes No Permitted to send Variable Response OAMPDUs Yes1 Yes Permitted to send Loopback Control OAMPDUs Yes No Reacts to Loopback Control OAMPDUs Yes1 Yes Permitted to send Organization Specific OAMPDUs Yes Yes BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 12 Link OAM. Use Case Dying Gasp (Remote Failure Indication) SNMP • OAM PDU is sent when station is about to go No SysLog down. Dedicated codes are created for power! different events Shut – Administrative shutdown down – Power Loss (extended HW capabilities are required) – Reboot Provider Bridges • After receiving OAMPDU remote peers can Customer react depending on configured actions Link – SNMP trap OAM – sysLog message – Disable interface Benefit: – Activate Interworking mechanisms No need for sending service team in case of lost connectivity BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 13 For your Link OAM. Use Case reference Dying Gasp. SNMP interface ….. No SysLog no ip address power! ethernet oam max-rate 5 Shut ethernet oam min-rate 2 ethernet oam timeout 30 down ethernet oam remote-failure link-fault action error-disable-interface ethernet oam remote-failure dying-gasp action error-disable-interface ethernet oam remote-failure critical-event action error-disable-interface ethernet oam Provider Bridges snmp-server traps ethernet oam events Customer Link OAM template oam Could be ethernet oam max-rate 5 interface ….. ethernet oam min-rate 2 no ip address defined as ethernet oam mode passive ethernet oam template ethernet oam timeout 30 ….. BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 14 Link OAM. Use Case Remote Loopback • Ethernet data traffic can be looped back on a per port / per VLAN basis • Use cases: – Service turn-up Customer – Post service turn-up troubleshooting External M2 M1 – Out-of-service throughput testing • Enabled via CLI configuration M1 M2 • Configurable direction: Internal – External Loopback (facing and testing wire) – Internal Loopback (facing and testing wire & bridge) • Complements CFM Loopback Cisco extension: MAC address swap. • External central Test Head allows for flexible and Original 802.3ah assumes pure data sophisticated test traffic patterns loopback BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 15 For your Link OAM. Use Case reference Remote Loopback Networ_Switch# ethernet oam remote-loopback start interface fas1/3 6d22h: %ETHERNET_OAM-SP-6-LOOPBACK: Interface Fa1/3 has entered the master loopback mode. Customer External Syslog message Internal Customer_Switch# Remote 1w0d: %ETHERNET_OAM-SP-6-LOOPBACK: Interface Fa4/3 has entered the slave activation loopback mode. BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 16 1 Protocol Overview Connectivity Fault Management CFM (Connectivity Fault Management) Overview • Family of protocols that provides capabilities to detect, verify, isolate and report end-to-end Ethernet connectivity faults • Employs regular Ethernet frames that travel in-band with the customer traffic – Devices that cannot interpret CFM Messages forward them as normal data frames • CFM frames are distinguishable by Ether-Type (0x8902) and dMAC address (for multicast messages) • Standardized – IEEE std. 802.1ag-2007 – Y.1731/ G.8013 (2008, 2011, 2013) Y.1731/G.8013 (Fault Management) was design to be compatible with 802.1ag. Frame formats (Multicast Address, Ethertype, and common OAM PDU fields) and base functionality are generally agreed upon across IEEE 802.1ag and Y.1731/ G.8013 BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 18 CFM Concepts Maintenance Entity Point A Point B • Simply: “The entity between two of the flow/connection points“ • Extended definition in ITU documentation “G.8013/Y.1731” referring to “G.8001/Y.1354” finally referring to referring to “G.8010/Y.1306” BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 19 CFM Concepts Management hierarchy CE CE Service Provider Customer • Minimum (but relevant) information principle. Customer is interested only with his/her service • Maintenance Domain from Customer perspective is defined end-to-end BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 20 CFM Concepts More levels CE CE Operator B Service Provider Customer • Service Provider should have full visibility inside owned network • If Service Provider is using 3rd Party network – acting as “customer”, visibility of Operator B network structure is not necessary. Very often this type of information is confidential. BRKNMS-2202 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public 21 CFM Concepts CE CE Operator A Operator B Service Provider Customer • Defined by Operational/Contractual Boundaries – e.g. Customer/Service Provider/Operator • ME may nest and touch, but never intersect • Up to 8 levels of “nesting”: ME Level (0..7) – The higher the level, the broader its reach • ME Name Format: null, MAC address, DNS or string-based BRKNMS-2202 © 2015 Cisco