Manual

Layer 2 Tunnel Protocol Version 3
How to Configure Layer 2 Tunnel Protocol Version 3
41
Cisco IOS Releases 12.0(29)S and 12.2(25)S
Configuring the Xconnect Attachment Circuit for ATM VP Mode Single Cell
Relay over L2TPv3
The ATM VP Mode Single Cell Relay over L2TPv3 feature allows cells coming into a predefined PVP
on the ATM interface to be transported over an L2TPv3 pseudowire to a predefined PVP on the egress
ATM interface. This task binds a PVP to an L2TPv3 pseudowire for Xconnect service.
SUMMARY STEPS
1. enable
2. configure terminal
Step 5
l2tp id local-session-id remote-session-id
Example:
Router(config-if-xconn)# l2tp id 222 111
Configures the identifiers for the local L2TPv3 session and
for the remote L2TPv3 session on the peer PE router.
• This command is required to complete the attachment
circuit configuration and for a static L2TPv3 session
configuration.
Step 6
l2tp cookie local size low-value [high-value]
Example:
Router(config-if-xconn)# l2tp cookie local 4
54321
(Optional) Specifies the value that the peer PE must include
in the cookie field of incoming (received) L2TP packets.
• The size of the cookie field can be 4 or 8 bytes. If you
do not enter this command, no cookie value is included
in the header of L2TP packets.
• If you configure the cookie length in incoming packets
as 8 bytes, you must specify a 4-byte high value and a
4-byte low value.
Step 7
l2tp cookie remote size low-value [high-value]
Example:
Router(config-if-xconn)# l2tp cookie remote 4
12345
(Optional) Specifies the value that the router includes in the
cookie field of outgoing (sent) L2TP packets.
• The size of the cookie field can be 4 or 8 bytes. If you
do not enter this command, no cookie value is included
in the header of L2TP packets.
• If you configure the cookie length in outgoing packets
as 8 bytes, you must specify a 4-byte high value and a
4-byte low value.
Step 8
l2tp hello l2tp-class-name
Example:
Router(config-if-xconn)# l2tp hello
l2tp-defaults
(Optional) Specifies the L2TP class name to use (see the
section “Configuring L2TP Control Channel Parameters”)
for control channel configuration parameters, including the
interval to use between hello keepalive messages.
Note This command assumes that there is no control
plane to negotiate control channel parameters and
that a control channel is to be used to provide
keepalive support through an exchange of L2TP
hello messages. By default, no hello messages are
sent.
Command or Action Purpose