This KB describes the scenario when "JL2TPD_TUNNEL_IN_STALLED_STATE: TUNNEL POSSIBLY IN STALLED STATE" is generated by jl2tpd and suggests next steps that could be taken to identify the root cause of such behavior.

In subscriber-management environment on L2TP LNS server the following log may be observed:

jl2tpd: JL2TPD_TUNNEL_IN_STALLED_STATE: TUNNEL POSSIBLY IN STALLED STATE, Uid X, TunnelLocalId Y, TunnelRemoteId Z Flow Controlled: NO

This log message happens when same subscriber is not able to negotiate PPP session more than 25 times in a row. To confirm the root cause it's recommended to:

1. Enable general-authentication-service traceoptions under [edit system processes general-authentication-service traceoptions]
2. Enable ppp-service traceoption under [edit protocols ppp-service traceoptions]
3. Analyze events in the log just before "JL2TPD_TUNNEL_IN_STALLED_STATE: TUNNEL POSSIBLY IN STALLED STATE, Uid X, TunnelLocalId Y, TunnelRemoteId Z Flow Controlled: NO" happened for any abnormalities
4. If nothing found it's recommended opening a case with JTAC for further investigation