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 ARP entry). These entries are not shown in 
sh ip route by default (unless you're running very old code) - I 
assume you are using sh ip route am to see these? If so, completely expected.


We can take the discussion to cisco-nsp or offline if you need more 
information.


Hope that helps,
Tim


At 09:36 PM 10/29/2010, Colby Glass uttered:


  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.

Colby

On Sat, Oct 30, 2010 at 12:04 AM, christian koch  wrote:

> 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 where this value is coming from. Also unable
>> to find out what "am" mean (adjacency module?). Does anyone have an
>> explanation for this one?
>>
>> *  via 192.168.21.49, Vlan13, [2/0], 00:44:52, am*
>>
>> Thanks
>>
>> --
>> Colby Glass
>> Network Engineer
>> http://blog.alwaysthenetwork.com
>>
>
>


--
Colby Glass
Network Engineer
http://blog.alwaysthenetwork.com





Tim Stevenson, tstev...@cisco.com
Routing & Switching CCIE #5561
Distinguished Technical Marketing Engineer, Cisco Nexus 7000
Cisco - http://www.cisco.com
IP Phone: 408-526-6759

The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.

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.

Colby

On Sat, Oct 30, 2010 at 12:04 AM, christian koch  wrote:

> 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 where this value is coming from. Also unable
>> to find out what "am" mean (adjacency module?). Does anyone have an
>> explanation for this one?
>>
>> *  via 192.168.21.49, Vlan13, [2/0], 00:44:52, am*
>>
>> Thanks
>>
>> --
>> Colby Glass
>> Network Engineer
>> http://blog.alwaysthenetwork.com
>>
>
>


-- 
Colby Glass
Network Engineer
http://blog.alwaysthenetwork.com

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 where this value is coming from. Also unable
> to find out what "am" mean (adjacency module?). Does anyone have an
> explanation for this one?
>
> *  via 192.168.21.49, Vlan13, [2/0], 00:44:52, am*
>
> Thanks
>
> --
> Colby Glass
> Network Engineer
> http://blog.alwaysthenetwork.com
>

Weird Nexus AD

2010-10-29 Thread Colby Glass 
We're seeing an AD of 2 on some routes on our Nexus 7k. I can't find
anything (Google) to indicate where this value is coming from. Also unable
to find out what "am" mean (adjacency module?). Does anyone have an
explanation for this one?

*  via 192.168.21.49, Vlan13, [2/0], 00:44:52, am*

Thanks

-- 
Colby Glass
Network Engineer
http://blog.alwaysthenetwork.com