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 _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
