Configuration Fundamentals

ExtremeCloud IQ - Site Engine Configuration

To configure Endpoint Tracking, you must perform the following:

• Using the ExtremeConnect component, configure and manage your third-party virtualization platform.

• Using the ExtremeControl component, configure and manage the RADIUS server used for Endpoint Tracking authentication.

For information about configuring ExtremeCloud IQ - Site Engine, see the ExtremeCloud IQ - Site Engine documentation at https://www.extremenetworks.com/support/documentation/.

Switch Configuration

To configure Endpoint Tracking, you must perform the following:

• Add, configure, and enable the RADIUS server host as configured in the ExtremeCloud IQ - Site Engine to function as the switch authentication server for Endpoint Tracking. Ensure that you select endpoint-tracking for the used-by variable. Add, configure and enable the RADIUS dynamic-server client. For information about adding a RADIUS server host and a RADIUS dynamic-server client to the switch, see RADIUS.

• Optionally configure a global I-SID offset value.

  When you provision the Endpoint Tracking RADIUS server in ExtremeCloud IQ - Site Engine, you choose which outbound attributes the RADIUS server includes in each authentication response. If you always include an I-SID value in those outbound attributes, you do not need to configure an I-SID offset value on the switch.

  For MACs that do not receive an I-SID attribute from the RADIUS server, use Auto-ISID-Offset functionality. The configured I-SID offset value is used to calculate an I-SID value for a switched UNI when no I-SID value is provided by the RADIUS server in the outbound attributes. In that case, the I-SID value is calculated as follows:

  I-SID = VLAN ID + configured I-SID offset value.

• After optionally configuring a global I-SID offset value, enable Endpoint Tracking globally on the switch.

• Create and enable Endpoint Tracking on each interface. Ensure that you have deleted any existing VLAN bindings on the interfaces, as the Endpoint Tracking bindings are dynamic.

  CLI commands provide the functionality to separate the creation, deletion, enabling, and disabling of Endpoint Tracking on interfaces. For example, if you want to flush all VLAN:ISID bindings on a port, you can disable (but not delete) Endpoint Tracking on that port, keeping the port distinct from other ports where Endpoint Tracking is not yet created.