We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byAustin Miles
Modified over 3 years ago
1 © 2004 Cisco Systems, Inc. All rights reserved. Ethernet Connectivity Fault Management for Broadband Yves Hertoghs, Wojciech Dec, email@example.com@cisco.com, firstname.lastname@example.org@cisco.com
222 © 2004 Cisco Systems, Inc. All rights reserved. Ethernet OAM IEEE 802.1ag, IEEE 802.3ah, MEF E-LMI, ITU-T Lots of stuff happening with regards to Operation & Management of Service Provider Ethernet Services 802.3ah; link level OAM ELMI: at the UNI 802.1ag: service level OAM (per S-VLAN) Aka Connectivity Fault Management (CFM) This document focuses on using 802.1ag as a cornerstone for an Ethernet OAM scheme for DSL aggregation. It also introduces concepts to allow interworking of CFM with link level OAM schemes such as 802.3ah and ATM OAM
333 © 2004 Cisco Systems, Inc. All rights reserved. A Generic Model Maintenance End Point Maintenance Intermediate Point RG = Residential Gateway BBNG = Broadband Network Gateway aka Router RG Access_NodeAggr_Switch BBNG Problems with this model: RG might not have MAC-address RG might only be able to run legacy link level OAM schemes (802.3ah, ATM) CCMs from RG are potential DoS targets Would generate a lot of CCMs CCM
444 © 2004 Cisco Systems, Inc. All rights reserved. IEEE 802.1ag – Connectivity Fault Management CCM: Connectivity Check Message MEP: Maintenance End Point. A CFM station that can initiate and listen to CFM messages MIP: Maintenance Intermediate Point. A CFM station that listens to CFM messages (might be allowed to send AIS).
555 © 2004 Cisco Systems, Inc. All rights reserved. Continuity Check Message /CCM ( Auto and On-demand) Multicast from MEP. Received by MEPs and MIPs. Catalogued by receiving MEPs. Traceroute Message and Reply (TM, TR) Next-hop Multicast from MEP to next MEP or MIP along route. Receiver both replies with unicast to original MEP, and sends Traceroute to next MEP/MIP. Loopback Message and Reply (LM, LR) Unicast from MEP to MEP or MIP, which replies with unicast to originating MEP Alarm Indication (AIS) Multicast from MEP or MIP when link in a certain inferior domain fails (is send in opposite direction) CE Customer Domain Provider Domain Operator Domain Eth Access MPLS Core MPLS Access Customer Service Provider Network OAM Service OAM PW/MPLS OAM MPLS Domain Maintenance End Point Maintenance Intermediate Point Ethernet OAM – 802.1ag 0 3 5 7
666 © 2004 Cisco Systems, Inc. All rights reserved. CFM Terminology Bridge-Brain Model: All OAM messages are responded by the brain of the bridge. The bridge has no ability to understand where an OAM frame entered the switch. Uses a single MAC- address for all MEP/MIPs, using different MEPids. * Bridge-Port Model: OAM messages can be responded by using dedicated per port hardware/software. Requires a unique MAC-address per MEP/MIP. The bridge knows where an OAM frame entered the switch. Domain: Boundaries of CFM management Level: Access control structure for CFM Domain information & state. higher numbers (towards physical level) are bounded by lower numbers (towards service level)
777 © 2004 Cisco Systems, Inc. All rights reserved. Changes to 802.1ag 802.1ag LM are towards MAC-addresses Makes sense to summarize all MEPs on an access node under a single MAC-address Most Access Nodes would use brain model Interworking would mean brain model almost by defintion. MEPs can be made unique by MEPid (13 bit integer) and MAID It is assumed that multiple MAs can be created per S-VLAN if needed. Loopback Messages can not target a MEPid New Message (Inquiry/Status) must be added to CFM Allows a MEP to query a remote bridge about the status of a Port or MEP (by targetting MEPid). Remote Bridge will respond after performing local test of the Port/MEP Typically send by the BBNG CCMs would need to be (optionally) turned off for mass rollout of broadband services
888 © 2004 Cisco Systems, Inc. All rights reserved. CFM terminology Inward MEP: MEP on a bridge port which is responding to messages originated at other side of relay function Outward MEP: MEP on a bridge port which is responding to messages originated at same side of relay function MEP Interior Facing Function (IFF): main function of the MEP i.e. this the function that sends CCs, maintains a DB, sends and replies to LBs and TRs. MEP Exterior Facing Function (EFF): function that can send signals in the opposite direction of the MEP i.e. for AIS. MEP Virtual Interior Facing Function (VIFF): MEP that maintains a DB not by relying on CCs, but rather on physical level or link-level OAM such as MPLS OAM, ATM OAM, 802.3ah OAM).
999 © 2004 Cisco Systems, Inc. All rights reserved. Conceptual Model of an Optimised Solution DSL Port has 1 outward MEP, MIP and inward MEP stacked MEP at level 7 on Access Node port sees signals through its VIFF MEP on RG at level 7 (and level 0) are virtual MEPs i.e. logically on RG, physically a software construct on access node EFF on outward MEP at level 7 in AN can send AIS, which will bubble up level 0 to reach BBNG CCs can also be sent from inward MEP at level 5 in AN to signal health of DSL line (removing the need for this virtual MEPs. See next slide) ATM signals (AIS, CC) could be translated to appropriate CFM signals. We still need a new opcode to check the DSL line, as all MEPs (inward /outward, any level), are probably operated by the same bridge-brain. RG Access_NodeAggr_Switch BBNG Level 0 Level 3 Level 7 (link) DSL Domain Ethernet Domain Virtual
10 © 2004 Cisco Systems, Inc. All rights reserved. Implementation of the model without virtual MEPs MEP on access node is inward facing (level 3) State of the MEP is dependent on underlying ATM/802.3ah/physical health. Could use LifeTime=0 TLV or Port State TLV in CCs, or just stop sending CCs if something went wrong with DSL Line. No way to translate any ATM signals to CFM signals. Can AIS be used if CCs are turned off ? We still need a new opcode to check the DSL line, bridge-brain model is assumed. RG Access_NodeAggr_Switch BBNG Level 3 DSL DomainEthernet Domain
11 © 2004 Cisco Systems, Inc. All rights reserved. Line Identification MEPid is a 13-bit integer value Allows 8k MEPs per S-VLAN *might* not be enough for broadband, unless we could have different, side by side maintenance associations per S-VLAN Broadband usually uses circuit-id as a way of identifying DSL line, next to S-VLAN/C-VLAN (if a VLAN per dsl line is used). You could think of the circuit-id as the MEP Name Not easy way to link MEP Name id to MEP id and MEP MAC-address (for sure when CCs are turned off)
12 © 2004 Cisco Systems, Inc. All rights reserved. MEP Name Should IFF definition be extended to include MEP Name TLV ? MEP Name TLV could take format from RFC3046 (DHCP Option82) DSL Forum is developing a global circuit-id syntax using RFC3046 MEP Name TLV (184.108.40.206.2) is already defined and compatible with RFC3046 notation MEP Name can be part of CCMs If CCMs are turned off, we still need a protocol to translate MEP Name to MEP id + MEP MAC-address Introducing the Maintenance Point Resolution Protocol
13 © 2004 Cisco Systems, Inc. All rights reserved. MP Resolution Query Message (MRQM) MRQMs purpose is to query within the S-VLAN and MA level all MEPs about who is carrying a given MEP Name MEP Name, MAID are carried as TLVs in a multicast message with a new opcode targetted at the MA level MEPs who do not recognise this opcode must behave according to the specified 802.1ag behaviour when not recognising opcodes MEPs not finding a local match silently drop the message and take no further action Queries that time out will generate a MEP NAME Unresolved- Message to be communicated to the administrator
14 © 2004 Cisco Systems, Inc. All rights reserved. MP Resolution Response Message (MRRM) Upon receiving a MRQM and recognising the MEP Name, a MEP will reply with a MRRM message New Opcode needed, unicast message back to originating MEP containing MEP Name, MEP ID, MAID, MEP Mac-address TLVs Upon receiving the MRRM a MEP can update its local database Both MRRM and CCMs can populate the database If multiple responses are received, the MEP should print a MEP Name inconsistency error and report to the administrator No unsollicited MRRMs are allowed
15 © 2004 Cisco Systems, Inc. All rights reserved. Summary 802.1ag can be used as a cornerstone for broadband access networks 802.1ag needs to be enhanced Ability to turn off CCMs Extra Opcodes (Inquiry/Status) to accommodate bridge brain models Clear interworking scenarios E-LMI, 802.3ah, ATM Either through virtual MEP or through binding dsl line health to MEP Port State Need MEP name resolving protocol MEP Name to MEP id + MAC-address
16 © 2004, Cisco Systems, Inc. All rights reserved.
ag Discussion May 18, 2004 Ali Sajassi Paul Bottorf
802.1ag - Connectivity Fault Management Tutorial – Part 1 Dinesh Mohan July 12, 2004.
1 Introducing the Specifications of the Metro Ethernet Forum.
Ethernet OAM Update Overview & Technical Aspects Dinesh Mohan May 18, 2004.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 MPLS –TP Fault OAM draft-sfv-mpls-tp-fault-00 George Swallow
Virtual Trunk Protocol
Chapter 4: Managing LAN Traffic. Frames Frame is the term used to describe data transmitted at Layer 2 of the OSI model. The source and destination addresses.
Nortel Confidential Information 1 MPLS & Ethernet OAM Interworking (draft-mohan-pwe3-mpls-eth-oam-iwk) L2VPN WG, IETF-71 (Philadelphia) Mar 13, 2008 Dinesh.
MEF 30 Service OAM Fault Management Implementation Agreement
Ethernet 802.1ag Fault Management Across Domains Freek Dijkstra, Sander Boele, Ronald van der Pol – SARA TERENA Networking Conference – Reykjavík, 23 May.
MEF 30.1 Service OAM Fault Management Implementation Agreement
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 9 Virtual Trunking Protocol.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 MPLS –TP Fault OAM draft-ietf-mpls-tp-fault-01 George Swallow
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 7 Spanning Tree Protocol.
Text TCS Internal October 17, 2014 Introduction to Ethernet OAM.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 1 v3.1 Module 6 Ethernet Fundamentals.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA TCP/IP Protocol Suite and IP Addressing Halmstad University Olga Torstensson
PAR for Media Converters r2IEEE interim, October, PAR for Media Converters revision 2 Norman Finn Cisco Systems.
1 MEF Reference Presentation November 2011 Carrier Ethernet Service OAM.
1 draft-sajassi-mohan-l2vpn-vpls-fm-00.txt draft-mohan-sajassi-l2vpn-vpls-pm-00.txt Dinesh Mohan (Nortel) IETF-59, Seoul March.
1 Metro Ethernet Forum OAM An Update Matt Squire Hatteras Networks.
© 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—2-1 Extending Switched Networks with Virtual LANs Introducing VLAN Operations.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 1 v3.1 Module 10 Routing Fundamentals and Subnets.
© 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—6-1 Establishing Serial Point-To-Point Connections Introducing Frame Relay.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 2 v3.1 Module 1 WANs and Routers.
1 Introducing the Specifications of the Metro Ethernet Forum MEF 17 Service OAM Framework and Requirements February 2008.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Introduction to IPv4 Introduction to Networks.
IEEE 802.1ag Ethernet OAM Ronald van der Pol SARA Architecture Workshop, 1-2 Dec, Amsterdam.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 Static Routing Routing Protocols and Concepts – Chapter 2.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS Concepts Identifying MPLS Applications.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS VPN Technology Introducing MPLS VPN Architecture.
1 Ethernet Access Services Definition and Implementation.
© 2006 Cisco Systems, Inc. All rights reserved. MPLS v MPLS VPN Technology Introducing the MPLS VPN Routing Model.
CMPT 471 Networking II Address Resolution IPv4 ARP RARP 1© Janice Regan, 2012.
Cisco Confidential 1 bz-nfinn-soln-station-subset-0113-v02.pdf Solutions for P802.1Qbz / P802.11ak: Station subset issue Norman Finn January, 2013 Version.
VLAN Trunking Protocol (VTP) W.lilakiatsakun. VLAN Management Challenge (1) It is not difficult to add new VLAN for a small network.
1 DRNI Examples and DAS position Maarten Vissers Version 01.
Exploring the Packet Delivery Process Chapter
Chapter 19 - Binding Protocol Addresses Translation Address Resolution ARP (Address Resolution Protocol) Note: Sections 19.4 to 19.7, and will.
© 2007 Cisco Systems, Inc. All rights reserved. 1 Network Addressing Networking for Home and Small Businesses – Chapter 5 Darren Shaver – Modified Fall.
© 2007 Cisco Systems, Inc. All rights reserved. 1 Network Addressing Networking for Home and Small Businesses – Chapter 5.
1 Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Dynamic Host Configuration Protocol (DHCP)
Chapter 5. An IP address is simply a series of binary bits (ones and zeros). How many binary bits are used? 32.
Switching Basics and Intermediate Routing CCNA 3 Chapter 8.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 5: Inter-VLAN Routing Routing & Switching.
Experiences with IEEE 802.1ah (Provider Backbone Bridges) Ronald van der Pol SARA Sep 2009NORDUnet meeting, Copenhagen.
© 2017 SlidePlayer.com Inc. All rights reserved.