Monday, April 9, 2012
MPLS Applications
- MPLS change network design
- by eliminating the need for an Overlay (full mesh of routers).
- Performance is improved
- because packets are switched instead of routed.
- QoS can be implemented end to end
- by having an PE router classify packets & map a value to the Experimental (EXP) field of the MPLS label stack.
- Traffic Engineering is made possible through label stacking & traffic-engineered tunnels.
MPLS OPERATION
- Unlabeled packet enter into the service provider network via PE router.
- PE router add label impose a label to the unlabeled packet & then forward to the P router(also known as LSR) along the Label Switch Path(LSP) in the core network of service provider.
- In the core network of service provider each P routers forward the packet by swapping the labels along the LSR learned by protocol LDP.
- At other end when leaving service provider network PE router (also known as Edge-LSR) pops the label by mechanism called Penultimate Hop Popping.
- Penultimate meaning is "next to last"
- last hop in the service provider network must
- look up MPLS label
- POP MPLS label
- Look for IPv4 destination
- PHP avoids extra look up for MPLS label on last hop
- For this implict NULL label was advertised
MPLS Architecture
- Labels are bound to routes in the routing table
- MPLS architecture components:
- Control plane
- Forwarding plane
- CONTROL:
- Responsible for
- binding a label to network routes
- for this we need routing table
- to get routing table we need a routing protocol
- and distribute those bindings among other MPLS enabled routers
- for this 2 protocols are used
- TDP
- LDP
- Tag Distribution Protocol(TDP):
- Cisco proprietary protocol
- used to bind tags to network routes in the routing table.
- FORWARDING:
- The routing table is built in the control plane & cached in forwarding plane.
- Forward Information Base is built by CEF.
- FIB is a cached version of the ip routing table that eliminates the need for a lookup of routing table.
- Router compares the packet's destination ip address to the CEF FIB, ignore the ip routing table.
- CEF optimizes the organization of FIB, so that router easily find the correct FIB entry,
- resulting in a smaller forwarding delay & high volume of packets per second through a router.
- For each packet, the router finds the matching FIB entry,
- then finds the adjacency table entry referenced by the matching FIB entry,
- and forward the packet
Subscribe to:
Posts (Atom)