I'm not sure why is that but apparently Cisco sets it by this way on purpose:
Nexus#show run all | i "ip adjacency" ip adjacency route distance 250
Meaning that all routes installed by Adjacency Manager have AD set to 250. In my opinion this could be very dangerous because if by any chance there is same /32 route installed by any routing protocol (e.g. OSPF or BGP) it would have lower AD and would be preferred over directly attached route installed by Adjacency Manager. Actually I have seen this on one of our Nexus switches where vPC keepalive peer link was broken because of this.
You can set AD of routes installed by Adjacency Manager to lower value by command:
ip adjacency route distance <value>
I'm not sure but I would say that older NX-OS versions had AD value for Adjacency Manager routes set to 2. Not sure why Cisco changed it to 250 in recent NX-OS versions.
I know im 2 years late to the party but im running into this very issue. Whats happening is im trying to force path control using host routes, but OSPF is propagating the host route and overriding the AM host route in neighboring Nexus Switches because OSPF has a lower AD (110) than the AM (250). This makes zero sense to me as to why a directly connected AM route learned from an ARP would be less attractive than one learned from literally ANY routing protocol. Just thought Id share my plight and say I found this thread very helpful.
Do you recommend setting the AD of the AM learned routes to 2? Any adverse affects from this? Thanks.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...