Display And Maintenance Commands For L2Tp; L2Tp Configuration Examples; Example: Configuring A Nas-Initiated L2Tp Tunnel - H3C SR8800-F Configuration Manual

Comware 7 user access
Hide thumbs Also See for SR8800-F:
Table of Contents

Advertisement

To configure IMSI/SN binding authentication on the LNS:
Step
1.
Enter system view.
2.
Create a VT interface and
enter its view
3.
Enable the LNS to initiate
IMSI/SN binding
authentication requests.
4.
(Optional.) Replace the
client username with the
IMSI or SN information for
authentication.

Display and maintenance commands for L2TP

Execute display commands in any view and reset commands in user view.
Task
Display L2TP tunnel information.
Display L2TP session information.
Display access control information for PPP
sessions on a VT interface.
Display information about temporary L2TP
sessions.
Display information about virtual PPP interfaces.
Disconnect an L2TP tunnel.
Clear the statistics for virtual PPP interfaces.

L2TP configuration examples

Example: Configuring a NAS-initiated L2TP tunnel

Network configuration
As shown in
Set up an L2TP tunnel between the LAC and LNS to allow the PPP user to access the corporate
network.
Command
system-view
interface virtual-template
interface-number
ppp user replace { imsi | sn }
Figure
83, a PPP user is connected to an LNS through an LAC.
Enable the LNS to initiate
IMSI/SN binding authentication
requests:
ppp lcp imsi request
ppp lcp sn request
Configure the separator for the
received authentication
information:
ppp user accept-format
imsi-sn split splitchart
Command
display l2tp tunnel [ statistics ]
display l2tp session [ statistics ]
display ppp access-control interface
virtual-template interface-number
display l2tp session temporary
display interface [ virtual-ppp [ interface-number ] ]
[ brief [ description | down ] ]
reset l2tp tunnel { id tunnel-id | name remote-name }
reset counters interface [ virtual-ppp
[ interface-number ] ]
267
Remarks
N/A
N/A
By default, the LNS does not
initiate IMSI/SN binding
authentication requests, and no
separator is configured for the
received authentication
information.
By default, the client username
is used for authentication.

Advertisement

Table of Contents
loading

Table of Contents