[j-nsp] OSPF in High-Availability environments

[Raymond Cheh]

Ras,

May I ask if you have any routing protocols running between the router
on the left (MSPBCR001P) and the clients side? If the client device
doesn't learn from this router that the route has been withdrawn,
MSPBCR001P will continue to send the ICMP unreachable back.

BTW, what is the media-type for EES00005LON? If the link goes down
during the link failure or node failure, MSPBCR001P should notice it
right away and ospf redo the spf and the blackholing situation should
not occur.

Thanks.

Raymond

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
> bounces at puck.nether.net] On Behalf Of Jee Kay
> Sent: Monday, June 19, 2006 11:05 AM
> To: Raymond Cheh
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] OSPF in High-Availability environments
> 
> On 19/06/06, Raymond Cheh <rcheh at juniper.net> wrote:
> > Sending ICMP unreachable packets is independent of the routing
protocol.
> > Will enabling BFD help? It allows fast link failure detection.
> 
> BFD does have a time to detection of around 300ms which certainly cuts
> down the window of opportunity. While blackholing traffic for that
> long isn't a huge problem, I wonder if it will address the more
> fundamental problem which seems to be one of eligible routes not
> getting installed into the FIB in a timely manner.... I don't think my
> current problem is caused by the 3 seconds it is taking OSPF to notice
> the neighbour is dead, but more by what happens immediately after
> that, until the entire path has reconverged.
> 
> Ras
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp