Tunnel Concentrator Service Settings

For a list of field descriptions for the Tunnel Concentrator Service configuration on ExtremeCloud‌ IQ, see Tunnel Concentrator Service Settings. All fields are mandatory configurations, unless indicated otherwise.

Table 1. Tunnel Concentrator Service Settings

Field
Description
Name Enter a name for the Tunnel Concentrator Service.
Description (Optional)

Enter a description for the Tunnel Concentrator Service.

Single Tunnel Concentrator

Redundant Tunnel Concentrator

Select one of the following options:
  • Select Single Tunnel Concentrator if the service will use a single instance of Tunnel Concentrator.

  • Select Redundant Tunnel Concentrator if the service will use a pair of Tunnel Concentrator instances in an HA configuration.

Tunnel IP Address/CIDR Enter the IP address and network mask to which APs should direct tunneled traffic (for example, 10.10.10.3/24). Note that address functionality differs depending on whether or not you configured High Availability:
  • For a single Tunnel Concentrator service, this address is the tunnel termination point for this Tunnel Concentrator.

  • For a redundant Tunnel Concentrator service, this address is a VRRP address that is used by the service to provide High Availability. Tunneled traffic that arrives at this address is redirected to the IP address for the active Tunnel Concentrator in the pair.

Gateway (Optional)

Enter the IP address of the default gateway.

Note: The address must be on the same subnet as the address for Tunnel IP Address/CIDR.
VRRP Router ID (Redundant Tunnel Concentrator only)

Enter the ID for the VRRP router. This value gets assigned to both the primary and backup Tunnel Concentrators (range 1–255).

The VRRP Router ID must be different for each cluster of VRRP devices. In addition, the ID must be different from the VRRP Router IDs that were configured on the data ports for the individual Tunnel Concentrator instances.

Native VLAN Enter the Native VLAN ID. This VLAN is untagged.
Note: If you selected Redundant Tunnel Concentrator Service, the fields in this section appear twice because the service includes two instances. In this case, complete the fields separately with values that are relevant to each instance.
Device Tunnel Concentrator From the drop-down, select a specific Tunnel Concentrator device instance to assume this role in the service.
Note: For a redundant service, both instances within the service must belong to the same Network Policy.
Tunnel Port From the menu, select a port for the tunnel for this Tunnel Concentrator instance. If you are deploying LAG on this Tunnel Concentrator, select a LAG port.
VLAN ID Select the tunneling VLAN ID for this Tunnel Concentrator instance. If the VLAN is untagged, select Untagged.
IP Address (Redundant Tunnel Concentrator only)

Enter an IP address to act as tunnel termination point for this instance in the HA pair. Data that goes from the AP to the Tunnel IP Address gets redirected to this IP Address when this Tunnel Concentrator is active.

Note: These IP addresses must be on the same subnet as the Tunnel IP Address/CIDR that this service uses.
Bridge Port From the menu, select a bridge port for the tunnel for this Tunnel Concentrator instance. If you are deploying LAG on this Tunnel Concentrator instance, you can select a LAG port, although it's not mandatory.
Keepalive Settings
AP Keepalive Interval (seconds)

This parameter specifies the interval that APs use for sending keepalives to Tunnel Concentrator. A keepalive consists of a ping that the AP sends inside a tunnel, after which the AP listens for a response.

At each interval, the AP sends a keepalive down each tunnel that is not in use, and which leads to a Tunnel Concentrator service (primary, secondary, and tertiary tunnels). The AP listens for Tunnel Concentrator's response and tracks the results for each tunnel separately.

  • If the AP receives a response, the AP sets the tunnel status to Active and continues to send keepalives at scheduled intervals.
  • If the interval expires, and the AP has not received a response for a given tunnel, the AP sends another keepalive down that tunnel, but only changes the status to Inactive if the maximum number of keepalive retries for that tunnel has been met, as specified by the AP Keepalive Retries parameter.

Possible values are 1–60 seconds. The default is 3 seconds.

Note: APs send keepalives only to tunnels that are not in use. If the AP detects that the tunnel is in use, the AP sets the tunnel status to Active, but does not send a keepalive.
AP Keepalive Retries

This parameter specifies the maximum number of retry attempts for a failed keepalive before the AP changes the tunnel status to Inactive. A failed keepalive is a keepalive where the AP did not receive a response from Tunnel Concentrator within the allotted interval, as specified by AP Keepalive Interval.

If a keepalive interval passes where the AP did not receive a keepalive response from a given tunnel:

  • If the number of previous keepalive retries for this tunnel is less than the value of AP Keepalive Retries, the AP retries the keepalive, but leaves the tunnel status unchanged.
  • If the number of previous keepalive retries for this tunnel matches the value of AP Keepalive Retries, the AP changes the tunnel status to Inactive and continues to send keepalives at regular intervals.

Possible values are 1–10 retries. The default is 5 retries.

Note: If an AP receives a keepalive response for an inactive tunnel, the AP changes the tunnel status to Active and continues to send keepalives at regular intervals. However, the number of previous keepalive retry attempts for this tunnel resets to 0.
Broadcast/Multicast Control
Permitted Multicast IP Addresses
Note: Not supported in v26.01.01.
Block Non-Essential Broadcast When this setting is selected (the default setting), the Tunnel Concentrator service blocks all broadcast traffic, except for ARP and DHCP traffic.
Note: It's not supported in v26.01.01 to disable this setting.
ARP Proxy When this setting is selected (the default setting), the Tunnel Concentrator service maintains an ARP table and can proxy and respond to ARP requests.
Note: It's not supported in v26.01.01 to disable this setting.