R3303-HP HSR6800 Routers Layer 2 - WAN Configuration Guide

89
Disconnecting tunnels by force
Either the LAC or the LNS can initiate a tunnel disconnection request. You can also disconnect a tunnel
when no users are online or a network failure occurs. Once a tunnel is disconnected, the control
connection and all the sessions within the tunnel are removed. When a user dials in, a new tunnel is
established.
To disconnect tunnels by force:
Task Command Remarks
Disconnect tunnels by force.
reset l2tp tunnel { id tunnel-id | name
remote-name }
Available in user view.
Displaying and maintaining L2TP
Task Command Remarks
Display L2TP tunnel information.
display l2tp tunnel [ | { begin |
exclude | include }
regular-expression ]
Available in any view.
Display L2TP session information.
display l2tp session [ | { begin |
exclude | include }
regular-expression ]
Available in any view.
Display statistics about dynamic
firewalls on the VA interfaces
created on the specified VT
interface.
display ppp access-control
{ interface interface-type
interface-number } [ | { begin |
exclude | include }
regular-expression ]
Available in any view.
L2TP configuration examples
Configuration example for NAS-initiated VPN
Network requirements
As shown in Figure 28, a VPN user accesses the corporate headquarters in the following procedure:
1. The user dials in to the NAS (LAC).
2. The NAS determines whether the user is a valid VPN client. If so, it initiates a tunneling request to
the LNS.
3. After a tunnel is set up between the NAS and the LNS, the NAS transfers the results of its
negotiation with the VPN user to the LNS.
4. The LNS decides whether to accept the connection request according to the negotiated results.
5. The user communicates with the headquarters over the tunnel between the NAS and the LNS.