Stephen Haddock September 13, 2012

Slides:



Advertisements
Similar presentations
Experiences with IEEE 802.1ah (Provider Backbone Bridges) Ronald van der Pol SARA Sep 2009NORDUnet meeting, Copenhagen.
Advertisements

Split Brain Detection Version 00 Nigel Bragg September 4 th,
DRNI – Intra-DAS Link Version 01 Stephen Haddock July 20,
Link Selection and OAM Version 01 Stephen Haddock July 18,
1 DRNI Examples and DAS position Maarten Vissers
1 DRNI Examples and DAS position Maarten Vissers Version 01.
1 Distributed Network Protection (DNP) architecture study Maarten Vissers v4 v2: includes a few slides at the end illustrating segment protection.
Virtual LANs.
1 DRNI and Distributed Protection Examples Maarten Vissers v01 Based on slides presented in IW meeting in Nanjing on Thursday Sept 22.
1 Distributed Network Protection (DNP) architecture study Maarten Vissers v3 v2: includes a few slides at the end illustrating segment protection.
Geneva, Switzerland, 13 July AX-REV – Link Aggregation Revision Panagiotis Saltsidis, Senior Specialist, Ericsson Joint IEEE-SA and ITU Workshop.
Compute Aggregate 1 must advertise this link. We omit the physical port on the switch to which the node is directly connected. Network Aggregate Links.
DRNI Examples, DAS position, MEP/MIP position
Ethernet and switches selected topics 1. Agenda Scaling ethernet infrastructure VLANs 2.
1 K. Salah Module 4.0: Network Components Repeater Hub NIC Bridges Switches Routers VLANs.
VLANs Semester 3, Chapter 3 Allan Johnson Website:
Institute of Technology, Sligo Dept of Computing Semester 3, version Semester 3 Chapter 3 VLANs.
1 CCNA 3 v3.1 Module 9. 2 CCNA 3 Module 9 VLAN Trunking Protocol.
1 K. Salah Module 4.3: Repeaters, Bridges, & Switches Repeater Hub NIC Bridges Switches VLANs GbE.
© Wiley Inc All Rights Reserved. CCNA: Cisco Certified Network Associate Study Guide CHAPTER 8: Virtual LANs (VLANs)
(part 3).  Switches, also known as switching hubs, have become an increasingly important part of our networking today, because when working with hubs,
1 DRNI Data Plane Model I/II Comparison & MAC Address Values in DRNI Maarten Vissers v00.
Semester 3, v Chapter 3: Virtual LANs
VLAN Trunking Protocol (VTP)
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.
Rough Outline for a Intra-Portal Protocol Version 03 Stephen Haddock September 12,
© 1999, Cisco Systems, Inc. Module 9: Understanding Virtual LANs.
Rough Outline for a Intra-Portal Protocol Version 02 Stephen Haddock August 23,
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 9 Virtual Trunking Protocol.
Cisco S3C3 Virtual LANS. Why VLANs? You can define groupings of workstations even if separated by switches and on different LAN segments –They are one.
Chapter 3 - VLANs. VLANs Logical grouping of devices or users Configuration done at switch via software Not standardized – proprietary software from vendor.
Virtual Local Area Networks (VLANs) Part II
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.0 Module 9 VLAN Trunking Protocol Cisco Networking Academy.
Configuring VLAN Chapter 14 powered by DJ 1. Chapter Objectives At the end of this Chapter you will be able to:  Understand basic concept of VLAN  Configure.
Chapter 4 Version 1 Virtual LANs. Introduction By default, switches forward broadcasts, this means that all segments connected to a switch are in one.
CCNA3 v3 Module 9 v3 CCNA 3 Module 9 JEOPARDY K. Martin.
1 Large-scale (Campus) Lan design (Part II)  VLANs  Hierarchical LAN design.
VLAN Trunking Protocol (VTP)
Discussion for Distributed Aggregation Sublayer Ting Ao, Yuehua Wei, Jinghai Yu 1IEEE Plenary San Francisco 2011.
Portal Models Maarten Vissers v2
1 Distributed Network Protection (DNP) architecture study Maarten Vissers v1.
Supporting VUNI in DRNI Maarten Vissers v00
CCNA 3 Chapter 10 Virtual Trunking Protocol
Large-scale (Campus) Lan design (Part II)
Switching and VLANs.
Instructor Materials Chapter 6: VLANs
Pertemuan 12 Virtual Trunking Protocol
SUPA/YMCA (Yang Models for Configuration and topology Abstraction)
Marc Holness Version May 2016
– Chapter 5 – Secure LAN Switching
VLANs: Virtual Local Area Networks
Chapter 5: Inter-VLAN Routing
Link Aggregation Simulator Version 1
Introduction to Networking
Virtual LANs.
Virtual Local Area Network
802.1AX-REV – Link Aggregation Revision
Routing and Switching Essentials v6.0
802-1AX-2014-Cor-1-d0-5 Sponsor Ballot Comments Version 1
Mobile Agents.
Ethernet Network Network Interface: Heavy or Light?
CCNA 3 v3 JEOPARDY Module 9 CCNA3 v3 Module 9 K. Martin.
Chapter 3 VLANs Chaffee County Academy
Virtual LAN VLAN Trunking Protocol and Inter-VLAN Routing
DRNI and Distributed Network Protection Model Evolution: Maarten  Norm  Steve Maarten Vissers v1  
May 2004 doc.: IEEE /629r1 May 2004 The Nature of an ESS
Lecture#7: Trunking and STP
TIME-SHARED LINK – DRNI LEARNING
TAPI Photonic Media Model
Presentation transcript:

Stephen Haddock September 13, 2012 Link Selection and OAM Version 02 (added a Conclusion slide capturing the results of the discussion following presentation on 9/12/12) Stephen Haddock September 13, 2012

Example Scenario Client connects to a Server in a Co-Location facility Carrier Network Data Center Network Server Client Client connects to a Server in a Co-Location facility A single VLAN is used to carry this service within the Data Center Network All frames transmitted and received by Server are untagged. VLAN is monitored using CFM with Up MEPs at each interface to the Data Center Network.

Server connects with Link Aggregation MAC Relay Server VLAN (6.9) Link Agg Link Agg MAC MAC MAC MAC Server connects using Link Aggregation 5-tuple hash used to distribute frames among LAG links. Up MEP sits above Link Aggregation In practice, separation of the physical ports of the LAG may complicate implementation of the MEP, forcing it to be either distributed between the ports or centralized but not resident on a single physical port.

Server connects with DRNI Server connects to two physically separate nodes (Systems A and B) The logical view, as seen from the point of view of the Server and the Data Center Network, is that there the Server connects to a third node (Emulated System C) through a single logical port. Server B A Relay (B) Server Distributed Relay (EmulatedSystem C) (6.9) Relay (A) MAC (6.9) (6.9) VLAN (6.9) (6.9) MAC MAC Link Agg Link Agg MAC MAC MAC MAC MAC Gateway Links (virtual)

Distributed Relay as seen by Systems A and B Relay (B) (6.9) (6.9) MAC Selected Gateway for this VLAN MAC Server Distributed Relay (C)* Distributed Relay (C)* (6.9) (6.9) (6.9) (6.9) (6.9) (6.9) MAC LAG* MAC MAC LAG* MAC Link Agg MAC MAC MAC MAC MAC IPL Link Selection still based on 5-tuple hash, so both LAG links carry data. Where does the Up MEP go?

Options for MEP Implementation Distribute MEP functionality across the physical DRNI ports. Requires standardizing how MEP functionality gets distributed. Almost certainly requires support from the Intra-Portal Protocol. Distribute MEP functionality across the Intra-Portal Port and the DRNI ports in the system with the selected Gateway. Distributes MEP functionality among ports in the same physical system (which is the same problem that arises with today’s LAG). Intra-Portal Link is not included in the MA monitored by the MEP. MEP functionality moves when the selected Gateway changes. Constrain the Link Selection such that all frames that would pass through the same MEP use the same DRNI link. VERY restrictive constraint. Are there any other options?

2nd Example: DRNI at an I-tagged service interface Carrier A Network Carrier B Network B A B-components (B-BEBs) The service ID on an I-tagged service interface is the I-SID. Link selection is by I-SID Multiple I-SIDs map into a B-VLAN in the Carrier A Network The B-VLAN is monitored using CFM with Up MEPs at each interface to the Carrier A Network. * Reference: 802-1Q Figure 25-9 and 26.6.2

I-tagged DRNI as seen by Systems A and B Relay (A) Relay (B) (6.9) (6.9) MAC Selected Gateway for this B-VLAN MAC Distributed Relay (C)* Distributed Relay (C)* (6.9) (6.11) (6.9) (6.9) (6.11) (6.9) MAC LAG* MAC MAC LAG* MAC MAC MAC MAC IPL Link Selection based on I-SID, so I-SIDs from both LAG links could map to the B-VLAN. Where does the Up MEP go?

Conclusion on 9/12/12 The conclusion of the discussion in the 802.1 Interworking session on 9/12/12 was to favor a slightly different expression of option 2: The system that acts as the selected Gateway for a VLAN is responsible for implementing an Up MEP monitoring that VLAN (if such a MEP is configured). How the system implements the MEPs, i.e. whether the functionality is distributed across multiple physical ports or centralized somewhere in the system, is implementation dependent and will not be specified in the standard. The Intra-Portal Link is outside the MA monitored by this MEP. The MEP functionality moves when the Gateway changes. The MEP state is not synchronized during such a move, which may result in things such as a discontinuity in counters maintained by the MEP.

Thank You .