ethernet oam update overview & technical aspects dinesh mohan may 18, 2004
TRANSCRIPT
Ethernet OAM UpdateOverview & Technical Aspects
Dinesh Mohan
May 18, 2004
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 2
Brief OverviewIEEE 802.1 + ITU-T Q.3/13 + MEF + IETF L2VPN WG Activities
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 3
Ethernet OAM Layering
CE U-PE U-PEN-PEN-PE CEB B P P P PDevice View
Ethernet Layer
Eth Access MPLS Core MPLS Access
Customer CustomerService Provider
• Example: network/service with Ethernet & other technologies
• The Ethernet Layer implies the visibility to Ethernet frames– BUT Flat! Difficult to manage and identify accountability
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 4
OAM Domain – Service/Network
Eth Access MPLS Core MPLS Access
Customer CustomerService Provider
Customer Domain
Provider Domain
Operator Domain Operator Domain
Operator Domain
• Solution: OAM Domains
• Domains necessary to bound OAM Flows & OAM responsibilities
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 5
OAM Layering Introduced since:
• Multiple technologies involved in ITU-T
• IETF focuses on MPLS/IP and uses Ethernet as a service
– draft-sajassi-mohan-l2vpn-vpls-fm-00.txt– draft-mohan-sajassi-l2vpn-vpls-pm-00.txt
• Need for Requirements and/or Framework documents:
– Y.1730 – Ethernet OAM Requirements - Approved– MEF – MEF Service Requirements & Framework– L2VPN – tbd.
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 6
Maintenance Entity Points (MEP) & Maintenance Intermediate Points (MIP)
Network OAM
Service OAM
Customer Domain
Provider Domain
Operator Domain Operator Domain
Operator Domain
Eth Access MPLS Core MPLS Access
Customer CustomerService Provider
MPLS Domain MPLS Domain
Maintenance Entity PointMaintenance Intermediate Point
PW/MPLS OAM
• MEPs initiate/terminate/react to all OAM flows
• MIPs react to some OAM flows
• MEPs & MIPs dependent on Business Models & Deployment Scenarios
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 7
Ethernet MEPs & MIPs
CustomerEquipment
CustomerEquipment
Operator ABridges
Operator BBridges
ETH
ETY
1 2 3 4 5 6 7 8 9
• Another representation for positioning of MEPs and MIPs on devices with consideration for ingress and egress.
Maintenance Entity PointMaintenance Intermediate Point
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 8
OAM Models
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 9
OAM Functionality
• a) Discovery– i) Service
• e.g. discover all PEs supporting common service instance
– ii) Network• e.g. discover all devices (PE and P) common to a domain
• b) CC – Continuity Check• Multicast unidirectional heartbeat • Use: Fault Detection, Performance Monitoring (delay variance, frame loss)
• c) Loopback – Connectivity Check• Unicast and Multicast bi-directional request/response• Unicast (e.g. ICMP ping) Use: Fault detection, verification, delay, delay variance,
frameloss, • Multicast Use: Discovery
• d) Traceroute• Use: Fault Isolation
• e) FDI/RDI• Use: E<->W Fault propagation, Alarm Suppression
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 10
Maintenance Entities Mapped
• Example MEs identified– 2 Service Providers (SP1 & SP2)– SP2 has two domains (operators)– MEs 1,2,3,4 are required for Business relationship– MEs 5,6 are required for convenience
Customer CustomerService Provider
1. UNI_C-UNI_C ME2. UNI_N-UNI_N ME3. UNI ME 3. UNI ME
SP 1 SP 2 SP 2
4. E-NNI ME
5. Inter-domain ME (SP)
6. Intra-domain ME 6. Intra-domain ME6. Intra-domain ME (Operator)
UNI UNIE-NNI
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 11
End-to-end OAM – 2 Models
• Provider End-to-end OAM? CE-CE (terminating UNIs)– 2 Possible Models
Strong-Trust E-NNI• ME (3) + ME (2) + ME (3)
Weak-Trust E-NNI• ME (3) + ME (6) + ME (4) + ME (5) + ME(3) or• ME (3) + ME (6) + ME (4) + ME (6) + ME(3)
Customer CustomerService Provider
1. UNI_C-UNI_C ME2. UNI_N-UNI_N ME3. UNI ME 3. UNI ME
SP 1 SP 2 SP 2
4. E-NNI ME
5. Inter-domain ME (SP)
6. Intra-domain ME 6. Intra-domain ME6. Intra-domain ME (Operator)
UNI UNIE-NNI
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 12
OAM Functions mapped to MEs
Customer CustomerService Provider
1. a (i), b, c2. a (i), b, c, d, e
• Specifically for ME (3) and ME (4)– IEEE 802.3ah EFM OAM can be used for network/link OAM
when UNI/E-NNI is an Ethernet link– When single service carried across a link, network OAM can
map to service OAM
3. a (i), b, c, e
SP 1 SP 2 SP 2
3. a (i), b, c, e4. a (i), b, c,
e 5. a (ii), b, c, d, e
6. a (ii), b, c, d, e 6. a (ii), b, c, d, e6. a (ii), b, c, d, e
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 13
Maintenance Entities – P2P Case
• All MEs may not be needed always
• MEPs realize Maintenance Entities (MEs)
ETH_TFPETH_FP ETH_FP
ETHFPPLink ETH_FP
ETH_TFPETH_FP
ETHFPPLink
Service provider Y
User X User X
UNI_C to UNI_C maintenance entity
UNI_N to UNI_Nmaintenance entity
IntraDomain ME
UNI UNI
Access Link ME Access Link ME
NetworkOperator B
ETHFPP Link
NNI
InterDomain ME
IntraDomain ME
NetworkOperator AETH_TFP
ETH_FP ETH_FP
ETHFPPLink ETH_FP
ETH_TFPETH_FP
ETHFPPLink
Service provider Y
User X User X
UNI_C to UNI_C maintenance entity
UNI_N to UNI_Nmaintenance entity
IntraDomain ME
UNI UNI
Access Link ME Access Link ME
NetworkOperator B
ETHFPP Link
NNI
InterDomain ME
IntraDomain ME
NetworkOperator A
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 14
Maintenance Entities – MP2MP Case
ETH_TFPTH_FP ETH_FP
ETHLink ETH_FP ETH_FP
ETHLink
ETH_TFPETH_FP
ETHLink
ETH_FPETHLink
Service Provider Y
Network Operator BNetwork Operator AUser X User X
UNI NNI UNI
UNI
ETH_TFPETH_FP
ETH_TFPETH_FP
ETHLink
UNI
ETH_FP ETH_FP
UNI_C to UNI_C maintenance entities
UNI_N to UNI_N maintenance entities
Intra Domain MEs Intra Domain MEs
Access Link MEs Access Link MEsInter Domain ME
ETH ETH
• All MEs may not be needed always
• MEPs realize Maintenance Entities (MEs)
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 15
Maintenance Entities – CPE based Network Demarcation Access
• All MEs may not be needed always
ETH_FP
Service. Provider YNetwork Operator B
User X
UNI_C to UNI_C ME
UNI_N to UNI_N ME
Access Link ME
ETH_TFP ETH_FP
User X
Access Link ME
Extension Link ME
User Location
UNI_NP to UNI_NP ME
UNI ETH_FP
ETH Link
Private NNI
ETH_FP
Network Operator A
ETH Link
NNIETH_FP ETH_FP ETH_FP
ETH FPP Link
UNI
ETH FPP Link
ETH_TFP ETH_FP
NDD
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 16
Maintenance Entities – CPE based Network Demarcation Access
• All MEs may not be needed always
1 2 3 4 5 6 7 8 9
ETH_FP
Service. Provider YNetwork Operator B
User X
ETH_TFP ETH_FP
User X
User Location
UNI ETH_FP
ETH Link
Private NNI
ETH_FP
Network Operator A
ETH Link
NNIETH_FP ETH_FP ETH_FP
ETH FPP Link
UNI
ETH FPP Link
ETH_TFP ETH_FP
NDD
NDD
Ethernet OAM (May 18, 2004) [Dinesh Mohan] - 17
Service/Network OAM – How does it come together?
Ethernet link OAM
PW/MPLSOAM
EoSONET OAM
Other OAM
Network OAM
Service OAM
Transport Links
Network
Services
• OAM Interworking possible to utilize OAM across Layers
• However, each layer must support OAM capabilities independently