The current table population looks fine show route table mpls.0 terse protocol ldp mpls.0: 381 destinations, 388 routes (381 active, 0 holddown, 0 hidden)
show route table inet.3 terse protocol ldp inet.3: 15 destinations, 19 routes (15 active, 0 holddown, 0 hidden) On 30 April 2016 at 13:06, Khairul Alam < [email protected]> wrote: > Try checking the size of your label tables (inet.3 and mpls.0). We had > similar issue with our LDP sessions after over-population of the label > table on ACX. Apparently they have a size of around 1K/2K but they > fluctuated when we hit around 800+ labels. > LDP in juniper works by only generating labels for specific routes (/32) > unlike Cisco and end to end IGP routing is a must. > > ----- Original Message ----- > From: "Aaron" <[email protected]> > To: "joel ahumuza" <[email protected]>, "Alexandre Guimaraes" < > [email protected]> > Cc: [email protected], [email protected] > Sent: Friday, April 29, 2016 5:25:06 PM > Subject: Re: [j-nsp] LDP flaps specifically present on ACX Juniper > routers (ACX4000 and ACX1100) > > Thanks Alexandre, I meant the LDP RID....i recall hearing something about > the LDP RID needing to be a /32 and ip-reachable from adjacent (T)LDP > neighbors. > > Aaron > > root@r8-j> show configuration interfaces lo0.0 family inet | display set > set interfaces lo0 unit 0 family inet address 1.1.1.8/32 > > root@r8-j> show ldp overview | grep "Router ID" > Router ID: 1.1.1.8 > > > -----Original Message----- > From: juniper-nsp [mailto:[email protected]] On Behalf > Of > joel ahumuza > Sent: Friday, April 29, 2016 3:14 AM > To: Alexandre Guimaraes <[email protected]> > Cc: [email protected]; [email protected] > Subject: Re: [j-nsp] LDP flaps specifically present on ACX Juniper routers > (ACX4000 and ACX1100) > > 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 > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > > -- > > > Khairul Alam Ananda > > Assistant Engineer > > Planning, Architecture and Designing > > +8801616669420 > > > > > -- Blessings, AJ. SkypeID - jl.hmz ahumuza-joel.blogspot.ug _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
