A network engineer is configuring MPLS L3VPN on a Cisco IOS-XE PE router. The engineer creates a VRF named CUSTOMER_A with route-target import and export 100:1. After configuring the VRF on the interface connected to the CE router, the CE router can ping the PE's VRF interface IP, but cannot reach any remote VPNv4 routes. The BGP session between PE and route reflector is up. What is the most likely cause?
Trap 1: The route-target import/export values are mismatched with the route…
Incorrect because the route-target values are only relevant for route distribution among PEs; the route reflector simply reflects VPNv4 routes regardless of RT.
Trap 2: The CE router is not configured with a default route pointing to…
Incorrect because the CE can ping the PE's VRF interface, indicating Layer 3 connectivity; the issue is with remote route reachability.
Trap 3: The PE router needs the mpls ip command on the interface facing the…
Incorrect because MPLS is not required on the CE-facing interface; it is needed on core-facing interfaces.
- A
The route-target import/export values are mismatched with the route reflector's configuration.
Why wrong: Incorrect because the route-target values are only relevant for route distribution among PEs; the route reflector simply reflects VPNv4 routes regardless of RT.
- B
The VRF is not activated under BGP using the address-family ipv4 vrf CUSTOMER_A command.
Correct because without this command, the PE does not redistribute VRF routes into VPNv4 or import VPNv4 routes into the VRF.
- C
The CE router is not configured with a default route pointing to the PE.
Why wrong: Incorrect because the CE can ping the PE's VRF interface, indicating Layer 3 connectivity; the issue is with remote route reachability.
- D
The PE router needs the mpls ip command on the interface facing the CE router.
Why wrong: Incorrect because MPLS is not required on the CE-facing interface; it is needed on core-facing interfaces.