Manual

Layer 2 Tunnel Protocol Version 3
xconnect
144
Cisco IOS Releases 12.0(29)S and 12.2(25)S
xconnect
To bind an attachment circuit to a Layer 2 pseudowire and enter xconnect configuration mode, use the
xconnect command in interface configuration mode, l2transport PVP configuration mode, or connect
configuration mode.
xconnect peer-ip-address vcid pseudowire-parameters [sequencing {transmit | receive | both}]
Syntax Description
Defaults The default behavior is to use L2TPv3 as the data encapsulation method with sequencing off.
Command Modes Interface configuration
l2transport PVP configuration (for ATM)
Frame Relay DLCI interface configuration mode
peer-ip-address The IP address of the remote provider edge (PE) peer.
vcid The 32-bit identifier of the virtual circuit between the routers at each end of
the L2TPv3 control channel.
pseudowire-parameters The encapsulation and pseudowire class parameters to be used for the
L2TPv3 control channel. At least one of the following pseudowire
parameters must be configured:
encapsulation {l2tpv3 [manual] | mpls}—The encapsulation
pseudowire class parameter specifies the tunneling method used to
encapsulate data in the pseudowire:
l2tpv3—L2TPv3 is the tunneling method to be used.
manual—(Optional) No signaling is to be used in the L2TPv3
control channel. This command places the router in xconnect
configuration mode for manual configuration of L2TPv3
parameters for the attachment circuit.
mpls—Multiprotocol Label Switching (MPLS) is the tunneling
method to be used.
pw-class pw-class-name—The pseudowire class configuration from
which the data encapsulation type (L2TPv3) will be taken. This option
is mandatory if you select L2TPv3 as your data encapsulation method.
sequencing {transmit |
receive | both}
(Optional) Sets the sequencing method to be used for packets received or
sent in L2TP sessions:
transmit—Sequencing of L2TP data packets received from the
L2TPv3 session.
receive—Sequencing of L2TP data packets sent into the L2TPv3
session.
both—Sequencing of L2TP data packets that are both sent and received
from the L2TPv3 session.
Note The both keyword is not supported with the Any Transport over
MPLS feature.