1 / 128

TRILL Tutorial Transparent Interconnection of Lots of Links

TRILL Tutorial Transparent Interconnection of Lots of Links. Donald E. Eastlake 3 rd Co-Chair, TRILL Working Group Principal Engineer, Huawei d3e3e3@gmail.com. Donald E. Eastlake, 3 rd Principal Engineer at Huawei Technologies

alaura
Download Presentation

TRILL Tutorial Transparent Interconnection of Lots of Links

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TRILL TutorialTransparent Interconnection of Lots of Links RIPE TRILL Tutorial Donald E. Eastlake 3rd Co-Chair, TRILL Working Group Principal Engineer, Huawei d3e3e3@gmail.com

  2. Donald E. Eastlake, 3rd • Principal Engineer at Huawei Technologies • Previously with Cisco Systems and before that with Motorola Laboratories. • Co-Chair of the IETF TRILL Working Group • Chair of the IETF PPPEXT Working Group • Chair of the IEEE 802.11ak Task Group • Author of 61 IETF RFCs. RIPE TRILL Tutorial Note: This tutorial represents my personal views, not those of the TRILL WG or Huawei. It is a high level technical overview. It is not practical to include all the details in the specification documents in a presentation of this length.

  3. CONTENTS • What is TRILL? • TRILL Features • TRILL History • Two TRILL Examples • TRILL Packet Headers • Step-by-Step Processing Example • Fine Grained Labeling • How TRILL Works • Peering and Layers • TRILL Support of DCB • TRILL OAM • TRILL Products • Comparisons • Standardization andReferences RIPE TRILL Tutorial

  4. What is TRILL? • A Compatible Protocol • Attached end nodes just think it is Ethernet. • The more bridges you convert to TRILL switches, the better your network’s stability and bandwidth utilization. • Terminates Spanning Tree Protocols RIPE TRILL Tutorial

  5. Whatis TRILL? • Basically a simple idea: • Encapsulate native frames in a transport header providing a hop count • Route the encapsulated frames using IS-IS • Decapsulate native frames before delivery • Provides • Least cost paths with zero/minimal configuration • Equal Cost Multi-Pathing of unicast • Multi-paths of multi-destination RIPE TRILL Tutorial

  6. Whatis TRILL? • TRansparentInterconnection of Lots of Links • TRILL WG Charter • http://www.ietf.org/dyn/wg/charter/trill-charter.html • Standardized by IETF TRILL Working Group: • Donald E. Eastlake 3rd (Huawei), Co-Chair • Erik Nordmark (Cisco), Co-Chair • Jon Hudson (Brocade), Secretary • TRILL Switch / RBridge (Routing Bridge) • Device that implements TRILL • TRILL/RBridge Campus – • A network of RBridges, links, and any intervening bridges, that connects end stations and layer 3 routers. RIPE TRILL Tutorial

  7. A TRILL Campus = end station = Ethernet = Any technology L3 Router • End stations and Layer 3 routers are connected to TRILL switches by Ethernet. • TRILL switches can be connected to each other with arbitrary technology. • In both cases, the connection can be a bridged LAN. L3 Router Bridge 1 RB4 RB1 Bridge 2 RB5 RB2 RB3 Bridge 3 RIPE TRILL Tutorial RB6

  8. CONTENTS • What is TRILL? • TRILL Features • TRILL History • Two TRILL Examples • TRILL Packet Headers • Step-by-Step Processing Example • Fine Grained Labeling • How TRILL Works • Peering and Layers • TRILL Support of DCB • TRILL OAM • TRILL Products • Comparisons • Standardization andReferences RIPE TRILL Tutorial

  9. Unicast Least Cost Paths = end station B1 RIPE TRILL Tutorial B3 B2 A three bridge network

  10. Unicast Least Cost Paths = end station B1 RIPE TRILL Tutorial B3 B2 Spanning tree eliminates loopsby disabling ports

  11. Unicast Least Cost Paths = end station RB1 RIPE TRILL Tutorial RB3 RB2 A three RBridge network: better performance using all facilities

  12. Unicast Multi-Pathing B1 B3 B2 B5 RIPE TRILL Tutorial B4 = end station Bridges limit traffic to one path

  13. Unicast Multi-Pathing RB1 RB5 RB3 RB2 RIPE TRILL Tutorial RB4 = end station RBridges supportmulti-path for higher throughput

  14. Multi-Pathing (Unicast) B5 B6 B7 RIPE TRILL Tutorial B2 B3 B4 B1 = end station Bridges limit traffic to one path

  15. Multi-Pathing (Unicast) RB5 RB6 RB7 RIPE TRILL Tutorial RB2 RB3 RB4 RB1 = end station RBridges supportmulti-pathing for higher throughput

  16. Multi-Pathing(Multi-destination) B5 B6 B7 RIPE TRILL Tutorial B2 B3 B4 B1 = end station Spanning tree yields a single bi-directional tree for flooding multi-destination frames limiting bandwidth

  17. Multi-Pathing(Multi-destination) RB5 RB6 RB7 RIPE TRILL Tutorial RB2 RB3 RB4 RB1 = end station RBridges support multiple distribution trees. The encapsulating RBridge chooses which to use. RB2 can split multi-destination traffic over three trees.

  18. Routing versus Bridging • Routingonly sends data out a port when it receives control messages on that port indicating this is safe and routing has a TTL for safety. • If control messages are not received or not processed, it “fails safe” and does not forward data. • Bridging (Spanning Tree Protocol) forwards data out all ports (except the one where the data was received) unless it receives control messages on that port indicate this is unsafe. There is no TTL. • If control messages are not received or not processed, it “fails unsafe”, forwards data, and can melt down due to data loops. RIPE TRILL Tutorial

  19. TRILL Features • Transparency • Plug & Play • Virtual LANs • Multi-tenant support • Frame Priorities • Data Center Bridging • Virtualization Support Bridges TRILL Switch Routers • Multi-pathing • Optimal Paths • Rapid Fail Over • The safety of a TTL • Implemented in data plane • Extensions RIPE TRILL Tutorial

  20. More TRILL Features • Breaks up and minimizes spanning tree for greater stability. • Unicast forwarding tables at transit RBridges scale with the number of RBridges, not the number of end stations. • Transit RBridges do not learn end station addresses. • Compatible with existing IP Routers. TRILL switches are as transparent to IP routers as bridges are. • Support for VLANs, frame priorities, and 24-bit data labels (“16 million VLANs”). RIPE TRILL Tutorial

  21. More TRILL Features • MTU feature and jumbo frame support including jumbo routing frames. • Has a poem. • The only other bridging or routing protocol with a poem is Spanning Tree (see Algorhyme). RIPE TRILL Tutorial

  22. Algorhyme V2 (TRILL and RBridges) • I hope that we shall one day see • A graph more lovely than a tree. • A graph to boost efficiency • While still configuration-free. • A network where RBridges can • Route packets to their target LAN. • The paths they find, to our elation, • Are least cost paths to destination! • With packet hop counts we now see, • The network need not be loop-free! • RBridges work transparently, • Without a common spanning tree. • - By Ray Perlner (Radia Perlman’s son) RIPE TRILL Tutorial

  23. CONTENTS • What is TRILL? • TRILL Features • TRILL History • Two TRILL Examples • TRILL Packet Headers • Step-by-Step Processing Example • Fine Grained Labeling • How TRILL Works • Peering and Layers • TRILL Support of DCB • TRILL OAM • TRILL Products • Comparisons • Standardization andReferences RIPE TRILL Tutorial

  24. Inspired by a Real Life Incident • In November 2002, Beth Israel Deaconess Hospital in Boston, Massachusetts, had a total network meltdown: • Their network took four days of heroic efforts to be restored to an operational state! In the mean time the staff was reduced to using paper and pencil. • Beth Israel Deaconess had grown by acquiring various clinics and just plugged all those bridged networks together. • The article in Boston’s primary newspaper specifically mentioned “Spanning Tree Protocol” as the problem! • Radia Perlman, who invented spanning tree over 25 years ago, decided it was time to come up with a better way. RIPE TRILL Tutorial

  25. TRILL History up to 2008 • 1964: Packet switching/routing invented by Paul Baran. • 1973: Ethernet invented by Robert Metcalfe • 1979: Link State Routing invented by John McQuillan. • 1985: Radia Perlman invents the Spanning Tree Protocol. • 1987: DECnet Phase V / IS-IS designed by Radia Perlman. • 2002: Beth Israel Deaconess Hospital network in Boston melts down due to deficiencies in the Spanning Tree Protocol. • 2004: TRILL presented by inventor Radia Perlman at Infocom. • 2005: TRILL presented to IEEE 802 by Radia Perlman, rejected. • 2005: TRILL presented to IETF which Charters the TRILL Working Group. • 2008: MTU problem delays protocol while fix is incorporated. RIPE TRILL Tutorial

  26. TRILL in 2009/2011 • 2009: RFC 5556 “TRILL: Problem and Applicability Statement” • 2009: TRILL Protocol passed up to IESG for Approval. • 2010: TRILL approved IETF Standard (2010-03-15) • Ethertypes, Multicast addresses & NLPID assigned • 2010: Successful TRILL control plane interop at UNH IOL • 2011: TRILL Protocol base document set: • RFC 6325: “RBridges: TRILL Base Protocol Specification” • RFC 6326: “TRILL Use of IS-IS” • RFC 6327: “RBridges: Adjacency” • RFC 6361: “TRILL over PPP” • RFC 6439: “RBridges: Appointed Forwarders” • 2011: TRILL Working Group Re-Chartered to do further development of the TRILL protocol RIPE TRILL Tutorial

  27. TRILL in 2012/2013 • 2012: Second Successful TRILL control plane interop at UNH IOL • 2013: Additional TRILL documents published: • RFC 6447: FCoE (Fibre Channel over Ethernet) over TRILL • RFC 6850: RBridge MIB • RFC 6905: TRILL OAM Requirements • 2013: Third TRILL interop for control and data plane at UNH IOL week of May 20th • 2013: TRILL Working Group Re-Chartered to do further development of the TRILL protocol RIPE TRILL Tutorial

  28. CONTENTS • What is TRILL? • TRILL Features • TRILL History • Two TRILL Examples • TRILL Packet Headers • Step-by-Step Processing Example • Fine Grained Labeling • How TRILL Works • Peering and Layers • TRILL Support of DCB • TRILL OAM • TRILL Products • Comparisons • Standardization andReferences RIPE TRILL Tutorial

  29. Two TRILL Examples • “Acme Power Plant” Process Control • Large process control commonly uses Ethernet • Some process control protocols interpret network interruption >1 second as equipment failure • Even Rapid Spanning Tree Protocol can take >3 second to recover from root bridge failure • Core RBridges reduce/eliminate spanning tree • “Acme Data Center” • 1:1 to N:1 Backup Improvement RIPE TRILL Tutorial

  30. A A A A A A A A A A A A GB GB GB GB 1. Acme Power Plant Bridged Process Control Network Rapid Spanning Tree Protocol Domain CB CB RIPE TRILL Tutorial GB GB A = Access Bridge GB = aGreggation Bridge CB = Core Bridge A A A A A A

  31. A A A A A A A A A A A A GB GB GB GB 1. Acme Power Plant Spanning Tree Eliminates Loops by Disabling Ports Rapid Spanning Tree Protocol Domain CB CB RIPE TRILL Tutorial GB GB A = Access Bridge GB = aGreggation Bridge CB = Core Bridge A A A A A A

  32. A A A A A A A A A A A A RSTP Domain RSTP Domain GB GB GB GB CRB CRB 1. Acme Power Plant Process Control Network with RBridge Core breaking up spanning tree RIPE TRILL Tutorial GB GB RSTP Domain A = Access Bridge GB = aGreggation Bridge CRB = Core RBridge A A A A A A

  33. A A A A A A A A A A A A GRB GRB GRB GRB 1. Acme Power Plant Process Control Network with RBridge Mesh eliminating spanning tree RIPE TRILL Tutorial GRB GRB A = Access Bridge GRB = aGreggation RBridge A A A A A A

  34. 2. Acme Data Center Network with Bridges 1:1 Backup Distribution Bridges must be able to handle 100% of the load. Only 1 path available between any pair of “B”s. Wan Router Wan Router Dist. Bridge Dist. Bridge B = Head of Rack Bridge RIPE TRILL Tutorial B B B B B B B B B B B B B B B

  35. N:1 Backup Distribution Bridges need to handle only 25% of the load. Multiple available paths between “H”s. 2. Acme Data Center Network with RBridges Wan Router Wan Router Dist. RBridge Dist. RBridge Dist. RBridge Dist. RBridge Dist. RBridge H = Head of Rack RBridge RIPE TRILL Tutorial H H H H H H H H H H H H H H H

  36. CONTENTS • What is TRILL? • TRILL Features • TRILL History • Two TRILL Examples • TRILL Packet Headers • Step-by-Step Processing Example • Fine Grained Labeling • How TRILL Works • Peering and Layers • TRILL Support of DCB • TRILL OAM • TRILL Products • Comparisons • Standardization andReferences RIPE TRILL Tutorial

  37. TRILLPacket Headers • TRILL Data packets between RBridgeshave a local link header and TRILL Header. • The local link headeron Ethernet is addressed from the local source RBridge to the next hop RBridge for known unicast frames or to the All-RBridges multicast address for multi-destination frames. • The TRILL Header specifies the first/ingress RBridge and either the last/egress RBridge for known unicast frames or the distribution tree for multi-destination frames. RIPE TRILL Tutorial

  38. TRILLPacket Headers • Reasons for TRILL Header: • Provides a hop count to reduce loop issues • To hide the original source address to avoid confusing any bridges present as might happen if multi-pathing were in use • To direct unicast frames toward the egress RBridge so that forwarding tables in transit RBridges need only be sized with the number of RBridges in the campus, not the number of end stations • To provide a separate outer VLAN tag, when necessary, for forwarding traffic between RBridges, independent of the original VLAN of the frame RIPE TRILL Tutorial

  39. TRILLPacket Headers • TRILL Header • Nicknames – auto-configured 16-bit campus local names for RBridges • V = Version (2 bits) • R = Reserved (2 bits) • M = Multi-Destination (1 bit) • ExtLng = Length of TRILL Header Extensions • Hop = Hop Limit (6 bits) TRILL Ethertype V R M ExtLng Hop Egress RBridge Nickname Ingress RBridge Nickname RIPE TRILL Tutorial

  40. TRILL OverEthernet DA SA VLAN* TRILL Ethertype0x22F3 FCS TRILL Header Payload Frame(DA, SA, VLAN/Tenant, Data) Data: Original Frame withVLAN/Tenant Label Ethernet Link Transport Header FCS SA DA VLAN* L2-IS-IS Ethertype0x22F4 IS-IS PDU RIPE TRILL Tutorial IS-IS: Ethernet Cloud RBridge Two RBridge One RBridge Three * Link Transport VLAN only needed for VLAN sensitive link.

  41. TRILL OverPPP PPP FCS TRILL Header Payload Frame(DA, SA, VLAN/Tenant, Data) PPP TRILL Data Protocol0x005D Data: Original Frame withVLAN/Tenant Label PPP LinkTransport Header PPP TRILL IS-IS Protocol0x405D PPP FCS IS-IS PDU RIPE TRILL Tutorial IS-IS: PPP RBridge One RBridge Two

  42. CONTENTS • What is TRILL? • TRILL Features • TRILL History • Two TRILL Examples • TRILL Packet Headers • Step-by-Step Processing Example • Fine Grained Labeling • How TRILL Works • Peering and Layers • TRILL Support of DCB • TRILL OAM • TRILL Products • Comparisons • Standardization andReferences RIPE TRILL Tutorial

  43. Ethernet UnicastProcessing Example • Step-by-Step on Following Slides: • Input Port Processing • TRILL Unicast Ingress • TRILL Unicast Transit • TRILL Unicast Egress • Output Port Processing RIPE TRILL Tutorial

  44. Input Port Processing • Detailed example of unicast frame TRILL routing on an Ethernet link • Input port adds VLAN-ID and priority if frame untagged Input Native Frame on link: Dest MAC Src MAC Data FCS VLAN RIPE TRILL Tutorial Input Native Frame after input port: VLAN Dest MAC Src MAC Data FCS

  45. TRILL Unicast Ingress Input Native Frame: Dest MAC Src MAC VLAN Data FCS Look Up Egress, Next Hop DA & Output Port Output TRILL Data Frame: TTL=n Ingress Egress DA SA VLAN1 TRILL Header Payload Frame New FCS RIPE TRILL Tutorial Ingressing RBridge Original Frame withVLAN or Tenant ID Link Transport Header 1Outer VLAN tag is a transport artifact and only needed if RBridges are connected by a bridged LAN or carrier Ethernet requiring a VLAN tag or the like.

  46. TRILL Unicast Transit Incoming Link Transport Header Input TRILL Data Frame: TTL=n DA SA VLAN1 TRILL Hdr Payload Frame FCS Egress Ingress Transit RBridge Look Up Next DA & Output Port RIPE TRILL Tutorial TTL=n-1 DA SA VLAN1 TRILL Hdr Payload Frame New FCS Egress Ingress Output TRILL Data Frame: Outgoing Link Transport Header 1 Input and output Outer VLANs can differ. The true VLAN or Tenant ID of the data is inside the payloadframe. Outer VLAN is only needed if link is VLAN sensitive.

  47. TRILL Unicast Egress Link Transport Header Egressing RBridge Input TRILL Data Frame: DA SA VLAN1 TRILL Hdr Payload Frame FCS Egress Ingress Output Native Frame: RIPE TRILL Tutorial Dest MAC Src MAC VLAN2 Data New FCS Look Up Output Port 1 Outer VLAN only needed if RBridges are connected by a bridged LAN or carrier Ethernet requiring a VLAN tag or the like. 2 Final native frame VLAN tag may be omitted depending on RBridge output port configuration.

  48. Output Port Processing • Output port may be configured to output untagged and will do so by default for the port VLAN ID Output Native Frame before output port: Dest MAC Src MAC VLAN Data New FCS RIPE TRILL Tutorial Dest MAC Src MAC Data New FCS

  49. CONTENTS • What is TRILL? • TRILL Features • TRILL History • Two TRILL Examples • TRILL Packet Headers • Step-by-Step Processing Example • Fine Grained Labeling • How TRILL Works • Peering and Layers • TRILL Support of DCB • TRILL OAM • TRILL Products • Comparisons • Standardization andReferences RIPE TRILL Tutorial

  50. Fine Grained Labeling • Fine Grained Labeling (FGL)provides extended 24-bit label (or tenant ID) as the inner data label. • Ingress/egress TRILL switches that support FGL: • Map native frame VLAN and input port into a fine grained label on ingress and • do the reverse mapping on egress. • Remember the priority and DEI of native frames on ingress and restores them on egress. • Fine Grained Label TRILL switches are a superset of a base protocol TRILL switches. They support VLANs as in the base standard on a port if not configured to do Fine Grained Labeling. RIPE TRILL Tutorial

More Related