Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) - Manual (Page 1197)

Brocade Mobility RFS Controller CLI Reference Guide 1189
53-1003098-01
Chapter
23
L2TPV3-POLICY
This chapter summarizes Layer 2 Tunnel Protocol Version 3 (L2TPv3) policy commands in the CLI
command structure.
The L2TPv3 policy defines control and encapsulation protocols for tunneling different types of layer
2 frames between two IP nodes. The L2TPv3 control protocol controls dynamic creation,
maintenance, and tear down of L2TP sessions. The L2TPV3 encapsulation protocol is used to
multiplex and de-multiplex L2 data streams between two L2TP nodes across an IP network.
L2TPv3 is an IETF standard used for transporting different types of layer 2 frames in an IP network
(and access point profile). L2TPv3 defines control and encapsulation protocols for tunneling layer 2
frames between two IP nodes. Use L2TPv3 to create tunnels for transporting layer 2 frames.
L2TPv3 enables Mobility supported controllers and access points to create tunnels for transporting
Ethernet frames to and from bridge VLANs and physical ports. L2TPv3 tunnels can be defined
between Mobility devices and other vendor devices supporting the L2TPv3 protocol.
Multiple pseudowires can be created within an L2TPv3 tunnel. Mobility supported devices support
an Ethernet VLAN pseudowire type exclusively. A pseudowire is an emulation of a layer 2
point-to-point connection over a packet-switching network (PSN). A pseudowire was developed out
of the necessity to encapsulate and tunnel layer 2 protocols across a layer 3 network. Ethernet
VLAN pseudowires transport Ethernet frames to and from a specified VLAN. One or more L2TPv3
tunnels can be defined between tunnel end points. Each tunnel can have one or more L2TPv3
sessions. Each tunnel session corresponds to one pseudowire. An L2TPv3 control connection (an
L2TPv3 tunnel) needs to be established between the tunneling entities before creating a session.
NOTE
A pseudowire is an emulation of a layer 2 point-to-point connection over a packet-switching network
(PSN). A pseudowire was developed out of the necessity to encapsulate and tunnel layer 2 protocols
across a layer 3 network.
Ethernet VLAN pseudowires transport Ethernet frames to and from a specified VLAN. One or more
L2TPv3 tunnels can be defined between tunnel end points. Each tunnel can have one or more
L2TPv3 sessions. Each tunnel session corresponds to one pseudowire. An L2TPv3 control
connection (a L2TPv3 tunnel) needs to be established between the tunneling entities before
creating a session.
For optimal pseudowire operation, both the L2TPv3 session originator and responder need to know
the psuedowire type and identifier. These two parameters are communicated during L2TPv3
session establishment. An L2TPv3 session created within an L2TPv3 connection also specifies
multiplexing parameters for identifying a pseudowire type and ID.
The working status of a pseudowire is reflected by the state of the L2TPv3 session. If a L2TPv3
session is down, the pseudowire associated with it must be shut down. The L2TPv3 control
connection keep-alive mechanism can serve as a monitoring mechanism for the pseudowires
associated with a control connection.