[j-nsp] LDP flaps specifically present on ACX Juniper routers (ACX4000 and ACX1100)

[Aaron]

Are the ldp id's /32's ?

They might need to be, I don't recall, but I will say that I always use
/32's on a loopback and then add that loopback and the phy int to the ldp
process...

agould at eng-lab-5048-1# show protocols ldp
interface ae0.0;
interface ae10.0;
interface lo0.0;

{master:0}[edit]
agould at eng-lab-5048-1# show protocols mpls
interface ae0.0;
interface ae10.0;

{master:0}[edit]
agould at eng-lab-5048-1# show routing-options
router-id 10.101.12.245;


Aaron

-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
joel ahumuza
Sent: Thursday, April 28, 2016 10:38 AM
To: juniper-nsp at puck.nether.net
Cc: tech at roketelkom.co.ug
Subject: [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 juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp