1
1 DRNI and Distributed Protection Examples Maarten Vissers 2011-09-26 v01 Based on slides presented in 802.1 IW meeting in Nanjing on Thursday Sept 22 Details have been added to reflect the discussions during the presentation MAC Address considerations have been added based on discussions during the presentation and questions have been added triggered by comment that CFM has been developed under the assumption that MAC address of MEP/MIP can be changed during the lifetime of the EC

18
18 Notes/Observations PB Portal Data Plane Model  Use of MAC Address values @S and @W/@P at multiple locations reduces ability to perform connectivity fault localization  Physical subsystem is identified either by build in EUI-48 value, or by operator configured EUI-48 value; default MAC Address is inherited from physical subsystem  Distributed protection/restoration introduces requirement to configure MAC Address of selected MEP/MIP sets (on a service instance (EC) basis); not required/supported today  EC NO MA supports endpoint on E-NNI port card  I-NNI port may have to support network link, intra-DSS link and intra-DAS link and the associated MAC Address values Bridge Model of DAS  Removes the ability to localize misconnection in a Half-DAS function due to use of common MAC address values (@S)  Require that Intra-DAS link port uses EC NO MEP and EC E-NNI MEP functions and @S  EC NO MA does not always support endpoint on E-NNI port card; instead endpoint may be at active gateway node, and the E-NNI port is behind the Intra-DAS link

19
19 PBB IB-BEB Portal with DRNI; EC SNCP in carrier network Two Data Plane models (I, II) are possible, which differ in the location of the EC Network Operator MEP and EC E-NNI MEP functions; see PB slides for the differences. Data Plane model I is used in the slides hereafter Two data plane models (1,2) are possible, which differ in the presence of a single or multiple switch fabrics: 1)Separate B-VLAN switch fabric and S-VLAN switch fabric 2)Combined B-/S-VLAN switch fabric

20
20 Carrier B Carrier A DRNI in PBBN IB-BEBs – Multi-domain PBBN For the case the carrier network consists of multiple PBBN domains (e.g. PBBN 1, PBBN 2), protection of the S-VLAN is not possible by means of B-VLAN recovery under all conditions Instead it will be necessary to protect the individual S-VLAN connections by means of G.8031 ETH SNC Protection. Working and Protection S-VLAN connections must be carried by disjoint B-VLANs in each PBBN and by disjoint LANs between PBBN domains PBBN 1 PBBN 2 PBBN 3 IB-BEB PBB- TEN 4 IB-BEB DSNCP WP SNCP DSNCP