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

1212 Brocade Mobility RFS Controller CLI Reference Guide
53-1003098-01
23
use critical-resource <CRM-NAME1> {<CRM-NAME2>} <CRM-NAME3>} <CRM-NAME4>}
use l2tpv3-policy <L2TPV3-POLICY-NAME>
Parameters
use critical-resource <CRM-NAME1> {<CRM-NAME2>} {<CRM-NAME3>} {<CRM-NAME4>}
use l2tpv3-policy <L2TPV3-POLICY-NAME>
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
L2TPV3-POLICY
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:
<DEVICE>(config-profile-default-rfs7000)#l2tpv3 manual-session <SESSION-NAME>
use critical-resource
<CRM-NAME1>
{<CRM-NAME2>}
{<CRM-NAME3>}
{<CRM-NAME4>} Specifies the critical resource(s) to use with this tunnel
•
<CRM1-NAME> – Specify the first critical resource name
•
<CRM-NAME2/3/4> – Optional. Specify the second/third/fourth critical resource names.
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 <CRM-NAME1>.................. <CRM-NAME4> arguments are available at the time of tunnel
establishment.
NOTE: In case of L2TPv3 tunnel termination, all incoming tunnel establishment requests are rejected if
the critical resources specified by the <CRM-NAME1>.............. <CRM-NAME4> arguments are not
available.
use l2tpv3-policy
<L2TPV3-POLICY-NAME> Associates a specified L2TPv3 policy with this tunnel
•
<L2TPV3-POLICY-NAME> – Specify the policy name.
no Removes the L2TPv3 policy configured with a tunnel and reverts to the default tunnel policy