[j-nsp] JUNOS 9,6 AND IS-IS ISSUE
Stefan Fouant
sfouant at shortestpathfirst.net
Mon Apr 4 11:39:38 EDT 2011
> -----Original Message-----
> From: Mario Andres Rueda Jaimes [mailto:maeve2009 at gmail.com]
> Sent: Monday, April 04, 2011 11:28 AM
> To: Stefan Fouant
> Cc: juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] JUNOS 9,6 AND IS-IS ISSUE
>
> 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
Is this just coincidental that there are Layer 2 VPN failures at precisely the same time as you have routing issues? It also appears this might be related to an RE switchover.
Looks like you've got RPD indicating bad kernel routing table information due to the loss of interfaces and these happen around the same time that a possible switchover took place...
I don't think you've given us all the information. Can you describe your set up and the events leading up to this in a bit more detail?
Stefan Fouant, CISSP, JNCIEx2
www.shortestpathfirst.net
GPG Key ID: 0xB4C956EC
More information about the juniper-nsp
mailing list