1 802.1Q description of G.8031 Ethernet Connection (EC) SubNetworkConnection (SNC) Protection “VLAN Segment Protection” Maarten Vissers 2012-01-17 v2.

Slides:



Advertisements
Similar presentations
Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality.
Advertisements

Satoshi NARIKAWA NTT (G.8032 Acting Co-editor)
Slide 111 May 2008 Point-to-Multipoint in 802.1Qay Nurit Sprecher, Nokia Siemens Networks Hayim Porat, Ethos Networks.
1 Transport Services Layer Protection Switching Types Interacting with DRNI Maarten Vissers
1 DRNI Examples and DAS position Maarten Vissers
1 DRNI Examples and DAS position Maarten Vissers Version 01.
1 Alternative solution for EC Type II support Maarten Vissers
1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers v01.
M Vinod Kumar Dr. Abhay Karandikar. Multiplex Entity CBP PIP Towards Core Towards Core All fault indications are available on one port All fault indications.
1 Distributed Network Protection (DNP) architecture study Maarten Vissers v4 v2: includes a few slides at the end illustrating segment protection.
802.1Qay PBB-TE Protection Switching Overview
1 DRNI and Distributed Protection Examples Maarten Vissers v01 Based on slides presented in IW meeting in Nanjing on Thursday Sept 22.
Packet Switching COM1337/3501 Textbook: Computer Networks: A Systems Approach, L. Peterson, B. Davie, Morgan Kaufmann Chapter 3.
1 Distributed Network Protection (DNP) architecture study Maarten Vissers v3 v2: includes a few slides at the end illustrating segment protection.
DRNI Examples, DAS position, MEP/MIP position
Oct 12, 2004CS573: Network Protocols and Standards1 Virtual LANs Network Protocols and Standards Autumn
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 10: DHCP Routing & Switching.
© 2009 Cisco Systems, Inc. All rights reserved. SWITCH v1.0—6-1 Implementing Layer 3 High Availability Configuring Layer 3 Redundancy with HSRP.
1 DRNI  Network Protection Interaction Some examples in which one or more faults in DRNI require a change in Network Protection Some examples in which.
1 Common network architectures for PBB, PBB-TE and EOTN networks version 01 Maarten Vissers v01 includes new slides 10 and 12: Slide 10 presents.
1 DRNI and G.8031 ETH SNCP interworking Maarten Vissers
Jan 10, 2008CS573: Network Protocols and Standards1 Virtual LANs Network Protocols and Standards Winter
TCP/IP Protocol Suite 1 Chapter 3 Objectives Upon completion you will be able to: Underlying Technology Understand the different versions of wired Ethernet.
Orion Telecom Networks Inc E1 Automatic Protection Switching Solution (1+1 E1 Redundancy Switch) Updated : November, 2005 Slide , Avenue of.
1 25\10\2010 Unit-V Connecting LANs Unit – 5 Connecting DevicesConnecting Devices Backbone NetworksBackbone Networks Virtual LANsVirtual LANs.
1 Multipoint Ethernet Connection Protection
CECS 474 Computer Network Interoperability Tracy Bradley Maples, Ph.D. Computer Engineering & Computer Science Cal ifornia State University, Long Beach.
1 DRNI Data Plane Model I/II Comparison & MAC Address Values in DRNI Maarten Vissers v00.
1 Data Plane Summary Maarten Vissers v1.
1 Supporting VUNI in DRNI Maarten Vissers v01 v01: added multiple virtual UNI with hairpin.
Basic Networking Components
CECS 5460 – Assignment 3 Stacey VanderHeiden Güney.
Chapter 4: Managing LAN Traffic
1 Common network architectures for PBB, PBB-TE and EOTN networks Maarten Vissers
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 10: DHCP Routing & Switching.
LAN Switching and Wireless – Chapter 2
Slide title In CAPITALS 50 pt Slide subtitle 32 pt PBB-TE Status Report Panagiotis Saltsidis.
Access Protocols PPP vs. DHCP Chapter 5. Overview PPP DHCP User identities Assignment of IP addresses Assignment of other parameters.
Repeaters and Hubs Repeaters: simplest type of connectivity devices that regenerate a digital signal Operate in Physical layer Cannot improve or correct.
1 Portal Models Maarten Vissers v1. 2 DRNI Applicability DRNI model is applicable to many different portal types 1.PB Portal (S-DRNI) 2.BCB.
Hub  A hub is a piece of hardware that connects multiple wired devices together on a single network. Hubs work at the physical layer (layer 1) of the.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Configure a Switch LAN Switching and Wireless – Chapter 2.
N ETWORKING C OMPONENTS A-3 LTEC 4550 by Joe Garcia.
Communication Networks Fourth Meeting. Types of Networks  What is a circuit network?  Two people are connected and allocated them their own physical.
1 Kyung Hee University Chapter 15 Connecting LANs, Backbone Networks, and Virtual LANs.
Computer Networks 15-1 Chapter 15. Connecting LANs, Backbone Networks, and Virtual LANs 15.1 Connecting devices 15.2 Backbone networks 15.3 Virtual LANs.
Cisco 3 - Switching Perrine. J Page 16/4/2016 Chapter 4 Switches The performance of shared-medium Ethernet is affected by several factors: data frame broadcast.
Slide 1 MPLS-TP Linear Protection / Author / RTP IE Fixed CET I insert classification level © Nokia Siemens Networks MPLS-TP Linear Protection.
15.1 Chapter 15 Connecting LANs, Backbone Networks, and Virtual LANs Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or.
McGraw-Hill©The McGraw-Hill Companies, Inc., 2004 Chapter 16 Connecting LANs, Backbone Networks, and Virtual LANs.
Network Components Kortney Horton LTEC October 20, 2013 Assignment 3.
1 Introduction filtering-0710-v04.pdfhttp://
Chapter 16 Connecting LANs, Backbone Networks, and Virtual LANs
Ch. 15 Connecting LANs.
1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers
Portal Models Maarten Vissers v2
Kevin Harrison LTEC 4550 Assignment 3.  Ethernet Hub  An unsophisticated device that is used for connecting multiple Ethernet devices together.  Typically.
Doc.: IEEE 11-14/0562r0 May 2014 SubmissionSlide 1Norman Finn, Cisco Systems, Mark Hamilton, Spectralink ak and 802.1AC Convergence Function Date:
1 Distributed Network Protection (DNP) architecture study Maarten Vissers v1.
LAN Switching and Wireless – Chapter 2
Supporting VUNI in DRNI Maarten Vissers v00
VLANs: Virtual Local Area Networks
Alternative solution for EC Type II support
© 2002, Cisco Systems, Inc. All rights reserved.
Network Virtualization
LAN Switching and Wireless – Chapter 2
E-OTN status update and service interface question [associated with ITU-T liaison statement liaison-itut-sg15-ols ] version 01 New slides:
Chapter 16 Connecting LANs, Backbone Networks, and Virtual LANs
DRNI and Distributed Network Protection Model Evolution: Maarten  Norm  Steve Maarten Vissers v1  
LAN Switching and Wireless – Chapter 2
Presentation transcript:

Q description of G.8031 Ethernet Connection (EC) SubNetworkConnection (SNC) Protection “VLAN Segment Protection” Maarten Vissers v2

2 SNCP CTRL Ext.CMD W SF/SD P SF/SD G.8031 P2P EC SNCP Architecture Normal (N) CTRL: Control, SF: Signal Fail, SD: Signal Degrade Bridge Working (W) Protection (P) SNCP CTRL Automatic Protection Switching (APS) Ext.CMD SF/SD W SF/SD P Two end points Each end point includes Protection Bridge, Selector and SNCP Control processes SNCP Control process controls status of Bridge and Selector processes SNCP Control processes at both end points are synchronized via APS channel SNCP Control process acts on SF, SD, APS and External Command (Ext.CMD) input signals Selector Normal (N) Bridge Working (W) Protection (P) Selector MEP

3 Protection Switching SF, SD, APS access G.8021 MEP  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) APSSF SD G.8021 MEP ISS

4 G.8031 P2P EC SNCP Architectures “Protection Bridge” & “Protection Selector” Types Two “Protection Selector” types  Two implementations, same behaviour Three “Protection Bridge” types  All have different behaviour 1:1 selective bridge W P N WP N WP N 1+1 permanent bridge1:1 broadcast bridge W P N W P N Selective selectorMerging selector W: Working, P: Protection, N: Normal

5 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 selective bridge architecture W P N W P N WP N WP N W P N W P N SNCP CTRL APS Ext.CMD 1+1 architecture1:1 broadcast bridge architecture SF/SD W SF/SD P SNCP CTRL APSSF/SD W SF/SD P SNCP CTRL APSSF/SD W SF/SD P W: Working, P: Protection, N: Normal

Q 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

Q model 1+1 permanent bridge P2P EC SNCP configuration c8.6.3 MAC Relay c19.3 c19.2 c19.3 c19.2 c19.3 c19.2 c6.9 P2P SNCP FID RVID(N)RVID(W)RVID(P) aaabb c6.9 cc c8.5 SNCP CTRL WP N W P N Ext.CMD SNCP CTRL APSSF/SD W SF/SD P c8.6.3 MAC Relay c19.3 c19.2 c19.3 c19.2 c19.3 c19.2 c6.9 P2P SNCP FID RVID(N)RVID(W)RVID(P) aaabb c6.9 cc c8.5 SNCP CTRL WP N W P N Ext.CMD SNCP CTRL APSSF/SD W SF/SD P SNCP CTRL process controls RVID(W) and RVID(P) registration on Port P10 MAC learning should be disabled for this SNCP FID P10P11P12P10P11P12 VID values W MEP P MEP P10 P11P12 P10 P11P12 P10 P11P12 P10 P11P12

Q model 1:1 selective bridge P2P EC SNCP configuration c8.6.3 MAC Relay c19.3 c19.2 c19.3 c19.2 c19.3 c19.2 c6.9 P2P SNCP FID RVID(N)RVID(W)RVID(P) aaabb c6.9 cc c8.5 SNCP CTRL c8.6.3 MAC Relay c19.3 c19.2 c19.3 c19.2 c19.3 c19.2 c6.9 P2P SNCP FID RVID(N)RVID(W)RVID(P) aaabb c6.9 cc c8.5 SNCP CTRL W P N Ext.CMD SNCP CTRL APSSF/SD W SF/SD P W P N Ext.CMD SNCP CTRL APSSF/SD W SF/SD P W P N W P N 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 P10P11P12P10P11P12 W MEP P MEP P10 P11P12 P10 P11P12 P10 P11P12 P10 P11P12 VID values

Q model 1:1 broadcast bridge P2P EC SNCP configuration c8.6.3 MAC Relay c19.3 c19.2 c19.3 c19.2 c19.3 c19.2 c6.9 P2P SNCP FID RVID(N)RVID(W)RVID(P) aaabb c6.9 cc c8.5 SNCP CTRL c8.6.3 MAC Relay c19.3 c19.2 c19.3 c19.2 c19.3 c19.2 c6.9 P2P SNCP FID RVID(N)RVID(W)RVID(P) aaabb c6.9 cc c8.5 SNCP CTRL W P N Ext.CMD SNCP CTRL APSSF/SD W SF/SD P W P N Ext.CMD SNCP CTRL APSSF/SD W SF/SD P W P N W P N P10P11P12P10P11P12 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 W MEP P MEP P10 P11P12 P10 P11P12 P10 P11P12 P10 P11P12 VID values

10 Distributed SNCP Architecture Refer to slides 24 and 25 in xbq-vissers-dnp-architectures-0112-v5.pptx xbq-vissers-dnp-architectures-0112-v5.pptx

11 c19.3 c19.2 c19.3 c Q model Distributed SNCP Configurations (1:1 selective bridge example) c8.6.3 MAC Relay c19.3 c19.2 c19.3 c19.2 c19.3 c19.2 c6.9 P2P SNCP FID RVID(N)RVID(W)RVID(P) aaabb c6.9 cc c8.5 Dist, SNCP CTRL c8.6.3 MAC Relay c19.3 c19.2 c19.3 c19.2 c19.3 c19.2 c6.9 P2P SNCP FID RVID(N)RVID(W)RVID(P) aaabb c6.9 cc c8.5 Dist. SNCP CTRL P10P11P12P10P11P12 W MEP P MEP VID values c8.6.3 MAC Relay P2P SNCP FID RVID(N)RVID(W)RVID(P) Dist. SNCP CTRL c19.3 c19.2 c6.9 aaabb cc c8.5 W MEPP MEP 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; MAC learning disabled for this SNCP FID P10P11P12

12 VLAN based P2P EC SNCP configuration in S- & I-Components

SVLAN MAC Relay P2P EC SNCP functionality inside S- & I-Component One or more EC SNCP FID processes may be active per MAC Relay (one illustrated) W and P SVLAN MEPs determine SF and SD conditions P SVLAN MEP provides access to APS messages /2/ /7/ /2/ /7/ /2/ /7/ P2P EC SNCP FID & SNCP CTRL W P N SF/SD W/P-SVLAN SNCP MEP n 6.7 APS S/I-Component with S-VLAN SNCP n n n n 6.7 ONP PIP PNP CNP 6.17

14 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

BVLAN A and B MEPs BVLAN MAC Relay P2P EC SNCP functionality inside CBP 19.2 BVLAN A and B MEPs BVLAN MAC Relay 6.17 c6.11 CBP function control is extended with G.8031 P2P EC SNCP functionality  1:1 selective bridge is supported (via per ISID BVID value control)  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) P BSI SNCP MEP provides access to APS messages n BSI SP MEP BSI UNI/ENNI MEP 6.17 N W/P-BSI SNCP MEP P2P EC SNCP W P SF/SD APS CBP with BSI SNCP Additional BSI MUX and BSI MEP/MIP functions