40-29
Catalyst 6500 Series Switch Software Configuration Guide—Release 8.7
OL-8978-04
Chapter 40 Configuring 802.1X Authentication
Configuring 802.1X Authentication on the Switch
ACL commit in progress.
ACL 'grpacl' successfully committed.
Console> (enable)
Console> (enable)
show dot1x group all
Group Manager Info
Current Group Count = 1
-------------------------------------------------------------
Info of Group ip-permit-group
User Count = 0
Console> (enable)
Configuring 802.1X with QoS ACLs
These sections describe how to configure 802.1X with QoS ACLs:
•
802.1X with QoS ACLs Configuration Guidelines, page 40-29
•
802.1X with QoS ACLs Configuration Example, page 40-30
•
Configuring the RADIUS Server, page 40-31
The RADIUS server sends a policy name to the 802.1X client. The policy is already defined and
committed on the switch. The user is able to fully utilize all existing QoS features when defining the QoS
policy. The 802.1X client interacts with the QoS subsystem and applies the policy on an interface after
authentication has been made. The policy is removed when the authenticated client leaves the interface.
If 802.1X has attached a policy to an interface, it is still possible for you to unmap the policy directly
through the switch CLI.
802.1X with QoS ACLs Configuration Guidelines
This section describes the guidelines for configuring 802.1X with QoS ACLs:
•
If a QoS policy misconfiguration exists and 802.1X attempts to authenticate a user on an interface,
the authentication will fail.
•
If you misconfigure a QoS policy after 802.1X has properly authenticated the interface,
authentication will fail when reauthentication is attempted on the interface with that same QoS
policy.
•
If multiple QoS policies are applied at the same time (input and output policies), authentication will
fail if any of the QoS policies fail.
•
If you apply a port-based policy and a VLAN-based policy to the same interface, the authentication
will fail.
•
The 802.1X security and QoS policies are applied only when an 802.1X user logs in. If you change
the 802.1X security and/or QoS policy on the switch or the RADIUS server, the changes are not
applied until the 802.1X user reauthenticates. If reauthentication is enabled (nondefault), the policy
will take effect usually within one hour. If reauthentication is disabled (default), the policy changes
will not take effect until each 802.1X user logs out and logs back in.
•
The existing QoS commands are used to create and show the QoS policy information. The
commands include but are not limited to the
set qos enable
,
set qos acl
, and
commit qos acl
commands. Scheduling commands and port-based QoS commands may also be used to build the
dynamic QoS policy.