cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
828
Views
10
Helpful
8
Replies

L2TP "Dataplane down" : PPP sessions not coming up

Louey
Level 1
Level 1

Hello

On our LNS, we have some log errors about some PPP sessions over VPDN that cannot come up.

we have 3 LNS and all of them are impacted, not all PPP sessions are impacted and L2TP tunnels are still up.

Here is the error message : 

Oct 13 2022 10:03:27.304: %VPDN-6-CLOSED: L2TP LNS t2e04a closed Vi3.179 user KY46890@; Result 1, Error 0, Dataplane down

Has someone faced this before ?

Kind regards

1 Accepted Solution

Accepted Solutions

Hello

I want to share with you the issue after it has been resolved :
The issue was on ASR-1009K router, we don't know for the moment if only this model is impacted. This is due to implementing those flowspec commands on our routers :

flowspec
 local-install interface-all
 address-family ipv4
  local-install interface-all
 address-family ipv6
  local-install interface-all
 
By removing those commands and reloading the routers => the issue is resolved.
Thanks for the help
Regards

View solution in original post

8 Replies 8

show vpdn history failure
share this 

Please find it here : 

, MID = 21928
NAS: 1011.sra8.p33bdx.kosc.lac, IP address = 9, CLID = 1706
Gateway: , CLID = 33292
Log time: Oct 13 16:46:36.368, Error repeat count: 2
Failure type: The remote server closed this session
Failure reason: Result 1, Error 0, Dataplane down

 

Thanks but this is not our case. We dont have this issue.

Regards

https://bst.cisco.com/bugsearch/bug/CSCvb50530

data plane down I think mostly it bug so according to show history I found the bug relate to this error.

Thank you for your sharing.

The router has just few sessions (not even 1000) and we already tried the reload/reboot. But still having the same issue.

ok, 
share 
show vpnd session all 
show vpdn 

also what is router you use for LNS ?

Hello

I want to share with you the issue after it has been resolved :
The issue was on ASR-1009K router, we don't know for the moment if only this model is impacted. This is due to implementing those flowspec commands on our routers :

flowspec
 local-install interface-all
 address-family ipv4
  local-install interface-all
 address-family ipv6
  local-install interface-all
 
By removing those commands and reloading the routers => the issue is resolved.
Thanks for the help
Regards