Difference between revisions of "Manual:MPLS/Overview"

From MikroTik Wiki
Jump to navigation Jump to search
(New page: == MPLS Overview == MPLS stands for MultiProtocol Label Switching. It kind of replaces IP routing - packet forwarding decision (outgoing interface and next hop router) is no longer based...)
 
Line 46: Line 46:


To ensure compatibility with other manufacturer equipment ensure that required features match, if uncertain, consult with Mikrotik support. RouterOS LDP implementation has been tested with Cisco LDP.
To ensure compatibility with other manufacturer equipment ensure that required features match, if uncertain, consult with Mikrotik support. RouterOS LDP implementation has been tested with Cisco LDP.
[[Category:Routing]]

Revision as of 08:45, 23 April 2008

MPLS Overview

MPLS stands for MultiProtocol Label Switching. It kind of replaces IP routing - packet forwarding decision (outgoing interface and next hop router) is no longer based on fields in IP header (usually destination address) and routing table, but on labels that are attached to packet. This approach speeds up forwarding process because next hop lookup becomes very simple compared to routing lookup (finding longest matching prefix).

Efficency of forwarding process is the main benefit of MPLS, but it must be taken into account that MPLS forwarding disables processing of network layer (e.g. IP) headers, therefore no network layer based actions like NAT and filtering can be applied to MPLS forwarded packets. Any network layer based actions should be taken on ingress or egress of MPLS cloud, with preferred way being ingress - this way, e.g. traffic that is going to be dropped anyway does not travel through MPLS backbone.

In the simplest form MPLS can be thought of like improved routing - labels are distributed for routes that are active and labelled packet takes the same path it would take if it was not labelled. Router that routes unlabelled packet using some route for which it has received label from next hop, imposes label on packet and send it to next hop - it gets MPLS switched further along its path. Router that receives packet with label it has assigned to some route changes packet label with one received from next hop of particular route and sends packet to next hop. Label switched path ensures delivery of data to the MPLS cloud egress point. Applications of MPLS are based on this basic MPLS concept of label switched paths.

Taking into account complexity, new protocols and applications that MPLS introduces and differences of concepts that MPLS adds to routed/bridged network, it is recommended to have in depth understanding of MPLS concepts before implementing MPLS in production network. Some suggested reading material:

RouterOS MPLS features

RouterOS at the moment supports the following MPLS/VPLS features:

  • MPLS switching with penultimate hop popping support
  • static local label bindings for IPv4
  • static remote label bindings for IPv4
  • Label Distribution Protocol (RFC3036) for IPv4
    • downstream unsolicited label advertisement
    • independent label distribution control
    • liberal label retention
    • targeted session establishment
  • Virtual Private Lan Service
    • VPLS LDP signalling (RFC 4762)
    • VPLS pseudowire fragmentation and reassembly (RFC 4623)
    • VPLS MP-BGP based autodiscovery and signaling (RFC 4761), see BGP based VPLS


MPLS features that RouterOS DOES NOT HAVE yet:

  • IPv6 support
  • LDP features:
    • downstream on demand label advertisement
    • ordered label distribution control
    • conservative label retention
  • MP-BGP based MPLS IP VPN
  • MPLS TE support using RSVP


To ensure compatibility with other manufacturer equipment ensure that required features match, if uncertain, consult with Mikrotik support. RouterOS LDP implementation has been tested with Cisco LDP.