Axbq Vissers Drni and Sncp Inter Working 0511 v00

8/2/2019 Axbq Vissers Drni and Sncp Inter Working 0511 v00

1/20

1

DRNI and G.8031 ETH SNCP interworking

Maarten Vissers

2011-05-09


2/20

2

Introduction

The following slides illustrate the structure of an EC which is set up tosupport a protected E-Line service EVC in

One Carrier network (X)

Two Carrier networks (X,Y)

Each Carrier network includes access, metro and core domains

EC is set up with Dual Node Interconnections between Carrier Networks andoptionally also between domains

Between carrier X/carrier Y networks four nodes are used to interconnect

If EC in Carrier network is more than 1200 km, it is necessary to segment theprotection in the carrier network and deploy dual node interconnections between

carrier network segments As an example, between access/metro and metro/core domains two nodes are used to

interconnect (see slide 20)

Protected EC is not loop free and it is required to block forwarding ofVLAN/BSI frames on the alternative paths

This is normal behavior within protected P2P connections

MEF12.1: Ethernet Connection (EC) supports an EVC, EC Segment supports an OVC


3/20

3

DRNI within the MEF Ethernet ServicesArchitecture

DataPlane

ControlPlane

ManagementP

lane

Transport Services Layer

Ethernet Services Layer

Application Services Layer

Ordering , Provisioning, Billing,Management and SupportDRNI is performed in this

layer, which is an ETH(S-VLAN) or ETH(BSI) layer

EC signals are transported over p2p VLAN, ESP, PW, transport-LSP, VC-

n, ODUk, mp2mp B-VLAN, mp2p LSP connections and 802.3 links

This layer supportsEthernet Connections (EC)

EC protection switching:G.8031 ETH SNCP

G.8032 ERPp802.1AXbq DRNI


4/204

AccessAccess

Metro(partial mesh of

virtual links)

Core

(full mesh of

virtual links)Metro(EC ring)

3

4 6

5

B

7

8 10

9

A

2

1

Carrier X Network

UNI UNI

i EC Terminating or Bridging Node Physical link Ethernet virtual link supported by Transport Services layer connection

Multi-Domain Carrier Network Architecture

Aggregation & Encapsulation

Aggregation

Aggregation

EVC

EC

S-VLAN MAC Relay (in S-Comp orI-Comp) or BSI Relay (inside c6.11)

VLAN, ESP, LSP,PW, VC-n or ODUkconnection

A

2 4 6 8 10

B


5/205

3

4 6

5

B

7

8 10

9

A

2

1

UNI UNI

SNC Protected P2P EC in Carrier X network (


6/206

6.186..18

19.3

19.3

19.2

19.5

8.5

6.18

19.2

802.n

19.3

19.3

19.2

6.18

19.2

19.3

19.3

19.2

6..18

19.2

8.6.3 SVLAN MAC Relay

G.8031 ETH SNCP functionality insideS/I-Components and CBP

c6.11 CBP function is extended withG.8031 ETH SNCP functionality

CBP is extended with BSI SNCPMEP/MIP functionality to determineSF/SD status of W-BSI and P-BSI

c8.6.3 S-VLAN MAC Relay function isextended with G.8031 ETH SNCPfunctionality

19.3

8.6.1/2/4

19.3

19.2

19.5

8.6.6/7/8

8.5

6.9

19.3

8.6.1/2/4

19.3

19.2

19.5

8.6.6/7/8

8.5

6.9

19.3

8.6.1/2/4

19.3

19.2

19.5

8.6.6/7/8

8.5

6.9

6.14

G.8031 ETH SNCPW P N

SF/SD

SF/SD

W/P-SVLANSNCP MEP

SVLAN

SP MEP

19.2

802.n

6.7

APS

S/I-Component with S-VLAN SNCP

6.1519.2

802.n

6.7

6.10

19.2

802.n

6.7

6.1519.2

802.n

6.7

6.10

19.2

802.n

6.7

ONP PIP PNP ONP PIP PNP

CNP

6.11

G.8031 ETH SNCPW P N

SF/SD

SF/SD

W/P-BSI

SNCP MEP

BSISP MEP

6.7

APS

CBP with BSI SNCP

BVLANSNCP MEP

8.6.3BVLAN MAC Relay

6.186..17

6..17

adminPointToPointMAC parameter set to

ForceTrue; no C-MAC/B-MAClearning and flushing


7/207

Core

(full mesh)

Access

Core

(full mesh)

Metro(EC ring)

3

4 6

5

A

2

1

Access

Metro

(partial mesh)

B

10

9

13 14

11 12

7

8

Carrier X Network

Carrier Y Network

E-NNI

UNI

UNI

DRNI

i EC Terminating or Bridging Node Physical link Ethernet virtual link supported by Transport Services layer connection

Multi-Carrier Network Architecture

Node types:PB, IB-BEB, IB-BEB-TE,

TB, S-PE, B-BEB

Network types:

PBN, PBBN, PBB-TEN,SDH, OTN, MPLS(-TP)


8/208

3

4 6

5

A

2

1

B

10

9

13 14

11 12

7

8

Carrier X Network

Carrier Y Network

E-NNI

UNI

UNI

DNI protected P2P EC in Carrier X and Y networks

blockforwardingof frames in

EC

DNI ProtectedP2P EC

VLAN/BSI

frame in EC

E-Line EVC

SNC Protected P2P EC Segment in

Carrier X network (


9/209

Distributed ETH SNCP architecture

ETH SNCP has got distributedcontrol in E-NNI nodes (DSNCP)

Carrier X ETH APS may terminate inDSNCP process in nodes 11 or 12

Carrier Y ETH APS may terminate inDSNCP process in nodes 13 or 14

Either W_MEP/P_MEP* pair, orW_MEP*/P_MEP pair is active

The DRNI status controls if

carrier X APS terminates in 11 or 12 carrier Y APS terminates in 13 or 14

carrier X active DSNCP MEP pair

carrier Y active DSNCP MEP pair

11 12

13 14

DSNCP DSNCP

DSNCPDSNCP

P_MEP W_MEP

P_MEP W_MEP

Carrier XETH SNCP

Carrier YETH SNCP

DRNIDRNI

DRNIDRNI

W_MEP* P_MEP*

W_MEP* P_MEP*

S-VLAN EC

or BSI EC

E-NNI

APS

APS

NOTE MEPs for DRNI part are outside scope of this contribution


10/2010

Distributed ETH SNCP architectureconfiguration examples

11 12

13 14

DSNCP DSNCP

DSNCPDSNCP

P_MEP W_MEP

P_MEP W_MEP

Carrier XETH SNCP

Carrier YETH SNCP

DRNIDRNI

DRNIDRNI

W_MEP* P_MEP*

W_MEP* P_MEP*

E-NNI

APS

APS

11 12

13 14

DSNCP DSNCP

DSNCPDSNCP

P_MEP W_MEP

P_MEP W_MEP

Carrier XETH SNCP

Carrier YETH SNCP

DRNIDRNI

DRNIDRNI

W_MEP* P_MEP*

W_MEP* P_MEP*

E-NNI

APS

APS

X


11/2011

Distributed ETH SNCP architectureconfiguration examples

11 12

13 14

DSNCP DSNCP

DSNCPDSNCP

P_MEP W_MEP

P_MEP W_MEP

Carrier XETH SNCP

Carrier YETH SNCP

DRNIDRNI

DRNIDRNI

W_MEP* P_MEP*

W_MEP* P_MEP*

E-NNI

APS

APS

11 12

13 14

DSNCP DSNCP

DSNCPDSNCP

P_MEP W_MEP

P_MEP W_MEP

Carrier XETH SNCP

Carrier YETH SNCP

DRNIDRNI

DRNIDRNI

W_MEP* P_MEP*

W_MEP* P_MEP*

E-NNI

APS

APS

X

X

X


12/20

12

Network Operator MEP functions

NO_MEP functions are located on theE-NNI ports

The DRNI status controls which E-NNI port is the active port for an EC

The NO_MEP on the active E-NNI portis used to monitor the EC Segment inthe carrier network

11 12

13 14

DSNCP DSNCP

DSNCPDSNCP

NO_MEP

DRNIDRNI

DRNIDRNI

S-VLAN ECor BSI EC

E-NNINO_MEP*

NO_MEP***NO_MEP**

NO_MEPNO_MEP***NO_MEP*NO_MEP**

EC Segment

Far end NO_MEP

SP_MEP


13/20

13

DSNCP, DRNI, SNCP MEP and NO MEPfunctionality inside S/I-Components

DSNCP and DRNI both controlthe EC(SVLAN) connectivity

DSNCP process interacts withSNCP process at far end of SNCprotected EC Segment

DSNCP process requirementsand behaviour is TBD

DRNI process has to beperformed prior to the NO_MEPand SP_MIP functions

DRNI differs from common LAGin that LAG distributes MACframes independent of the ECthey belong to, while DRNIcontrols EC connectivity

19.3

8.6.1/2/4

19.3

19.2

19.5

8.6.6/7/8

8.5

6.9

8.6.3 SVLAN MAC Relay

19.3

8.6.1/2/4

19.3

19.2

19.5

8.6.6/7/8

8.5

6.9

19.3

8.6.1/2/4

19.3

19.2

19.5

8.6.6/7/8

8.5

6.9

19.3

8.6.1/2/4

19.3

19.2

19.5

8.6.6/7/8

8.5

6.9

DSNCPW P* N

SF/SD

SF/SD

W/P_S-VLANSNCP MEP

S-VLAN

NO_MEP

APS

S/I-Component with S-VLAN DSNCP and DRNI

ONP, PNP,PIP spec.

ONP, PNP,PIP spec.

19.3

8.6.1/2/4

19.3

19.5

8.6.6/7/8

8.5

6.9

ONP, PNP,PIP spec.

CNP spec.

DRNI

CNP spec.E-NNI

to/from DRNI peer node

S-VLANSP_MIP


14/20

14

6.186..18

19.3

19.3

19.2

19.5

8.5

6.18

19.2

802.n

19.3

19.3

19.2

6.18

19.2

19.3

19.3

19.2

6..18

19.2

DSNCP, DRNI, SNCP MEP and NO MEPfunctionality inside CBP

DSNCP and DRNI bothcontrol the EC(BSI)connectivity

c6.11 CBP function supportsDSNCP and DRNI within aBSI Relay type of process

with SID based forwardingand protection (but no MACbased forwarding)

Default Backbone Destinationparameter has to be switchedtogether with ;i.e. WP

6.11

DSNCPW P* N

SF/SD

SF/SD

W/P-BSISNCP MEP

BSI

NO_MEP

6.7

APS

CBP with BSI DSNCP & DRNI

B-VLAN

MEP

8.6.3B-VLAN MAC Relay

6.186..17

6..17

6.18

19.3

19.3

6.18

19.2

DRNI

19.3

19.3

19.2

19.5

8.5

6.18

19.2

802.n

6.7

6.18

to/from DRNI peer node

E-NNI

BSISP_MIP


15/20

15

Some considerations on items in slides 7-10 of http://www.ieee802.org/1/files/public/docs2010/new-

haddock-resilient-network-interconnect-addressing-1110-v1.pdf
http://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdf


16/20

16

Working & protection paths in area network

S

S S

SS

S

C

DSNCP

DRNI

S

DSNCP

DRNI

B

B B

BB

CBP

DSNCP

DRNI

CBP

DSNCP

DRNI

BB

SNCP

CBP

SNCP

S

B B

BB

S

DSNCP

DRNI

S

DSNCP

DRNI

SNCP

BB

CBPCBPPIPPIP

B

CBP

PIP

CBP

PIP

CBPCBPPIPPIP

Protection

SVLAN

Working

SVLAN

Protection

SVLAN

Working

SVLAN

Protection

BSI

Working

BSI

http://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdf slide 7

B-BEB

B-B

EB B

-BEB

IB-BEB

or

IB-BEB

-TE

IB-BEBorIB-BEB-TE

IB-B

EBorIB-BEB-TE

PEB

PB PB

PBB: each PIP and CBP have different addressPBB-TE: each PIP/CBP pair has different address
http://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdfhttp://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-interconnect-addressing-1110-v1.pdf


17/20

17

Backbone Edge Bridge at an S-tagged RNNIPoint-to-Point Backbone Service Instances

Four disjoint BVLANs or TESIs ZA

ZB

AB(DSNCP)

AB(DNRI)

PBB: Four disjoint BSIs, one per

BVLAN Fixed Default Backbone Destination

values

PBB: Each PIP and CBP havedifferent address

PBB-TE: Each PIP/CBP pair hasdifferent address

p2p SNC protected EC does notrequire MAC learning

adminPointToPointMAC parameterset to ForceTrue in PIPshttp://www.ieee802.org/1/files/public/do

cs2010/new-haddock-resilient-network-

interconnect-addressing-1110-v1.pdf slides 8, 9

S

B B

BB

S

DSNCP

DRNI

S

DSNCP

DRNI

SNCP

BB

CBPCBPPIPPIP

B

CBP

PIP

CBP

PIP

CBPCBPPIPPIP

Protection

SVLAN

Working

SVLAN

IB-BEB

or

IB-BEB-TE

IB-BEBorIB-BEB-TE

IB-B

EBorIB-BEB-TE


18/20

18

E-Line Services and Point-to-Point OVCs

Six BVLANs or TESIs

Six BSIs, one per BVLAN

Working SVLAN EC Segmentcan have 4 variations

DB

DBA

CDB

CDBA

Protection SVLAN EC Segmentcan have 4 variations

DCAB

DCA CAB

CA

W/P EC Segment can beextended; this is a newcapability. Requires further

study.

http://www.ieee802.org/1/files/public/docs2010/new-haddock-resilient-network-

interconnect-addressing-1110-v1.pdf slide 10

B B

BB

S

DSNCP

DRNI

S

DSNCP

DRNI

BB

CBPCBP

PIPPIP

CBPCBP

PIPPIP

IB-BEBorIB-BEB-TE

IB-BEBorIB-BEB-TE

S

DSNCP

DRNI

S

DSNCP

DRNI

B B

CBP CBP

PIP PIP

CBP CBP

PIP PIP

IB-B

EBorIB-BEB-TEI

B-BEBorIB-BEB-TE

Protection

SVLAN

Working

SVLAN


19/20

19

Long EC Segments, >1200 km

Compact DRNI

ETH SNCP & DRNI P t t d EC


20/20

20

3

4 6

5

A

2

1

B

10

9

13 14

11 12

7

8

Carrier X Network

Carrier Y Network

E-NNI

UNI

UNI

DNI protected P2P EC in Carrier X and Y networks

blockforwardingof frames in

EC

DNI ProtectedP2P EC

VLAN/BSI

frame in EC

E-Line EVC

OVC OVC

ETH SNCP & DRNI Protected EC (S-VLAN, BSI)EC-Segments >1200 km

Is it possible to usea special versionof DRNI here?

Documents

Axbq Vissers Drni and Sncp Inter Working 0511 v00