â– Forward the packet to a particular neighbor as directed by the table entry, for
example in a Martini layer 2 transport case.
NOTE: Forwarding of traffic for labeled IPv6 unicast routes with native IPv6 next-hop
addresses does not work.
Figure 47 on page 210 shows a simple MPLS domain, consisting of multiple LSRs.
The LSRs serving as ingress and egress nodes are also referred to as label edge routers
(LERs). The ingress router is sometimes referred to as the tunnel head end, or the
head-end router. The egress router is sometimes referred to as the tunnel tail end, or
the tail-end router. LSPs are unidirectional, carrying traffic only in the downstream
direction from the ingress node to the egress node.
Figure 47: Simple MPLS Domain
MPLS LSRs
Each LSR, also known as an MPLS node, must have the following:
â– At least one layer 3 routing protocol
â– A label distribution protocol
â– The ability to forward packets based on their labels
The router can use BGP, IS-IS, or OSPF as its layer 3 routing protocol, and BGP, LDP,
or RSVP-TE as its label distribution protocol.
MPLS Label Switching: Push, Look Up, and Pop
MPLS can label packets by using the existing layer 2 header or an encapsulation
header that carries the MPLS label. During LSP negotiation, the LSRs in an MPLS
domain agree on a labeling method. Labels have only local meaning; that is, meaning
for two LSR peers. Each pair of LSRs—consisting of a label originator and a label
acceptor—must use a label distribution protocol to agree on the label-to-FEC binding.
Because of the local label assignment, packet labels typically change at each segment
in the LSP path, as shown in Figure 48 on page 211. The ingress node, LSR 1, receives
210 â– MPLS Label Switching and Packet Forwarding
JUNOSe 11.1.x BGP and MPLS Configuration Guide
To Next Page
Loading...
Need help?
General
