Ruijie Community

Title: When an RSR Functions as an L2TP LNS, the Client Dial-up Fails. After the debug vpdn Command Is Executed on the LNS, the Prompt "ctrl pak can't find tunnel" Is Displayed. [Print this page]

Author: admin Time: 2017-5-4 19:32
Title: When an RSR Functions as an L2TP LNS, the Client Dial-up Fails. After the debug vpdn Command Is Executed on the LNS, the Prompt "ctrl pak can't find tunnel" Is Displayed.
When an RSR Functions as an L2TP LNS, the Client Dial-up Fails. After the debug vpdn Command Is Executed on the LNS, the Prompt "ctrl pak can't find tunnel" Is Displayed.

Author: admin Time: 2017-5-4 19:35

*Apr 11 15:56:49: %7: L2TP: received 112 bytes data from UDP

*Apr 11 15:56:49: %7: L2TP: I SCCRQ from pdsn ip 115.168.101.149 sport 1701 rtnlid 146

*Apr 11 15:56:49: %7: L2TP: ctrl pak can't find tunnel

The debug information shows that the cause for the client dial-up failure is that a matched tunnel cannot be found locally, which is generally due to inconsistency between the peer identifierand the local identifier.

According to the preceding debug information, the peer identifier is PDSN. Check whether local identifier configured using the terminate-from hostname command is PDSN.

Welcome to Ruijie Community (https://community.ruijienetworks.com/)