TRILL

Last updated

TRILL (Transparent Interconnection of Lots of Links) is a networking protocol for optimizing bandwidth and resilience in Ethernet networks, [1] implemented by devices called TRILL switches. TRILL combines techniques from bridging and routing, and is the application of link-state routing to the VLAN-aware customer-bridging problem. [2] Routing bridges (RBridges) are compatible with, and can incrementally replace, previous IEEE 802.1 customer bridges. TRILL Switches are also compatible with IPv4 and IPv6, routers and end systems. They are invisible to current IP routers, and like conventional routers, RBridges terminate the broadcast, unknown-unicast and multicast traffic of DIX Ethernet and the frames of IEEE 802.2 LLC including the bridge protocol data units of the Spanning Tree Protocol.

Contents

TRILL was designed as a successor to the Spanning Tree Protocol, both having been created by the same person, Radia Perlman. The catalyst for TRILL was an event at Beth Israel Deaconess Medical Center which began on 13 November 2002. [3] [4] The concept of Rbridges [5] [sic] was first proposed to the Institute of Electrical and Electronics Engineers in 2004, [6] who in 2005 [7] rejected what came to be known as TRILL, and in 2006 through 2012 [8] devised an incompatible variation known as Shortest Path Bridging.

General overview

TRILL switches, or RBridges, run the IS-IS link-state routing protocol amongst themselves. [9] In this protocol, connectivity is broadcast to all the RBridges, so that each RBridge knows about all the other RBridges, and the connectivity between them. This gives RBridges enough information to compute pair-wise optimal paths for unicast, and calculate distribution trees for delivery of frames either to destinations whose location is unknown or to multicast or broadcast groups. In contrast to Spanning Tree Protocol, which ensures a loop-free network topology by blocking otherwise active ports, TRILL establishes paths over all active links.

IS-IS was chosen because:

To mitigate temporary loop issues, RBridges forward based on a header with a hop count. RBridges also specify the next-hop RBridge as the frame destination when forwarding unicast frames across a shared-media link, which avoids spawning additional copies of frames during a temporary loop. A reverse-path forwarding check and other checks are performed on multi-destination frames to further control potentially looping traffic.

The first RBridge that a unicast frame encounters in a campus, RB1, encapsulates the received frame with a TRILL header that specifies the last RBridge, RB2, where the frame is decapsulated. RB1 is known as the "ingress RBridge" and RB2 is known as the "egress RBridge". To save room in the TRILL header and simplify forwarding lookups, a dynamic nickname acquisition protocol is run among the RBridges to select two-octet nicknames for RBridges, unique within the campus, which are an abbreviation for the six-octet IS-IS system ID of the RBridge. The two-octet nicknames are used to specify the ingress and egress RBridges in the TRILL header.

The TRILL header consists of six octets: the first two octets include a six-bit decrementing hop count, plus flags; the next two octets contain the egress RBridge nickname; the final two octets contain the ingress RBridge nickname. For multi-destination frames, the "egress RBridge nickname" specifies a distribution tree for the frame, where the (nick)named RBridge is the root of the distribution tree. The ingress RBridge selects which distribution tree the frame should travel along.

Even though RBridges are transparent to Layer 3 devices, and all the links interconnected by RBridges appear to Layer 3 devices to be a single link, RBridges act as link routers in the sense that, in the forwarding of a frame by a transit RBridge, the outer Layer 2 header is replaced at each hop with an appropriate Layer 2 header for the next hop, and the hop count is decreased. Despite these modifications of the outer Layer 2 header and the hop count in the TRILL Header, the original encapsulated frame is preserved, including the original frame's VLAN tag.

Multipathing of multi-destination frames through alternative distribution tree roots and equal-cost multi-path routing (ECMP) of unicast frames are supported. Networks with a more mesh-like structure benefit to a greater extent from the multipathing and optimal paths provided by TRILL than networks with a more tree-like structure.

A host with multiple interfaces running the Internet Protocol requires that each of the interfaces [or the group of interfaces in a team] have a unique address, whereas when using TRILL the multiple-interface host can have a single IP address for all of its interfaces attached to a common broadcast domain — akin to the case of a network service access point address (NSAP) on an end system in CLNP.

From the point of view of TRILL, a link can be any of a wide variety of link technologies, including IEEE 802.3 (Ethernet), PPP (Point to Point Protocol)., [10] or a Pseudo-wire. [11] Ethernet links between RBridges can incorporate IEEE customer or provider 802.1 bridges. In other words, an arbitrary bridged LAN appears to an RBridge as a multi-access link.

It is essential that only one RBridge act as the ingress RBridge for any given native frame and TRILL has an Appointed Forwarder [12] mechanism to assure this. TRILL does allow load splitting of this duty on a link based on VLAN, so that only one RBridge on each link encapsulates and decapsulates native frames for each VLAN.

RBridge ports

RBridge ports can compatibly implement a wide variety of existing and proposed link level and IEEE 802.1 port level protocols including PAUSE (IEEE 802.3 Annex 31B), the Link Layer Discovery Protocol (IEEE 802.1AB), link aggregation (IEEE 802.1AX), MAC security (IEEE 802.1AE), or port based access control (IEEE 802.1X). This is because RBridges are layered above the IEEE 802.1 EISS (Extended Internal Sublayer Service) with the exception that an RBridge port handles spanning tree and VLAN registration PDUs differently.

Open source implementations

Proprietary implementations

Cisco FabricPath is a proprietary implementation of TRILL that utilizes the TRILL control plane (including IS-IS for Layer 2), but a non-interoperable data plane. [15] Brocade Virtual Cluster Switching, uses the TRILL data plane but a proprietary control plane and so is not interoperable with standards conformant TRILL. [16]

VLAN support

The TRILL protocol provides mandatory support for the usual 4K VLANs and can optionally support 24-bit Fine Grain Labels (FGL) in addition to VLANs. [17]

Competitors

During its development, the IEEE 802.1aq standard (Shortest Path Bridging – SPB) was considered the major competitor of TRILL. As one 2011 book noted, "the evaluation of relative merits and difference of the two standards proposals is currently a hotly debated topic in the networking industry." [18] Neither standard has seen significant adoption, in contrast to more recent overlay approaches such as EVPN. [19] [20]

Product support

Related Research Articles

In computer networking, the maximum transmission unit (MTU) is the size of the largest protocol data unit (PDU) that can be communicated in a single network layer transaction. The MTU relates to, but is not identical to the maximum frame size that can be transported on the data link layer, e.g., Ethernet frame.

Intermediate System to Intermediate System is a routing protocol designed to move information efficiently within a computer network, a group of physically connected computers or similar devices. It accomplishes this by determining the best route for data through a packet switching network.

A network switch is networking hardware that connects devices on a computer network by using packet switching to receive and forward data to the destination device.

The Spanning Tree Protocol (STP) is a network protocol that builds a loop-free logical topology for Ethernet networks. The basic function of STP is to prevent bridge loops and the broadcast radiation that results from them. Spanning tree also allows a network design to include backup links providing fault tolerance if an active link fails.

<span class="mw-page-title-main">VLAN</span> Network communications domain that is isolated at the data link layer

A virtual local area network (VLAN) is any broadcast domain that is partitioned and isolated in a computer network at the data link layer. In this context, virtual refers to a physical object recreated and altered by additional logic, within the local area network. Basically, a VLAN behaves like a virtual switch or network link that can share the same physical structure with other VLANs while staying logically separate from them. Between network devices, VLANs work by applying tags to network frames and handling these tags in networking systems –creating the appearance and functionality of network traffic that is physically on a single network but acts as if it were split between separate networks. In this way, VLANs can keep network applications separate despite being connected to the same physical network, and without requiring multiple sets of cabling and networking devices to be deployed.

The data link layer, or layer 2, is the second layer of the seven-layer OSI model of computer networking. This layer is the protocol layer that transfers data between nodes on a network segment across the physical layer. The data link layer provides the functional and procedural means to transfer data between network entities and may also provide the means to detect and possibly correct errors that can occur in the physical layer.

IEEE 802.1Q, often referred to as Dot1q, is the networking standard that supports virtual local area networking (VLANs) on an IEEE 802.3 Ethernet network. The standard defines a system of VLAN tagging for Ethernet frames and the accompanying procedures to be used by bridges and switches in handling such frames. The standard also contains provisions for a quality-of-service prioritization scheme commonly known as IEEE 802.1p and defines the Generic Attribute Registration Protocol.

Cisco Inter-Switch Link (ISL) is a Cisco proprietary link layer protocol that maintains VLAN information in Ethernet frames as traffic flows between switches and routers, or switches and switches. ISL is Cisco's VLAN encapsulation protocol and is supported only on some Cisco equipment over the Fast and Gigabit Ethernet links. It is offered as an alternative to the IEEE 802.1Q standard, a widely used VLAN tagging protocol, although the use of ISL for new sites is deprecated by Cisco.

The Multiple Spanning Tree Protocol (MSTP) and algorithm, provides both simple and full connectivity assigned to any given virtual LAN (VLAN) throughout a bridged local area network. MSTP uses bridge protocol data unit (BPDUs) to exchange information between spanning-tree compatible devices, to prevent loops in each Multiple Spanning Tree instance (MSTI) and in the common and internal spanning tree (CIST), by selecting active and blocked paths. This is done as well as in Spanning Tree Protocol (STP) without the need of manually enabling backup links and getting rid of switching loop danger.

<span class="mw-page-title-main">Network bridge</span> Device that creates a larger computer network from two smaller networks

A network bridge is a computer networking device that creates a single, aggregate network from multiple communication networks or network segments. This function is called network bridging. Bridging is distinct from routing. Routing allows multiple networks to communicate independently and yet remain separate, whereas bridging connects two separate networks as if they were a single network. In the OSI model, bridging is performed in the data link layer. If one or more segments of the bridged network are wireless, the device is known as a wireless bridge.

<span class="mw-page-title-main">Radia Perlman</span> American software designer and network engineer

Radia Joy Perlman is an American computer programmer and network engineer. She is a major figure in assembling the networks and technology to enable what we now know as the internet. She is most famous for her invention of the Spanning Tree Protocol (STP), which is fundamental to the operation of network bridges, while working for Digital Equipment Corporation, thus earning her nickname "Mother of the Internet". Her innovations have made a huge impact on how networks self-organize and move data. She also made large contributions to many other areas of network design and standardization: for example, enabling today's link-state routing protocols, to be more robust, scalable, and easy to manage.

IEEE 802.1ah is an amendment to the IEEE 802.1Q networking standard which adds support for Provider Backbone Bridges. It includes an architecture and a set of protocols for routing over a provider's network, allowing interconnection of multiple provider bridge networks without losing each customer's individually defined VLANs. It was initially created by Nortel before being submitted to the IEEE 802.1 committee for standardization. The final version was approved by the IEEE in June 2008 and has been integrated into IEEE 802.1Q-2011.

In computer networking, an Ethernet frame is a data link layer protocol data unit and uses the underlying Ethernet physical layer transport mechanisms. In other words, a data unit on an Ethernet link transports an Ethernet frame as its payload.

Data center bridging (DCB) is a set of enhancements to the Ethernet local area network communication protocol for use in data center environments, in particular for use with clustering and storage area networks.

IEEE 802.1aq is an amendment to the IEEE 802.1Q networking standard which adds support for Shortest Path Bridging (SPB). This technology is intended to simplify the creation and configuration of Ethernet networks while enabling multipath routing.

IEEE 802.1ad is an amendment to the IEEE 802.1Q-1998 networking standard which adds support for provider bridges. It was incorporated into the base 802.1Q standard in 2011. The technique specified by the standard is known informally as stacked VLANs or QinQ.

A routing bridge or RBridge, also known as a TRILL switch, is a network device that implements the TRILL protocol and should not be confused with BRouters. RBridges are compatible with previous IEEE 802.1 customer bridges as well as IPv4 and IPv6 routers and end nodes. They are invisible to current IP routers and, like routers, RBridges terminate the bridge spanning tree protocol.

Intelligent Resilient Framework (IRF) is a proprietary software virtualization technology originally developed by Huawei 3Com. It can connect and configure multiple network devices through physical ports and then virtualize the devices. This enables the unified management and maintenance of multiple devices. This technology is similar to the Cisco Virtual PortChannel (vpC).

Virtual Extensible LAN (VXLAN) is a network virtualization technology that uses a VLAN-like encapsulation technique to encapsulate OSI layer 2 Ethernet frames within layer 4 UDP datagrams, using 4789 as the default IANA-assigned destination UDP port number, although many implementations that predate the IANA assignment use port 8472. VXLAN attempts to address the scalability problems associated with large cloud computing deployments. VXLAN endpoints, which terminate VXLAN tunnels and may be either virtual or physical switch ports, are known as VXLAN tunnel endpoints (VTEPs).

References

  1. ↑ J. Touch; R. Perlman (May 2009). Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement. Networking Working Group. doi: 10.17487/RFC5556 . RFC 5556.Informational.
  2. ↑ R. Perlman; D. Eastlake III; D. Dutt; S. Gai; A. Ghanwani (July 2011). Routing Bridges (RBridges): Base Protocol Specification. Internet Engineering Task Force (IETF). doi: 10.17487/RFC6325 . ISSN   2070-1721. RFC 6325.Proposed Standard. Updated by RFC  6327, 6439, 7172, 7177, 7179, 7180, 7357, 7455, 7780, 7783, 8139, 8249, 8361 and 8377.
  3. ↑ "All Systems Down" (PDF). cio.com. IDG Communications, Inc. Archived from the original (PDF) on 23 September 2020. Retrieved 9 January 2022.
  4. ↑ "All Systems Down". cio.com. IDG Communications, Inc. Archived from the original on 9 January 2022. Retrieved 9 January 2022.
  5. ↑ "Rbridges: Transparent Routing" (PDF). courses.cs.washington.edu. Radia Perlman, Sun Microsystems Laboratories. Archived from the original (PDF) on 9 January 2022. Retrieved 9 January 2022.
  6. ↑ "Rbridges: Transparent Routing". researchgate.net. Radia Perlman, Sun Microsystems; Donald Eastlake 3rd, Motorola.
  7. ↑ "TRILL Tutorial" (PDF). postel.org. Donald E. Eastlake 3rd, Huawei.
  8. ↑ "IEEE 802.1: 802.1aq - Shortest Path Bridging". ieee802.org. Institute of Electrical and Electronics Engineers.
  9. ↑ D. Eastlake III; T. Senevirathne; A. Ghanwani; D. Dutt; A. Banerjee (May 2014). Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS. Internet Engineering Task Force (IETF). doi: 10.17487/RFC7176 . ISSN   2070-1721. RFC 7176.Proposed Standard. Obsoletes RFC  6326.
  10. ↑ "PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol".
  11. ↑ "Transparent Interconnection of Lots of Links (TRILL) Transport Using Pseudowires".
  12. ↑ "Routing Bridges (RBridges): Appointed Forwarders".
  13. ↑ "GitHub - Gandi/quagga at dev_trill". GitHub. Retrieved 2023-05-10.
  14. ↑ MichaelQQ (2022-08-28), MichaelQQ/Quagga-PE , retrieved 2023-05-10
  15. ↑ "Cisco FabricPath". Data Center Handbook. 2014-03-06. Archived from the original on 2016-03-03. Retrieved 2014-10-14.
  16. ↑ "DON'T LIE ABOUT PROPRIETARY PROTOCOLS". 2011-03-04. Retrieved 2014-10-14.
  17. ↑ D. Eastlake III; P. Agarwal; R. Perlman; D. Dutt (May 2014). Transparent Interconnection of Lots of Links (TRILL): Fine-Grained Labeling. Internet Engineering Task Force (IETF). doi: 10.17487/RFC7172 . ISSN   2070-1721. RFC 7172.Proposed Standard. Updates RFC  6325.
  18. ↑ Borivoje Furht; Armando Escalante (2011). Handbook of Data Intensive Computing. Springer. p. 16. ISBN   978-1-4614-1415-5.
  19. ↑ Hollingsworth, Tom (29 November 2021). "Migrating from FabricPath to EVPN/VxLAN" . Retrieved 9 May 2023.
  20. ↑ Pepelnjak, Ivan (3 May 2022). "What Happened to FabricPath and Its Friends?" . Retrieved 9 May 2023.
  21. ↑ "BDCOM S5800 Series" (PDF). bdcom.cn.
  22. ↑ "BDCOM S9500 Series" (PDF). bdcom.cn.
  23. ↑ DH-S7602
  24. ↑ DH-S7606
  25. ↑ "Q A: Which platforms do support TRILL? | Extreme Portal". extremeportal.force.com.
  26. ↑ "HPE FlexFabric 5700 Switch Series" (PDF). hpe.com.
  27. ↑ "HPE FlexFabric 5940 Switch Series" (PDF). hpe.com.
  28. ↑ "HPE FlexFabric 12900E Switch Series Data sheet" (PDF). hpe.com.
  29. ↑ "Huawei CloudEngine 5800 Series Data Center Switches". e-file.huawei.com.
  30. ↑ "Huawei CloudEngine 6860 Switch Datasheet". e-file.huawei.com.
  31. ↑ "Huawei CloudEngine 8800 Switch Datasheet". e-file.huawei.com.
  32. ↑ "Huawei CloudEngine 12800 Switch Datasheet". e-file.huawei.com.
  33. ↑ "IgniteNet™ MeshLinq™". ignitenet.com.
  34. ↑ "MeshLinq™ Datasheet" (PDF). ignitenet.com.
  35. ↑ "Products & Technology- H3C S6800 Series Data Center Switches- H3C". h3c.com.
  36. ↑ "H3C S6800 Series Data Center Switches" (PDF). downloadcdn.h3c.com.
  37. ↑ "Products & Technology- H3C S6860 Series Data Center Switches- H3C". h3c.com.
  38. ↑ "H3C S6860 Series Data Center Switches" (PDF). downloadcdn.h3c.com.
  39. ↑ "Products & Technology- H3C S10500 Series Switches- H3C". h3c.com.
  40. ↑ "Products & Technology- H3C S10500X Series Next Generation Multiservice Core Switch- H3C". h3c.com.
  41. ↑ "H3C S10500X Series Next Generation Multiservice Core Switch" (PDF). downloadcdn.h3c.com.
  42. ↑ "SwitchesRG-S6220 Switch Series - Ruijie networks". ruijienetworks.com.
  43. ↑ "RG-S6220 Series Data Center Switches Datasheet - Ruijie networks". ruijienetworks.com.
  44. ↑ "RG-S12000 Series Data Center Core Switch Datasheet - Ruijie networks". ruijienetworks.com.
  45. ↑ "YH-S5800 数据中心 TOR 交换机系列". youhuatech.com.
  46. ↑ "YH-S9500 高性能核心交换机系列". youhuatech.com.
  47. ↑ "ZXR10 5960 Series Switch - Ethernet Switch - ZTE Product". zte.com.cn.
  48. ↑ "ZXR10 9900(-S) Series Switch - Ethernet Switch - ZTE Product". zte.com.cn.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.