A community-college host cannot reach a shared service in another VN even though underlay ping between locators works. Which overlay troubleshooting focus is most appropriate?
Select an answer to reveal the explanation.
Short Explanation
If the roads between switches are fine but the destination still looks unknown, your phone book entry is probably missing. That phone book is LISP map-cache / map resolution for the EID. Underlay ping only proves locator reachability—it does not guarantee the overlay knows where the shared service lives.
Full Explanation
SD-Access overlay forwarding depends on LISP mapping between endpoint identifiers and routing locators. When underlay connectivity between locators is healthy yet inter-VN or shared-service reachability fails, operators should examine map-cache entries, map-requests/replies, and related resolution failures. Bridging VNs at L2 or rebuilding the underlay first often misdiagnoses an overlay mapping problem.