On Sun, 2 Feb 2020 at 17:22, Aaron Gould wrote:
> is there a reason why ?
I think you got a bunch of replies, but I'm not sure if the specific
reason was addressed. TLV137 is part of LSP PDU and the neighbour is
seen at one of the three possible Hello PDU, which does not yet
contain TLV137.
--
Thanks y'all
-Aaron
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
>> is there a reason why ?
>
> Looks to me like you are pretty fast in repetitive show commands :)
>
> What actually may be happening here is that adj. comes up fast and at this
> point your router does not yet have the dynamic name. After some time it
> receives it from the neighbor via
On 2/Feb/20 17:22, Aaron Gould wrote:
> funny, for a moment there it actually displayed the sys id of r1 instead of
> the word "r1"
>
>
>
> is there a reason why ?
Pretty normal when the adjacency comes up for the first time. A few
moments later as everything settles down, the System ID's
> is there a reason why ?
Looks to me like you are pretty fast in repetitive show commands :)
What actually may be happening here is that adj. comes up fast and at this
point your router does not yet have the dynamic name. After some time it
receives it from the neighbor via flooding in TLV
funny, for a moment there it actually displayed the sys id of r1 instead of
the word "r1"
is there a reason why ?
r2#sh isis neighbors
System Id Type Interface IP Address State Holdtime Circuit Id
.. L1 Fa0/0 1.2.3.1 UP23 r2.01
