Refer to the exhibit.
Why is R2 unable to ping the loopback interface of R4?
A.
The local preference is too high.
B.
The weight is too low.
C.
The next hop is not reachable from R2.
D.
The route originated from within the same AS.
Why is R2 unable to ping the loopback interface of R4?
Refer to the exhibit.
Why is R2 unable to ping the loopback interface of R4?
The next-hop for the BGP route pointing to R4’s loopback points to the local interface on R4. Since R2 cannot recurse this next-hop to an outgoing interface, it is ignored (this is technically listed as being performed prior to best path according to Cisco’s documentation)
“Why Routers Ignore Paths
– Paths for which the NEXT_HOP is inaccessible”
http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13753-25.html
next-hop-self need to be configured