Re: Weird Nexus AD

2010-10-30 Thread Tim Stevenson
am = adjacency manager. Since NXOS is a modular OS, different processes/services source routes to the URIB, and AM is one of them. OSPF, BGP, other RPs, HSRP, etc also feed their routes to the URIB. AM really only feeds directly connected host prefixes (/32) to the RIB (ie, for each resolved A

Re: Weird Nexus AD

2010-10-29 Thread Colby Glass
system:version 4.2(2a) I've read that am = adjacency module or adjacency manager. The words mean less to me than why I seem to be learning this route from a phantom module/manager/interface with no visible explanation. I can try on c-nsp as well. Thought NANOG might be a better choice. Col

Re: Weird Nexus AD

2010-10-29 Thread christian koch
in x/y, x= preference, y= metric am= adjacency module, *= best unicast route a better place to have asked this would be c-nsp hth -ck On Fri, Oct 29, 2010 at 7:21 PM, Colby Glass wrote: > We're seeing an AD of 2 on some routes on our Nexus 7k. I can't find > anything (Google) to indicate wher