User Guidelines
Single-Host Mode
The single-host mode manages the authentication status of the port: the port is authorized if there is an authorized host.
In this mode, only a single host can be authorized on the port.
When a port is unauthorized and the guest VLAN is enabled, untagged traffic is remapped to the guest VLAN. Tagged traffic
is dropped unless the VLAN tag is the guest VLAN or the unauthenticated VLANs. If guest VLAN is not enabled on the port, only
tagged traffic belonging to the unauthenticated VLANs is bridged.
When a port is authorized, untagged and tagged traffic from the authorized host is bridged based on the static vlan membership
configured at the port. Traffic from other hosts is dropped.
A user can specify that untagged traffic from the authorized host will be remapped to a VLAN that is assigned by a RADIUS
server during the authentication process. In this case, tagged traffic is dropped unless the VLAN tag is the RADIUS-assigned
VLAN or the unauthenticated VLANs.
The switch removes from FDB all MAC addresses learned on a port when its authentication status is changed from authorized
to unauthorized.
Multi-Host Mode
The multi-host mode manages the authentication status of the port: the port is authorized after at least one host is authorized.
When a port is unauthorized and the guest VLAN is enabled, untagged traffic is remapped to the guest VLAN. Tagged traffic
is dropped unless the VLAN tag is the guest VLAN or the unauthenticated VLANs. If guest VLAN is not enabled on the port, only
tagged traffic belonging to the unauthenticated VLANs is bridged.
When a port is authorized, untagged and tagged traffic from all hosts connected to the port is bridged based on the static
vlan membership configured at the port.
A user can specify that untagged traffic from the authorized port will be remapped to a VLAN that is assigned by a RADIUS
server during the authentication process. In this case, tagged traffic is dropped unless the VLAN tag is the RADIUS assigned
VLAN or the unauthenticated VLANs.
The switch removes from FDB all MAC addresses learned on a port when its authentication status is changed from authorized
to unauthorized.
Multi-Sessions Mode
Unlike the single-host and multi-host modes (port-based modes) the multi-sessions mode manages the authentication status for
each host connected to the port (session-based mode). If the multi-sessions mode is configured on a port the port does have
any authentication status. Any number of hosts can be authorized on the port. The command can limit the maximum number of authorized hosts allowed on the port.
Each authorized client requires a TCAM rule. If there is no available space in the TCAM, the authentication is rejected.
When using the dot1x host-mode command to change the port mode to single-host or multi-host when authentication is enabled, the port state is set to unauthorized.
If the dot1x host-mode command changes the port mode to multi-session when authentication is enabled, the state of all attached hosts is set to unauthorized.
To change the port mode to single-host or multi-host, set the port (dot1x port-control) to force-unauthorized, change the port mode to single-host or multi-host, and set the port to authorization auto.
Tagged traffic belonging to the unauthenticated VLANs is always bridged regardless if a host is authorized or not.
When the guest VLAN is enabled, untagged and tagged traffic from unauthorized hosts not belonging to the unauthenticated VLANs
is bridged via the guest VLAN.
Traffic from an authorized hosts is bridged in accordance with the port static configuration. A user can specify that untagged
and tagged traffic from the authorized host not belonging to the unauthenticated VLANs will be remapped to a VLAN that is
assigned by a RADIUS server during the authentication process.
The switch does not remove from FDB the host MAC address learned on the port when its authentication status is changed from
authorized to unauthorized. The MAC address will be removed after the aging timeout expires.
802.1x enabled on a port associated with a port channel has the following limitations: