Hi Alexandre, Unfortunately the filters are not helping, the flaps are still present 😞. Still looking for ways to mitigate this issue.
On 29 April 2016 at 11:14, joel ahumuza <[email protected]> wrote: > Hi All, > Aaron, > Not all ldp interfaces are /32, my loopbacks are /32s other interfaces > attached to the ldp process are p2p links with /31 masks. > > Alexandre, > Thank you, I have applied the filters to our devices. I will monitor and > advise. > > On 28 April 2016 at 23:43, Alexandre Guimaraes < > [email protected]> wrote: > >> Had experienced the same thing. >> >> After adding this to the loopback filter, the problem gone >> >> >> set firewall family inet filter PROTECT-RE term aceita-ldp from protocol >> tcp >> set firewall family inet filter PROTECT-RE term aceita-ldp from protocol >> udp >> set firewall family inet filter PROTECT-RE term aceita-ldp from >> source-port 646 >> set firewall family inet filter PROTECT-RE term aceita-ldp from >> destination-port 646 >> set firewall family inet filter PROTECT-RE term aceita-ldp then accept >> >> Alexandre >> >> -----Mensagem original----- >> De: juniper-nsp [mailto:[email protected]] Em nome de >> joel ahumuza >> Enviada em: quinta-feira, 28 de abril de 2016 12:38 >> Para: [email protected] >> Cc: [email protected] >> Assunto: [j-nsp] LDP flaps specifically present on ACX Juniper routers >> (ACX4000 and ACX1100) >> >> Hi All, >> >> We are experiencing an issue with ACX routers running on 12.3X54-D20.7 >> where the LDP sessions are continuously flapping, the logs indicate the >> following; >> >> Apr 21 03:36:31 hostname rpd[2299]: RPD_LDP_SESSIONDOWN: LDP session >> x.x.x.x is down, reason: hold time expired Apr 21 03:36:34 hostname >> rpd[2299]: RPD_LDP_NBRDOWN: LDP neighbor x.x.x.x >> (lo0.0) is down >> Apr 21 03:36:38 hostname rpd[2299]: RPD_LDP_NBRDOWN: LDP neighbor x.x.x.x >> (lo0.0) is down >> Apr 21 03:36:38 hostname rpd[2299]: RPD_LDP_SESSIONDOWN: LDP session >> x.x.x.x is down, reason: all adjacencies down Apr 21 03:55:34 hostname >> rpd[2299]: RPD_LDP_SESSIONDOWN: LDP session x.x.x.x is down, reason: >> received notification from peer Apr 21 03:55:34 hostname rpd[2299]: >> RPD_LDP_SESSIONDOWN: LDP session x.x.x.x is down, reason: received >> notification from peer Apr 21 03:55:35 hostname rpd[2299]: >> RPD_LDP_SESSIONDOWN: LDP session x.x.x.x is down, reason: received >> notification from peer Apr 21 03:55:35 hostname rpd[2299]: >> RPD_LDP_SESSIONDOWN: LDP session x.x.x.x is down, reason: received >> notification from peer >> >> The physical connections are okay, no flaps or errors on the p2p >> connections We are running ISIS as the IGP, whose adjacency is stable. >> >> Actions taken from our team was; >> - Increase the hold time setting on the ldp enabled interfaces. >> - Increase the time interval on the same ldp enabled interfaces. >> - setting the ldp session protection setting on the ldp enabled loopback >> interface. >> >> Unfortunately the actions did not yield much since the flaps have been >> ongoing. >> >> Anyone have any Idea on what the problem / solution might be? >> >> -- >> Blessings, >> >> AJ. >> SkypeID - jl.hmz >> ahumuza-joel.blogspot.ug >> _______________________________________________ >> juniper-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > > > > -- > Blessings, > > AJ. > SkypeID - jl.hmz > ahumuza-joel.blogspot.ug > -- Blessings, AJ. SkypeID - jl.hmz ahumuza-joel.blogspot.ug _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
