Brocade Mobility Access Point System Reference Guide (Supporting software release 5.5.0.0 and later) - Manual (Page 128)

118 Brocade Mobility Access Point System Reference Guide
53-1003100-01
5
10. Define the following Settings required for the L2TP tunnel configuration:
11. Refer to the Peer table to review the configurations of the peers available for tunnel
connection.
Select + Add Row to populate the table with a maximum of two peer configurations.
Local IP Address Enter the IP address assigned as the local tunnel end point address, not the interface IP address.
This IP is used as the tunnel source IP address. If this parameter is not specified, the source IP
address is chosen automatically based on the tunnel peer IP address. This parameter is applicable
when establishing the tunnel and responding to incoming tunnel create requests.
MTU Set the maximum transmission unit (MTU). The MTU is the size (in bytes) of the largest protocol
data unit the layer can pass between tunnel peers. Define a MTU between
128 - 1,460 bytes. The default setting is 1,460. A larger MTU means processing fewer packets for
the same amount of data.
Use Tunnel Policy Select the L2TPv3 tunnel policy. The policy consists of user defined values for protocol specific
parameters which can be used with different tunnels. If none is available a new policy can be
created or an existing one can be modified. For more information, refer to L2TP V3 Configuration on
page 7-497.
Local Hostname Provide the tunnel specific hostname used by this tunnel. This is the hostname advertised in tunnel
establishment messages.
Local Router ID Specify the router ID sent in tunnel establishment messages with a potential peer device.
Establishment Criteria Configure establishment criteria for creating a tunnel between the device and the NOC. This criteria
ensures only one tunnel is created between two sites where the tunnel is established between the
vrrp-master/cluster master/rf-domain manager at the remote site and the controller at the NOC.
The tunnel is created based on the role of the remote peer.
•
always – The tunnel is always created irrespective of the role of the local device.
•
vrrp-master – The tunnel is only created when the local device is a VRRP master.
•
cluster-master – The tunnel is only created when the local device is a cluster master.
•
rf-domain-manager – The tunnel is only created when the local device is a RF-Domain
manager.
In all the above cases, if the local device goes offline for any reason, the tunnel is brought down.
VRRP Group This field is enabled only when the Establishment Criteria is set to vrrp-master. Use the spinner to
select the VRRP group.
Critical Resource Enter the critical resources required for creating and maintaining a L2TPV3 tunnel. A tunnel is only
established when all critical resources for the tunnel to be operational are available at the time
when the tunnel is created. If any one of the listed critical resources goes down, the tunnel is
disabled.
When a tunnel is established, the listed critical resources are checked for availability. Tunnel
establishment is started if the critical resources are available. Similarly, for incoming tunnel
termination requests, listed critical resources are checked and tunnel terminations are only
allowed when the critical resources are available.
For more information on managing critical resources, see Profile Critical Resources on page 5-191.