No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

L2TP Dial-up Failed After the NE20 Was Upgraded from VRP3.30 to VRP5.30

Publication Date:  2012-07-27 Views:  73 Downloads:  0
Issue Description
The L2TP dial-up failed after the NE20 (LNS) of a certain carrier was upgraded from VRP3.30-0520.01 to VRP5.30-23138003. 
Alarm Information
Null
Handling Process
Through the check of the upgraded configuration, the engineer found that the tunnel destination command was not configured in L2TP-group.
#
l2tp-group 10
undo tunnel authentication
mandatory-lcp
allow l2tp virtual-template 1 remote lac-1
When the NE20 works as LNS, the binding of tunnel destination interface is unnecessary because L2TP packets are all forwarded through the software in the versions earlier than VRP3.30-0520.03. In VRP3.30-0520.03 and later versions, NP implements L2TP fast forwarding. Therefore, the tunnel destination command must be configured on the interface in L2TP-group.
The preceding problem can be solved in the following ways:
1. Configure the loopback interface and associate it with L2TP-group by running the tunnel destination command. Advertise the routes of the interface to LAC or configure the static route to the IP address of the interface on LAC.
#
interface LoopBack10
ip address 10.110.1.1 255.255.255.255
#
l2tp-group 10
undo tunnel authentication
mandatory-lcp
allow l2tp virtual-template 1 remote ladd
tunnel destination LoopBack10
#
2. Associate the physical interface to L2TP-group by running the tunnel destination command. Then you need to advertise the routes of the interface to LAC or configure the static route to the IP address of the interface on LAC.
#
interface Ethernet1/0/0
ip address 188.1.1.1 255.255.255.0
#
l2tp-group 10
undo tunnel authentication
mandatory-lcp
allow l2tp virtual-template 1 remote ladd
tunnel destination Ethernet1/0/0
#
3. Associate the physical interface to L2TP-group by running the tunnel destination command. Then you need to advertise the routes of the IP address to LAC or configure the static route to the IP address of the interface on LAC.
l2tp-group 10
undo tunnel authentication
mandatory-lcp
allow l2tp virtual-template 1 remote ladd
tunnel destination ip-address 188.1.1.1 
 
Root Cause
1. Configuration change after the upgrade
2. Problem in negotiation for parameters 
 
Suggestions
Pay attention to the changes in the equipment features after the upgrade. 

END