[j-nsp] IS-IS database leaking across virtual routers?

[Stefan Fouant]

> -----Original Message-----
> From: Clarke Morledge [mailto:chmorl at wm.edu]
> Sent: Monday, August 16, 2010 2:27 PM
> To: Stefan Fouant
> Cc: juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] IS-IS database leaking across virtual routers?
> 
> Just to put a little closure on this topic from two months ago for the
> archives:   The issue I was having was NOT due to IS-IS database
> leaking
> across VRFs.   I had some routing policy problems due to configuration
> errors.
> 
> However, the fact that Juniper will only assign one IS-IS hostname per
> router regardless of the number of VRFs is a convenient red herring.
> Juniper is essentially overwriting the TLV 137 information within the
> router database everytime a TLV 137 LSP is received from a neighbor on
> a
> different VRF.  This is very annoying.  I did compare Juniper's IS-IS
> VRF
> implementation with Cisco's, and Cisco does not have this problem.
> Cisco
> will assign the same IS-IS hostname across multiple VRFs without
> causing
> any confusion.
> 
> Perhaps Juniper can learn something from their primary competitor :-)

Clarke,

You can get around this behavior by using Logical-Systems as opposed to
Virtual Routers.  Juniper will probably tell you that this is their answer
to this, but I do understand what you are getting at and it would be nice if
Juniper would fix this behavior.

On another positive and completely irrelevant note, I'm sure you're glad to
see that TRILL is really starting to pick up some steam ;)

Stefan Fouant, CISSP, JNCIEx2
www.shortestpathfirst.net
GPG Key ID: 0xB5E3803D