[j-nsp] JUNOS 9,6 AND IS-IS ISSUE

[Mario Andres Rueda Jaimes]

Hi 

Basicly these are the log lines prompted:

Mar 31 16:43:19  x2 rpd[4564]: L2CKT acquiring mastership for standby
Mar 31 16:43:19  x2 rpd[4564]: L2VPN acquiring mastership for standby
Mar 31 16:43:20  2 rpd[4564]: RPD_KRT_KERNEL_BAD_ROUTE: KRT: lost ifl 97
for route 10.10.200.1
Mar 31 16:43:20  x2 rpd[4564]: RPD_KRT_KERNEL_BAD_ROUTE: KRT: lost ifl
91 for route 172.31.20.5
Mar 31 16:43:20  x2 rpd[4564]: RPD_KRT_KERNEL_BAD_ROUTE: KRT: lost ifl
72 for route 192.168.8.5
Mar 31 16:43:20  x2 rpd[4564]: RPD_KRT_KERNEL_BAD_ROUTE: KRT: lost ifl
72 for route 192.168.8.9



We suspect there is a bad prefix rounding, but we"re not sure about it

Thanks

mario

El lun, 04-04-2011 a las 11:19 -0400, Stefan Fouant escribió:
> > -----Original Message-----
> > From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
> > bounces at puck.nether.net] On Behalf Of Mario Andres Rueda Jaimes
> > Sent: Monday, April 04, 2011 10:34 AM
> > To: juniper-nsp at puck.nether.net
> > Subject: [j-nsp] JUNOS 9,6 AND IS-IS ISSUE
> > 
> > Hi All
> > 
> > We recently experimented a bizarre behavior in one of our m20 routers,
> > it is
> > running Junos 9,6R3.8 and is experimenting a crash of the RSP process
> > when
> > he received an update of protocol isis (for example: One Juniper member
> > of
> > the network goes down ) and his address is no more learned by Is-Is
> > Protocol.
> > 
> > Anybody has any idea about this Issue?
> 
> You should be able to get the coredump if a process is crashing and have
> JTAC take a look at it.  Also, I'd advise maybe enabling some IS-IS
> traceoptions to monitor what's going on - when it crashes again there might
> be something in the log which provides more information, like perhaps the
> device received a Malformed IS-IS LSP or something along those lines... 
> 
> Stefan Fouant, CISSP, JNCIEx2
> www.shortestpathfirst.net
> GPG Key ID: 0xB4C956EC
>