[c-nsp] show isis neighbors - system id shown
Robert Raszuk
robert at raszuk.net
Sun Feb 2 10:42:23 EST 2020
> 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 137 and then creates a
mapping hence in subsequent commands you see the name.
Works as designed :) Flooding that TLV may take a bit of time as well as
your local system may not treat it as top important info.
Ref: Original Henk's RFC 2763 later replaced by RFC 5301
Best,
R.
On Sun, Feb 2, 2020 at 4:22 PM Aaron Gould <aaron1 at gvtc.com> wrote:
> 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
>
> 1111.1111.1111 L1 Fa0/0 1.2.3.1 UP 23 r2.01
>
> 1111.1111.1111 L2 Fa0/0 1.2.3.1 UP 24 r2.01
>
>
>
> r2#sh isis neighbors
>
>
>
> System Id Type Interface IP Address State Holdtime Circuit Id
>
> r1 L1 Fa0/0 1.2.3.1 UP 27 r2.01
>
> r1 L2 Fa0/0 1.2.3.1 UP 28 r2.01
>
> r2#sh isis neighbors
>
>
>
> System Id Type Interface IP Address State Holdtime Circuit Id
>
> r1 L1 Fa0/0 1.2.3.1 UP 23 r2.01
>
> r1 L2 Fa0/0 1.2.3.1 UP 24 r2.01
>
> r2#sh isis neighbors
>
>
>
> System Id Type Interface IP Address State Holdtime Circuit Id
>
> r1 L1 Fa0/0 1.2.3.1 UP 22 r2.01
>
> r1 L2 Fa0/0 1.2.3.1 UP 23 r2.01
>
> r2#sh isis neighbors
>
>
>
> System Id Type Interface IP Address State Holdtime Circuit Id
>
> r1 L1 Fa0/0 1.2.3.1 UP 21 r2.01
>
> r1 L2 Fa0/0 1.2.3.1 UP 22 r2.01
>
> r2#
>
>
>
> -Aaron
>
>
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list