from r2:

[EMAIL PROTECTED]> show configuration protocols isis 
lsp-lifetime 65535;
level 2 {
    wide-metrics-only;
}

interface ge-0/0/0.0 {
    point-to-point;
    level 1 disable;
    level 2 {
         hello-interval 10;
    }
}

------------------------------

[EMAIL PROTECTED]> show isis adjacency 
Interface             System         L State        Hold (secs) SNPA
...
ge-4/0/0.0            r1                2 Up                        24

------------------------------------------------

[EMAIL PROTECTED]> show isis database level 2 r2.00-00 detail        
IS-IS level 2 link-state database:

r2.00-00 Sequence: 0x5ad8, Checksum: 0xb90c, Lifetime: 65330 secs
   ...
   IS neighbor: r1.00                                   Metric:        10


----- Original Message ----
From: Stefan Fouant <[EMAIL PROTECTED]>
To: snort bsd <[EMAIL PROTECTED]>
Cc: juniper-nsp <juniper-nsp@puck.nether.net>
Sent: Friday, 28 March, 2008 2:06:33 PM
Subject: Re: [j-nsp] isis adjacencies and isis database entries

On Fri, Mar 28, 2008 at 4:25 PM, snort bsd <[EMAIL PROTECTED]> wrote:
On r1, r2 is in list of "show isis adjacency". with the help of traceoptions 
under "protocols isis" (r1), I can see LSPs (other routers) coming via the 
interface (connecting to r2). Obviously r2 is advertising LSPs via this link.


 
You are seeing LSPs coming from the other routers coming via the interface 
connected to r2 because r2 is flooding out the LSPs it is receiving from those 
routers.  By no means should this be an indication that r2 is advertising 
anything... it is simply propogating the information received.  This is the 
nature of link-state protocols.
 
What I am getting at is that r2 might not be configured to advertise anything, 
hence you see nothing in the IS-IS database for r2, even though you have an 
established adjacency.  There is not necessarily a direct one-to-one 
correlation between adjacencies and database information.
 
What is interesting to me is that even if r2 has no export policy to export any 
routing information into IS-IS, I would surely expect to see it advertising the 
direct interface routes for the interfaces on which IS-IS is explicitly 
configured.
 
Can you access r2?  Let us see the contents of your protocols isis stanza on r2.
 
Thanks

-Dave 





 
HTHs.
 
Stefan Fouant







      Get the name you always wanted with the new y7mail email address. 
www.yahoo7.com.au/y7mail
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to