Ethernet OAM
Maintenance Entities in ITU-T Q.3/13
Dinesh Mohan
Paul Bottorff
Nortel Networks
1
OAM Layering
2
Ethernet OAM Layering
Customer
Service Provider
Customer
Eth Access
Device
View
CE
U-PE B
B
MPLS Core
N-PE
P
P
MPLS Access
P
N-PE
P
U-PE
Ethernet
Layer
• An example to highlight network/service involving Ethernet
and other technologies
• The Ethernet Layer implies the visibility to Ethernet frames
3
CE
OAM Domain – Service/Network
Customer
Service Provider
Eth Access
Customer
MPLS Core
MPLS Access
Customer Domain
Provider Domain
Operator
Domain
Operator Domain
Operator
Domain
• Domains concept is necessary to contain OAM flows & bound
OAM responsibilities
4
Maintenance Entity Points (MEP) &
Maintenance Intermediate Points (MIP)
Customer
Service Provider
Eth Access
Customer
MPLS Core
MPLS Access
Customer Domain
Service
OAM
Provider Domain
Operator
Domain
Operator Domain
Operator
Domain
Network
OAM
PW/MPLS
OAM
Maintenance Entity Point
Maintenance Intermediate Point
MPLS Domain
MPLS
Domain
• Location of MEPs and MIPs is dependent on Business Models
5
& Deployment Scenarios
Service/Network OAM –
How does it come together?
Services
Service OAM
Network
Network OAM
Transport
Links
Ethernet link
OAM
PW/MPLS
OAM
EoSONET
OAM
Other
OAM
• OAM Interworking possible to utilize OAM across Layers
• However, each layer must support OAM capabilities independently
6
Q.3/13
Maintenance Entity Points (MEP)
&
Maintenance Intermediate Points (MIP)
7
Networks using MEPs & MIPs
Customer
Equipment
1
Operator A
Bridges
2
3
Operator B
Bridges
4
5
6
7
Customer
Equipment
8
9
ETH
ETH or
SRV
Maintenance Entity Point
Maintenance Intermediate Point
• MEPs and MIPs used to identify Maintenance Entities (MEs)
• MEs identifies what need to be managed
8
Dual Relay Model
as
Single Integrated Provider Device
9
MEP, MIP, TCP for Dual-Relay Model:
Single Integrated Provider Device
Customer
Equipment
1
Operator A
Bridges
2a
2b
Operator B
Bridges
3
4
5
6b
Customer
Equipment
6a
ETH
• 2a and 6a allow for peering of L2CP + multiplexing of user flows
10
• Additional MEs may need to be managed
7
Customer Bridge 1
Example without ETH link ME
802.1ag Up CM Shim
LLC
LLC
Relay
MEP
11
LLC
802.1Q Tagging “Y”
802.1ag Down CM Shim
LLC
802.1ag Down CM Shim
LLC
802.1ag Up CM Shim
LLC
802.1Q Tagging “Y”
Higher Layer Entities
Provider Bridge 2a
Example without ETH link ME
802.1ag Up CM Shim
LLC
Relay
MEP
MIP
LLC
MIP
MEP
12
LLC
802.1Q Tagging “Y”
802.1ag Down CM Shim
LLC
802.1ag Down CM Shim
LLC
802.1ag Up CM Shim
LLC
802.1Q Tagging “Y”
Higher Layer Entities
Provider Bridge 2b
Example without ETH link ME
802.1ag Up CM Shim
LLC
Relay
MEP
MEP
MIP
LLC
MIP
13
LLC
802.1Q Tagging “Y”
802.1ag Down CM Shim
LLC
802.1ag Down CM Shim
LLC
802.1ag Up CM Shim
LLC
802.1Q Tagging “Y”
Higher Layer Entities
Dual Relay Model
with
Single Relay as Provider Device
14
MEP, MIP, TCP for Dual-Relay Model:
Single Relay as Provider Device
Customer
Equipment
1
Operator A
Bridges
2b
Operator B
Bridges
3
4
5
Customer
Equipment
6b
• 2b and 6b do not allow for peering of L2CP + single service per
customer link
15
• Additional MEs may be needed at Customer side
7
Customer Bridge 1
Example without ETH link ME
802.1ag Up CM Shim
LLC
LLC
Relay
MEP
16
LLC
802.1Q Tagging “Y”
802.1ag Down CM Shim
LLC
802.1ag Down CM Shim
LLC
802.1ag Up CM Shim
LLC
802.1Q Tagging “Y”
Higher Layer Entities
Provider Bridge 2b
Example without ETH link ME
802.1ag Up CM Shim
LLC
Relay
MEP
MEP
MIP
LLC
MIP
17
LLC
802.1Q Tagging “Y”
802.1ag Down CM Shim
LLC
802.1ag Down CM Shim
LLC
802.1ag Up CM Shim
LLC
802.1Q Tagging “Y”
Higher Layer Entities
Dual Relay Model
with
Bundling for
Single Integrated Provider Device
18
MEP, MIP, TCP for Dual-Relay Model:
Bundling - Single Integrated Provider Device
Customer
Equipment
1
Operator A
Bridges
2a
2b
Operator B
Bridges
3
4
5
6b
Customer
Equipment
6a
11
C-Tag 12
21
22
ETH
11
C-Tag 12
21
22
Untagged
10
S-Tag 20
19
7
Customer Bridge 1
Example without ETH link ME - TBD
802.1ag Up CM Shim
LLC
Relay
LLC
MEP MEP MEP MEP
20
LLC
802.1Q Tagging “Y”
802.1ag Down CM Shim
LLC
802.1ag Down CM Shim
LLC
802.1ag Up CM Shim
LLC
802.1Q Tagging “Y”
Higher Layer Entities
Provider Bridge 2a
Example without ETH link ME - TBD
802.1ag Up CM Shim
LLC
Relay
MEP MEP MEP MEP
MIP
MIP
MIP
MIP
LLC
21
LLC
802.1Q Tagging “Y”
802.1ag Down CM Shim
LLC
802.1ag Down CM Shim
LLC
802.1ag Up CM Shim
LLC
802.1Q Tagging “Y”
Higher Layer Entities
Provider Bridge 2b
Example without ETH link ME - TBD
802.1ag Up CM Shim
LLC
LLC
Relay
MEP MEP
MEP MEP
MIP
MIP
22
LLC
802.1Q Tagging “Y”
802.1ag Down CM Shim
LLC
802.1ag Down CM Shim
LLC
802.1ag Up CM Shim
LLC
802.1Q Tagging “Y”
Higher Layer Entities
Dual Relay Model
with
Bundling for
Single Relay as Provider Device
23
MEP, MIP, TCP for Dual-Relay Model:
Bundling - Single Relay as Provider Device
Customer
Equipment
Operator A
Bridges
1
2b
Operator B
Bridges
3
4
5
Customer
Equipment
6b
7
11
C-Tag 12
21
22
Untagged
10
ETH
S-Tag 20
24
Dual Relay Model
with
All-to-One Bundling for
Single Relay as Provider Device
25
MEP, MIP, TCP for Dual-Relay Model:
All-to-One Bundling
Customer
Equipment
Operator A
Bridges
1
2b
Operator B
Bridges
3
4
5
Customer
Equipment
6b
7
11
C-Tag 12
21
22
Untagged
S-Tag 10
ETH
26