802.1Q description of G.8031 Ethernet
Connection (EC) SubNetworkConnection
(SNC) Protection
“VLAN Segment Protection”
Maarten Vissers
2012-01-17
v2
1
G.8031 P2P EC SNCP Architecture
Two end points
Normal (N)
Each end point includes Protection
Bridge, Selector and SNCP Control
processes
SNCP Control process acts on SF,
SD, APS and External Command
(Ext.CMD) input signals
CTRL: Control, SF: Signal Fail, SD: Signal Degrade
Protection (P)
Working (W)
MEP
MEP
Selector
Bridge
SNCP CTRL
Automatic Protection Switching (APS)
Selector
Protection (P)
SNCP Control processes at both end
points are synchronized via APS
channel
Bridge
Working (W)
SNCP Control process controls
status of Bridge and Selector
processes
Ext.CMD
SF/SD SF/SD
W
P
W
P
SF/SD SF/SD
SNCP CTRL
Ext.CMD
Normal (N)
2
Protection Switching SF, SD, APS access
G.8021 MEP
SF SD APS
ISS
G.8021
MEP
ISS
 Generates Signal Fail (SF)
and Signal Degrade (SD)
parameters
 Extracts the Automatic
Protection Switching (APS)
messages from the VLAN
 Inserts APS messages into
the VLAN
 Linear APS messages are
specified in ITU-T Y.1731
(OpCode=39) and G.8031
(PDU format)
3
G.8031 P2P EC SNCP Architectures
“Protection Bridge” & “Protection Selector” Types
Two “Protection
Selector” types
Selective selector
 Two implementations,
same behaviour
Merging selector
N
N
Three “Protection
Bridge” types
 All have different
behaviour
1+1 permanent bridge
W
1:1 selective bridge
W
P
W: Working, P: Protection, N: Normal
W
P
1:1 broadcast bridge
N
N
W
P
N
P
W
P
4
G.8031 P2P EC SNCP Architectures
Protection architecture types
Three point-to-point EC SNCP
architectures
SNCP CTRL process can be
considered as an 802.1Q “higher
layer” process, which controls the
state of the protection “bridge” and
“selector” processes
1+1 architecture
1:1 selective bridge architecture
Ext.CMD
N
N
SNCP CTRL
W
P
W
P
1:1 broadcast bridge architecture
Ext.CMD
N
Ext.CMD
N
N
N
SNCP CTRL
W
APS SF/SD SF/SD
W
P
P W
W: Working, P: Protection, N: Normal
P
APS SF/SD SF/SD
W
P
SNCP CTRL
W
P W
P
APS SF/SD SF/SD
W
P
5
802.1Q model of P2P EC SNCP
P2P EC SNCP based forwarding may be described by means
of




Asymmetric VLANs with three RVID values N,W,P
VID Translation and Egress VID Translation
RVID registration under control of SNCP Control process
Disabled MAC learning for SNCP FID (to support permanent bridge and
broadcast bridge options)
The following three slides present the 802.1Q based models
along the above lines
6
802.1Q model
1+1 permanent bridge P2P EC SNCP configuration
P10
P10
P10
P10
Ext.CMD
N
Ext.CMD
N
N
N
SNCP CTRL
W
P W
SNCP CTRL
W
APS SF/SD SF/SD
W
P
P
P11 P12 P11 P12
P W
APS SF/SD SF/SD
W
P
P
P11 P12 P11 P12
RVID(N)
RVID(W)
RVID(P)
c19.3
c19.2
c19.3
c19.2
c6.9
bb
P10
VID values
c c
RVID(W)
c19.3
c19.2
aaa
c6.9
c8.5
P12
RVID(P)
c19.3
c19.2
c19.3
c19.2
W MEP
c6.9
c8.5
P11
RVID(N)
P MEP
c6.9
c8.5
P2P SNCP FID
c19.3
c19.2
W MEP
aaa
c8.6.3 MAC Relay
SNCP
CTRL
SNCP
CTRL
c8.6.3 MAC Relay
P2P SNCP FID
bb
c6.9
c8.5
P10
P MEP
c c
c6.9
c8.5
P11
SNCP CTRL process controls RVID(W) and RVID(P) registration on Port P10
MAC learning should be disabled for this SNCP FID
c8.5
P12
7
802.1Q model
1:1 selective bridge P2P EC SNCP configuration
P10
P10
P10
P10
Ext.CMD
N
Ext.CMD
N
N
N
SNCP CTRL
W
P
W
P
SNCP CTRL
W
APS SF/SD SF/SD
W
P
P11 P12 P11 P12
P W
P
APS SF/SD SF/SD
W
P
P11 P12 P11 P12
RVID(N)
RVID(W)
RVID(P)
c19.3
c19.2
c19.3
c19.2
c6.9
bb
VID values
P10
c c
RVID(W)
c19.3
c19.2
aaa
c6.9
c8.5
P12
RVID(P)
c19.3
c19.2
c19.3
c19.2
W MEP
c6.9
c8.5
P11
RVID(N)
P MEP
c6.9
c8.5
P2P SNCP FID
c19.3
c19.2
W MEP
aaa
c8.6.3 MAC Relay
SNCP
CTRL
SNCP
CTRL
c8.6.3 MAC Relay
P2P SNCP FID
bb
c6.9
c8.5
P10
P MEP
c c
c6.9
c8.5
P11
c8.5
P12
SNCP CTRL process controls RVID(W) and RVID(P) registration on Port P10 and RVID(N) registration on P11 and P12
MAC learning should be disabled for this SNCP FID
8
802.1Q model
1:1 broadcast bridge P2P EC SNCP configuration
P10
P10
P10
P10
Ext.CMD
N
Ext.CMD
N
N
N
SNCP CTRL
W
P
W
P
SNCP CTRL
W
APS SF/SD SF/SD
W
P
P11 P12 P11 P12
P W
P
APS SF/SD SF/SD
W
P
P11 P12 P11 P12
RVID(N)
RVID(W)
RVID(P)
c19.3
c19.2
c19.3
c19.2
c6.9
bb
VID values
P10
c c
RVID(W)
c19.3
c19.2
aaa
c6.9
c8.5
P12
RVID(P)
c19.3
c19.2
c19.3
c19.2
W MEP
c6.9
c8.5
P11
RVID(N)
P MEP
c6.9
c8.5
P2P SNCP FID
c19.3
c19.2
W MEP
aaa
c8.6.3 MAC Relay
SNCP
CTRL
SNCP
CTRL
c8.6.3 MAC Relay
P2P SNCP FID
bb
c6.9
c8.5
P10
P MEP
c c
c6.9
c8.5
P11
c8.5
P12
SNCP CTRL process controls RVID(W) and RVID(P) registration on Port P10 and RVID(N) registration on P12
MAC learning should be disabled for this SNCP FID
9
Distributed SNCP Architecture
Refer to slides 24 and 25 in
http://www.ieee802.org/1/files/public/docs2012/a
xbq-vissers-dnp-architectures-0112-v5.pptx
10
802.1Q model
Distributed SNCP Configurations (1:1 selective bridge example)
c8.6.3 MAC Relay
Dist.
SNCP
CTRL
Distributed SNCP CTRL process controls
- [top] RVID(W) registration on Port P12 and
RVID(P) registration on P11 to establish
“relay” configuration in Standby Gateway
portal node; W&P MEPs disabled
- [bottom] RVID(W) and RVID(P) registration
on Port P10 and RVID(N) registration on
P11 and P12 to establish “drop”
configuration in Active Gateway portal
node;
P2P SNCP FID
RVID(N)
RVID(W)
RVID(P)
c19.3
c19.2
c19.3
c19.2
c19.3
c19.2
W MEP
aaa
c6.9
P MEP
bb
c6.9
c8.5
MAC learning disabled for this SNCP FID
c c
c6.9
c8.5
P10
c8.5
P11
P12
RVID(N)
RVID(W)
RVID(P)
c19.3
c19.2
c19.3
c19.2
c6.9
bb
VID values
P10
c c
RVID(W)
c19.3
c19.2
aaa
c6.9
c8.5
P12
RVID(P)
c19.3
c19.2
c19.3
c19.2
W MEP
c6.9
c8.5
P11
RVID(N)
P MEP
c6.9
c8.5
P2P SNCP FID
c19.3
c19.2
W MEP
aaa
c8.6.3 MAC Relay
Dist.
SNCP
CTRL
Dist,
SNCP
CTRL
c8.6.3 MAC Relay
P2P SNCP FID
bb
c6.9
c8.5
P10
P MEP
c c
c6.9
c8.5
P11
c8.5
P12
11
VLAN based P2P EC SNCP configuration
in S- & I-Components
12
P2P EC SNCP functionality inside
S- & I-Component
S/I-Component with S-VLAN SNCP
8.6.3 SVLAN MAC Relay
P2P EC SNCP FID & SNCP CTRL
P
W
6.17
6.17
19.2
19.3
19.3
19.3
6.17
6.17
6.17
SF/SD
APS
6.17
SF/SD
N
8.6.1/2/4
6.17
6.17
6.17
19.3
19.3
19.3
19.2
19.2
6.17
6.17
6.17
19.5
19.5
19.5
8.6.6/7/8
8.6.6/7/8
8.6.6/7/8
6.9
6.9
6.9
8.5
8.5
8.5
19.2
6.14
6.7
802.n
CNP
6.15
6.10
19.2
6.7
19.2
6.7
802.n 802.n
ONP PIP PNP
6.15
W and P SVLAN MEPs determine SF
and SD conditions
8.6.1/2/4
8.6.1/2/4
One or more EC SNCP FID processes
may be active per MAC Relay (one
illustrated)
P SVLAN MEP provides access to
APS messages
W/P-SVLAN
SNCP MEP
6.10
19.2
6.7
19.2
6.7
802.n 802.n
ONP PIP PNP
13
BSI based P2P EC SNCP configuration in
CBP
SNCP for BSI ECs is also possible
It requires some extension of the CBP port as
illustrated in the next slide
14
P2P EC SNCP functionality inside CBP
c6.11 CBP function control is extended
with G.8031 P2P EC SNCP functionality
802.n

6.7
19.5

19.2
8.5

6.18
19.2
BSI UNI/ENNI MEP

19.3
CBP with BSI SNCP
19.3
BSI SP MEP
19.2
6.18
N
W
6.11
P2P EC SNCP
P
6.17
W/P-BSI SNCP MEP
19.3
6.18
19.2
SF/SD
APS
6.18
SF/SD
BVLAN A and B MEPs
19.3
6.17
19.3
8.6.3
BVLAN MAC Relay
19.2
19.3
6.18
6.18
19.2
1:1 selective bridge is supported (via per
ISID BVID value control)
Additional
BSI MUX
and BSI
MEP/MIP
functions
1+1 permanent and 1:1 broadcast bridge is
not supported
Merging selector is supported (same as in
TESI protection)
NOTE: TESI protection protects group of EC
signals (group of ISIDs). G.8031 SNCP
protects individual EC signals (individual
ISID).
CBP is extended with BSI SNCP MEP/MIP
functionality to determine SF/SD status
of W-BSI and P-BSI
W-BSI via BVLAN A and P-BSI via BVLAN
B; BVLAN A and B must have route
diversity
One or more BSI EC SNCP processes
may be active on CBP (one is illustrated)
19.2
BVLAN A and B MEPs
6.17
8.6.3
BVLAN MAC Relay
P BSI SNCP MEP provides access to APS
messages
15