The L2TP Tunnel unable to be established due to incorrect remote tunnel name

Publication Date:  2013-05-02 Views:  247 Downloads:  0
Issue Description
the L2TP tunnel is established between the PC and the Eudemon 1000E-U/X. The PC serves as the client and the Eudemon 1000E-U/X serves as the LNS. After the tunnel is successfully established, the PC can access the server.
Alarm Information
During the dial-up on the PC, the system prompts that the link protocol negotiation is terminated and the L2TP tunnel cannot be established.
Handling Process
The tunnel name sent from the PC and the remote tunnel name configured on the Eudemon 1000E-U/X are inconsistent. Therefore, the corresponding L2TP group cannot be found. As a result, the L2TP negotiation fails.
Root Cause
1. In the user view, run debug l2tp packet to enable the debugging switch. The following debugging information is displayed:
Eudemon %%01L2TP/8/L2TDBG(d):  L2TP::Check SCCRQ MSG Type 1
Eudemon %%01L2TP/8/L2TDBG(d):  L2TP::Parse AVP Protocol version:  100
Eudemon %%01L2TP/8/L2TDBG(d):  L2TP::Parse AVP Framing capability : 1
Eudemon %%01L2TP/8/L2TDBG(d):  L2TP::Parse AVP Bearer capability, value: 0
Eudemon %%01L2TP/8/L2TDBG(d):  L2TP::Parse AVP Firmware revision, value: 1280
Eudemon %%01L2TP/8/L2TDBG(d):  L2TP::Parse AVP Host name, value: maple-54b168e59
Eudemon %%01L2TP/8/L2TDBG(d):  L2TP::requested host isn't in the define l2tp group , refuse the requested
Eudemon %%01L2TP/8/L2TDBG(d):  L2TP::Clear Calls On Tunnel ID=1 Reason=1
In the debugging information, L2TP::requested host isn't in the define l2tp group indicates that the requested host is not defined in the L2TP group. This problem may be caused by inconsistency between the tunnel name sent from the PC and the remote tunnel name configured on the Eudemon 1000E-U/X.

2. The tunnel name in the L2TP negotiation initiated by the PC is the PC name.
3. The L2TP remote tunnel name configured on the Eudemon 1000E-U/X is client1. You can configure the remote tunnel name as follows: allow l2tp virtual-template 1 remote client1
4. The tunnel name sent from the PC is different from the remote tunnel name configured on the Eudemon 1000E-U/X. Therefore, the L2TP negotiation fails.
Suggestions
You can use either of the following methods to resolve this problem:

1. Modify the PC name.

Set the PC name to client1 to ensure that it is the same as the tunnel name configured on the Eudemon 1000E-U/X.

2. Modify the remote tunnel name on the Eudemon 1000E-U/X.

On the Eudemon 1000E-U/X, change allow l2tp virtual-template 1 remote client1 to allow l2tp virtual-template 1.

END