Embed Size (px)
Citation preview
1
DRNI Data Plane Model I/II Comparison& MAC Address Values in DRNI
Maarten Vissers2011-10-18
v00
2
Contents
Introduction DRNI Data Plane Models I/II for PB, PBB(-TE) IB-BEB and EOTN TB Portals
EC MEP/MIP configuration examples in Model I Portal EC MEP/MIP configuration examples in Model II Portal Comparison between Models I and II
Generic DRNI Data Plane Model MAC address considerations
EUI48 values Model I
– EC ENNI Maintenance Associations– EC Network Operator Maintenance Associations– MAC address considerations
Model II – EC Network Operator Maintenance Associations– EC ENNI Maintenance Associations
Comparison of Models I and II Conclusion
3
Introduction
The following slides focus on the DRNI functionality and associated MAC addresses in the portal nodes of a DRNI protected Ethernet ENNI; the slides are a follow up of axbq-vissers-drni-and-distributed-protection-examples-a3-0911-v01.pptx
The carrier network specific functionality has been removed; it will be addressed in a separate document
The simplest DRNI configuration is assumed, including two nodes in a portal, with one ENNI Link per node and an intra-DAS (virtual) link between the two nodes in the portal
A portal supports DRNI protected ECs and unprotected ECs (as per MEF requirement); unprotected ECs are considered to be outside DRNI control
Two data plane models I and II for PB, PBB IB-BEB, PBB-TE IB-BEB and EOTN TB portals are presented and compared from a MEP/MIP deployment
MAC address requirement is investigated to understand which functions must use the ENNI or Intra-DAS link port’s EUI48 values, which functions may use these values and which functions must not use these values
4
PB Portal DRNI Data Plane Model
5
19.2/3/519.2/3/5 19.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
PB Portal DRNI Data Plane Model
S-RelayS-Relay
Intra-DAS Link
EC NOMEP
EC ENNIMEP
EC SP/ENNIMIP
ENNI Link MEP
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
EC NO/ENNI MIP
There are two models to configure the EC’s MEP and MIP functions in the data plane (see next slides):Model I) Unprotected ECs and DRNI protected ECs:
- NO MEP, SP MIP and ENNI MEP on ENNI Link Ports - NO MIP on Intra-DAS Link Ports
Model II) Unprotected ECs: - NO MEP, SP MIP and ENNI MEP on ENNI Link Ports
DRNI protected ECs: - NO MEP, SP MIP and ENNI MEP on Active Gateway’s ENNI or Intra-DAS Link Port - ENNI MIP on Standby Gateway’s ENNI and Intra-DAS Link Ports
NO: Network Operator, SP: Service Provider
Link end points
Link MEP
6
19.2/3/519.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
PB Portal DRNI Data Plane Model I All ECs: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
S-RelayS-Relay
Intra-DAS Link
EC NOMEP
EC ENNIMEP
EC SPMIP
Link MEP
EC NO MIP EC NO MIP
ENNI LinkMEP
6.9, 9.5b
8.5
19.2
6.7
802.3
Unprotected EC #4 Protected EC
#2
Protected EC #1
EC NOMEP
EC ENNIMEP
EC SPMIP
ENNI Link MEP
Link MEP
Unprotected EC #3
Protected EC #1 has its NO MEP, SP MIP and ENNI MEP functions on the ENNI Link 2 Port. In addition EC NO MIP functions are present on the left/right Intra-DAS Ports.
Unprotected EC #4 has its NO MEP, SP MIP and ENNI MEP functions on ENNI Link 1 Port.
Protected EC #2’s has its NO MEP, SP MIP and ENNI MEP functions on the ENNI Link 2 Port.
Unprotected EC #3 has its NO MEP, SP MIP and ENNI MEP functions on ENNI Link 2 Port.
NO: Network Operator, SP: Service Provider See also backup slides
7
19.2/3/519.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/5
PB Portal DRNI Data Plane Model IIProtected EC: NO MEP, EC SP MIP, EC ENNI MEP on Active GatewayUnprotected EC: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
19.2/3/5
S-RelayS-Relay
Intra-DAS Link
EC NO MEP
EC ENNI MEP
EC SP MIP
Link MEP
EC ENNI MIP
Link MEPENNI Link
MEP
EC SP/ENNIMIP
Half-DASHalf-DAS
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
Unprotected EC #4 Protected EC
#2
Protected EC #1
Unprotected EC #3
EC NOMEP
EC ENNIMEP
Protected EC #1’s active GW is left, and its NO MEP, SP MIP and ENNI MEP functions are on its Intra-Das Port. In addition EC ENNI MIP functions are present on the Intra-DAS Port and ENNI Link 2 Ports in the right node.
Unprotected EC #4 has its NO MEP, SP MIP and ENNI MEP functions on ENNI Link 1 Port.
Protected EC #2’s active GW is right, and its NO MEP, SP MIP and ENNI MEP functions are on its ENNI Link 2 Port.
Unprotected EC #3 has its NO MEP, SP MIP and ENNI MEP functions on ENNI Link 2 Port.
NO: Network Operator, SP: Service Provider See also backup slides
8
Comparison of PB Portal DRNI Data Plane Models I and II
Model I ENNI Link ports
EC Up MEP and EC Down MEP functions are active for every S-VID
EC MIP functions are active for every S-VID All EC MIP functions operate on SP MA level
Intra-DAS Link ports EC MIP functions are active for every S-VID All EC MIP functions operate on NO MA level
Static EC MEP and MIP activation on ENNI and Intra-DAS ports
Model II ENNI Link ports
EC Up MEP and EC Down MEP functions may be active or inactive; active if node is Active GW or if EC is unprotected, inactive if node is Standby GW
EC MIP functions are active for every S-VID EC MIP functions may operate at SP or ENNI MA
levels; SP MA level if node is Active GW or if EC is unprotected, ENNI MA level if node is Standby GW
Intra-DAS Link ports EC Up MEP and EC Down MEP functions
may be active or inactive; active if node is Active GW, inactive if node is Standby GW
EC MIP functions are active for every S-VID EC MIP functions may operate at SP or
ENNI MA levels; SP MA level if node is Active GW, ENNI MA level if node is Standby GW
Dynamic EC MEP and MIP activation on ENNI and Intra-DAS ports
9
PBB IB-BEB Portal DRNI Data Plane Model
10
19.2/3/5 19.2/3/519.2/3/5 19.2/3/5
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
PBB IB-BEB Portal DRNI Data Plane Model(separate B- and S-VLAN fabrics)
19.2
6.7
802.n
19.2
6.7
802.n
S-RelayS-Relay
B-Relay B-Relay
19.2/3/5
6.9, 9.5b
8.5
19.2/3/5
6.9, 9.5b
8.5
BVLAN MEP
LinkMEP
These functions support the BVLAN connections and can be removed from the view; see next slide
Intra-DAS Virtual Link
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
NO: Network Operator, SP: Service Provider
EC NOMEP
EC ENNIMEP
EC SP/ENNIMIP EC NO/ENNI MIP
BVLAN end points
BVLAN MIP
ENNI Link MEP
11
19.2/3/519.2/3/5 19.2/3/5
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
PBB IB-BEB Portal DRNI Data Plane Model(separate B- and S-VLAN fabrics)
S-RelayS-Relay
Intra-DAS BVLAN (Virtual Link)
BVLAN MEP
EC NOMEP
EC E-NNIMEP
EC SPMIP EC NO MIP
BVLAN connections represent the lower layersB-MAC space
The DAS function operates in the S-MAC spacec6.10: S-MAC B-MACc6.11: BSI Group Address Default Backbone Destination
(DBD); DBD = {CBP, Group} Address
S-MAC space
BVLAN connections replace the Ethernet Link connections in the PB case. SVLAN EC examples are very similar to SVLAN EC examples in PB case
Half-DASHalf-DAS
E-NNILink 1
19.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
ENNI Link MEP
12
19.2/3/519.2/3/5 19.2/3/5
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
PBB IB-BEB Portal DRNI Data Plane Model (separate B- and S-VLAN fabrics)
S-RelayS-Relay
Intra-DAS BVLAN (Virtual Link)
BVLAN MEP
EC NOMEP
EC E-NNIMEP
EC SPMIP EC NO MIP
BVLAN connections represent the lower layersB-MAC space
S-MAC space
Half-DASHalf-DAS
E-NNILink 1
19.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
MUX MUX MUX MUX
The functionality of the clause 6.9, 9.5b, 8.5, 6.14, 6.14 and 6.11 functions on PIP/CBP can be summarized as a (set of) S-VLAN into B-VLAN ‘MUX’ function(s).
PBB data plane model is now very similar with PB data plane model; PBB has a Intra-DAS (BVLAN) virtual link, where PB has a Intra-DAS link.
ENNI Link MEP
13
PBB IB-BEB Portal DRNI Data Plane Models I and II
The behaviour is the same as for the PB Portal DRNI Data Plane Models I and II
14
PBB-TE IB-BEB Portal DRNI Data Plane Model
15
19.2/3/519.2/3/5 19.2/3/5 19.2/3/5
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
PBB-TE IB-BEB Portal DRNI Data Plane Model (separate TESI and S-VLAN fabrics)
19.2
6.7
802.n
19.2
6.7
802.n
S-RelayS-Relay
TESI-Relay TESI-Relay
19.2/3/5
6.9, 9.5b
8.5
19.2/3/5
6.9, 9.5b
8.5
Intra-DAS Virtual Link
TESI MEP
LinkMEP
EC NOMEP
EC E-NNIMEP
EC SPMIP EC NO MIP
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
These functions support the TESI connections and can be removed from the view; see next slide
TESI end points
TESI MIP
ENNI Link MEP
16
19.2/3/519.2/3/5
PBB-TE IB-BEB Portal DRNI Data Plane Model (separate TESI and S-VLAN fabrics)
19.2/3/5 19.2/3/5
Half-DAS
S-Relay
Half-DAS
S-Relay
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
Intra-DAS TESI (Virtual Link)
TESI MEP
EC NOMEP
EC E-NNIMEP
EC SPMIP EC NO MIP
ESP-MAC space
S-MAC space
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
ENNI Link MEP
17
19.2/3/519.2/3/5
PBB-TE IB-BEB Portal DRNI Data Plane Model (separate TESI and S-VLAN fabrics)
19.2/3/5 19.2/3/5
Half-DAS
S-Relay
Half-DAS
S-Relay
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
6.14
6.10
6.14
6.11, 9.5c
19.2/3/5
Intra-DAS TESI (Virtual Link)
TESI MEP
EC NOMEP
EC E-NNIMEP
EC SPMIP EC NO MIP
ESP-MAC space
S-MAC space
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5
6.9
8.5MUX MUX MUX MUX
The functionality of the clause 6.9, 9.5b, 8.5, 6.14, 6.14 and 6.11 functions on PIP/CBP can be summarized as a (set of) S-VLAN into TESI ‘MUX’ function(s).
PBB-TE data plane model is now very similar with PB data plane model; PBB-TE has a Intra-DAS (TESI) virtual link, where PB has a Intra-DAS link.
ENNI Link MEP
18
PBB-TE IB-BEB Portal DRNI Data Plane Models I and II
The behaviour is the same as for the PB Portal DRNI Data Plane Models I and II
19
EOTN TB Portal DRNI Data Plane Model
20
19.2/3/519.2/3/5
EOTN TB Portal DRNI Data Plane Model (separate ODUk and S-VLAN fabrics)
S-RelayS-Relay
ODUk-Relay ODUk-Relay
ODU MUX
Intra-DAS Virtual Link
ODUk MEP
OTN LinkMEP
EC NOMEP
EC E-NNIMEP
EC SPMIP
These functions support the ODUk connections and can be removed from the view; see next slide
ODU MUX
EC NO MIP
Half-DAS
E-NNILink 1
19.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
19.2/3/5
6.9, 9.5b
8.5
6.9, 9.5b
8.5
6.15 6.15
Half-DAS
6.9, 9.5b
8.5
6.9, 9.5b
8.5
6.156.15
ODUk end points
ENNI Link MEP
21
19.2/3/5 19.2/3/5
EOTN TB Portal DRNI Data Plane Model (separate ODUk and S-VLAN fabrics)
19.2/3/5 19.2/3/5
S-RelayS-Relay
Intra-DAS ODUk (Virtual Link)
ODUk MEP
EC NOMEP
EC E-NNIMEP
EC SPMIP
ODUk connections represent the lower layers
EC NO MIP
S-MAC space
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
6.9, 9.5b
8.5
6.9, 9.5b
8.5
6.15 6.15
6.9, 9.5b
8.5
6.9, 9.5b
8.5
6.156.15ENNI Link MEP
22
19.2/3/5 19.2/3/5
EOTN TB Portal DRNI Data Plane Model (separate ODUk and S-VLAN fabrics)
19.2/3/5 19.2/3/5
S-RelayS-Relay
Intra-DAS ODUk (Virtual Link)
ODUk MEP
EC NOMEP
EC E-NNIMEP
EC SPMIP
ODUk connections represent the lower layers
EC NO MIP
S-MAC space
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
6.9, 9.5b
8.5
6.9, 9.5b
8.5
6.15 6.15
6.9, 9.5b
8.5
6.9, 9.5b
8.5
6.156.15MUX MUX MUX MUX
The functionality of the clause 6.9, 9.5b, 8.5 and 6.15 functions on ONP can be summarized as a (set of) S-VLAN into ODUk ‘MUX’ function(s).
EOTN TB data plane model is now very similar with PB data plane model; EOTN TB has a Intra-DAS (ODUk) virtual link, where PB has a Intra-DAS link.
ENNI Link MEP
23
EOTN TB Portal DRNI Data Plane Models I and II
The behaviour is the same as for the PB Portal DRNI Data Plane Models I and II
24
Summary
EC DRNI functionality is independent of the network technology deployed in a carrier network and used for the Intra-DAS Link Intra-DAS Link is either supported by an Ethernet Link, a BVLAN based virtual link, a TESI
based virtual link, or an ODUk based virtual link DRNI operation is agnostic to the specific Intra-DAS link type A Generic DRNI Data Plane Model can be used for further DRNI specific architecture
considerations
Data Plane Models I and II deploy the same data plane; the difference between the two models is the location of the EC NO MEP and EC ENNI MEP functions Model I has those MEPs only on ENNI Link ports less complex model Model II has those MEPs on ENNI Link and Intra-DAS Link ports more complex model
25
Generic DRNI Data Plane Model
DRNI Data Plane Models can be addressed in a generic, Intra-DAS Link technology agnostic manner
The link or virtual link between the two nodes in a portal may be shared by Intra-DAS and Network ECs. See top figure in next slide.
Alternatively, Intra-DAS ECs and Network ECs are carried over dedicated links or virtual links. See bottom figure in next slide.
The EC NO MEP, EC SP MIP, EC ENNI MEP and EC NO MIP function allocation in the DRNI is however agnostic to those shared/dedicated (virtual) link cases
26
19.2/3/519.2/3/5 19.2/3/5
MUX
19.2/3/5
MUX
Generic DRNI Data Plane Model
S-RelayS-Relay
Intra-DAS (Virtual) Link
EC NOMEP
EC ENNIMEP
EC SP/ENNIMIP
ENNI Link MEP
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
EC NO/ENNI MIP
19.2/3/519.2/3/5 19.2/3/5
MUX
19.2/3/5
MUX
S-RelayS-Relay
Intra-DAS (Virtual) Link
EC NOMEP
EC ENNIMEP
EC SP/ENNIMIP
ENNI Link MEP
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
EC NO/ENNI MIP
MUX MUX
single (virtual) link endpoint
single (virtual) link endpoint
multiple virtual link endpoints
multiple virtual link endpoint
the (virtual) link may be shared by Intra-DAS ECs and Network ECs
Intra-DAS ECs may use a dedicated (virtual) link.Network ECs may use another (virtual) link.
Server MEP
Server MEP
27
MAC Address Considerations
28
19.2/3/519.2/3/5 19.2/3/5
MUX
19.2/3/5
MUX
EUI48 value allocation (@A, @B, @C, @D)
S-RelayS-Relay
Intra-DAS (Virtual) Link
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
19.2/3/519.2/3/5 19.2/3/5
MUX
19.2/3/5
MUX
S-RelayS-Relay
Intra-DAS (Virtual) Link
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
MUX MUX
@A @B @C @D
@A @B @C @D
Physical subsystems (e.g. ports) have an EUI48 value. ENNI and Intra-DAS Link ports in a two node portal may have EUI48 values @A, @B, @C, @D as illustrated in the figures above and below. By default, the MAC Source Address value of primitives generated on those ports inherit the port’s EUI48 value. Is there a requirement to overrule the inheriting of local EUI48 value for a MAC Source Address within DRNI?
29
MAC Address Considerations for Generic DRNI Data Plane Model I’s EC ENNI MA and EC NO MA
30
@A @B @C @DMUX
19.2
MUX
19.2
Intra-DAS (Virtual) Link
19.2/3/519.2/3/5 19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
Generic DRNI Data Plane Model I EC ENNI MA
S-RelayS-Relay
EC NOMEP
EC ENNIMEP
EC SPMIP
Server MEP
EC NO MIP EC NO MIP
ENNI LinkMEP
EC NOMEP
EC ENNIMEP
EC SPMIP
ENNI Link MEP Server MEP
@a @b @c @dMUX
19.2
MUX
19.2
Intra-DAS (Virtual) Link
19.2/3/519.2/3/5 19.2/3/519.2/3/5
Half-DASHalf-DAS
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
S-RelayS-Relay
EC NOMEP
EC ENNIMEP
EC SPMIP
Server MEP
EC NO MIP EC NO MIP
ENNI LinkMEP
EC NOMEP
EC ENNIMEP
EC SPMIP
ENNI Link MEP Server MEP
The EC ENNI MAs are fixed MAs; MEP ID and MA ID values in each EC ENNI MEP can be configured permanently; MAC SA values can be inherited from the EUI48 value of ports (@A,@D,@a,@d)E
C E
NN
I M
A
31
Generic DRNI Data Plane Model I4 alternative P2P EC Network Operator (NO) MAs
@A @B @C @DMUX
19.2
MUX
19.2
Intra-DAS (Virtual) Link
19.2/3/519.2/3/5 19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
S-RelayS-Relay
EC NOMEP
EC ENNIMEP
EC SPMIP
Server MEP
EC NO MIP EC NO MIP
ENNI LinkMEP
EC NOMEP
EC ENNIMEP
EC SPMIP
ENNI Link MEP Server MEP
Active GWStandby GW
P2P EC Network Operator MA
animated slide
Three alternatives for the operation of these two EC NO MEP functions in the two nodes in a carrier’s portal:1. Behave as two independent MEP functions with their own MEPID (2, 3) and their own MAC Address (@A, @D)2. Behave as one virtual MEP function with the same MEPID (2) but with different MAC Addresses (@A, @D)3. Behave as one virtual MEP function with the same MEPID (2) and the same MAC address (@S)
MEPID=1
32
Generic DRNI Data Plane Model I 4 alternative MP EC Network Operator (NO) MAs
@A @B @C @DMUX
19.2
MUX
19.2
Intra-DAS (Virtual) Link
19.2/3/519.2/3/5 19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
S-RelayS-Relay
EC NOMEP
EC ENNIMEP
EC SPMIP
Server MEP
EC NO MIP EC NO MIP
ENNI LinkMEP
EC NOMEP
EC ENNIMEP
EC SPMIP
LinkMEP Server MEP
Active GWStandby GW
MP EC Network Operator MA
animated slide
Three alternatives for the operation of these two EC NO MEP functions in the two nodes in a carrier’s portal:1. Behave as two independent MEP functions with their own MEPID (4, 5) and their own MAC Address (@A, @D)2. Behave as one virtual MEP function with the same MEPID (4) but with different MAC Addresses (@A, @D)3. Behave as one virtual MEP function with the same MEPID (4) and the same MAC address (@S)
MEPID=1MEPID=3MEPID=2
33
Comparing alternatives 1, 2 and 3 from MEP operation
Alternative 1 P2P EC EC NO MEP functions may
deploy multicast DA values; agnostic to different MAC Address values
MEP #1 will detect loss of CCM from either MEP #2 or MEP #3
Either MEP #2 or MEP #3 will detect loss of CCM from MEP #1
Alternative 1 MP EC Same loss of CCM issue EC NO MEP functions must
deploy unicast DA values for MCC, LMM, 1DM, DMM and SLM
MEPs #1, #2, #3 will have to adapt their unicast DA value for MCC, LMM, 1DM, DMM and SLM when the active ENNI Link is changed; currently not supported in G.798
Alternative 2 P2P EC EC NO MEP functions may
deploy multicast DA values; agnostic to different MAC Address values
No loss of CCM detection in MEP #1 as MEP #2/#3 have same MEPID (2)
Either MEP #2 or MEP #3 will detect loss of CCM from MEP #1; should be suppressed under control of Virtual MEP behaviour
Alternative 2 MP EC EC NO MEP functions must
deploy unicast DA values for MCC, LMM, 1DM, DMM and SLM
MEPs #1, #2, #3 will have to adapt their unicast DA value for MCC, LMM, 1DM, DMM and SLM when the active ENNI Link is changed; currently not supported in G.798
Alternative 3 P2P EC EC NO MEP functions may
deploy multicast DA values; agnostic to different MAC Address values
No loss of CCM detection in MEP #1 as MEP #2/#3 have same MEPID (2)
Either MEP #2 or MEP #3 will detect loss of CCM from MEP #1; should be suppressed under control of Virtual MEP behaviour
Alternative 3 MP EC EC NO MEP functions must
deploy unicast DA values for MCC, LMM, 1DM, DMM and SLM
No adaptation of the unicast DA value for MCC, LMM, 1DM, DMM and SLM in MEPs #1, #2, #3 when the active ENNI Link is changed
Y.1731 Ethernet OAM and G.8021 Ethernet Equipment support the use of unicast DA values for MCC, LMM/R 1DM, DMM/R and SLM/R OAM. In P2P EC cases, multicast DA values for MCC, LMM, 1DM, DMM and SFM may be used instead of unicast DA values.
P2P & MP EC OAM problems MP EC OAM problems No EC OAM problems
34
Summary
From the perspective of the EC Network Operator MEP operation it is helpful if the EC NO MEP functions in the ENNI Link ports share a common MAC address (@S). This address @S should be used instead of the local EUI48 values (@A, @D).
All other MEP functions and all the NO MIP functions may use the EUI48 value of the local port
Question 1: Is it possible to configure the MAC Address of an individual MEP to overrule the local EUI48 value?
Question 2: From an Ethernet OAM perspective it is possible to operate the EC SP MIP function on the basis of the EUI48 value of the local port; would there be an advantage if the EC SP Up Half MIP function deploys the common MAC address @S in a PBB IB-BEB portal case?
35
MAC Address Considerations for Generic DRNI Data Plane Model II
36
Generic DRNI Data Plane Model II 4 alternative P2P EC Network Operator (NO) MAs
@A @B @C @DMUX
19.2
MUX
19.2
Intra-DAS (Virtual) Link
19.2/3/519.2/3/5 19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
S-RelayS-Relay
EC NOMEP
EC ENNIMEP
EC SPMIP
Server MEP
EC SP MIP EC SP MIP
ENNI LinkMEP
EC NOMEP
EC ENNIMEP
EC SPMIP
LinkMEP Server MEP
Active GWStandby GW
P2P EC Network Operator MA
animated slide
Three alternatives for the operation of these four EC NO MEP functions in the two nodes in a carrier’s portal:1. Behave as four independent MEP functions with their own MEPID (2, 3,4,5) and their own MAC Address
(@A,@B,@C,@D)2. Behave as one virtual MEP function with the same MEPID (2) but with different MAC Addresses (@A,@B,@C,@D)3. Behave as one virtual MEP function with the same MEPID (2) and the same MAC address (@S)
MEPID=1
EC NO MEP EC NO MEP
37
Generic DRNI Data Plane Model II 4 alternative MP EC Network Operator (NO) MAs
@A @B @C @DMUX
19.2
MUX
19.2
Intra-DAS (Virtual) Link
19.2/3/519.2/3/5 19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
S-RelayS-Relay
EC NOMEP
EC ENNIMEP
EC SPMIP
Server MEP
EC SP MIP EC SP MIP
ENNI LinkMEP
EC NOMEP
EC ENNIMEP
EC SPMIP
LinkMEP Server MEP
Active GWStandby GW
animated slide
Three alternatives for the operation of these four EC NO MEP functions in the two nodes in a carrier’s portal:1. Behave as four independent MEP functions with their own MEPID (4,5,6,7) and their own MAC Address
(@A,@B,@C,@D)2. Behave as one virtual MEP function with the same MEPID (4) but with different MAC Addresses (@A,@B,@C,@D)3. Behave as one virtual MEP function with the same MEPID (4) and the same MAC address (@S)
MEPID=1
EC NO MEP EC NO MEP
MP EC Network Operator MA
MEPID=3MEPID=2
38
@A @B @C @DMUX
19.2
MUX
19.2
Intra-DAS (Virtual) Link
19.2/3/519.2/3/5 19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
Generic DRNI Data Plane Model II Unprotected EC ENNI MA
S-RelayS-Relay
EC NOMEP
EC ENNIMEP
Server MEP
EC SP MIPEC ENNI MIP
EC NO MIPEC ENNI MIP
ENNI LinkMEP
EC NO MEP
EC ENNIMEP
EC SP MIPEC ENNI MIP
ENNI Link MEP Server MEP
@a @b @c @dMUX
19.2
MUX
19.2
Intra-DAS (Virtual) Link
19.2/3/519.2/3/5 19.2/3/519.2/3/5
Half-DASHalf-DAS
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
S-RelayS-Relay
EC NOMEP
EC ENNIMEP
EC SPMIP
Server MEP
EC NO MIP EC NO MIP
ENNI LinkMEP
EC NOMEP
EC ENNIMEP
EC SPMIP
ENNI Link MEP Server MEP
EC
EN
NI
MA
EC ENNI MEP
EC NO MEP
EC SP MIPEC ENNI MIP
The Unprotected EC ENNI MAs are fixed MAs; MEP ID and MA ID values in each EC ENNI MEP can be configured permanently; MAC SA values can be inherited from the EUI48 value of ports (@A,@D,@a,@d).
39
@A @B @C @DMUX
19.2
MUX
19.2
Intra-DAS (Virtual) Link
19.2/3/519.2/3/5 19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
Generic DRNI Data Plane Model II 8 alternative DRNI Protected EC ENNI MAs
S-RelayS-Relay
EC NOMEP
EC ENNIMEP
Server MEP
EC SP MIPEC ENNI MIP
EC SP MIPEC ENNI MIP
ENNI LinkMEP
EC NO MEP
EC ENNIMEP
EC SP MIPEC ENNI MIP
ENNI Link MEP Server MEP
@a @b @c @dMUX
19.2
MUX
19.2
Intra-DAS (Virtual) Link
19.2/3/519.2/3/5 19.2/3/519.2/3/5
Half-DASHalf-DAS
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
S-RelayS-Relay
EC NOMEP
EC ENNIMEP
Server MEP ENNI LinkMEP
EC NOMEP
EC ENNIMEP
ENNI Link MEP Server MEP
EC ENNI MEP
EC NO MEP
EC SP MIPEC ENNI MIP
The DRNI protected EC ENNI MAs are dynamic MAs; their configuration depends on the location of the Active Gateway in each Portal. Each EC has eight alternative ENNI MA configurations in this basic DRNI architecture. COMPLEX!!
animated slide
EC ENNI MEP
EC NO MEP
EC SP MIPEC ENNI MIP
EC SP MIPEC ENNI MIP
EC SP MIPEC ENNI MIP
EC ENNI MEP
EC NO MEP
EC SP MIPEC ENNI MIP
EC ENNI MEP
EC NO MEP
40
Comparison of DRNI Data Plane Models I and II
Model I has Very simple and fixed EC ENNI MA
architecture for unprotected and DRNI protected ECs
Four alternative EC Network Operator MA configurations with endpoints on the E-NNI Link ports
Fixed configuration of EC’s Network Operator MEP, Service Provider MIP, ENNI MEP and Network Operator MIP functions
Simple operation & management
Model II has Very simple and fixed EC ENNI MA
architecture for unprotected Ecs Very complex and dynamic EC ENNI MA
architecture for DRNI protected ECs with already eight alternative configurations for a basic DRNI architecture
Four alternative EC Network Operator MA configurations with endpoints on the E-NNI and Intra-DAS Link ports
Dynamic configuration of EC’s Network Operator MEP, Service Provider MIP, ENNI MEP and ENNI MIP functions
Complex operation & management
41
Conclusion
DRNI Data Plane Model II introduces unnecessary operational and management complexity
Therefore we should select DRNI Data Plane Model I for inclusion in p802.1AXbq
From an Ethernet OAM perspective, the Network Operator MEP functions on the ENNI Link ports for a DRNI protected EC should
deploy a common MAC address, overruling the local EUI48 value Network Operator MEP functions in unprotected ECs and ENNI MEP functions for all ECs on
ENNI Link ports should deploy the local EUI48 value as their MAC address Network Operator MIP functions for ECs on Intra-DAS Link ports should deploy the local EUI48
as their MAC address Service Provider MIP functions for unprotected ECs should use the local EUI48 value as their
MAC address Service Provider Down Half MIP functions for DRNI protected ECs should use the local EUI48
value as their MAC address Service Provider Up Half MIP functions for a DRNI protected EC could use the local EUI48
value as their MAC address, but in a PBB IB-BEB portal it might be beneficial to use a common MAC address, overruling the local EUI48 value (for further study)
42
Backup
EC MEP/MIP locations in Data Plane Models I and II
43
19.2/3/519.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
PB Data Plane Model I of DRNI functionalityAll ECs: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
S-RelayS-Relay
Intra-DAS Link
EC NOMEP
EC ENNIMEP
EC SPMIP
Link MEP
@O@S
@P@S
@K@K
@Q@S
@R@S
@L@L
EUI48:MAC:
ENNI LinkMEP
6.9, 9.5b
8.5
19.2
6.7
802.3
Protected EC #1
Link MEP
NO: Network Operator, SP: Service Provider
NO MEPSP MIP
ENNI MEP
44
19.2/3/519.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
PB Data Plane Model I of DRNI functionalityAll ECs: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
S-RelayS-Relay
Intra-DAS Link
EC NOMEP
EC ENNIMEP
EC SPMIP
Link MEP
@O@S
@P@S
@K@K
@Q@S
@R@S
@L@L
EUI48:MAC:
EC NO MIP EC NO MIP
ENNI LinkMEP
6.9, 9.5b
8.5
19.2
6.7
802.3
Protected EC #1
Link MEP
NO: Network Operator, SP: Service Provider
NO MEPSP MIP
ENNI MEP
NO MIP NO MIP
45
19.2/3/519.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
PB Data Plane Model I of DRNI functionalityAll ECs: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
S-RelayS-Relay
Intra-DAS Link
Link MEP
@O@S
@P@S
@K@K
@Q@S
@R@S
@L@L
EUI48:MAC:
EC NO MIP EC NO MIP
6.9, 9.5b
8.5
19.2
6.7
802.3
Protected EC #1
EC NOMEP
EC ENNIMEP
EC SPMIP
LinkMEP Link MEP
NO: Network Operator, SP: Service Provider
NO MEPSP MIP
ENNI MEP
NO MIP NO MIP
46
19.2/3/519.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
PB Data Plane Model I of DRNI functionalityAll ECs: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
S-RelayS-Relay
Intra-DAS Link
@O@S
@P@S
@K@K
@Q@S
@R@S
@L@L
EUI48:MAC:
6.9, 9.5b
8.5
19.2
6.7
802.3
Protected EC #1
EC NOMEP
EC ENNIMEP
EC SPMIP
LinkMEP
NO: Network Operator, SP: Service Provider
NO MEPSP MIP
ENNI MEP
47
19.2/3/519.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
S-RelayS-Relay
Intra-DAS Link
EC NOMEP
EC ENNIMEP
EC SPMIP
@O@S
@P@S
@K@K
@Q@S
@R@S
@L@L
EUI48:MAC:
ENNI LinkMEP
6.9, 9.5b
8.5
19.2
6.7
802.3
Protected EC #1
NO: Network Operator, SP: Service Provider
PB Data Plane Model II of DRNI functionaltiyProtected EC: NO MEP, EC SP MIP, EC ENNI MEP on Active GatewayUnprotected EC: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
NO MEPSP MIP
ENNI MEP
48
19.2/3/519.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
S-RelayS-Relay
Intra-DAS Link
EC ENNIMIP
Link MEP
@O@S
@P@S
@K@K
@Q@S
@R@S
@L@L
EUI48:MAC:
EC SP MIP EC ENNI MIP
ENNI LinkMEP
6.9, 9.5b
8.5
19.2
6.7
802.3
Protected EC #1
EC NO MEP
Link MEP
NO: Network Operator, SP: Service Provider
PB Data Plane Model II of DRNI functionaltiyProtected EC: NO MEP, EC SP MIP, EC ENNI MEP on Active GatewayUnprotected EC: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
EC ENNI MEP
NO MEPSP MIP
ENNI MEP
ENNI MIP ENNI MIP
49
19.2/3/519.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
S-RelayS-Relay
Intra-DAS Link
EC NOMEP
EC ENNIMEP
EC SPMIP
Link MEP
@O@S
@P@S
@K@K
@Q@S
@R@S
@L@L
EUI48:MAC:
EC NO MIP EC NO MIP
ENNI LinkMEP
6.9, 9.5b
8.5
19.2
6.7
802.3
Protected EC #1
EC NOMEP
EC ENNIMEP
EC SPMIP
LinkMEP Link MEP
NO: Network Operator, SP: Service Provider
PB Data Plane Model II of DRNI functionaltiyProtected EC: NO MEP, EC SP MIP, EC ENNI MEP on Active GatewayUnprotected EC: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
NO MEPSP MIP
ENNI MEP
ENNI MIP ENNI MIP
50
19.2/3/519.2/3/5
6.9, 9.5b
8.5
19.2
6.7
802.3
19.2/3/519.2/3/5
Half-DASHalf-DAS
E-NNILink 1
6.9, 9.5b
8.5
19.2
6.7
802.3
6.9, 9.5b
8.5
19.2
6.7
802.3
E-NNILink 2
S-RelayS-Relay
Intra-DAS Link
EC NOMEP
EC ENNIMEP
EC SPMIP
Link MEP
@O@S
@P@S
@K@K
@Q@S
@R@S
@L@L
EUI48:MAC:
EC NO MIP EC NO MIP
ENNI LinkMEP
6.9, 9.5b
8.5
19.2
6.7
802.3
Protected EC #1
EC NOMEP
EC ENNIMEP
EC SPMIP
LinkMEP Link MEP
NO: Network Operator, SP: Service Provider
PB Data Plane Model II of DRNI functionaltiyProtected EC: NO MEP, EC SP MIP, EC ENNI MEP on Active GatewayUnprotected EC: NO MEP, EC SP MIP, EC ENNI MEP on ENNI Link Port
NO MEPSP MIP
ENNI MEP
51
MAC Address & MEP ID
DRNI presents the Network Operator (NO) MEP functions for an EC on the different E-NNI ports as one virtual NO MEP function with one S-MAC Address and one MEP ID
Question: Is the same S-MAC address really required? Evaluate requirement from perspective of:
• CFM (CCM, LBM/R, SLM/R, LMM/R, DMM/R, …) between NO MEP on UNI-N and E-NNI ports and MIP functions on I-NNI ports inside carrier network
• B-MAC learning inside B-VLAN relays
• S-MACB-MAC learning inside c6.10 PIP function
• Translation of ‘BSI Group Address’ into ‘Default Backbone Destination (DBD)’ (and vice versa) inside c6.11 CBP function
Question: Is the same MEP ID really required? Evaluate requirement from perspective of:
• CFM (CCM) between NO MEP functions on UNI-N and E-NNI ports
DRNI presents the Service Provider (SP) MIP functions for an EC on the different E-NNI ports as one virtual SP MIP function with one S-MAC Address
Question: Is the same S-MAC address really required? Evaluate requirement from perspective of:
• CFM (LBM/R, LTM/R) between SP MEPs on UNI-N ports and SP MIPs on E-NNI ports
• B-MAC learning inside B-VLAN relays
• S-MACB-MAC learning inside c6.10 PIP function
52
MAC Address & MEP ID
DRNI presents the E-NNI MEP functions for an EC on the different E-NNI ports as one virtual E-NNI MEP function with one S-MAC Address and one MEP ID
Question: Is the same S-MAC address really required? Evaluate requirement from perspective of:
• CFM (CCM, LBM/R, SLM/R, LMM/R, DMM/R, …) between E-NNI MEP functions (Data Plane Model I), or between E-NNI MEP functions on E-NNI or Intra-DAS ports and DRNI MIP functions on Intra-DAS or E-NNI ports (Model II)
• S-MAC learning inside S-VLAN relays in DRNI
Question: Is the same MEP ID really required? Evaluate requirement from perspective of:
• CFM (CCM) between E-NNI MEP functions on E-NNI ports (model I), or E-NNI MEP functions on E-NNI or Intra-DAS ports (model II)
