Blueprint topics covered in this chapter:
This chapter covers the following subtopics from the Cisco CCIE Routing and Switching written exam blueprint. Refer to the full blueprint in Table I-1 in the Introduction for more details on the topics covered in each chapter and their context within the blueprint.
- Label Switching Router (LSR)
- Label Switched Path (LSP)
- Route Descriptor
- Label Format
- Label Imposition/Disposition
- Label Distribution
Multiprotocol Label Switching (MPLS) remains a vitally important part of many service provider (SP) networks. MPLS is still growing in popularity in enterprise networks as well, particularly in larger enterprise internetworks. This chapter introduces the core concepts with MPLS, particularly its use for unicast IP forwarding and for MPLS VPNs.
"Do I Know This Already?" Quiz
Table 19-1 outlines the major headings in this chapter and the corresponding "Do I Know This Already?" quiz questions.
Table 19-1. "Do I Know This Already?" Foundation Topics Section-to-Question Mapping
Foundation Topics Section
Questions Covered in This Section
MPLS Unicast IP Forwarding
Other MPLS Applications
In order to best use this pre-chapter assessment, remember to score yourself strictly. You can find the answers in Appendix A, "Answers to the 'Do I Know This Already?' Quizzes."
Imagine a frame-based MPLS network configured for simple unicast IP forwarding, with four routers, R1, R2, R3, and R4. The routers connect in a mesh of links so that they are all directly connected to the other routers. R1 uses LDP to advertise prefix 220.127.116.11/24, label 30, to the other three routers. What must be true in order for R2 to advertise a label for 18.104.22.168/24 to R1 using LDP?
- R2 must learn an IGP route to 22.214.171.124/24.
- R2 will not advertise a label to R1 due to split horizon rules.
- R2 can advertise a label back to R1 before learning an IGP route to 126.96.36.199/24.
- R2 must learn a route to 188.8.131.52/24 using MP-BGP before advertising a label.
In a frame-based MPLS network configured for unicast IP forwarding, LSR R1 receives a labeled packet, with a label value of 55. Which of the following could be true?
- R1 makes its forwarding decision by comparing the packet to the IPv4 prefixes found in the FIB.
- R1 makes its forwarding decision by comparing the packet to the IPv4 prefixes found in the LFIB.
- R1 makes its forwarding decision by comparing the packet to the MPLS labels found in the FIB.
- R1 makes its forwarding decision by comparing the packet to the MPLS labels found in the LFIB.
R1, R2, and R3 are all MPLS LSRs that use LDP and connect to the same LAN. None of the three LSRs advertise a transport IP address. Which of the following could be true regarding LDP operation?
- The LSRs discover the other two routers using LDP Hellos sent to IP address 184.108.40.206.
- Each pair of LSRs forms a TCP connection before advertising MPLS labels.
- The three LSRs must use their LAN interface IP addresses for any LDP TCP connections.
- The LDP Hellos use port 646, with the TCP connections using port 711.
In a frame-based MPLS network configured for simple unicast IP forwarding, MPLS TTL propagation has been enabled for all traffic. Which of the following could be true?
- A traceroute command issued from outside the MPLS network will list IP addresses of the LSRs inside the MPLS network.
- A traceroute command issued from outside the MPLS network will not list IP addresses of the LSRs inside the MPLS network.
- Any IP packet with a TCP header, entering the MPLS network from outside the MPLS network, would not have its IP TTL field copied into the MPLS TTL field.
- An ICMP echo sent into the MPLS network from outside the MPLS network would have its IP TTL field copied into the MPLS TTL field.
Which of the following is an extension to the BGP NLRI field?
- Route Distinguisher
- Route Target
- BGP Extended Community
Which of the following controls into which VRFs a PE adds routes when receiving an IBGP update from another PE?
- Route Distinguisher
- Route Target
- IGP metric
- AS Path length
An ingress PE router in an internetwork configured for MPLS VPN receives an unlabeled packet. Which of the following is true?
- It injects a single MPLS header.
- It injects at least two MPLS headers.
- It injects (at least) a VPN label, which is used by any intermediate P routers.
- It uses both the FIB and LFIB to find all the required labels to inject before the IP header.
An internetwork configured to support MPLS VPNs uses PHP. An ingress PE receives an unlabeled packet and then injects the appropriate label(s) to the packet before sending the packet into the MPLS network. Which of the following is/are true about this packet?
- The number of MPLS labels in the packet will only change when the packet reaches the egress PE router, which extracts the entire MPLS header.
- The number of MPLS labels in the packet will change before the packet reaches the egress PE.
- The PHP feature will cause the egress PE to act differently than it would without PHP enabled.
- None of the other answers is correct.
Which of the following answers help define which packets are in the same MPLS FEC when using MPLS VPNs?
- IPv4 prefix
- ToS byte
- The MPLS VRF
- The TE tunnel