Provider Backbone Bridge Traffic Engineering

Last updated

Provider Backbone Bridge Traffic Engineering (PBB-TE) is a computer networking technology specified in IEEE 802.1Qay, an amendment to the IEEE 802.1Q standard. [1] PBB-TE adapts Ethernet to carrier class transport networks. It is based on the layered VLAN tags and MAC-in-MAC encapsulation defined in IEEE 802.1ah (Provider Backbone Bridges (PBB)), but it differs from PBB in eliminating flooding, dynamically created forwarding tables, and spanning tree protocols. Compared to PBB and its predecessors, PBB-TE behaves more predictably and its behavior can be more easily controlled by the network operator, at the expense of requiring up-front connection configuration at each bridge along a forwarding path. PBB-TE Operations, Administration, and Management (OAM) is usually based on IEEE 802.1ag. It was initially based on Nortel's Provider Backbone Transport (PBT).

Contents

PBB-TE's connection-oriented features and behaviors, as well as its OAM approach, are inspired by SDH/SONET. PBB-TE can also provide path protection levels similar to the UPSR (Unidirectional Path Switched Ring) protection in SDH/SONET networks.

Principle of operation

The IEEE 802.1Qay PBB-TE standard extends the functionality of IEEE 802.1ah Provider Backbone Bridges, adding a connection-oriented mode using point-to-point trunks that deliver resiliency and configurable performance levels. [2]

A service is identified by an I-SID (Backbone Service Instance Identifier) and each service is associated with a PBB-TE trunk. Each PBB-TE trunk is identified by a triplet of B-SA, B-DA and B-VID. The B-SA and B-DA identify the source and destination bridges, respectively, that are the endpoints of the trunk. The B-VID is a backbone VLAN identifier that is used to distinguish different trunks to the same destination. The management system configures the PBB-TE trunks on all the edge and core bridges by creating static forwarding database entries; the management system is responsible for ensuring that there are no forwarding loops.

The backbone edge bridges map frames to and from an I-SID and perform the MAC header encapsulation and decapsulation functions. The core bridges act as transit nodes. The packets are forwarded based on outer VLAN ID (B-VID) and Destination MAC address (B-DA).

Forwarding is based on the static forwarding database (FDB) entries; dynamic MAC learning is not used. Any incoming broadcast or multicast frames are either dropped or encapsulated as unicast within the trunk. All Destination Lookup Failure packets are dropped rather than flooded. By eliminating any broadcasting or flooding, and by using only the loop-free forwarding paths configured by management, there is no longer any need to use a spanning tree protocol.

Path protection is provided by configuring one work and one protect B-VID for each backbone service instance. In case of work path failure (as indicated by loss of 802.1ag continuity check messages, CCMs) the source bridge swaps the B-VID value to redirect the traffic onto the preconfigured protection path within 50 ms.

PBB-TE equipment leverages economies of scale inherent in Ethernet, promising solutions that are 30% to 40% cheaper than T-MPLS networks with identical features and capabilities, [3] giving PBB-TE a better overall return on investment. [4]

Key features

History

Provider Backbone Bridge Traffic Engineering was originally developed in 2006 as a Nortel specific protocol named Provider Backbone Transport (PBT). The company championed the technology and brought it to the IEEE 802.1 committee where it was renamed to PBB-TE and a working group, P802.1Qay, was chartered on May 7, 2007. [5] 802.1Qay was in sponsor ballot from January 2009 [6] to April 2009. [7] It was ratified by the IEEE Standards Association on June 18, 2009. [1] It was published in August 2009. [8]

See also

Related Research Articles

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.

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.

<span class="mw-page-title-main">Metro Ethernet</span> Metropolitan area network based on Ethernet standards

A metropolitan-area Ethernet, Ethernet MAN, carrier Ethernet or metro Ethernet network is a metropolitan area network (MAN) that is based on Ethernet standards. It is commonly used to connect subscribers to a larger service network or for internet access. Businesses can also use metropolitan-area Ethernet to connect their own offices to each other.

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.

IEEE 802.1ag is an amendment to the IEEE 802.1Q networking standard which introduces Connectivity Fault Management (CFM). This defines protocols and practices for the operations, administration, and maintenance (OAM) of paths through 802.1 bridges and local area networks (LANs). The final version was approved by the IEEE in 2007.

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.

Connection-oriented Ethernet refers to the transformation of Ethernet, a connectionless communication system by design, into a connection-oriented system. The aim of connection-oriented Ethernet is to create a networking technology that combines the flexibility and cost-efficiency of Ethernet with the reliability of connection-oriented protocols. Connection-oriented Ethernet is used in commercial carrier grade networks.

<span class="mw-page-title-main">Metro Ethernet Routing Switch 8600</span>

Metro Ethernet Routing Switch 8600 or MERS 8600 is a modular chassis router and/or switch manufactured by Nortel now acquired by Ciena. The MERS 8600 supports the Provider Backbone Bridges (PBB), Provider Backbone Transport (PBT) technologies and carrier class Operations Administration & Maintenance (OAM) tools.

Hierarchical VLAN (HVLAN) is a proposed Ethernet standard that extends the use of enterprise Ethernet VLAN (802.1Q) to carrier networks. A number of developments have emerged in recent years to help bring Ethernet, a flexible and cost-efficient packet transport technology, to carrier networks. These developments include Q-in-Q (802.1ad), PBB (802.1ah), PBT, and PBB-TE, which bring a set of features to traditional Ethernet to make it “carrier-grade”, adding to it high-availability, OA&M, and more.

Carrier Ethernet is a marketing term for extensions to Ethernet for communications service providers that utilize Ethernet technology in their networks.

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.

TRILL is a networking protocol for optimizing bandwidth and resilience in Ethernet networks, 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. 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.

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).

Time-Sensitive Networking (TSN) is a set of standards under development by the Time-Sensitive Networking task group of the IEEE 802.1 working group. The TSN task group was formed in November 2012 by renaming the existing Audio Video Bridging Task Group and continuing its work. The name changed as a result of the extension of the working area of the standardization group. The standards define mechanisms for the time-sensitive transmission of data over deterministic Ethernet networks.

<span class="mw-page-title-main">Broadcast, unknown-unicast and multicast traffic</span> Computer networking concept

Broadcast, unknown-unicast and multicast traffic is network traffic transmitted using one of three methods of sending data link layer network traffic to a destination of which the sender does not know the network address. This is achieved by sending the network traffic to multiple destinations on an Ethernet network. As a concept related to computer networking, it includes three types of Ethernet modes: broadcast, unicast and multicast Ethernet. BUM traffic refers to that kind of network traffic that will be forwarded to multiple destinations or that cannot be addressed to the intended destination only.

<span class="mw-page-title-main">Provider-provisioned VPN</span>

Provider-provisioned VPN (PPVPN) are Virtual Private Network implemented by the connectivity service providers or large enterprises on networks they operate by their own. They can be opposed to "customer-provisioned VPN" where the VPN is implemented by the customer who acquire the connectivity service on top of the technical specificities of the provider.

References

  1. 1 2 "IEEE Ratifies Computer Society-Sponsored 802.1Qay". June 23, 2009. Archived from the original on October 13, 2011. Retrieved August 6, 2011.
  2. ↑ EANTC. "Carrier Ethernet Services - The Future" (PDF). EANTC. Retrieved 29 May 2011.
  3. ↑ Cummings, Joanne (2007-06-18). "The T-MPLS vs. PBT debate".
  4. ↑ "Traffic engineering for Ethernet: PBT vs. T-MPLS". www.lightwaveonline.com.
  5. ↑ Gubbins, Ed (2008-06-11). "Will PBT go away?". Telephony Online. Retrieved 2008-06-13.
  6. ↑ "IEEE802.1Qay Project Status" (PDF).
  7. ↑ "IEEE-SA - News, Press Releases & Updates". IEEE . Archived from the original on June 13, 2009.
  8. ↑ "Virtual Bridged Local Area Networks Amendment 10: Provider Backbone Bridge Traffic Engineering" (PDF). IEEE Standard 802.1Qay-2009. August 2009. Archived from the original (PDF) on July 6, 2010. Retrieved August 6, 2011.
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.