This reports which neighbor-discovery mechanism, such as ARP, ND, or static configuration, was responsible for learning this specific adjacency, when all the information needed to build its frame header is available. Knowing the source mechanism tells an admin exactly which underlying protocol to investigate if this particular adjacency looks wrong or stale; an ARP-sourced adjacency issue points to Ethernet/ARP table problems, while an ND-sourced one points to IPv6 neighbor discovery instead. An adjacency reporting its source as ARP would lead an admin to check the router's ARP cache and the neighbor's MAC address directly, rather than looking at IPv6 neighbor discovery state for that same troubleshooting session.