In: Root » Computers and technology » Networks » Multiprotocol Label Switching and Asynchronous Transfer Mode Architecture
Asynchronous Transfer Mode is a connection-oriented protocol that the ITU-T developed. It is connection-oriented because virtual circuits are signaled that carry the Asynchronous Transfer Mode traffic. The Asynchronous Transfer Mode traffic consists of fixedsized cells of 53 bytes. Of those 53 bytes, 5 are the cell header and 48 are the cell data. The success of Asynchronous Transfer Mode was predominantly in the WAN network. Many vendors built Asynchronous Transfer Mode switches that could set up virtual circuits in the WAN network. The advantages of Asynchronous Transfer Mode are the following: ■ A fixed packet size, resulting in a transmission with low jitter
The success of Asynchronous Transfer Mode was limited to its use in the WAN network. As IP became the de facto standard networking protocol that almost everyone used, much effort was spent on getting IP traffic across the Asynchronous Transfer Mode core network. Several schemes were devised:
■ Encapsulation according to RFC 1483
RFC 1483 (made obsolete by RFC 2684) specified how to encapsulate multiple routed and bridged protocols over Asynchronous Transfer Mode adaptation layer (AAL) 5. LANE specified how to carry Ethernet frames across the Asynchronous Transfer Mode cloud. MPOA provided a tight integration of IP over Asynchronous Transfer Mode, but it was a complex solution. None of these solutions was perfect in providing a better fit between IP and Asynchronous Transfer Mode. One of the driving reasons for Multiprotocol Label Switching was just that: a better integration between IP and Asynchronous Transfer Mode. With Multiprotocol Label Switching, the Asynchronous Transfer Mode switches would need to run an IP routing protocol and a label distribution protocol to exchange IP prefixes and labels between themselves and to the routers. The result would be that the overlay model of IP over Asynchronous Transfer Mode would no longer be needed. With Multiprotocol Label Switching, it became a peer model. The GFC field provides local functions for the Asynchronous Transfer Mode cell. Local means that it is not end to end, and the intermediate switches override the field. Local functions might mean flow control and identification of multiple stations on a single Asynchronous Transfer Mode interface. The VPI and VCI fields are used together and identify the next destination of the Asynchronous Transfer Mode cell. The three bits of the PT field are defined as follows:
■ The first bit indicates whether the cell contains user data or control data.
Asynchronous Transfer Mode can have statically defined PVCs, or private network-network interface (PNNI) can assign the virtual circuits dynamically. PNNI is a hierarchical link-state routing protocol that lays out the virtual circuits throughout the Asynchronous Transfer Mode network. For the cells to be interpreted correctly and used by upper layer protocols, ITU-T specified a layer between the Asynchronous Transfer Mode layer and the upper layer protocols. This layer is called AAL, and it has five categories. AAL1 is connection-oriented and used for delay-sensitive services and circuit emulation. AAL2 is also connection-oriented, but it is used for variable rate services. AAL3/4 is connectionless and used mainly for the older SMDS. AAL5 can be connection-oriented or connectionless and is used for varying bit rate demands. It is used mostly for IP and LANE. To carry IP traffic across the Asynchronous Transfer Mode cloud, the routers on the edge of the Asynchronous Transfer Mode WAN cloud are interconnected across Asynchronous Transfer Mode PVCs. To connect the routers in the most efficient way, you need to connect them directly to each other across PVCs. This is needed so that the IP traffic does not cross the Asynchronous Transfer Mode cloud twice. Therefore, the routers need to be interconnected in a fully meshed way. This is called the overlay model because all the routers have an Interior Gateway Protocol (IGP) adjacency (a peering) with each other across the Asynchronous Transfer Mode cloud. For the traffic to be forwarded correctly through the Asynchronous Transfer Mode Label Switch Routers, the traffic must be Multiprotocol Label Switching encapsulated, and the Multiprotocol Label Switching label value must be mapped to VPI/VCI values. That is because the Asynchronous Transfer Mode switches are still switching Asynchronous Transfer Mode cells on virtual circuits. Because the Asynchronous Transfer Mode switches need to be able to map the Multiprotocol Label Switching label value to a VC, they must first learn those label values. Hence, the Asynchronous Transfer Mode switches must run a label distribution protocol. An Asynchronous Transfer Mode Label Switch Router consists of the following:
■ A routing protocol in the control plane
The Cisco Asynchronous Transfer Mode switches support Open Shortest Path First (OSPF) as the routing protocol and Label Distribution Protocol as the label distribution protocol. The Cisco Asynchronous Transfer Mode Label Switch Routers distribute the routes in OSPF and the label bindings associated with the routes with Label Distribution Protocol. The incoming and outgoing labels are mapped to incoming and outgoing VPI/VCI pairs. The result is that in the data plane, the Asynchronous Transfer Mode switch just needs to switch cells from the incoming virtual circuit to the outgoing virtual circuit, just like regular Asynchronous Transfer Mode forwarding. The Asynchronous Transfer Mode switch never forwards IP packets. If this is needed, the Asynchronous Transfer Mode switch would need to reassemble all incoming Asynchronous Transfer Mode cells into frames first. Every Asynchronous Transfer Mode switch along the path would need to do this. This is undesirable for performance reasons. Label EncodingAsynchronous Transfer Mode switches that are running Multiprotocol Label Switching are still switching Asynchronous Transfer Mode cells. As such, they cannot forward labeled frames. Because the Multiprotocol Label Switching labels are mapped to VCs in the Asynchronous Transfer Mode cloud, the Multiprotocol Label Switching label value is mapped to the VPI/VCI pair. If the labeled packet has a label stack with more than one label, only the value of the top label is mapped to the VPI/VCI fields. When the edge Asynchronous Transfer Mode Label Switch Router receives a frame, the frame is chopped up into cells. Only the top label value is encoded as a VPI/VCI value. The rest of the labels in the label stack are not needed to forward the cells. Nevertheless, the complete label stack is present in the frame (now chopped up). These labels will be needed again when the Asynchronous Transfer Mode cells are reassembled into a frame and the frame needs further Multiprotocol Label Switching forwarding outside the Asynchronous Transfer Mode network. The label value of the top label is encoded in the VPI/VCI field and changes at every Asynchronous Transfer Mode Label Switch Router, and the label value of the top label in the label stack is set to 0. The label is kept, however, for the three other fields: TTL, EXP, and End-of-Stack bit. The TTL sets the outgoing TTL when the packet is reassembled on the egress edge Asynchronous Transfer Mode Label Switch Router. The EXP bits set the QoS of the packet on the egress edge Asynchronous Transfer Mode Label Switch Router. Even if the label stack consists of only one label, it is still carried across the Asynchronous Transfer Mode cloud in the first cell. This enables the egress Asynchronous Transfer Mode Label Switch Router to figure out whether the packet actually had a label stack or not. Because the VCI value is 16 bits, there can be 216 or 65,536 labels. Considering that the number of VCs is limited on the Asynchronous Transfer Mode switch, this value alone should be enough for all the labels needed on one interface. The VPI value is 12 bits, so there can be 212 or 4096 labels there. |
legal disclaimer
Our website is not responsible for the information contained by this article. Web-articles is a free articles resource.
Suggestion: If you need fresh, daily updated content for your website, feel free to use our service. Click here for more information.
related articles
When the Multiprotocol Label Switching Label Distribution Protocol-IGP synchronization is active for an interface, the IGP announces that link with maximum metric until the synchronization is achieved, or until the Label Distribution Protocol session is running across that interface. The maximum link metric for OSPF is 65536 (hex 0xFFFF). No path through the interface where Label Distribution Protocol is down is used unless it is the only path. (No other paths have a better metric.) After the Label Distribution Protocol ...
The IGP and Label Distribution Protocol on the Asynchronous Transfer Mode Label Switch Routers cannot run directly over the Asynchronous Transfer Mode interface and establish a neighborship. A control VC is needed for the IGP and Label Distribution Protocol to run on between two adjacent Asynchronous Transfer Mode Label Switch Routers. When the IGP adjacency is built, the IGP can exchange IP prefixes which are put in the routing table. After Label Distribution Protocol forms a session across the control VC, it can exchange ...
3. Cisco Express Forwarding
Cisco Express Forwarding (CEF) is a packet forwarding or switching method that Cisco IOS uses. It is the latest IP switching method developed in Cisco IOS, and it is the default packet forwarding method being used now. CEF is needed in Multiprotocol Label Switching networks, which is why this article devotes an article to it. This article explains the basics of CEF so that you can understand its role in Multiprotocol Label Switching networks. Overview of Cisco IOS Switching Methods The b...
4. Load Balancing in CEF
CEF allows for load balancing or load sharing of traffic among multiple outgoing links. CEF needs multiple outgoing links as next hops in the routing table to perform load balancing. The command maximum-paths specifies how many paths or next hops are allowed per prefix in the routing table for the specific routing protocol. For instance, if you configure maximum-path 2 under the routing protocol Open Shortest Path First (OSPF), only two OSPF paths per prefix are allowed in the routing...
5. Multiprotocol Label Switching Virtual Private Network
Multiprotocol Label Switching Virtual Private Network, or Multiprotocol Label Switching Virtual Private Networks, is the most popular and widespread implementation of Multiprotocol Label Switching technology. Its popularity has grown exponentially since it was invented, and it is still growing steadily. Although most service providers have implemented it as a replacement for the Frame Relay and Asynchronous Transfer Mode services that were popular before it, Multiprotocol Label Switching Virtual Private Network is now see...
6. Virtual Private LAN Service
Virtual Private LAN Service (VPLS) emulates a LAN segment across the Multiprotocol Label Switching backbone across pseudowires or virtual circuits. VPLS creates one or more LANs for each customer who is using the service from the service provider. Each LAN, of course, is completely separate from the other emulated LAN segments—hence the “P” for “Private” in VPLS. When the customer with different Ethernet sites connects to an Multiprotocol Label Switching backbone where VPLS is deployed, it a...
7. Router Alert Option and Router Alert Label
IP packets can have a Router Alert option appended to the IP header. This option is an IP option indicating that the router should inspect the packet further when forwarding the packet, even though the packet is not directly addressed to that router. The transit router for the packet should not just forward the packet by doing an IP lookup, but the router should inspect it further before forwarding it. What this inspection means is not defined and is up to the software implementation on the router. The Router Alert ...
8. FCS Retention and OAM Protocols
Currently, in AToM networks, the frame check sequence (FCS) of Ethernet, Frame Relay, High- Level Data Link Control (HDLC), and PPP Layer 2 frames is removed before AToM sends the frames across the pseudowire. At the remote end of the pseudowire, the egress PE inserts the FCS by calculating it over the received Layer 2 frame. This behavior might lead to problems if intermediate Label Switch Routers introduce a problem whereby they change the payload of the Multiprotocol Label Switching packet. This problem can go undet...
9. Deploying a network security policy
Deploying a network security policy is a significant and serious undertaking. Making good decisions in this matter will save a great deal of money and prevent many future security issues on your network, while making incorrect or hasty decisions will lay the foundation for an insecure network infrastructure. Creating a network security policy will affect your organization in a number of ways, including (but not limited to): - Financial A new network security policy may require you to purch...
10. Cost of network infrastructure failure
Information Criticality It’s important to begin by looking at information criticality.You’ll find that this is a common theme throughout most security texts, because there’s no point in securing something no one wants. Information criticality is an assessment of what your network holds and how important that is in the overall scheme of things. Not all data is created equal, and if your company manufactures steel troughs for horse feed, there’s a good chance your network data is no...