350-501 · Question #630
An ISP that provides private network services across the country has recently migrated their infrastructure to support MPLS technology. A network engineer configured mpls ip on all routers and impleme
The correct answer is D. Implement mpls Idp autoconfig on all routers in the segment.. The ISP wants to ensure MPLS LDP label exchange occurs only on interfaces that are part of the OSPF IGP instance and are MPLS-enabled.
Question
An ISP that provides private network services across the country has recently migrated their infrastructure to support MPLS technology. A network engineer configured mpls ip on all routers and implemented the OSPF routing protocol with TE extensions in the backbone area. The ISP wants to ensure that label exchange is performed only on MPLS-enabled interfaces that are associated with the IGP instance. Which action must the engineer take to accomplish the goal?
Options
- AEnable Cisco Express Forwarding on all routers in the backbone area.
- BImplement mpls Idp sync on all routers in the segment.
- CUpdate the routers in the segment to use RSVP-TE for label distribution.
- DImplement mpls Idp autoconfig on all routers in the segment.
How the community answered
(31 responses)- A16% (5)
- B3% (1)
- C10% (3)
- D71% (22)
Why each option
The ISP wants to ensure MPLS LDP label exchange occurs only on interfaces that are part of the OSPF IGP instance and are MPLS-enabled.
Cisco Express Forwarding (CEF) is a prerequisite for MPLS functionality but does not control which interfaces participate in LDP label exchange.
The `mpls ldp sync` command synchronizes LDP session establishment with IGP convergence to prevent blackholing, not to control which interfaces LDP is enabled on.
RSVP-TE is a label distribution protocol used primarily for MPLS Traffic Engineering, not for automatically enabling LDP on IGP-associated interfaces.
The `mpls ldp autoconfig` command automatically enables LDP on interfaces that are participating in an IGP routing process, such as OSPF, and are also configured for MPLS IP forwarding. This directly achieves the goal of associating LDP label exchange with the active IGP instance on an interface, ensuring labels are distributed only where IGP routes are learned and MPLS is intended to run.
Concept tested: MPLS LDP interface auto-configuration
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_mpls/command/irm-cr-xe-3s-16-9-x/irm-cr-xe-3s-16-9-x-chapter_01.html#wp4150821950
Topics
Community Discussion
No community discussion yet for this question.