[131613] in North American Network Operators' Group
Re: Weird Nexus AD
daemon@ATHENA.MIT.EDU (Colby Glass)
Sat Oct 30 00:36:43 2010
In-Reply-To: <AANLkTin6AzXa-7EMcyco42ELqbz=c896gB_7aO9unKJw@mail.gmail.com>
Date: Sat, 30 Oct 2010 00:36:35 -0400
From: Colby Glass <colbycciestudy@gmail.com>
To: christian koch <ck@sandcastl.es>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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 <ck@sandcastl.es> 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 <colbycciestudy@gmail.com>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
