Revision of the Appointed Forwarder RFC draft-eastlake-trill-rfc6439-00.txt Donald E. Eastlake, 3 rd +1-508-333-2270 March 2015 Appointed.

Slides:



Advertisements
Similar presentations
Radia Perlman Intel Labs
Advertisements

TRILL ESADI draft-hu-trill-rbridge-esadi-00 Hongjun Zhai (ZTE) Fangwei hu (ZTE) Radia Perlman (Intel Labs) Donald Eastlake 3 rd (Huawei) July 20111TRILL.
Communication Networks Recitation 3 Bridges & Spanning trees.
Introduction to Computer Networks Spanning Tree 1.
Part 2: Preventing Loops in the Network
Overview of TRILL Active-Active Goals, Challenges, and Proposed Solutions Radia Perlman 1November 2013.
1 Introduction to ISIS SI-E Workshop AfNOG The Gambia Noah Maina.
Packet Switching COM1337/3501 Textbook: Computer Networks: A Systems Approach, L. Peterson, B. Davie, Morgan Kaufmann Chapter 3.
Joining LANs - Bridges. Connecting LANs 4 Repeater –Operates at the Physical layer no decision making, processing signal boosting only 4 Bridges –operates.
TRILL issue: Using Pseudonode Nicknames for Ingress RBridge Radia Perlman Hongjun Zhai Fangwei Hu 1November 2011.
Connecting LANs: Section Figure 15.1 Five categories of connecting devices.
Directory Assisted TRILL Encapsulation by non-TRILL nodes (Directory Reliant Smart End Node) Linda Dunbar Donald Eastlake Radia Perlman Igor Gashinsky.
Bridging. Bridge Functions To extend size of LANs either geographically or in terms number of users. − Protocols that include collisions can be performed.
Oct 12, 2004CS573: Network Protocols and Standards1 Virtual LANs Network Protocols and Standards Autumn
Single Area Border RBridge Nickname for TRILL Multilevel draft-zhang-trill-multilevel-single-nickname-00.txt Mingui Zhang, Donald Eastlake, Radia Perlman.
STP Spanning tree protocol. Trunk port : A trunk port is a port that is assigned to carry traffic for all the VLANs that are accessible by a specific.
Jan 10, 2008CS573: Network Protocols and Standards1 Virtual LANs Network Protocols and Standards Winter
Introduction to Computer Networks 09/23 Presenter: Fatemah Panahi.
Layer 2 Switch  Layer 2 Switching is hardware based.  Uses the host's Media Access Control (MAC) address.  Uses Application Specific Integrated Circuits.
TRILL Link Protocols Donald Eastlake Huawei Technologies July 20141Directory Assist.
TRILL over IP draft-ietf-trill-over-ip-01.txt IETF 91, Honolulu Margaret Wasserman Donald Eastlake, Dacheng Zhang.
TRILL OAM draft-eastlake-trill-rbridge-channel-00 draft-bond-trill-rbridge-oam-01 draft-manral-trill-bfd-encaps-01 Donald Eastlake 3 rd Huawei Technologies.
Transparent Bridging. Chapter Goals Understand transparent bridge processes of learning, filtering, forwarding, and flooding. Explain the purpose of the.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 3 v3.1 Module 7 Spanning Tree Protocol.
TRansparent Interconnection of Lots of Links (TRILL) March 11 th 2010 David Bond University of New Hampshire: InterOperability.
CSC 336 Data Communications and Networking Lecture 7d: Interconnecting LAN Dr. Cheer-Sun Yang Spring 2001.
Saeed Darvish Pazoki – MCSE, CCNA Abstracted From: Cisco Press – ICND 2 – Chapter 2 Spanning tree Protocol 1.
March 2008Protocol Draft Changes -06 to -071 TRILL Protocol Specification Changes from -06 to -07 Donald Eastlake 3 rd
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 LAN Switching and Wireless Implement Spanning Tree Protocols (STP) Chapter.
Steffen/Stettler, , 4-SpanningTree.pptx 1 Computernetze 1 (CN1) 4 Spanning Tree Protokoll 802.1D-2004 Prof. Dr. Andreas Steffen Institute for.
Rfc7180bis: Further TRILL Clarifications, Corrections, and Updates Donald Eastlake Mingui Zhang, Radia Perlman, Ayan Banerjee, Anoop Ghanwani, Sujay Gupta.
TRILL Base Protocol Clarifications and Corrections November 20111TRILL: Clear Correct Donald E. Eastlake, 3 rd (Huawei) Mingui Zhang (Huawei) Anoop Ghanwani.
1 Multilevel TRILL draft-perlman-trill-rbridge-multilevel-00.txt Radia Perlman Intel Labs March 2011.
November 2010Future TRILL Work1 Future TRILL Work 2 Donald Eastlake 3 rd 155 Beaver Street Milford, MA USA
TRILL OAM & BFD draft-eastlake-trill-rbridge-bfd-00.txt Donald E. Eastlake 3 rd 155 Beaver Street Milford, MA USA November 20101TRILL OAM & BFD Vishwas.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 6: Static Routing Routing and Switching Essentials.
86th IETF, Orlando, March 2013 IS-IS Support for Unidirectional Links draft-ginsberg-isis-udl-00.txt Les Ginsberg
Configuring Cisco Switches Chapter 13 powered by DJ 1.
Transparent Interconnection of Lots of Links(TRILL) Speaker: Hui-Hsiung Chung Date:2011/12/28 1.
TRILL remaining issues Radia Perlman
November 2013TRILL Directory Assist Mechanisms1 TRILL Directory Assistance Mechanisms draft-dunbar-trill-scheme-for-directory-assist-06 draft-eastlake-trill-ia-appsubtlv-03.
1 Data Link Layer Lecture 23 Imran Ahmed University of Management & Technology.
McGraw-Hill©The McGraw-Hill Companies, Inc., 2004 Chapter 16 Connecting LANs, Backbone Networks, and Virtual LANs.
Kireeti Kompella draft-kompella-mpls-rmr-01
Topic 5 Spanning tree protocol
Possible TRILL Use of GENAPP in draft-ietf-trill-rbridge-channel Donald E. Eastlake, 3 rd Huawei Technologies (USA) 24 July
Submission doc.: IEEE 11-13/0526r1 May 2013 Donald Eastlake, HuaweiSlide 1 Sub-Setting Date: Authors:
Doc.: IEEE /1091-r0 SubmissionGuenael Strutt, Jan KruysSlide 1 July 2006 Interworking Considerations Date: Authors: Notice: This document.
RBridges: Operations, Administration, and Maintenance (OAM) Support David Bond, Vishwas Manral UNH-IOL, IP Infusion draft-bond-trill-rbridge-oam-00 1.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Implement Spanning Tree Protocols (STP) LAN Switching and Wireless – Chapter.
March th IETF - Prague1 TRILL Working Group Changes from draft-trill-rbridge-protocol-02.txt to draft-trill-rbridge-protocol-03.txt Dinesh Dutt,
November 2006IETF TRILL WG1 TRILL Working Group draft-gai-perlman-trill-encap-00.txt as modified by Radia Ed Bowen, IBM Dinesh Dutt, Cisco Silvano Gai,
March 2007RBridge Extensions1 RBridge Protocol Extensions and the Inner Q-tag Location Donald Eastlake 3rd
86th IETF, Orlando, March 2013 Flooding Scope PDUs draft-ginsberg-isis-fs-lsp-00.txt Les Ginsberg Stefano Previdi.
March 2015 TRILL Link Security March 2015 TRILL Link Security
Spanning Tree Protocol
Transparent Bridging.
ISIS Flooding Reduction in MSDC
Topic: Spanning Tree Protocol
RBridge Channel Tunnel Protocol
TRILL Directory Assistance Mechanisms
Configuring Catalyst Switch Operations
Spanning Tree Protocol
Additional TRILL Work/Documents
Spanning Tree Protocol
NT2640 Unit 9 Activity 1 Handout
TRILL Adjacency Document Status
TRILL Header Extension Improvements
TRILL Adjacency Document Status
Presentation transcript:

Revision of the Appointed Forwarder RFC draft-eastlake-trill-rfc txt Donald E. Eastlake, 3 rd March 2015 Appointed Forwarder Revision 1

Background TRILL base protocol supports multiple TRILL switches (RBridges) on a link providing end station service where traffic is allocated among the RBridges by VLAN. The RBridge handling native end station traffic to/from the link in VLAN-x is called the Appointed Forwarder for VLAN-x The current details are in RFC 6439 which was updated by RFC March 2015 Appointed Forwarder Revision 2

Background March 2015 Appointed Forwarder Revision 3 TRILL Campus RB1 RB2 RB3 BR-1BR-2 RBridges > Bridges > End Stations > ES12 ES11 ES22 ES21

Current rfc6439bis Draft Add mandatory E-L1CS FS-LSP support. The current rfc6439bis draft requires support of Extended Level 1 Circuit Scoped (E-L1CS) Flooding Scope LSPs as specified in RFC Expands space for link local state and configuration advertisements from the very limited space in the IS-IS Hello up to 2**16 link local LSP fragments. This eliminates the current restrictions on appointing forwarders on a link due to lack of space in a Hello for appointment information. March 2015 Appointed Forwarder Revision 4

Current rfc6439bis Draft (cont.) Specifies APPsub-TLVs for sending efficiently encoded forwarder appointments in E-L1CS in cases other than contiguous blocks of VLANs. Blocks of contiguous VLANs efficiently encoded by Appointed Forwarders sub-TLV [RFC7176]. Scattered VLANs over a narrow range efficiently encoded by Appointment Bitmap APPsub-TLV in rfc6439bis. Scattered VLANs over a large range efficiently encoded by Appointment List APPsub-TLV in rfc6439bis. Incorporates Appointed Forwarder material from RFC 7180 that optionally reduced the number of VLANs in which Hellos must be sent. Adds optional FGL mapping consistency check on a link. March 2015 Appointed Forwarder Revision 5

Further Possible Improvements Two further optional improvements that could be incorporated into this draft: 1.Port failure/shutdown notification 2.Root bridge change optimizations There is IPR on these improvements that will be disclosed. March 2015 Appointed Forwarder Revision 6

1. Port failure/shutdown notification An RBridge may have a planned shut down of a port on a link or might detect port failure at the physical or other level. Port failure is not currently noticed by other RBridges until multiple Hellos from that port are missed, which can take many seconds. March 2015 Appointed Forwarder Revision 7

1. Port failure/shutdown notification The proposal is to send an RBridge Channel message indicating port failure/shutdown. Message is serially unicast through the TRILL campus to other RBridges on the link and/or (in the case of shutdown) broadcast on the link. The port can be unambiguously identified by the RBridge’s IS-IS System ID and the port’s Port ID. This message can be secured using the RBridge Channel Tunnel protocol. March 2015 Appointed Forwarder Revision 8

1. Port failure/shutdown notification Other RBridges on the link, on receipt of this message, drop adjacency to the port that failed or is being shutdown. If that RBridge/port had been elected Designated RBridge (DRB) on the link, a new DRB is elected. If that RBridge/port was Appointed Forwarder, a new forwarder can be appointed immediately. [Similar steps can be taken if an RBridge on the link crashes but no new message is needed in that case as this is visible via LSPs.] March 2015 Appointed Forwarder Revision 9

2. Root bridge change optimizations Many links are point-to-point but, in the case of multiple RBridges and end stations on a link, are likely to be bridge LANs. Bridges and links can go down or come up. As a result a bridged LAN could partition or bridged LANs could merge. While bridging protocols are settling for the new bridge LAN topology, there could be multiple VLAN-x Appointed Forwarders, TRILL Hellos can be blocked, etc.. March 2015 Appointed Forwarder Revision 10

2. Root bridge change optimizations As a result, when a CIST root bridge change is detected by an RBridge port, current TRILL protocol requires that the port be “inhibited” for a configurable fixed length of time. Note: “Inhibition” has no effect on TRILL Data or IS-IS packets. It only stops ingress and egress of native frames from/to end stations. There are at least three cases where this is not necessary. March 2015 Appointed Forwarder Revision 11

2. Root bridge change optimizations 2.Three cases where the CIST root Bridge Identifier changes but inhibition is unnecessary or can be terminated early: a)If the Bridge Identifier changes to a lower priority value. b)If the the root Bridge Address stays the same. c)If, since the Identifier change, Hellos have been received from all known RBridges on the bridged LAN. March 2015 Appointed Forwarder Revision 12

2. Root bridge change optimizations a)If the Bridge Identifier changes to a lower priority value. This implies that a bridge or link crashed, possibly partitioning the bridge LAN. In this case, no inhibition is required. A change is unsafe only for an RBridge port that sees a new higher priority CIST root Bridge Identifier. March 2015 Appointed Forwarder Revision 13

2. Root bridge change optimizations b)If, when the CIST Bridge Identifier changes, the Bridge Address part stays the same. This implies that the only thing that happened was that the other bits in the Bridge Identifier have been configured to a different value but he bridge that was CIST root is unchanged. In this case, no inhibition is required. March 2015 Appointed Forwarder Revision 14

2. Root bridge change optimizations c)If, since the Identifier change, Hellos have been received from all known RBridges on the bridged LAN. RBridges are required to report the CIST root Bridge Address that they see in their LSPs. All RBridges attached to the same bridged LAN will see the same root. Either there is connectivity outside the bridge LAN to another RBridges on the bridge LAN or not. In the first case, you will know about the other RBridge and can wait for a new Hello or the inhibition timeout. The second case, where connectivity is only through the bridged LAN, is loop safe. So, inhibition can be terminated as soon as new Hellos have been received from all other RBridges on the bridged LAN as known through LSP root Bridge Address reports. March 2015 Appointed Forwarder Revision 15

END Donald E. Eastlake, 3 rd March 2015 Appointed Forwarder Revision 16