Hello Alex, interface do not flap at all every time... Sometimes ospf neighbor is up and revenue traffic of the customer (tcp traffic) is loss.
Cheers James 2015-10-19 17:24 GMT+02:00 Alexander Arseniev <arsen...@btinternet.com>: > Hello, > Not sure what exactly You are trying to achieve, looks like You want to > delay announcing this link into OSPF (and by extension, using it for > transit traffic) unless it has been stable for 3 secs. > You could achieve this by defaulting this link to broadcast (if it is > currently configured as"interface-type p2p") - there is a Waiting state > equal to Dead timer once the OSPF interface comes up. And it interface > flaps during this time, Waiting timer starts again. > HTH > Thanks > Alex > > On 19/10/2015 15:33, james list wrote: > > Dear experts, > > I currently have a wan link between two MXs that sometimes is experiencing > errors. > > I’ve on top of the link OSPF (timer 1/3) as routing protocol and I’d like > to find out any possible way to exclude the link when errors are in place > and below to the 3 seconds of the OSPF timers. > > > I’ve analyzed the following: > > 1) BFD with OSPF but it doesn’t support hold-time (as BGP does), in > order to avoid OSPF flapping and generate higher instability I cannot use it > > 2) RPM event based script: probe interval is currently not below of 1 > second, hence to detect results with no false positive I need some sampling > and we’re still at 3 seconds or more > > Any other possible options ? > > OAM ? does it support hold-time ? > > > Cheers > > James > _______________________________________________ > juniper-nsp mailing list > juniper-nsp@puck.nether.nethttps://puck.nether.net/mailman/listinfo/juniper-nsp > > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp