L2tpv3-manual-session-commands – Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) User Manual
Page 1220
![background image](/manuals/361696/1220/background.png)
1212
Brocade Mobility RFS Controller CLI Reference Guide
53-1003098-01
23
use critical-resource
use l2tpv3-policy
Parameters
use critical-resource
use l2tpv3-policy
Example
rfs7000-37FABE(config-profile default-rfs7000-l2tpv3-tunnel-Tunnel1)#use
l2tpv3-
policy L2TPV3Policy1
rfs7000-37FABE(config-profile default-rfs7000-l2tpv3-tunnel-Tunnel1)#show
context
l2tpv3 tunnel Tunnel1
peer 2 hostname tunnel1peer1 udp port 100
use l2tpv3-policy L2TPV3Policy1
session tunnel1peer1session1 pseudowire-id 5000 traffic-source vlan 10-20
native-vlan 1
router-id 2000
establishment-criteria cluster-master
rfs7000-37FABE(config-profile default-rfs7000-l2tpv3-tunnel-Tunnel1)#
Related Commands:
l2tpv3-manual-session-commands
After a successful tunnel connection and establishment, individual sessions can be created. Each
session is a single data stream. After successful session establishment, data corresponding to that
session (pseudowire) can be transferred. If a session is down, the pseudowire associated with it is
shut down as well.
Use the (profile-context) instance to manually configure a L2TPv3 session. To navigate to the
L2TPv3 manual session configuration mode, use the following command in the profile context:
use critical-resource
{
{
{
Specifies the critical resource(s) to use with this tunnel
•
•
Maximum of four critical resources can be monitored.
NOTE: In case of tunnel initiator, L2TPv3 tunnel is established only if the critical resources identified by
the
establishment.
NOTE: In case of L2TPv3 tunnel termination, all incoming tunnel establishment requests are rejected if
the critical resources specified by the
available.
use l2tpv3-policy
Associates a specified L2TPv3 policy with this tunnel
•
Removes the L2TPv3 policy configured with a tunnel and reverts to the default tunnel policy