A site uses 3G dial to operator, 3G dialing connections failed?

Publication Date:  2012-11-23 Views:  239 Downloads:  0
Issue Description
A site through 3G dialing to operator, trigger operators and the company headquarters establish L2TP tunnel to access to the internal resources, shown as the below picture:

Branch tips “697” error in the dialing?
Alarm Information
None.
Handling Process
Check whether the 3G card dialing is normal, “debugging ppp all” in branch router, LCP and NCP negotiated successfully, 3G dialing has no problem. Check the interconnection configuration of the operators and the LNS equipment of company headquarters. The LNS has no problem when customer direct dialing, the LNS configuration has no problem, the problem may be caused by the operator's parameter configuration is not consistent, we at the company's headquarters through “debugging l2tp all” to check, can see:
*0.1295056890 USG2200 L2TP/7/L2TDBG: L2TP::Check SCCRQ MSG Type 1
*0.1295056970 USG2200 L2TP/7/L2TDBG: L2TP::Parse AVP Protocol version:  100
*0.1295057060 USG2200 L2TP/7/L2TDBG: L2TP::Parse AVP Host name, value: USG5100
*0.1295057160 USG2200 L2TP/7/L2TDBG: L2TP::requested host isn't in the define
l2tp group , refuse the requested // check the LNS configuration
l2tp-group 2
undo tunnel authentication
allow l2tp virtual-template 0 remote abc domain huawei.com
tunnel name lns
The name configured remote dialing is ABC, but from debugging can see the name of the dialing device is USG5100, it will cause LNS refuses the request, change the device name or configure the “TUNNEL NAME” to abc in L2TP-GROUP, dialing succeeds.
Root Cause
Operators configured the tunnel name to the tunnel name of LNS, should configure it to be the remote dialing name which is set by LNS
Suggestions
In this scene, we can't check whether the parameters configuration of LNS and operators are consistent, can only through in the dialing configuration, debug L2TP in the LNS and check the parameters configured in LAC to locate the problem.

END