In an MPLS L3VPN network with route reflectors, what is the default behavior regarding the BGP next-hop attribute for reflected VPNv4 routes?
Route reflectors preserve the next-hop attribute.
Why this answer
In an MPLS L3VPN network with route reflectors, the default behavior for VPNv4 routes is that the route reflector does not modify the BGP next-hop attribute. This is because the next-hop should remain the address of the originating PE router to ensure proper MPLS label switching and reachability. Changing the next-hop would break the MPLS forwarding path, as the P routers rely on the IGP to reach the PE's loopback, not the route reflector's.
Exam trap
Cisco often tests the misconception that route reflectors behave like route servers or that they must update the next-hop to themselves to ensure reachability, but in MPLS L3VPN, the next-hop must remain unchanged to preserve the MPLS forwarding path.
How to eliminate wrong answers
Option A is wrong because setting the next-hop to 0.0.0.0 would invalidate the route, as it is not a reachable address and would cause traffic to be dropped; this is not a default behavior for route reflectors. Option B is wrong because removing the next-hop attribute would make the route unusable for forwarding, as BGP requires a valid next-hop for recursive route resolution. Option C is wrong because setting the next-hop to the route reflector's loopback would break MPLS L3VPN functionality, as the P routers would attempt to reach the route reflector instead of the originating PE, disrupting label-switched path (LSP) establishment; route reflectors are not required to be in the MPLS forwarding path.