[j-nsp] isis adjacencies and isis database entries

[Danny McPherson]

On Mar 28, 2008, at 1:08 PM, snort bsd wrote:
> Hello, all:
>
> Shouldn't the entries in the output of "show isis adjacency" be one- 
> to-one relationship with the neighbor entries in "show isis database  
> details"?

Yes, if it's all the same level, that should be present and
reported in that level's LSP.

> Assume r1 peers with r2, r3 and r4 in level 2 (single connection to  
> each neighbor)
>
> user at r1> show isis database level 2 r1.00-00 detail
> IS-IS level 2 link-state database:
>
> r1.00-00 Sequence: 0x5a92, Checksum: 0xb28c, Lifetime: 65521 secs
>   IS neighbor: r2.00                           Metric:        10
>   IS neighbor: r3.00                           Metric:        10
>   IS neighbor: r4.00                           Metric:        10
>  ...
>
> user at r1> show isis adjacency
> Interface             System         L State        Hold (secs)  SNPA
> ge-1/0/0.0           r2                 2 Up                        18
> ge-2/2/0.0           r3                 2 Up                          
> 23
> so-0/2/0.0           r4                 2 Up                          
> 28
>
>
> but in some cases, they are not. I have one router (say r1), it has  
> adjacency with r2 (on the output of "show isis adjacency) but the r2  
> entry doesn't show up in the output of "show isis database details".
>
> user at r1> show isis adjacency
> Interface             System         L State        Hold (secs)  SNPA
> ge-1/0/0.0           r2                 2 Up                        18
> ge-2/2/0.0           r3                 2 Up                          
> 23
> so-0/2/0.0           r4                 2 Up                          
> 28
>
> user at r1> show isis database level 2 r1.00-00 detail
> IS-IS level 2 link-state database:
>
> r1.00-00 Sequence: 0x5a92, Checksum: 0xb28c, Lifetime: 65521 secs

Umm, this is the same LSP number with the same checksum
as above, and both from r1's LSDB, and the same remaining
lifetime, for that matter.  Was this perhaps at cut/paste error?

Are you suggesting that in this execution of the command the
"IS neighbor" r2.00 entry didn't exist?

>   IS neighbor: r3.00                           Metric:        10
>   IS neighbor: r4.00                           Metric:        10
> ...
>
> but on r2 router, i can see r1 entry on both outputs of "show isis  
> adjacency" and "show isis database details". also the interfaces are  
> taking traffic between r1 and r2. Why is that?

How about a "show isis adjacency" and "show isis database detail"
from both r1 and r2, with raw output.  That should illustrate the delta.

-danny