11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.

1x Port-Based Authentication [Cisco Catal…

Catalyst 3560 Software Con guration Guide, Release

12.2(52)SE
Chapter: Con guring IEEE 802.1x Port-Based Authentication

Chapter Contents
Understanding IEEE 802.1x Port-Based Authentication
Device Roles
Authentication Process
Authentication Initiation and Message Exchange
Authentication Manager
Port-Based Authentication Methods
Per-User ACLs and Filter-Ids
Authentication Manager CLI Commands
Ports in Authorized and Unauthorized States
802.1x Host Mode
Multidomain Authentication
802.1x Multiple Authentication Mode
MAC Move
802.1x Accounting
802.1x Accounting Attribute-Value Pairs
802.1x Readiness Check
802.1x Authentication with VLAN Assignment
Using 802.1x Authentication with Per-User ACLs
802.1x Authentication with Downloadable ACLs and Redirect URLs
Cisco Secure ACS and Attribute-Value Pairs for the Redirect URL
Cisco Secure ACS and Attribute-Value Pairs for Downloadable ACLs
VLAN ID-based MAC Authentication
802.1x Authentication with Guest VLAN
802.1x Authentication with Restricted VLAN
802.1x Authentication with Inaccessible Authentication Bypass
Support on Multiple-Authentication Ports
Authentication Results
Feature Interactions
802.1x Authentication with Voice VLAN Ports
802.1x Authentication with Port Security
802.1x Authentication with Wake-on-LAN
802.1x Authentication with MAC Authentication Bypass
802.1x User Distribution
802.1x User Distribution Con guration Guidelines
Network Admission Control Layer 2 802.1x Validation
Flexible Authentication Ordering
Open1x Authentication
Using Voice Aware 802.1x Security

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 1/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT)
Guidelines
Using IEEE 802.1x Authentication with ACLs and the RADIUS Filter-Id Attribute
Con guring 802.1x Authentication
Default 802.1x Authentication Con guration
802.1x Authentication Con guration Guidelines
802.1x Authentication
VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass
MAC Authentication Bypass
Maximum Number of Allowed Devices Per Port
Con guring 802.1x Readiness Check
Con guring Voice Aware 802.1x Security
Con guring 802.1x Violation Modes
Con guring 802.1x Authentication
Con guring the Switch-to-RADIUS-Server Communication
Con guring the Host Mode
Con guring Periodic Re-Authentication
Manually Re-Authenticating a Client Connected to a Port
Changing the Quiet Period
Changing the Switch-to-Client Retransmission Time
Setting the Switch-to-Client Frame-Retransmission Number
Setting the Re-Authentication Number
Enabling MAC Move
Con guring 802.1x Accounting
Con guring a Guest VLAN
Con guring a Restricted VLAN
Con guring the Inaccessible Authentication Bypass Feature
Con guring 802.1x Authentication with WoL
Con guring MAC Authentication Bypass
Con guring 802.1x User Distribution
Con guring NAC Layer 2 802.1x Validation
Con guring an Authenticator and a Supplicant Switch with NEAT
Con guring NEAT with ASP
Con guring 802.1x Authentication with Downloadable ACLs and Redirect URLs
Con guring Downloadable ACLs
Con guring a Downloadable Policy
Con guring VLAN ID-based MAC Authentication
Con guring Flexible Authentication Ordering
Con guring Open1x
Disabling 802.1x Authentication on the Port
Resetting the 802.1x Authentication Con guration to the Default Values
Displaying 802.1x Statistics and Status

IEEE 802.1x port-based authentication prevents unauthorized devices (clients) from gaining access to
the network.
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 2/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

The Catalyst 3560 switch command reference and the "RADIUS Commands" section in the Cisco IOS
Security Command Reference, Release 12.2, have command syntax and usage information.

• Understanding IEEE 802.1x Port-Based Authentication

• Con guring 802.1x Authentication

• Displaying 802.1x Statistics and Status

Understanding IEEE 802.1x Port-Based Authentication

The standard de nes a client-server-based access control and authentication protocol to prevent
unauthorized clients from connecting to a LAN through publicly accessible ports.The authentication
server authenticates each client connected to a switch port before making available any switch or LAN
services.

Until the client is authenticated, IEEE 802.1x access control allows only Extensible Authentication
Protocol over LAN (EAPOL), Cisco Discovery Protocol (CDP), and Spanning Tree Protocol (STP) tra c
through the port to which the client is connected. After authentication, normal tra c passes through the
port.

• Device Roles

• Authentication Process

• Authentication Initiation and Message Exchange

• Authentication Manager

• Ports in Authorized and Unauthorized States

• 802.1x Host Mode

• Multidomain Authentication

• 802.1x Multiple Authentication Mode

• MAC Move

• 802.1x Accounting

• 802.1x Accounting Attribute-Value Pairs

• 802.1x Readiness Check

• 802.1x Authentication with VLAN Assignment

• Using 802.1x Authentication with Per-User ACLs

• 802.1x Authentication with Guest VLAN

• 802.1x Authentication with Restricted VLAN

• 802.1x Authentication with Inaccessible Authentication Bypass

• 802.1x Authentication with Voice VLAN Ports

• 802.1x Authentication with Port Security

• 802.1x Authentication with Wake-on-LAN

• 802.1x Authentication with MAC Authentication Bypass

• 802.1x User Distribution

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 3/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

• Network Admission Control Layer 2 802.1x Validation

• Flexible Authentication Ordering

• Open1x Authentication

• Using Voice Aware 802.1x Security

• 802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT)

• 802.1x Authentication with Downloadable ACLs and Redirect URLs

• Using IEEE 802.1x Authentication with ACLs and the RADIUS Filter-Id Attribute

Device Roles
Device roles with 802.1x port-based authentication:

Figure 9-1 802.1x Device Roles

• Client—the device (workstation) that requests access to the LAN and switch services and responds to
requests from the switch. The workstation must be running 802.1x-compliant client software such as
that o ered in the Microsoft Windows XP operating system. (The client is the supplicant in the 802.1x
standard.)

Note To resolve Windows XP network connectivity and 802.1x authentication issues, read the Microsoft
Knowledge Base article at this URL:
http://support.microsoft.com/support/kb/articles/Q303/5/97.ASP

• Authentication server—performs the actual authentication of the client. The authentication server
validates the identity of the client and noti es the switch whether or not the client is authorized to
access the LAN and switch services. Because the switch acts as the proxy, the authentication service is
transparent to the client. In this release, the RADIUS security system with Extensible Authentication
Protocol (EAP) extensions is the only supported authentication server. It is available in Cisco Secure
Access Control Server Version 3.0 or later. RADIUS operates in a client/server model in which secure
authentication information is exchanged between the RADIUS server and one or more RADIUS clients.

• Switch (edge switch or wireless access point)—controls the physical access to the network based on
the authentication status of the client. The switch acts as an intermediary (proxy) between the client
and the authentication server, requesting identity information from the client, verifying that information
with the authentication server, and relaying a response to the client. The switch includes the RADIUS
client, which is responsible for encapsulating and decapsulating the EAP frames and interacting with
the authentication server. (The switch is the authenticator in the 802.1x standard.)

When the switch receives EAPOL frames and relays them to the authentication server, the Ethernet
header is stripped, and the remaining EAP frame is re-encapsulated in the RADIUS format. The
EAP frames are not modi ed during encapsulation, and the authentication server must support EAP

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 4/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

within the native frame format. When the switch receives frames from the authentication server,
the server's frame header is removed, leaving the EAP frame, which is then encapsulated for
Ethernet and sent to the client.

The devices that can act as intermediaries include the Catalyst 3750-E, Catalyst 3560-E,
Catalyst 3750, Catalyst 3560, Catalyst 3550, Catalyst 2975, Catalyst 2970, Catalyst 2960,
Catalyst 2955, Catalyst 2950, Catalyst 2940 switches, or a wireless access point. These devices
must be running software that supports the RADIUS client and 802.1x authentication.

Authentication Process
When 802.1x port-based authentication is enabled and the client supports 802.1x-compliant client
software, these events occur:

• If the client identity is valid and the 802.1x authentication succeeds, the switch grants the client access
to the network.

• If 802.1x authentication times out while waiting for an EAPOL message exchange and MAC
authentication bypass is enabled, the switch can use the client MAC address for authorization. If the
client MAC address is valid and the authorization succeeds, the switch grants the client access to the
network. If the client MAC address is invalid and the authorization fails, the switch assigns the client to
a guest VLAN that provides limited services if a guest VLAN is con gured.

• If the switch gets an invalid identity from an 802.1x-capable client and a restricted VLAN is speci ed,
the switch can assign the client to a restricted VLAN that provides limited services.

• If the RADIUS authentication server is unavailable (down) and inaccessible authentication bypass is
enabled, the switch grants the client access to the network by putting the port in the critical-
authentication state in the RADIUS-con gured or the user-speci ed access VLAN.

Note Inaccessible authentication bypass is also referred to as critical authentication or the AAA fail
policy.

Figure 9-2 shows the authentication process.

Figure 9-2 Authentication Flowchart

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 5/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

The switch re-authenticates a client when one of these situations occurs:

• Periodic re-authentication is enabled, and the re-authentication timer expires.

You can con gure the re-authentication timer to use a switch-speci c value or to be based on
values from the RADIUS server.

After 802.1x authentication using a RADIUS server is con gured, the switch uses timers based on
the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action RADIUS attribute
(Attribute [29]).

The Session-Timeout RADIUS attribute (Attribute[27]) speci es the time after which re-
authentication occurs.

The Termination-Action RADIUS attribute (Attribute [29]) speci es the action to take during re-
authentication. The actions are Initialize and ReAuthenticate. When the Initialize action is set (the
attribute value is DEFAULT), the 802.1x session ends, and connectivity is lost during re-
authentication. When the ReAuthenticate action is set (the attribute value is RADIUS-Request), the
session is not a ected during re-authentication.

• You manually re-authenticate the client by entering the dot1x re-authenticate interface interface-id
privileged EXEC command.

If Multidomain authentication (MDA) is enabled on a port, this ow can be used with some exceptions
that are applicable to voice authorization. For more information on MDA, see "Multidomain
Authentication" section.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 6/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Authentication Initiation and Message Exchange

During 802.1x authentication, the switch or the client can initiate authentication. If you enable
authentication on a port by using the authentication port-control auto or dot1x port-control auto
interface con guration command, the switch initiates authentication when the link state changes from
down to up or periodically as long as the port remains up and unauthenticated. The switch sends an
EAP-request/identity frame to the client to request its identity. Upon receipt of the frame, the client
responds with an EAP-response/identity frame.

However, if during boot up, the client does not receive an EAP-request/identity frame from the switch,
the client can initiate authentication by sending an EAPOL-start frame, which prompts the switch to
request the client's identity.

Note If 802.1x authentication is not enabled or supported on the network access device, any EAPOL
frames from the client are dropped. If the client does not receive an EAP-request/identity frame
after three attempts to start authentication, the client sends frames as if the port is in the authorized
state. A port in the authorized state e ectively means that the client has been successfully
authenticated. For more information, see the "Ports in Authorized and Unauthorized States"
section.

When the client supplies its identity, the switch begins its role as the intermediary, passing EAP frames
between the client and the authentication server until authentication succeeds or fails. If the
authentication succeeds, the switch port becomes authorized. If the authentication fails, authentication
can be retried, the port might be assigned to a VLAN that provides limited services, or network access is
not granted. For more information, see the "Ports in Authorized and Unauthorized States" section.

The speci c exchange of EAP frames depends on the authentication method being used. Figure 9-3
shows a message exchange initiated by the client when the client uses the One-Time-Password (OTP)
authentication method with a RADIUS server.

Figure 9-3 Message Exchange

If 802.1x authentication times out while waiting for an EAPOL message exchange and MAC
authentication bypass is enabled, the switch can authorize the client when the switch detects an Ethernet
packet from the client. The switch uses the MAC address of the client as its identity and includes this
information in the RADIUS-access/request frame that is sent to the RADIUS server. After the server
sends the switch the RADIUS-access/accept frame (authorization is successful), the port becomes
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 7/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

authorized. If authorization fails and a guest VLAN is speci ed, the switch assigns the port to the guest
VLAN. If the switch detects an EAPOL packet while waiting for an Ethernet packet, the switch stops the
MAC authentication bypass process and stops 802.1x authentication.

Figure 9-4 shows the message exchange during MAC authentication bypass.

Figure 9-4 Message Exchange During MAC Authentication Bypass

Authentication Manager
In Cisco IOS Release 12.2(46)SE and earlier, you could not use the same authorization methods,
including CLI commands and messages, on this switch and also on other network devices, such as a
Catalyst 6000. You had to use separate authentication con gurations. Cisco IOS Release 12.2(50)SE and
later supports the same authorization methods on all Catalyst switches in a network.

• Port-Based Authentication Methods

• Per-User ACLs and Filter-Ids

• Authentication Manager CLI Commands

Port-Based Authentication Methods

Table 9-1 lists the authentication methods supported in these host modes:

• Single host-Only one data or voice host (client) can be authenticated on a port.

• Multiple host-Multiple data hosts can be authenticated on the same port. (If a port becomes
unauthorized in multiple-host mode, the switch denies network access to all of the attached clients.)

• Multidomain authentication (MDA) -Both a data device and voice device can be authenticated on the
same switch port. The port is divided into a data domain and a voice domain.

• Multiple authentication-Multiple hosts can authenticate on the data VLAN. This mode also allows one
client on the VLAN if a voice VLAN is con gured.

Table 9-1 802.1x Features 

Authentication method Mode

Single Host Multiple Host MDA 1 Multiple
Authentication 2
802.1x VLAN VLAN VLAN Per-user ACL3
assignment assignment assignment
Filter-Id attribute3
Per-user ACL Per-user ACL
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 8/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Filter-ID Filter-ID Per-user ACL3 Downloadable

attribute attribute ACL3
Filter-Id
Downloadable Downloadable
attribute3 Redirect URL3
ACL3 ACL4
Downloadable
Redirect URL 3 Redirect URL 3
ACL3

Redirect URL3

MAC authentication bypass VLAN VLAN VLAN Per-user ACL3

assignment assignment assignment
Filter-Id attribute3
Per-user ACL Per-user ACL Per-user ACL3
Downloadable
Filter-ID Filter-ID Filter-Id
attribute attribute ACL3
attribute3
Downloadable Downloadable Redirect URL3
Downloadable
ACL3 ACL3
ACL3
Redirect URL3 Redirect URL3
Redirect URL3

Standalone web Proxy ACL, Filter-Id attribute, downloadable ACL2

authentication4

NAC Layer 2 IP validation Filter-Id Filter-Id Filter-Id Filter-Id attribute3

attribute3 attribute3 attribute3 Downloadable
Downloadable Downloadable Downloadable ACL3
ACL ACL ACL
Redirect URL3
Redirect URL Redirect URL Redirect URL

Web authentication as Proxy ACL Proxy ACL Proxy ACL Proxy ACL3
fallback method5 Filter-Id Filter-Id Filter-Id
Filter-Id attribute3
attribute3 attribute3 attribute3
Downloadable
Downloadable Downloadable Downloadable
ACL3
ACL3 ACL3 ACL3

1
MDA = Multidomain authentication.
2
Also referred to as multiauth.
3
Supported in Cisco IOS Release 12.2(50)SE and later.
4
Supported in Cisco IOS Release 12.2(50)SE and later.
5
For clients that do not support 802.1x authentication.

Per-User ACLs and Filter-Ids

In releases earlier than Cisco IOS Release 12.2(50)SE, per-user ACLs and lter Ids were only supported
in single-host mode. In Cisco IOS Release 12.2(50), support was added for MDA- and multiauth-
enabled ports. In 12.2(52)SE and later, support was added for ports in multihost mode.

In releases earlier than Cisco IOS Release 12.2(50)SE, an ACL con gured on the switch is not
compatible with an ACL con gured on another device running Cisco IOS software, such as a
Catalyst 6000 switch.

In Cisco IOS Release 12.2(50)SE or later, the ACLs con gured on the switch are compatible with other
devices running the Cisco IOS release.
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 9/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Note You can only set any as the source in the ACL.

Note For any ACL con gured for multiple-host mode, the source portion of statement must be any. (For
example, permit icmp any host 10.10.1.1.)

You must specify any in the source ports of any de ned ACL. Otherwise, the ACL cannot be applied and
authorization fails. Single host is the only exception to support backward compatibility.

More than one host can be authenticated on MDA- enabled and multiauth ports. The ACL policy applied
for one host does not e ect the tra c of another host.

If only one host is authenticated on a multi-host port, and the other hosts gain network access without
authentication, the ACL policy for the rst host can be applied to the other connected hosts by specifying
any in the source address.

Authentication Manager CLI Commands

The authentication-manager interface-con guration commands control all the authentication methods,
such as 802.1x, MAC authentication bypass, and web authentication. The authentication manager
commands determine the priority and order of authentication methods applied to a connected host.

The authentication manager commands control generic authentication features, such as host-mode,
violation mode, and the authentication timer. Generic authentication commands include the
authentication host-mode, authentication violation, and authentication timer interface con guration
commands.

802.1x-speci c commands begin with the dot1x keyword. For example, the authentication port-control
auto interface con guration command enables authentication on an interface. However, the dot1x
system-authentication control global con guration command only globally enables or disables 802.1x
authentication.

Note If 802.1x authentication is globally disabled, other authentication methods are still enabled on that
port, such as web authentication.

The authentication manager commands provide the same functionality as earlier 802.1x commands.

Table 9-2 Authentication Manager Commands and Earlier 802.1x Commands  

The authentication The equivalent Description

manager commands 802.1x commands in
in Cisco IOS Cisco IOS Release
Release 12.2(50)SE or 12.2(46)SE and
later earlier
authentication dot1x control- Enable authentication with the wake-on-LAN (WoL)
control-direction direction {both | in} feature, and con gure the port control as
{both | in} unidirectional or bidirectional.

authentication event dot1x auth-fail vlan Enable the restricted VLAN on a port.
dot1x critical Enable the inaccessible-authentication-bypass
(interface feature.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 10/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

con guration) Specify an active VLAN as an guest VLAN.

dot1x guest-vlan6

authentication dot1x fallback Con gure a port to use web authentication as a

fallback fallback- fallback-pro le fallback method for clients that do not support
pro le authentication.

authentication host- dot1x host-mode Allow a single host (client) or multiple hosts on an
mode [multi-auth | {single-host | multi- authorized port.
multi-domain | multi- host | multi-domain}
host | single-host]

authentication order dot1x mac-auth- Provides the exibility to de ne the order of

bypass authentication methods to be used.

authentication dot1x Enable periodic re-authentication of the client.

periodic reauthentication

authentication port- dot1x port-control Enable manual control of the authorization state of the
control {auto | force- {auto | force- port.
authorized | force-un authorized | force-
authorized} unauthorized}

authentication timer dot1x timeout Set the timers.

authentication dot1x violation- Con gure the violation modes that occur when a new
violation {protect | mode {shutdown | device connects to a port or when a new device
restrict | shutdown} restrict | protect} connects to a port after the maximum number of
devices are connected to that port.

For more information, see the command reference for this release.

Ports in Authorized and Unauthorized States

During 802.1x authentication, depending on the switch port state, the switch can grant a client access to
the network. The port starts in the unauthorized state. While in this state, the port that is not con gured
as a voice VLAN port disallows all ingress and egress tra c except for 802.1x authentication, CDP, and
STP packets. When a client is successfully authenticated, the port changes to the authorized state,
allowing all tra c for the client to ow normally. If the port is con gured as a voice VLAN port, the port
allows VoIP tra c and 802.1x protocol packets before the client is successfully authenticated.

If a client that does not support 802.1x authentication connects to an unauthorized 802.1x port, the
switch requests the client's identity. In this situation, the client does not respond to the request, the port
remains in the unauthorized state, and the client is not granted access to the network.

In contrast, when an 802.1x-enabled client connects to a port that is not running the 802.1x standard,
the client initiates the authentication process by sending the EAPOL-start frame. When no response is
received, the client sends the request for a xed number of times. Because no response is received, the
client begins sending frames as if the port is in the authorized state.

You control the port authorization state by using the authentication port-control or dot1x port-control
interface con guration command and these keywords:

• force-authorized—disables 802.1x authentication and causes the port to change to the authorized
state without any authentication exchange required. The port sends and receives normal tra c without
802.1x-based authentication of the client. This is the default setting.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 11/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

• force-unauthorized—causes the port to remain in the unauthorized state, ignoring all attempts by the
client to authenticate. The switch cannot provide authentication services to the client through the port.

• auto—enables 802.1x authentication and causes the port to begin in the unauthorized state, allowing
only EAPOL frames to be sent and received through the port. The authentication process begins when
the link state of the port changes from down to up or when an EAPOL-start frame is received. The
switch requests the identity of the client and begins relaying authentication messages between the
client and the authentication server. Each client attempting to access the network is uniquely identi ed
by the switch by using the client MAC address.

If the client is successfully authenticated (receives an Accept frame from the authentication server), the
port state changes to authorized, and all frames from the authenticated client are allowed through the
port. If the authentication fails, the port remains in the unauthorized state, but authentication can be
retried. If the authentication server cannot be reached, the switch can resend the request. If no response
is received from the server after the speci ed number of attempts, authentication fails, and network
access is not granted.

When a client logs o , it sends an EAPOL-logo message, causing the switch port to change to the
unauthorized state.

If the link state of a port changes from up to down, or if an EAPOL-logo frame is received, the port
returns to the unauthorized state.

802.1x Host Mode

You can con gure an 802.1x port for single-host or for multiple-hosts mode. In single-host mode (see
Figure 9-1), only one client can be connected to the 802.1x-enabled switch port. The switch detects the
client by sending an EAPOL frame when the port link state changes to the up state. If a client leaves or is
replaced with another client, the switch changes the port link state to down, and the port returns to the
unauthorized state.

In multiple-hosts mode, you can attach multiple hosts to a single 802.1x-enabled port. Figure 9-5 shows
802.1x port-based authentication in a wireless LAN. In this mode, only one of the attached clients must
be authorized for all clients to be granted network access. If the port becomes unauthorized (re-
authentication fails or an EAPOL-logo message is received), the switch denies network access to all of
the attached clients. In this topology, the wireless access point is responsible for authenticating the
clients attached to it, and it also acts as a client to the switch.

With the multiple-hosts mode enabled, you can use 802.1x authentication to authenticate the port and
port security to manage network access for all MAC addresses, including that of the client.

Figure 9-5 Multiple Host Mode Example

The switch supports multidomain authentication (MDA), which allows both a data device and a voice
device, such as an IP Phone (Cisco or non-Cisco), to connect to the same switch port. For more
information, see the "Multidomain Authentication" section.

Multidomain Authentication
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 12/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

The switch supports multidomain authentication (MDA), which allows both a data device and voice
device, such as an IP phone (Cisco or non-Cisco), to authenticate on the same switch port. The port is
divided into a data domain and a voice domain.

MDA does not enforce the order of device authentication. However, for best results, we recommend that
a voice device is authenticated before a data device on an MDA-enabled port.

Follow these guidelines for con guring MDA:

• To con gure a switch port for MDA, see the "Con guring the Host Mode" section.

• You must con gure the voice VLAN for the IP phone when the host mode is set to multidomain. For
more information, see Chapter 13 "Con guring VLANs."

• Voice VLAN assignment on an MDA-enabled port is supported in Cisco IOS Release 12.2(40)SE and
later.

Note If you use a dynamic VLAN to assign a voice VLAN on an MDA-enabled switch port on a switch
running Cisco IOS Release 12.2(37)SE, the voice device fails authorization.

• To authorize a voice device, the AAA server must be con gured to send a Cisco Attribute-Value (AV)
pair attribute with a value of device-tra c-class=voice. Without this value, the switch treats the voice
device as a data device.

• The guest VLAN and restricted VLAN features only apply to the data devices on an MDA-enabled port.
The switch treats a voice device that fails authorization as a data device.

• If more than one device attempts authorization on either the voice or the data domain of a port, it is
error disabled.

• Until a device is authorized, the port drops its tra c. Non-Cisco IP phones or voice devices are allowed
into both the data and voice VLANs. The data VLAN allows the voice device to contact a DHCP server
to obtain an IP address and acquire the voice VLAN information. After the voice device starts sending
on the voice VLAN, its access to the data VLAN is blocked.

• A voice device MAC address that is binding on the data VLAN is not counted towards the port security
MAC address limit.

• MDA can use MAC authentication bypass as a fallback mechanism to allow the switch port to connect
to devices that do not support 802.1x authentication. For more information, see the "MAC
Authentication Bypass" section.

• When a data or a voice device is detected on a port, its MAC address is blocked until authorization
succeeds. If the authorization fails, the MAC address remains blocked for 5 minutes.

• If more than ve devices are detected on the data VLAN or more than one voice device is detected on
the voice VLAN while a port is unauthorized, the port is error disabled.

• When a port host mode changes from single- or multihost to multidomain mode, an authorized data
device remains authorized on the port. However, a Cisco IP phone on the port voice VLAN is
automatically removed and must be reauthenticated on that port.

• Active fallback mechanisms such as guest VLAN and restricted VLAN remain con gured after a port
changes from single-host or multiple-host mode to multidomain mode.

• Switching a port host mode from multidomain to single-host or multiple-hosts mode removes all
authorized devices from the port.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 13/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

• If a data domain is authorized rst and placed in the guest VLAN, non-802.1x-capable voice devices
need their packets tagged on the voice VLAN to trigger authentication. The phone need not need to
send tagged tra c. (The same is true for an 802.1x-capable phone.)

• We do not recommend per-user ACLs with an MDA-enabled port. An authorized device with a per-
user ACL policy might impact tra c on both the port voice and data VLANs. You can use only one
device on the port to enforce per-user ACLs.

For more information, see the "Con guring the Host Mode" section.

802.1x Multiple Authentication Mode

Multiple-authentication (multiauth) mode allows multiple authenticated clients on the data VLAN. Each
host is individually authenticated. If a voice VLAN is con gured, this mode also allows one client on the
VLAN. (If the port detects any additional voice clients, they are discarded from the port, but no violation
errors occur.)

If a hub or access point is connected to an 802.1x-enabled port, each connected client must be
authenticated.

For non-802.1x devices, you can use MAC authentication bypass or web authentication as the per-host
authentication fallback method to authenticate di erent hosts with di erent methods on a single port.

There is no limit to the number of data hosts can authenticate on a multiauthport. However, only one
voice device is allowed if the voice VLAN is con gured. Since there is no host limit de ned violation will
not be trigger, if a second voice is seen we silently discard it but do not trigger violation.

For MDA functionality on the voice VLAN, multiple-authentication mode assigns authenticated devices to
either a data or a voice VLAN, depending on the VSAs received from the authentication server.

Note When a port is in multiple-authentication mode, the RADIUS-server-supplied VLAN assignment,

guest VLAN, and the authentication-failed VLAN features do not activate.

For more information about critical authentication mode and the critical VLAN, see the "802.1x
Authentication with Inaccessible Authentication Bypass" section.

For more information about con guring multiauth mode on a port, see the "Con guring the Host Mode"
section

MAC Move
When a MAC address is authenticated on one switch port, that address is not allowed on another 802.1x
port of the switch. If the switch detects that same MAC address on another 802.1x port, the address is
not allowed.

There are situations where a MAC address might need to move from one port to another on the same
switch. For example, when there is another device (for example a hub or an IP phone) between an
authenticated host and a switch port, you might want to disconnect the host from the device and
connect it directly to another port on the same switch.

You can globally enable MAC move so the device is reauthenticated on the new port. When a host moves
to a second port, the session on the rst port is deleted, and the host is reauthenticated on the new port.

MAC move is supported on all host modes. (The authenticated host can move to any port on the switch,
no matter which host mode is enabled on the that port.)

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 14/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Note MAC move is not supported on port-security enabled 802.1x ports. If MAC move is globally
con gured on the switch and a port security-enabled host moves to an 802.1x-enabled port, a
violation error occurs.

For more information see the "Enabling MAC Move" section.

802.1x Accounting
The 802.1x standard de nes how users are authorized and authenticated for network access but does
not keep track of network usage. 802.1x accounting is disabled by default. You can enable 802.1x
accounting to monitor this activity on 802.1x-enabled ports:

• User successfully authenticates.

• User logs o .

• Link-down occurs.

• Re-authentication successfully occurs.

• Re-authentication fails.

The switch does not log 802.1x accounting information. Instead, it sends this information to the RADIUS
server, which must be con gured to log accounting messages.

802.1x Accounting Attribute-Value Pairs

The information sent to the RADIUS server is represented in the form of Attribute-Value (AV) pairs. These
AV pairs provide data for di erent applications. (For example, a billing application might require
information that is in the Acct-Input-Octets or the Acct-Output-Octets attributes of a RADIUS packet.)

AV pairs are automatically sent by a switch that is con gured for 802.1x accounting. Three types of
RADIUS accounting packets are sent by a switch:

• START-sent when a new user session starts

• INTERIM-sent during an existing session for updates

• STOP-sent when a session terminates

Table 9-3 lists the AV pairs and when they are sent are sent by the switch:

Table 9-3 Accounting AV Pairs 

Attribute Number AV Pair Name START INTERIM STOP

Attribute[1] User-Name Always Always Always

Attribute[4] NAS-IP-Address Always Always Always

Attribute[5] NAS-Port Always Always Always

Attribute[8] Framed-IP-Address Never Sometimes1 Sometimes1

Attribute[25] Class Always Always Always

Attribute[30] Called-Station-ID Always Always Always

Attribute[31] Calling-Station-ID Always Always Always

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 15/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Attribute[40] Acct-Status-Type Always Always Always

Attribute[41] Acct-Delay-Time Always Always Always

Attribute[42] Acct-Input-Octets Never Always Always

Attribute[43] Acct-Output-Octets Never Always Always

Attribute[44] Acct-Session-ID Always Always Always

Attribute[45] Acct-Authentic Always Always Always

Attribute[46] Acct-Session-Time Never Always Always

Attribute[49] Acct-Terminate-Cause Never Never Always

Attribute[61] NAS-Port-Type Always Always Always

1
The Framed-IP-Address AV pair is sent only if a valid Dynamic Host Control Protocol (DHCP) binding exists for the host
in the DHCP snooping bindings table.

You can view the AV pairs that are being sent by the switch by entering the debug radius accounting
privileged EXEC command. For more information about this command, see the Cisco IOS Debug
Command Reference, Release 12.2 at this URL:

http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_command_reference_book09186
a00800872ce.html

For more information about AV pairs, see RFC 3580, "802.1x  Remote Authentication Dial In User
Service (RADIUS) Usage Guidelines."

802.1x Readiness Check

The 802.1x readiness check monitors 802.1x activity on all the switch ports and displays information
about the devices connected to the ports that support 802.1x. You can use this feature to determine if
the devices connected to the switch ports are 802.1x-capable. You use an alternate authentication such
as MAC authentication bypass or web authentication for the devices that do not support 802.1x
functionality.

This feature only works if the supplicant on the client supports a query with the NOTIFY EAP noti cation
packet. The client must respond within the 802.1x timeout value.

For information on con guring the switch for the 802.1x readiness check, see the "Con guring 802.1x
Readiness Check" section.

802.1x Authentication with VLAN Assignment

The RADIUS server sends the VLAN assignment to con gure the switch port. The RADIUS server
database maintains the username-to-VLAN mappings, assigning the VLAN based on the username of
the client connected to the switch port. You can use this feature to limit network access for certain users.

Voice device authentication is supported with multidomain host mode in Cisco IOS Release 12.2(37)SE.
In Cisco IOS Release 12.2(40)SE and later, when a voice device is authorized and the RADIUS server
returned an authorized VLAN, the voice VLAN on the port is con gured to send and receive packets on
the assigned voice VLAN. Voice VLAN assignment behaves the same as data VLAN assignment on
multidomain authentication (MDA)-enabled ports. For more information, see the "Multidomain
Authentication" section.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 16/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

When con gured on the switch and the RADIUS server, 802.1x authentication with VLAN assignment has
these characteristics:

• If no VLAN is supplied by the RADIUS server or if 802.1x authentication is disabled, the port is
con gured in its access VLAN after successful authentication. Recall that an access VLAN is a VLAN
assigned to an access port. All packets sent from or received on this port belong to this VLAN.

• If 802.1x authentication is enabled but the VLAN information from the RADIUS server is not valid,
authorization fails and con gured VLAN remains in use. This prevents ports from appearing
unexpectedly in an inappropriate VLAN because of a con guration error.

Con guration errors could include specifying a VLAN for a routed port, a malformed VLAN ID, a
nonexistent or internal (routed port) VLAN ID, an RSPAN VLAN, a shut down or suspended VLAN.
In the case of a mutlidomain host port, con guration errors can also be due to an attempted
assignment of a data VLAN that matches the con gured or assigned voice VLAN ID (or the
reverse).

• If 802.1x authentication is enabled and all information from the RADIUS server is valid, the authorized
device is placed in the speci ed VLAN after authentication.

• If the multiple-hosts mode is enabled on an 802.1x port, all hosts are placed in the same VLAN
(speci ed by the RADIUS server) as the rst authenticated host.

• Enabling port security does not impact the RADIUS server-assigned VLAN behavior.

• If 802.1x authentication is disabled on the port, it is returned to the con gured access VLAN and
con gured voice VLAN.

• If an 802.1x port is authenticated and put in the RADIUS server-assigned VLAN, any change to the
port access VLAN con guration does not take e ect. In the case of a multidomain host, the same
applies to voice devices when the port is fully authorized with these exceptions:

– If the VLAN con guration change of one device results in matching the other device con gured
or assigned VLAN, then authorization of all devices on the port is terminated and multidomain
host mode is disabled until a valid con guration is restored where data and voice device
con gured VLANs no longer match.

– If a voice device is authorized and is using a downloaded voice VLAN, the removal of the voice
VLAN con guration, or modifying the con guration value to dot1p or untagged results in voice
device un-authorization and the disablement of multi-domain host mode.

When the port is in the force authorized, force unauthorized, unauthorized, or shutdown state, it is put
into the con gured access VLAN.

The 802.1x authentication with VLAN assignment feature is not supported on trunk ports, dynamic ports,
or with dynamic-access port assignment through a VLAN Membership Policy Server (VMPS).

To con gure VLAN assignment you need to perform these tasks:

• Enable AAA authorization by using the network keyword to allow interface con guration from the
RADIUS server.

• Enable 802.1x authentication. (The VLAN assignment feature is automatically enabled when you
con gure 802.1x authentication on an access port).

• Assign vendor-speci c tunnel attributes in the RADIUS server. The RADIUS server must return these
attributes to the switch:

– [64] Tunnel-Type = VLAN

– [65] Tunnel-Medium-Type = 802

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 17/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

– [81] Tunnel-Private-Group-ID = VLAN name, VLAN ID, or VLAN-Group

– [83] Tunnel-Preference

Attribute [64] must contain the value VLAN (type 13). Attribute [65] must contain the value 802
(type 6). Attribute [81] speci es the VLAN name or VLAN ID assigned to the  802.1x-authenticated
user.

For examples of tunnel attributes, see the "Con guring the Switch to Use Vendor-Speci c RADIUS
Attributes" section.

Using 802.1x Authentication with Per-User ACLs

You can enable per-user access control lists (ACLs) to provide di erent levels of network access and
service to an 802.1x-authenticated user. When the RADIUS server authenticates a user connected to an
802.1x port, it retrieves the ACL attributes based on the user identity and sends them to the switch. The
switch applies the attributes to the 802.1x port for the duration of the user session. The switch removes
the per-user ACL con guration when the session is over, if authentication fails, or if a link-down
condition occurs. The switch does not save RADIUS-speci ed ACLs in the running con guration. When
the port is unauthorized, the switch removes the ACL from the port.

You can con gure router ACLs and input port ACLs on the same switch. However, a port ACL takes
precedence over a router ACL. If you apply input port ACL to an interface that belongs to a VLAN, the
port ACL takes precedence over an input router ACL applied to the VLAN interface. Incoming packets
received on the port to which a port ACL is applied are ltered by the port ACL. Incoming routed packets
received on other ports are ltered by the router ACL. Outgoing routed packets are ltered by the router
ACL. To avoid con guration con icts, you should carefully plan the user pro les stored on the RADIUS
server.

RADIUS supports per-user attributes, including vendor-speci c attributes. These vendor-speci c

attributes (VSAs) are in octet-string format and are passed to the switch during the authentication
process. The VSAs used for per-user ACLs are inacl#<n> for the ingress direction and outacl#<n> for the
egress direction. MAC ACLs are supported only in the ingress direction. The switch supports VSAs only
in the ingress direction. It does not support port ACLs in the egress direction on Layer 2 ports. For more
information, see Chapter 34 "Con guring Network Security with ACLs."

Use only the extended ACL syntax style to de ne the per-user con guration stored on the RADIUS
server. When the de nitions are passed from the RADIUS server, they are created by using the extended
naming convention. However, if you use the Filter-Id attribute, it can point to a standard ACL.

You can use the Filter-Id attribute to specify an inbound or outbound ACL that is already con gured on
the switch. The attribute contains the ACL number followed by .in for ingress ltering or .out for egress
ltering. If the RADIUS server does not allow the .in or .out syntax, the access list is applied to the
outbound ACL by default. Because of limited support of Cisco IOS access lists on the switch, the Filter-
Id attribute is supported only for IP ACLs numbered 1 to 199 and 1300 to 2699 (IP standard and IP
extended ACLs).

The maximum size of the per-user ACL is 4000 ASCII characters but is limited by the maximum size of
RADIUS-server per-user ACLs.

For examples of vendor-speci c attributes, see the "Con guring the Switch to Use Vendor-Speci c
RADIUS Attributes" section. For more information about con guring ACLs, see Chapter 34 "Con guring
Network Security with ACLs."

Note Per-user ACLs are supported only in single-host mode.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 18/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

To con gure per-user ACLs, you need to perform these tasks:

• Enable AAA authentication.

• Enable AAA authorization by using the network keyword to allow interface con guration from the
RADIUS server.

• Enable 802.1x authentication.

• Con gure the user pro le and VSAs on the RADIUS server.

• Con gure the 802.1x port for single-host mode.

For more con guration information, see the "Authentication Manager" section.

802.1x Authentication with Downloadable ACLs and Redirect URLs

You can download ACLs and redirect URLs from a RADIUS server to the switch during 802.1x
authentication or MAC authentication bypass of the host. You can also download ACLs during web
authentication.

Note A downloadable ACL is also referred to as a dACL.

If the host mode is single-host, MDA, or multiple-authentication mode, the switch modi es the source
address of the ACL to be the host IP address.

You can apply the ACLs and redirect URLs to all the devices connected to the 802.1x-enabled port.

If no ACLs are downloaded during 802.1x authentication, the switch applies the static default ACL on the
port to the host. On a voice VLAN port, the switch applies the ACL only to the phone.

Note If a downloadable ACL or redirect URL is con gured for a client on the authentication server, a
default port ACL on the connected client switch port must also be con gured.

Cisco Secure ACS and Attribute-Value Pairs for the Redirect URL
The switch uses these cisco-av-pair VSAs:

• url-redirect is the HTTP to HTTPS URL.

• url-redirect-acl is the switch ACL name or number.

The switch uses the CiscoSecure-De ned-ACL AV pair to intercept an HTTP or HTTPS request from the
endpoint device. The switch then forwards the client web browser to the speci ed redirect address. The
url-redirect AV pair on the Cisco Secure ACS contains the URL to which the web browser is redirected.
The url-redirect-acl AV pair contains the name or number of an ACL that speci es the HTTP or HTTPS
tra c to redirect. Tra c that matches a permit ACE in the ACL is redirected.

Note De ne the URL redirect ACL and the default port ACL on the switch.

If a redirect URL con gured for a client on the authentication server, a default port ACL on the connected
client switch port must also be con gured

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 19/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Cisco Secure ACS and Attribute-Value Pairs for Downloadable ACLs

You can set the CiscoSecure-De ned-ACL Attribute-Value (AV) pair on the Cisco Secure ACS with the
RADIUS cisco-av-pair vendor-speci c attributes (VSAs). This pair speci es the names of the
downloadable ACLs on the Cisco Secure ACS with the #ACL#-IP-name-number attribute.

• The name is the ACL name.

• The number is the version number (for example, 3f783768).

If a downloadable ACL is con gured for a client on the authentication server, a default port ACL on the
connected client switch port must also be con gured.

If the default ACL is con gured on the switch and the Cisco Secure ACS sends a host-access-policy to
the switch, it applies the policy to tra c from the host connected to a switch port. If the policy does not
apply, the switch applies the default ACL. If the Cisco Secure ACS sends the switch a downloadable
ACL, this ACL takes precedence over the default ACL that is con gured on the switch port. However, if
the switch receives an host access policy from the Cisco Secure ACS but the default ACL is not
con gured, the authorization failure is declared.

For con guration details, see the "Authentication Manager" section and the "Con guring 802.1x
Authentication with Downloadable ACLs and Redirect URLs" section.

VLAN ID-based MAC Authentication

You can use VLAN ID-based MAC authentication if you wish to authenticate hosts based on a static
VLAN ID instead of a downloadable VLAN. When you have a static VLAN policy con gured on your
switch, VLAN information is sent to an IAS (Microsoft) RADIUS server along with the MAC address of
each host for authentication. The VLAN ID con gured on the connected port is used for MAC
authentication. By using VLAN ID-based MAC authentication with an IAS server, you can have a xed
number of VLANs in the network.

The feature also limits the number of VLANs monitored and handled by STP.The network can be
managed as a xed VLAN.

Note This feature is not supported on Cisco ACS Server. (The ACS server ignores the sent VLAN-IDs
for new hosts and only authenticates based on the MAC address.)

For con guration information, see the "Con guring VLAN ID-based MAC Authentication" section.
Additional con guration is similar MAC authentication bypass, as described in the "Con guring MAC
Authentication Bypass" section.

802.1x Authentication with Guest VLAN

You can con gure a guest VLAN for each 802.1x port on the switch to provide limited services to clients,
such as downloading the 802.1x client. These clients might be upgrading their system for 802.1x
authentication, and some hosts, such as Windows 98 systems, might not be  802.1x-capable.

When you enable a guest VLAN on an 802.1x port, the switch assigns clients to a guest VLAN when the
switch does not receive a response to its EAP request/identity frame or when EAPOL packets are not
sent by the client.

The switch maintains the EAPOL packet history. If an EAPOL packet is detected on the interface during
the lifetime of the link, the switch determines that the device connected to that interface is an 802.1x-
capable supplicant, and the interface does not change to the guest VLAN state. EAPOL history is cleared

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 20/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

if the interface link status goes down. If no EAPOL packet is detected on the interface, the interface
changes to the guest VLAN state.

If devices send EAPOL packets to the switch during the lifetime of the link, the switch no longer allows
clients that fail authentication access to the guest VLAN.

If the switch is trying to authorize an 802.1x-capable voice device and the AAA server is unavailable, the
authorization attempt fails, but the detection of the EAPOL packet is saved in the EAPOL history. When
the AAA server becomes available, the switch authorizes the voice device. However, the switch no
longer allows other devices access to the guest VLAN. To prevent this situation, use one of these
command sequences:

• Enter the dot1x guest-vlan supplicant global con guration command to allow access to the guest
VLAN.

• Enter the shutdown interface con guration command followed by the no shutdown interface
con guration command to restart the port.

Note If an EAPOL packet is detected after the interface has changed to the guest VLAN, the interface
reverts to an unauthorized state, and 802.1x authentication restarts.

Any number of 802.1x-incapable clients are allowed access when the switch port is moved to the guest
VLAN. If an 802.1x-capable client joins the same port on which the guest VLAN is con gured, the port is
put into the unauthorized state in the user-con gured access VLAN, and authentication is restarted.

Guest VLANs are supported on 802.1x ports in single-host or multiple-hosts mode.

You can con gure any active VLAN except an RSPAN VLAN, a private VLAN, or a voice VLAN as an
802.1x guest VLAN. The guest VLAN feature is not supported on internal VLANs (routed ports) or trunk
ports; it is supported only on access ports.

The switch supports MAC authentication bypass. When MAC authentication bypass is enabled on an
802.1x port, the switch can authorize clients based on the client MAC address when  802.1x
authentication times out while waiting for an EAPOL message exchange. After detecting a client on an
802.1x port, the switch waits for an Ethernet packet from the client. The switch sends the authentication
server a RADIUS-access/request frame with a username and password based on the MAC address. If
authorization succeeds, the switch grants the client access to the network. If authorization fails, the
switch assigns the port to the guest VLAN if one is speci ed. For more information, see the"802.1x
Authentication with MAC Authentication Bypass" section.

For more information, see the "Con guring a Guest VLAN" section.

802.1x Authentication with Restricted VLAN

You can con gure a restricted VLAN (also referred to as an authentication failed VLAN) for each 802.1x
port on a switch to provide limited services to clients that cannot access the guest VLAN. These clients
are 802.1x-compliant and cannot access another VLAN because they fail the authentication process. A
restricted VLAN allows users without valid credentials in an authentication server (typically, visitors to an
enterprise) to access a limited set of services. The administrator can control the services available to the
restricted VLAN.

Note You can con gure a VLAN to be both the guest VLAN and the restricted VLAN if you want to
provide the same services to both types of users.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 21/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Without this feature, the client attempts and fails authentication inde nitely, and the switch port remains
in the spanning-tree blocking state. With this feature, you can con gure the switch port to be in the
restricted VLAN after a speci ed number of authentication attempts (the default value is 3 attempts).

The authenticator counts the failed authentication attempts for the client. When this count exceeds the
con gured maximum number of authentication attempts, the port moves to the restricted VLAN. The
failed attempt count increments when the RADIUS server replies with either an EAP failure or an empty
response without an EAP packet. When the port moves into the restricted VLAN, the failed attempt
counter resets.

Users who fail authentication remain in the restricted VLAN until the next re-authentication attempt. A
port in the restricted VLAN tries to re-authenticate at con gured intervals (the default is 60 seconds). If
re-authentication fails, the port remains in the restricted VLAN. If re-authentication is successful, the port
moves either to the con gured VLAN or to a VLAN sent by the RADIUS server. You can disable re-
authentication. If you do this, the only way to restart the authentication process is for the port to receive a
link down or EAP logo event. We recommend that you keep re-authentication enabled if a client might
connect through a hub. When a client disconnects from the hub, the port might not receive the link down
or EAP logo event.

After a port moves to the restricted VLAN, a simulated EAP success message is sent to the client. This
prevents clients from inde nitely attempting authentication. Some clients (for example, devices running
Windows XP) cannot implement DHCP without EAP success.

Restricted VLANs are supported only on 802.1x ports in single-host mode and on Layer 2 ports.

You can con gure any active VLAN except an RSPAN VLAN, a primary private VLAN, or a voice VLAN as
an 802.1x restricted VLAN. The restricted VLAN feature is not supported on internal VLANs (routed
ports) or trunk ports; it is supported only on access ports.

This feature works with port security. As soon as the port is authorized, a MAC address is provided to
port security. If port security does not permit the MAC address or if the maximum secure address count
is reached, the port becomes unauthorized and error disabled.

Other port security features such as dynamic ARP Inspection, DHCP snooping, and IP source guard can
be con gured independently on a restricted VLAN.

For more information, see the "Con guring a Restricted VLAN" section.

802.1x Authentication with Inaccessible Authentication Bypass

Use the inaccessible authentication bypass feature, also referred to as critical authentication or the AAA
fail policy, when the switch cannot reach the con gured RADIUS servers and new hosts cannot be
authenticated. You can con gure the switch to connect those hosts to critical ports.

When a new host tries to connect to the critical port, that host is moved to a user-speci ed access
VLAN, the critical VLAN. The administrator gives limited authentication to the hosts.

When the switch tries to authenticate a host connected to a critical port, the switch checks the status of
the con gured RADIUS server. If a server is available, the switch can authenticate the host. However, if all
the RADIUS servers are unavailable, the switch grants network access to the host and puts the port in
the critical-authentication state, which is a special case of the authentication state.

Support on Multiple-Authentication Ports

To support inaccessible bypass on multiple-authentication (multiauth) ports, you can use the
authentication event server dead action reinitialize vlan vlan-id. When a new host tries to connect to
the critical port, that port is reinitialized and all the connected hosts are moved to the user-speci ed
access VLAN.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 22/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

The authentication event server dead action reinitialize vlan vlan-id interface con guration command
is supported on all host modes.

Authentication Results
The behavior of the inaccessible authentication bypass feature depends on the authorization state of the
port:

• If the port is unauthorized when a host connected to a critical port tries to authenticate and all servers
are unavailable, the switch puts the port in the critical-authentication state in the RADIUS-con gured or
user-speci ed access VLAN.

• If the port is already authorized and reauthentication occurs, the switch puts the critical port in the
critical-authentication state in the current VLAN, which might be the one previously assigned by the
RADIUS server.

• If the RADIUS server becomes unavailable during an authentication exchange, the current exchange
times out, and the switch puts the critical port in the critical-authentication state during the next
authentication attempt.

You can con gure the critical port to reinitialize hosts and move them out of the critical VLAN when the
RADIUS server is again available. When this is con gured, all critical ports in the critical-authentication
state are automatically re-authenticated. For more information, see the command reference for this
release and the "Con guring the Inaccessible Authentication Bypass Feature" on page -50.

Feature Interactions
Inaccessible authentication bypass interacts with these features:

• Guest VLAN—Inaccessible authentication bypass is compatible with guest VLAN. When a guest VLAN is
enabled on 8021.x port, the features interact as follows:

– If at least one RADIUS server is available, the switch assigns a client to a guest VLAN when the
switch does not receive a response to its EAP request/identity frame or when EAPOL packets
are not sent by the client.

– If all the RADIUS servers are not available and the client is connected to a critical port, the switch
authenticates the client and puts the critical port in the critical-authentication state in the
RADIUS-con gured or user-speci ed access VLAN.

– If all the RADIUS servers are not available and the client is not connected to a critical port, the
switch might not assign clients to the guest VLAN if one is con gured.

– If all the RADIUS servers are not available and if a client is connected to a critical port and was
previously assigned to a guest VLAN, the switch keeps the port in the guest VLAN.

• Restricted VLAN—If the port is already authorized in a restricted VLAN and the RADIUS servers are
unavailable, the switch puts the critical port in the critical-authentication state in the restricted VLAN.

• 802.1x accounting—Accounting is not a ected if the RADIUS servers are unavailable.

• Private VLAN—You can con gure inaccessible authentication bypass on a private VLAN host port. The
access VLAN must be a secondary private VLAN.

• Voice VLAN—Inaccessible authentication bypass is compatible with voice VLAN, but the RADIUS-
con gured or user-speci ed access VLAN and the voice VLAN must be di erent.

• Remote Switched Port Analyzer (RSPAN)—Do not con gure an RSPAN VLAN as the RADIUS-con gured
or user-speci ed access VLAN for inaccessible authentication bypass.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 23/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

802.1x Authentication with Voice VLAN Ports

A voice VLAN port is a special access port associated with two VLAN identi ers:

• VVID to carry voice tra c to and from the IP phone. The VVID is used to con gure the IP phone
connected to the port.

• PVID to carry the data tra c to and from the workstation connected to the switch through the IP phone.
The PVID is the native VLAN of the port.

The IP phone uses the VVID for its voice tra c, regardless of the authorization state of the port. This
allows the phone to work independently of 802.1x authentication.

In single-host mode, only the IP phone is allowed on the voice VLAN. In multiple-hosts mode, additional
clients can send tra c on the voice VLAN after a supplicant is authenticated on the PVID. When multiple-
hosts mode is enabled, the supplicant authentication a ects both the PVID and the VVID.

A voice VLAN port becomes active when there is a link, and the device MAC address appears after the
rst CDP message from the IP phone. Cisco IP phones do not relay CDP messages from other devices.
As a result, if several IP phones are connected in series, the switch recognizes only the one directly
connected to it. When 802.1x authentication is enabled on a voice VLAN port, the switch drops packets
from unrecognized IP phones more than one hop away.

When 802.1x authentication is enabled on a port, you cannot con gure a port VLAN that is equal to a
voice VLAN.

Note If you enable 802.1x authentication on an access port on which a voice VLAN is con gured and to
which a Cisco IP Phone is connected, the Cisco IP phone loses connectivity to the switch for up to
30 seconds.

For more information about voice VLANs, see Chapter 14 "Con guring Voice VLAN."

802.1x Authentication with Port Security

You can con gure an 802.1x port with port security in either single-host or multiple-hosts mode. (You
also must con gure port security on the port by using the switchport port-security interface
con guration command.) When you enable port security and 802.1x authentication on a port, 802.1x
authentication authenticates the port, and port security manages network access for all MAC addresses,
including that of the client. You can then limit the number or group of clients that can access the network
through an 802.1x port.

These are some examples of the interaction between 802.1x authentication and port security on the
switch:

• When a client is authenticated, and the port security table is not full, the client MAC address is added
to the port security list of secure hosts. The port then proceeds to come up normally.

When a client is authenticated and manually con gured for port security, it is guaranteed an entry
in the secure host table (unless port security static aging has been enabled).

A security violation occurs if the client is authenticated, but the port security table is full. This can
happen if the maximum number of secure hosts has been statically con gured or if the client ages
out of the secure host table. If the client address is aged, its place in the secure host table can be
taken by another host.

If the security violation is caused by the rst authenticated host, the port becomes error-disabled
and immediately shuts down.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 24/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

The port security violation modes determine the action for security violations. For more
information, see the "Security Violations" section.

• When you manually remove an 802.1x client address from the port security table by using the no
switchport port-security mac-address mac-address interface con guration command, you should
re-authenticate the 802.1x client by using the dot1x re-authenticate interface interface-id privileged
EXEC command.

• When an 802.1x client logs o , the port changes to an unauthenticated state, and all dynamic entries in
the secure host table are cleared, including the entry for the client. Normal authentication then takes
place.

• If the port is administratively shut down, the port becomes unauthenticated, and all dynamic entries are
removed from the secure host table.

• Port security and a voice VLAN can be con gured simultaneously on an 802.1x port that is in either
single-host or multiple-hosts mode. Port security applies to both the voice VLAN identi er (VVID) and
the port VLAN identi er (PVID).

• You can con gure the authentication violation or dot1x violation-mode interface con guration
command so that a port shuts down, generates a syslog error, or discards packets from a new device
when it connects to an 802.1x-enabled port or when the maximum number of allowed devices have
been authenticated. For more information see the "Maximum Number of Allowed Devices Per Port"
section and the command reference for this release.

For more information about enabling port security on your switch, see the "Con guring Port Security"
section.

802.1x Authentication with Wake-on-LAN

The 802.1x authentication with the wake-on-LAN (WoL) feature allows dormant PCs to be powered
when the switch receives a speci c Ethernet frame, known as the magic packet. You can use this feature
in environments where administrators need to connect to systems that have been powered down.

When a host that uses WoL is attached through an 802.1x port and the host powers o , the 802.1x port
becomes unauthorized. The port can only receive and send EAPOL packets, and WoL magic packets
cannot reach the host. When the PC is powered o , it is not authorized, and the switch port is not
opened.

When the switch uses 802.1x authentication with WoL, the switch forwards tra c to unauthorized 802.1x
ports, including magic packets. While the port is unauthorized, the switch continues to block ingress
tra c other than EAPOL packets. The host can receive packets but cannot send packets to other devices
in the network.

Note If PortFast is not enabled on the port, the port is forced to the bidirectional state.

When you con gure a port as unidirectional by using the authentication control-direction in or dot1x
control-direction in interface con guration command, the port changes to the spanning-tree forwarding
state. The port can send packets to the host but cannot receive packets from the host.

When you con gure a port as bidirectional by using the authentication control-direction both or dot1x
control-direction both interface con guration command, the port is access-controlled in both
directions. The port does not receive packets from or send packets to the host.

802.1x Authentication with MAC Authentication Bypass

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 25/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

You can con gure the switch to authorize clients based on the client MAC address (see Figure 9-2) by
using the MAC authentication bypass feature. For example, you can enable this feature on 802.1x ports
connected to devices such as printers.

If 802.1x authentication times out while waiting for an EAPOL response from the client, the switch tries to
authorize the client by using MAC authentication bypass.

When the MAC authentication bypass feature is enabled on an 802.1x port, the switch uses the MAC
address as the client identity. The authentication server has a database of client MAC addresses that are
allowed network access. After detecting a client on an 802.1x port, the switch waits for an Ethernet
packet from the client. The switch sends the authentication server a RADIUS-access/request frame with
a username and password based on the MAC address. If authorization succeeds, the switch grants the
client access to the network. If authorization fails, the switch assigns the port to the guest VLAN if one is
con gured.

If an EAPOL packet is detected on the interface during the lifetime of the link, the switch determines that
the device connected to that interface is an 802.1x-capable supplicant and uses 802.1x authentication
(not MAC authentication bypass) to authorize the interface. EAPOL history is cleared if the interface link
status goes down.

If the switch already authorized a port by using MAC authentication bypass and detects an 802.1x
supplicant, the switch does not unauthorize the client connected to the port. When re-authentication
occurs, the switch uses 802.1x authentication as the preferred re-authentication process if the previous
session ended because the Termination-Action RADIUS attribute value is DEFAULT.

Clients that were authorized with MAC authentication bypass can be re-authenticated. The re-
authentication process is the same as that for clients that were authenticated with 802.1x. During re-
authentication, the port remains in the previously assigned VLAN. If re-authentication is successful, the
switch keeps the port in the same VLAN. If re-authentication fails, the switch assigns the port to the
guest VLAN, if one is con gured.

If re-authentication is based on the Session-Timeout RADIUS attribute (Attribute[27]) and the

Termination-Action RADIUS attribute (Attribute [29]) and if the Termination-Action RADIUS attribute
(Attribute [29]) action is Initialize, (the attribute value is DEFAULT), the MAC authentication bypass
session ends, and connectivity is lost during re-authentication. If MAC authentication bypass is enabled
and the 802.1x authentication times out, the switch uses the MAC authentication bypass feature to
initiate re-authorization. For more information about these AV pairs, see RFC 3580, "802.1X Remote
Authentication Dial In User Service (RADIUS) Usage Guidelines."

MAC authentication bypass interacts with the features:

• 802.1x authentication—You can enable MAC authentication bypass only if 802.1x authentication is
enabled on the port.

• Guest VLAN—If a client has an invalid MAC address identity, the switch assigns the client to a guest
VLAN if one is con gured.

• Restricted VLAN—This feature is not supported when the client connected to an 802.lx port is
authenticated with MAC authentication bypass.

• Port security—See the "802.1x Authentication with Port Security" section.

• Voice VLAN—See the "802.1x Authentication with Voice VLAN Ports" section.

• VLAN Membership Policy Server (VMPS)—802.1x and VMPS are mutually exclusive.

• Private VLAN—You can assign a client to a private VLAN.

• Network admission control (NAC) Layer 2 IP validation—This feature takes e ect after an 802.1x port is
authenticated with MAC authentication bypass, including hosts in the exception list.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 26/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

For more con guration information, see the "Authentication Manager" section.

802.1x User Distribution

You can con gure 802.1x user distribution to load-balance users with the same group name across
multiple di erent VLANs.

The VLANs are either supplied by the RADIUS server or con gured through the switch CLI under a VLAN
group name.

• Con gure the RADIUS server to send more than one VLAN name for a user. The multiple VLAN names
can be sent as part of the response to the user. The 802.1x user distribution tracks all the users in a
particular VLAN and achieves load balancing by moving the authorized user to the least populated
VLAN.

• Con gure the RADIUS server to send a VLAN group name for a user. The VLAN group name can be
sent as part of the response to the user. You can search for the selected VLAN group name among the
VLAN group names that you con gured by using the switch CLI. If the VLAN group name is found, the
corresponding VLANs under this VLAN group name are searched to nd the least populated VLAN.
Load balancing is achieved by moving the corresponding authorized user to that VLAN.

Note The RADIUS server can send the VLAN information in any combination of VLAN-IDs, VLAN names,
or VLAN groups.

802.1x User Distribution Con guration Guidelines

• Con rm that at least one VLAN is mapped to the VLAN group.

• You can map more than one VLAN to a VLAN group.

• You can modify the VLAN group by adding or deleting a VLAN.

• When you clear an existing VLAN from the VLAN group name, none of the authenticated ports in the
VLAN are cleared, but the mappings are removed from the existing VLAN group.

• If you clear the last VLAN from the VLAN group name, the VLAN group is cleared.

• You can clear a VLAN group even when the active VLANs are mapped to the group. When you clear a
VLAN group, none of the ports or users that are in the authenticated state in any VLAN within the group
are cleared, but the VLAN mappings to the VLAN group are cleared.

For more information, see the "Con guring 802.1x User Distribution" section.

Network Admission Control Layer 2 802.1x Validation

The switch supports the Network Admission Control (NAC) Layer 2 802.1x validation, which checks the
antivirus condition or posture of endpoint systems or clients before granting the devices network access.
With NAC Layer 2 802.1x validation, you can do these tasks:

• Download the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action RADIUS
attribute (Attribute[29]) from the authentication server.

• Set the number of seconds between re-authentication attempts as the value of the Session-Timeout
RADIUS attribute (Attribute[27]) and get an access policy against the client from the RADIUS server.

• Set the action to be taken when the switch tries to re-authenticate the client by using the Termination-
Action RADIUS attribute (Attribute[29]). If the value is the DEFAULT or is not set, the session ends. If the

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 27/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

value is RADIUS-Request, the re-authentication process starts.

• Set the list of VLAN number or name or VLAN group name as the value of the Tunnel Group Private ID
(Attribute[81]) and the preference for the VLAN number or name or VLAN group name as the value of
the Tunnel Preference (Attribute[83]). If you do not con gure the Tunnel Preference, the rst Tunnel
Group Private ID (Attribute[81]) attribute is picked up from the list.

• View the NAC posture token, which shows the posture of the client, by using the show authentication
or show dot1x privileged EXEC command.

• Con gure secondary private VLANs as guest VLANs.

Con guring NAC Layer 2 802.1x validation is similar to con guring 802.1x port-based authentication
except that you must con gure a posture token on the RADIUS server. For information about con guring
NAC Layer 2 802.1x validation, see the "Con guring NAC Layer 2 802.1x Validation" section and the
"Con guring Periodic Re-Authentication" section.

For more information about NAC, see the Network Admission Control Software Con guration Guide.

For more con guration information, see the "Authentication Manager" section.

Flexible Authentication Ordering

You can use exible authentication ordering to con gure the order of methods that a port uses to
authenticate a new host. MAC authentication bypass and 802.1x can be the primary or secondary
authentication methods, and web authentication can be the fallback method if either or both of those
authentication attempts fail. For more information see the "Con guring Flexible Authentication Ordering"
section.

Open1x Authentication
Open1x authentication allows a device access to a port before that device is authenticated. When open
authentication is con gured, a new host on the port can only send tra c to the switch. After the host is
authenticated, the policies con gured on the RADIUS server are applied to that host.

You can con gure open authentication with these scenarios:

• Single-host mode with open authentication-Only one user is allowed network access before and after
authentication.

• MDA mode with open authentication-Only one user in the voice domain and one user in the data
domain are allowed.

• Multiple-hosts mode with open authentication-Any host can access the network.

• Multiple-authentication mode with open authentication-Similar to MDA, except multiple hosts can be
authenticated.

For more information see the "Con guring the Host Mode" section.

Using Voice Aware 802.1x Security

You use the voice aware 802.1x security feature to con gure the switch to disable only the VLAN on
which a security violation occurs, whether it is a data or voice VLAN. When an attempt to authenticate
the data client caused a security violation in previous releases, the entire port shut down, resulting in a
complete loss of connectivity.

You can use this feature where a PC is connected to the IP phone. A security violation found on the data
VLAN shuts down only the data VLAN. The tra c on the voice VLAN continues without interruption.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 28/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

For information on con guring voice aware 802.1x security, see the "Con guring Voice Aware 802.1x
Security" section.

802.1x Supplicant and Authenticator Switches with Network Edge

Access Topology (NEAT)
The Network Edge Access Topology (NEAT) feature extends identity to areas outside the wiring closet
(such as conference rooms). This allows any type of device to authenticate on the port.

• 802.1x switch supplicant: You can con gure a switch to act as a supplicant to another switch by using
the 802.1x supplicant feature. This con guration is helpful in a scenario, where, for example, a switch
is outside a wiring closet and is connected to an upstream switch through a trunk port. A switch
con gured with the 802.1x switch supplicant feature authenticates with the upstream switch for secure
connectivity.

Once the supplicant switch authenticates successfully the port mode changes from access to
trunk.

• If the access VLAN is con gured on the authenticator switch, it becomes the native VLAN for the trunk
port after successful authentication.

You can enable MDA or multiauth mode on the authenticator switch interface that connects to one more
supplicant switches. Multihost mode is not supported on the authenticator switch interface.

Use the dot1x supplicant force-multicast global con guration command on the supplicant switch for
Network Edge Access Topology (NEAT) to work in all host modes.

• Host Authorization: Ensures that only tra c from authorized hosts (connecting to the switch with
supplicant) is allowed on the network. The switches use Client Information Signalling Protocol (CISP) to
send the MAC addresses connecting to the supplicant switch to the authenticator switch, as shown in
Figure 9-6.

• Auto enablement: Automatically enables trunk con guration on the authenticator switch, allowing user
tra c from multiple VLANs coming from supplicant switches. Con gure the cisco-av-pair as device-
tra c-class=switch at the ACS. (You can con gure this under the group or the user settings.)

Figure 9-6 Authenticator and Supplicant Switch using CISP

1 Workstations (clients) 2 Supplicant switch (outside wiring closet)

3 Authenticator switch 4 Access control server (ACS)

5 Trunk port    

Guidelines
• You can con gure NEAT ports with the same con gurations as the other authentication ports. When the
supplicant switch authenticates, the port mode is changed from access to trunk based on the switch
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 29/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

vendor-speci c attributes (VSAs). (device-tra c-class=switch).

• The VSA changes the authenticator switch port mode from access to trunk and enables 802.1x trunk
encapsulation and the access VLAN if any would be converted to a native trunk VLAN. VSA does not
change any of the port con gurations on the supplicant

• To change the host mode and the apply a standard port con guration on the authenticator switch port,
you can also use AutoSmart ports user-de ned macros, instead of the switch VSA. This allows you to
remove unsupported con gurations on the authenticator switch port and to change the port mode from
access to trunk. For more information, see Chapter 12 "Con guring Auto Smartports Macros".

For more information, see the "Con guring an Authenticator and a Supplicant Switch with NEAT"
section.

Using IEEE 802.1x Authentication with ACLs and the RADIUS Filter-Id
Attribute
The switch supports both IP standard and IP extended port access control lists (ACLs) applied to ingress
ports.

• ACLs that you con gure

• ACLs from the Access Control Server (ACS)

An IEEE 802.1x port in single-host mode uses ACLs from the ACS to provide di erent levels of service to
an IEEE 802.1x-authenticated user. When the RADIUS server authenticates this type of user and port, it
sends ACL attributes based on the user identity to the switch. The switch applies the attributes to the
port for the duration of the user session. If the session is over, authentication fails, or a link fails, the port
becomes unauthorized, and the switch removes the ACL from the port.

Only IP standard and IP extended port ACLs from the ACS support the Filter-Id attribute. It speci es the
name or number of an ACL. The Filter-id attribute can also specify the direction (inbound or outbound)
and a user or a group to which the user belongs.

• The Filter-Id attribute for the user takes precedence over that for the group.

• If a Filter-Id attribute from the ACS speci es an ACL that is already con gure, it takes precedence over
a user-con gured ACL.

• If the RADIUS server sends more than one Filter-Id attribute, only the last attribute is applied.

If the Filter-Id attribute is not de ned on the switch, authentication fails, and the port returns to the
unauthorized state.

Con guring 802.1x Authentication

These sections contain this con guration information:

• Default 802.1x Authentication Con guration

• 802.1x Authentication Con guration Guidelines

• Con guring 802.1x Readiness Check (optional)

• Con guring Voice Aware 802.1x Security (optional)

• Con guring 802.1x Violation Modes (optional)

• Con guring the Switch-to-RADIUS-Server Communication (required)

• Con guring the Host Mode (optional)

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 30/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

• Con guring Periodic Re-Authentication (optional)

• Manually Re-Authenticating a Client Connected to a Port (optional)

• Changing the Quiet Period (optional)

• Changing the Switch-to-Client Retransmission Time (optional)

• Setting the Switch-to-Client Frame-Retransmission Number (optional)

• Setting the Re-Authentication Number (optional)

• Con guring 802.1x Accounting (optional)

• Enabling MAC Move (optional)

• Con guring a Guest VLAN (optional)

• Con guring a Restricted VLAN (optional)

• Con guring the Inaccessible Authentication Bypass Feature (optional)

• Con guring 802.1x Authentication with WoL (optional)

• Con guring MAC Authentication Bypass (optional)

• Con guring NAC Layer 2 802.1x Validation (optional)

• Con guring an Authenticator and a Supplicant Switch with NEAT

• Con guring 802.1x Authentication with Downloadable ACLs and Redirect URLs

• Con guring Flexible Authentication Ordering

• Disabling 802.1x Authentication on the Port (optional)

• Resetting the 802.1x Authentication Con guration to the Default Values (optional)

Default 802.1x Authentication Con guration

Table 9-4 shows the default 802.1x authentication con guration.

Table 9-4 Default 802.1x Authentication Con guration 

Feature Default Setting

Switch 802.1x enable Disabled.
state

Per-port 802.1x enable Disabled (force-authorized).

state The port sends and receives normal tra c without 802.1x-based
authentication of the client.

AAA Disabled.

RADIUS server • None speci ed.

• IP address • 1812.
• UDP authentication • None speci ed.
port
• Key

Host mode Single-host mode.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 31/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Control direction Bidirectional control.

Periodic re- Disabled.

authentication

Number of seconds 3600 seconds.

between re-
authentication attempts

Re-authentication 2 times (number of times that the switch restarts the authentication process
number before the port changes to the unauthorized state).

Quiet period 60 seconds (number of seconds that the switch remains in the quiet state
following a failed authentication exchange with the client).

Retransmission time 30 seconds (number of seconds that the switch should wait for a response to
an EAP request/identity frame from the client before resending the request).

Maximum 2 times (number of times that the switch will send an EAP-request/identity
retransmission number frame before restarting the authentication process).

Client timeout period 30 seconds (when relaying a request from the authentication server to the
client, the amount of time the switch waits for a response before resending
the request to the client.)

Authentication server 30 seconds (when relaying a response from the client to the authentication
timeout period server, the amount of time the switch waits for a reply before resending the
response to the server.)
You can change this timeout period by using the authentication timer server
or dot1x timeout server-timeout interface con guration command.

Inactivity timeout Disabled.

Guest VLAN None speci ed.

Inaccessible Disabled.
authentication bypass

Restricted VLAN None speci ed.

Authenticator (switch) None speci ed.

mode

MAC authentication Disabled.

bypass

Voice-aware security Disabled

802.1x Authentication Con guration Guidelines

These section has con guration guidelines for these features:

• 802.1x Authentication

• VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass

• MAC Authentication Bypass

• Maximum Number of Allowed Devices Per Port

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 32/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

802.1x Authentication
• When 802.1x authentication is enabled, ports are authenticated before any other Layer 2 or Layer 3
features are enabled.

• If you try to change the mode of an 802.1x-enabled port (for example, from access to trunk), an error
message appears, and the port mode is not changed.

• If the VLAN to which an 802.1x-enabled port is assigned changes, this change is transparent and does
not a ect the switch. For example, this change occurs if a port is assigned to a RADIUS server-
assigned VLAN and is then assigned to a di erent VLAN after re-authentication.

If the VLAN to which an 802.1x port is assigned to shut down, disabled, or removed, the port
becomes unauthorized. For example, the port is unauthorized after the access VLAN to which a
port is assigned shuts down or is removed.

• The 802.1x protocol is supported on Layer 2 static-access ports, voice VLAN ports, and Layer 3 routed
ports, but it is not supported on these port types:

– Trunk port—If you try to enable 802.1x authentication on a trunk port, an error message appears,
and 802.1x authentication is not enabled. If you try to change the mode of an 802.1x-enabled
port to trunk, an error message appears, and the port mode is not changed.

– Dynamic ports—A port in dynamic mode can negotiate with its neighbor to become a trunk port.
If you try to enable 802.1x authentication on a dynamic port, an error message appears, and
802.1x authentication is not enabled. If you try to change the mode of an 802.1x-enabled port
to dynamic, an error message appears, and the port mode is not changed.

– Dynamic-access ports—If you try to enable 802.1x authentication on a dynamic-access (VLAN

Query Protocol [VQP]) port, an error message appears, and 802.1x authentication is not
enabled. If you try to change an 802.1x-enabled port to dynamic VLAN assignment, an error
message appears, and the VLAN con guration is not changed.

– EtherChannel port—Do not con gure a port that is an active or a not-yet-active member of an
EtherChannel as an 802.1x port. If you try to enable 802.1x authentication on an EtherChannel
port, an error message appears, and 802.1x authentication is not enabled.

– Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) destination ports—You can enable
802.1x authentication on a port that is a SPAN or RSPAN destination port. However, 802.1x
authentication is disabled until the port is removed as a SPAN or RSPAN destination port. You
can enable 802.1x authentication on a SPAN or RSPAN source port.

• Before globally enabling 802.1x authentication on a switch by entering the dot1x system-auth-control
global con guration command, remove the EtherChannel con guration from the interfaces on which
802.1x authentication and EtherChannel are con gured.

VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible

Authentication Bypass
• When 802.1x authentication is enabled on a port, you cannot con gure a port VLAN that is equal to a
voice VLAN.

• The 802.1x authentication with VLAN assignment feature is not supported on trunk ports, dynamic
ports, or with dynamic-access port assignment through a VMPS.

• You can con gure 802.1x authentication on a private-VLAN port, but do not con gure 802.1x
authentication with port security, a voice VLAN, a guest VLAN, a restricted VLAN, or a per-user ACL on
private-VLAN ports.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 33/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

• You can con gure any VLAN except an RSPAN VLAN, private VLAN, or a voice VLAN as an 802.1x
guest VLAN. The guest VLAN feature is not supported on internal VLANs (routed ports) or trunk ports; it
is supported only on access ports.

• After you con gure a guest VLAN for an 802.1x port to which a DHCP client is connected, you might
need to get a host IP address from a DHCP server. You can change the settings for restarting the
802.1x authentication process on the switch before the DHCP process on the client times out and tries
to get a host IP address from the DHCP server. Decrease the settings for the 802.1x authentication
process (authentication timer inactivity or dot1x timeout quiet-period) and authentication timer
reauthentication or dot1x timeout tx-period) interface con guration commands). The amount to
decrease the settings depends on the connected 802.1x client type.

• When con guring the inaccessible authentication bypass feature, follow these guidelines:

– The feature is supported on 802.1x port in single-host mode and multihosts mode.

– If the client is running Windows XP and the port to which the client is connected is in the critical-
authentication state, Windows XP might report that the interface is not authenticated.

– If the Windows XP client is con gured for DHCP and has an IP address from the DHCP server,
receiving an EAP-Success message on a critical port might not re-initiate the DHCP
con guration process.

– You can con gure the inaccessible authentication bypass feature and the restricted VLAN on an
802.1x port. If the switch tries to re-authenticate a critical port in a restricted VLAN and all the
RADIUS servers are unavailable, switch changes the port state to the critical authentication
state and remains in the restricted VLAN.

– You can con gure the inaccessible bypass feature and port security on the same switch port.

• You can con gure any VLAN except an RSPAN VLAN or a voice VLAN as an 802.1x restricted VLAN.
The restricted VLAN feature is not supported on internal VLANs (routed ports) or trunk ports; it is
supported only on access ports.

MAC Authentication Bypass

• Unless otherwise stated, the MAC authentication bypass guidelines are the same as the 802.1x
authentication guidelines. For more information, see the "802.1x Authentication" section.

• If you disable MAC authentication bypass from a port after the port has been authorized with its MAC
address, the port state is not a ected.

• If the port is in the unauthorized state and the client MAC address is not the authentication-server
database, the port remains in the unauthorized state. However, if the client MAC address is added to
the database, the switch can use MAC authentication bypass to re-authorize the port.

• If the port is in the authorized state, the port remains in this state until re-authorization occurs.

• You can con gure a timeout period for hosts that are connected by MAC authentication bypass but are
inactive. The range is 1to 65535 seconds. You must enable port security before con guring a time out
value. For more information, see the "Con guring Port Security" section.

Maximum Number of Allowed Devices Per Port

This is the maximum number of devices allowed on an 802.1x-enabled port:

• In single-host mode, only one device is allowed on the access VLAN. If the port is also con gured with
a voice VLAN, an unlimited number of Cisco IP phones can send and receive tra c through the voice
VLAN.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 34/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

• In multidomain authentication (MDA) mode, one device is allowed for the access VLAN, and one IP
phone is allowed for the voice VLAN.

• In multiple-host mode, only one 802.1x supplicant is allowed on the port, but an unlimited number of
non-802.1x hosts are allowed on the access VLAN. An unlimited number of devices are allowed on the
voice VLAN.

Con guring 802.1x Readiness Check

The 802.1x readiness check monitors 802.1x activity on all the switch ports and displays information
about the devices connected to the ports that support 802.1x. You can use this feature to determine if
the devices connected to the switch ports are 802.1x-capable.

The 802.1x readiness check is allowed on all ports that can be con gured for 802.1x. The readiness
check is not available on a port that is con gured as dot1x force-unauthorized.

Follow these guidelines to enable the readiness check on the switch:

• The readiness check is typically used before 802.1x is enabled on the switch.

• If you use the dot1x test eapol-capable privileged EXEC command without specifying an interface, all
the ports on the switch stack are tested.

• When you con gure the dot1x test eapol-capable command on an 802.1x-enabled port, and the link
comes up, the port queries the connected client about its 802.1x capability. When the client responds
with a noti cation packet, it is 802.1x-capable. A syslog message is generated if the client responds
within the timeout period. If the client does not respond to the query, the client is not 802.1x-capable.
No syslog message is generated.

• The readiness check can be sent on a port that handles multiple hosts (for example, a PC that is
connected to an IP phone). A syslog message is generated for each of the clients that respond to the
readiness check within the timer period.

Beginning in privileged EXEC mode, follow these steps to enable the 802.1x readiness check on the
switch:

  Command Purpose
Step 1  dot1x test eapol- Enable the 802.1x readiness check on the switch.
capable [interface (Optional) For interface-id specify the port on which to check
interface-id] for 802.1x readiness.
Note If you omit the optional interface keyword, all interfaces on
the switch are tested.

Step 1  con gure terminal (Optional) Enter global con guration mode.

Step 2  dot1x test timeout (Optional) Con gure the timeout used to wait for EAPOL response.
timeout The range is from 1 to 65535 seconds. The default is 10 seconds.

Step 3  end (Optional) Return to privileged EXEC mode.

Step 4  show running-con g (Optional) Verify your modi ed timeout values.

This example shows how to enable a readiness check on a switch to query a port. It also shows the
response received from the queried port verifying that the device connected to it is 802.1x-capable:

switch# dot1x test eapol-capable interface gigabitethernet0/13

DOT1X_PORT_EAPOL_CAPABLE:DOT1X: MAC 00-01-02-4b-f1-a3 on gigabitethernet0/13 is EAPOL
capable
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 35/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Con guring Voice Aware 802.1x Security

You use the voice aware 802.1x security feature on the switch to disable only the VLAN on which a
security violation occurs, whether it is a data or voice VLAN. You can use this feature in IP phone
deployments where a PC is connected to the IP phone. A security violation found on the data VLAN
results in the shutdown of only the data VLAN. The tra c on the voice VLAN ows through the switch
without interruption.

Follow these guidelines to con gure voice aware 802.1x voice security on the switch:

• You enable voice aware 802.1x security by entering the errdisable detect cause security-violation
shutdown vlan global con guration command. You disable voice aware 802.1x security by entering the
no version of this command. This command applies to all 802.1x-con gured ports in the switch.

Note If you do not include the shutdown vlan keywords, the entire port is shut down when it enters the
error-disabled state.

• If you use the errdisable recovery cause security-violation global con guration command to
con gure error-disabled recovery, the port is automatically re-enabled. If error-disabled recovery is not
con gured for the port, you re-enable it by using the shutdown and no-shutdown interface
con guration commands.

• You can re-enable individual VLANs by using the clear errdisable interface interface-id vlan [vlan-list]
privileged EXEC command. If you do not specify a range, all VLANs on the port are enabled.

Beginning in privileged EXEC mode, follow these steps to enable voice aware 802.1x security:

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  errdisable detect cause Shut down any VLAN on which a security violation error
security-violation shutdown occurs.
vlan Note If the shutdown vlan keywords are not included, the
entire port enters the error-disabled state and shuts
down.

Step 3  errdisable recovery cause (Optional) Enable automatic per-VLAN error recovery.
security-violation

Step 4  clear errdisable interface (Optional) Reenable individual VLANs that have been error
interface-id vlan [vlan-list] disabled.
• For interface-id specify the port on which to reenable
individual VLANs.
• (Optional) For vlan-list specify a list of VLANs to be re-
enabled. If vlan-list is not speci ed, all VLANs are re-
enabled.

Step 5  shutdown (Optional) Re-enable an error-disabled VLAN, and clear all

no-shutdown error-disable indications.

Step 6  end Return to privileged EXEC mode.

Step 7  show errdisable detect Verify your entries.

Step 8  (Optional) Save your entries in the con guration le.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 36/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

copy running-con g
startup-con g

This example shows how to con gure the switch to shut down any VLAN on which a security violation
error occurs:

Switch(config)# errdisable detect cause security-violation shutdown vlan

This example shows how to re-enable all VLANs that were error disabled on port Gigabit Ethernet 0/2.

Switch# clear errdisable interface gigabitethernet0/2 vlan

You can verify your settings by entering the show errdisable detect privileged EXEC command.

Con guring 802.1x Violation Modes

You can con gure an 802.1x port so that it shuts down, generates a syslog error, or discards packets
from a new device when:

• a device connects to an 802.1x-enable port

• the maximum number of allowed about devices have been authenticated on the port

Beginning in privileged EXEC mode, follow these steps to con gure the security violation actions on the
switch:

  Command Purpose
Step 1  con gure Enter global con guration mode.
terminal

Step 2  aaa new-model Enable AAA.

Step 3  aaa Create an 802.1x authentication method list.

authentication To create a default list to use when a named list is not speci ed in the
dot1x {default} authentication command, use the default keyword followed by the method
method1 that is to be used in default situations. The default method list is
automatically applied to all ports.
For method1, enter the group radius keywords to use the list of all RADIUS
servers for authentication.
Note Though other keywords are visible in the command-line help string,
only the group radius keywords are supported.

Step 4  interface Specify the port connected to the client that is to be enabled for 802.1x
interface-id authentication, and enter interface con guration mode.

Step 5  switchport Set the port to access mode.

mode access

Step 6  authentication Con gure the violation mode. The keywords have these meanings:
violation • shutdown-Error disable the port.
shutdown |
restrict | • restrict-Generate a syslog error.
protect} • protect-Drop packets from any new device that sends tra c to the port.
or
dot1x violation-
mode

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 37/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

{shutdown |
restrict |
protect}

Step 7  end Return to privileged EXEC mode.

Step 8  show Verify your entries.

authentication
or
show dot1x

Step 9  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

Con guring 802.1x Authentication

To con gure 802.1x port-based authentication, you must enable authentication, authorization, and
accounting (AAA) and specify the authentication method list. A method list describes the sequence and
authentication method to be queried to authenticate a user.

To allow per-user ACLs or VLAN assignment, you must enable AAA authorization to con gure the switch
for all network-related service requests.

This is the 802.1x AAA process:

Step 1 A user connects to a port on the switch.

Step 2 Authentication is performed.

Step 3 VLAN assignment is enabled, as appropriate, based on the RADIUS server con guration.

Step 4 The switch sends a start message to an accounting server.

Step 5 Re-authentication is performed, as necessary.

Step 6 The switch sends an interim accounting update to the accounting server, that is based on the
result of re-authentication.

Step 7 The user disconnects from the port.

Step 8 The switch sends a stop message to the accounting server.

Beginning in privileged EXEC mode, follow these steps to con gure 802.1x port-based authentication:

  Command Purpose
Step 1  con gure Enter global con guration mode.
terminal

Step 2  aaa new- Enable AAA.

model

Step 3  aaa Create an 802.1x authentication method list.

authentication To create a default list to use when a named list is not speci ed in the
dot1x {default} authentication command, use the default keyword followed by the method
method1 to use in default situations. The default method list is automatically applied
to all ports.
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 38/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

For method1, enter the group radius keywords to use the list of all RADIUS
servers for authentication.
Note Though other keywords are visible in the command-line help string,
only the group radius keywords are supported.

Step 4  dot1x system- Enable 802.1x authentication globally on the switch.

auth-control

Step 5  aaa (Optional) Con gure the switch to use user-RADIUS authorization for all
authorization network-related service requests, such as per-user ACLs or VLAN
network assignment.
{default} For per-user ACLs, single-host mode must be con gured. This setting is
group radius the default.

Step 6  radius-server (Optional) Specify the IP address of the RADIUS server.

host ip-
address

Step 7  radius-server (Optional) Specify the authentication and encryption key used between the
key string switch and the RADIUS daemon running on the RADIUS server.

Step 8  interface Specify the port connected to the client to enable for 802.1x authentication,
interface-id and enter interface con guration mode.

Step 9  switchport (Optional) Set the port to access mode only if you con gured the RADIUS
mode access server in Step 6 and Step 7.

Step 10  authentication Enable 802.1x authentication on the port.

port-control For feature interaction information, see the "802.1x Authentication
auto Con guration Guidelines" section.
or
dot1x port-
control auto

Step 11  end Return to privileged EXEC mode.

Step 12  show Verify your entries.

authentication
or
show dot1x

Step 13  copy running- (Optional) Save your entries in the con guration le.
con g
startup-con g

Con guring the Switch-to-RADIUS-Server Communication

RADIUS security servers are identi ed by their hostname or IP address, hostname and speci c UDP port
numbers, or IP address and speci c UDP port numbers. The combination of the IP address and the UDP
port number creates a unique identi er, which enables RADIUS requests to be sent to multiple UDP ports
on a server at the same IP address. If two di erent host entries on the same RADIUS server are
con gured for the same service—for example, authentication—the second host entry con gured acts as
the fail-over backup to the rst one. The RADIUS host entries are tried in the order in which they were
con gured.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 39/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Beginning in privileged EXEC mode, follow these steps to con gure the RADIUS server parameters on
the switch. This procedure is required.

  Command Purpose
Step 1  con gure Enter global con guration mode.
terminal

Step 2  radius-server Con gure the RADIUS server parameters.

host For hostname | ip-address, specify the hostname or IP address of the remote
{hostname | RADIUS server.
ip-address}
auth-port For auth-port port-number, specify the UDP destination port for
port-number authentication requests. The default is 1812. The range is 0 to 65536.
key string For key string, specify the authentication and encryption key used between
the switch and the RADIUS daemon running on the RADIUS server. The key
is a text string that must match the encryption key used on the RADIUS
server.
Note Always con gure the key as the last item in the radius-server host
command syntax because leading spaces are ignored, but spaces
within and at the end of the key are used. If you use spaces in the key,
do not enclose the key in quotation marks unless the quotation marks
are part of the key. This key must match the encryption used on the
RADIUS daemon.
If you want to use multiple RADIUS servers, re-enter this command.

Step 3  end Return to privileged EXEC mode.

Step 4  show running- Verify your entries.

con g

Step 5  copy running- (Optional) Save your entries in the con guration le.
con g
startup-con g

To clear the speci ed RADIUS server, use the no radius-server host {hostname | ip-address} global
con guration command.

This example shows how to specify the server with IP address 172.20.39.46 as the RADIUS server, to
use port 1612 as the authorization port, and to set the encryption key to rad123, matching the key on the
RADIUS server:

Switch(config)# radius-server host 172.l20.39.46 auth-port 1612 key rad123

You can globally con gure the timeout, retransmission, and encryption key values for all RADIUS servers
by using the radius-server host global con guration command. If you want to con gure these options
on a per-server basis, use the radius-server timeout, radius-server retransmit and the radius-server
key global con guration commands. For more information, see the "Con guring Settings for All RADIUS
Servers" section.

You also need to con gure some settings on the RADIUS server. These settings include the IP address of
the switch and the key string to be shared by both the server and the switch. For more information, see
the RADIUS server documentation.

Con guring the Host Mode

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 40/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Beginning in privileged EXEC mode, follow these steps to allow a single host (client) or multiple hosts on
an 802.1x-authorized port. Use the multi-domain keyword to con gure multidomain authentication
(MDA) to enable authentication of both a host and a voice device, such as an IP phone (Cisco or non-
Cisco) on the same switch port.

This procedure is optional.

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  radius-server vsa send Con gure the network access server to recognize and use
authentication vendor-speci c attributes (VSAs).

Step 3  interface interface-id Specify the port to which multiple hosts are indirectly
attached, and enter interface con guration mode.

Step 4  authentication host-mode The keywords have these meanings:

[multi-auth | multi-domain | • multi-auth-Allow one client on the voice VLAN and multiple
multi-host | single-host] authenticated clients on the data VLAN. Each host is
or individually authenticated.
dot1x host-mode {single- Note The multi-auth keyword is only available with the
host | multi-host | multi- authentication host-mode command.
domain} • multi-host-Allow multiple hosts on an 802.1x-authorized
port after a single host has been authenticated.
• multi-domain-Allow both a host and a voice device, such
as an IP phone (Cisco or non-Cisco), to be authenticated on
an 802.1x-authorized port.
Note You must con gure the voice VLAN for the IP phone
when the host mode is set to multi-domain. For more
information, see Chapter 14 "Con guring Voice VLAN."
• single-host-Allow a single host (client) on an 802.1x-
authorized port.
Make sure that the authentication port-control or dot1x
port-control interface con guration command set is set to
auto for the speci ed interface.

Step 5  switchport voice vlan vlan-id (Optional) Con gure the voice VLAN.

Step 6  end Return to privileged EXEC mode.

Step 7  show authentication Verify your entries.

interface interface-id
or
show dot1x interface
interface-id

Step 8  copy running-con g (Optional) Save your entries in the con guration le.
startup-con g

To disable multiple hosts on the port, use the no authentication host-mode or the no dot1x host-mode
multi-host interface con guration command.

This example shows how to enable 802.1x authentication and to allow multiple hosts:

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 41/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Switch(config)# interface gigabitethernet0/1

Switch(config-if)# dot1x port-control auto
Switch(config-if)# dot1x host-mode multi-host
Switch(config-if)# end

This example shows how to enable MDA and to allow both a host and a voice device on the port:

Switch(config)# interface gigabitethernet0/1

Switch(config-if)# dot1x port-control auto
Switch(config-if)# dot1x host-mode multi-domain
Switch(config-if)# switchport voice vlan 101
Switch(config-if)# end

Con guring Periodic Re-Authentication

You can enable periodic 802.1x client re-authentication and specify how often it occurs. If you do not
specify a time period before enabling re-authentication, the number of seconds between attempts
is 3600.

Beginning in privileged EXEC mode, follow these steps to enable periodic re-authentication of the client
and to con gure the number of seconds between re-authentication attempts. This procedure is optional.

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  interface interface-id Specify the port to be con gured, and enter interface
con guration mode.

Step 3  authentication periodic Enable periodic re-authentication of the client, which is

or disabled by default.

dot1x reauthentication

Step 4  authentication timer Set the number of seconds between re-authentication

{{[inactivity | attempts.
reauthenticate] [server | The authentication timer keywords have these meanings:
am]} {restart value}}
• inactivity—Interval in seconds after which if there is no
or activity from the client then it is unauthorized
dot1x timeout reauth- • reauthenticate—Time in seconds after which an automatic
period {seconds | server} re-authentication attempt is be initiated
• server am—Interval in seconds after which an attempt is made
to authenticate an unauthorized port
• restart value—Interval in seconds after which an attempt is
made to authenticate an unauthorized port
The dot1x timeout reauth-period keywords have these
meanings:
• seconds—Sets the number of seconds from 1 to 65535; the
default is 3600 seconds.
• server—Sets the number of seconds based on the value of
the Session-Timeout RADIUS attribute (Attribute[27]) and the
Termination-Action RADIUS attribute (Attribute [29]).
This command a ects the behavior of the switch only if
periodic re-authentication is enabled.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 42/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Step 5  end Return to privileged EXEC mode.

Step 6  show authentication Verify your entries.

interface-id
or
show dot1x interface
interface-id

Step 7  copy running-con g (Optional) Save your entries in the con guration le.
startup-con g

To disable periodic re-authentication, use the no authentication periodic or the no dot1x

reauthentication interface con guration command. To return to the default number of seconds between
re-authentication attempts, use the no authentication timer or the no dot1x timeout reauth-period
interface con guration command.

This example shows how to enable periodic re-authentication and set the number of seconds between
re-authentication attempts to 4000:

Switch(config-if)# dot1x reauthentication

Switch(config-if)# dot1x timeout reauth-period 4000

Manually Re-Authenticating a Client Connected to a Port

You can manually re-authenticate the client connected to a speci c port at any time by entering the
dot1x re-authenticate interface interface-id privileged EXEC command. This step is optional. If you
want to enable or disable periodic re-authentication, see the "Con guring Periodic Re-Authentication"
section.

This example shows how to manually re-authenticate the client connected to a port:

Switch# dot1x re-authenticate interface gigabitethernet0/1

Changing the Quiet Period

When the switch cannot authenticate the client, the switch remains idle for a set period of time and then
tries again. The dot1x timeout quiet-period interface con guration command controls the idle period. A
failed client authentication might occur because the client provided an invalid password. You can provide
a faster response time to the user by entering a number smaller than the default.

Beginning in privileged EXEC mode, follow these steps to change the quiet period. This procedure is
optional.

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  interface interface- Specify the port to be con gured, and enter interface con guration
id mode.

Step 3  dot1x timeout Set the number of seconds that the switch remains in the quiet state
quiet-period after a failed authentication exchange with the client.
seconds The range is 1 to 65535 seconds; the default is 60.

Step 4  end Return to privileged EXEC mode.

Step 5  show authentication Verify your entries.

interface-id
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 43/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

or
show dot1x
interface interface-
id

Step 6  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

To return to the default quiet time, use the no dot1x timeout quiet-period interface con guration
command.

This example shows how to set the quiet time on the switch to 30 seconds:

Switch(config-if)# dot1x timeout quiet-period 30

Changing the Switch-to-Client Retransmission Time

The client responds to the EAP-request/identity frame from the switch with an EAP-response/identity
frame. If the switch does not receive this response, it waits a set period of time (known as the
retransmission time) and then resends the frame.

Note You should change the default value of this command only to adjust for unusual circumstances
such as unreliable links or speci c behavioral problems with certain clients and authentication
servers.

Beginning in privileged EXEC mode, follow these steps to change the amount of time that the switch
waits for client noti cation. This procedure is optional.

  Command Purpose
Step 1  con gure Enter global con guration mode.
terminal

Step 2  interface Specify the port to con gure, and enter interface con guration mode.
interface-id

Step 3  dot1x timeout tx- Set the number of seconds that the switch waits for a response to an
period seconds EAP-request/identity frame from the client before resending the request.
The range is 1 to 65535 seconds; the default is 5.

Step 4  end Return to privileged EXEC mode.

Step 5  show Verify your entries.

authentication
interface-id
or
show dot1x
interface
interface-id

Step 6  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 44/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

To return to the default retransmission time, use the no dot1x timeout tx-period interface con guration
command.

This example shows how to set 60 as the number of seconds that the switch waits for a response to an
EAP-request/identity frame from the client before resending the request:

Switch(config-if)# dot1x timeout tx-period 60

Setting the Switch-to-Client Frame-Retransmission Number

You can change the number of times that the switch sends an EAP-request/identity frame (assuming no
response is received) to the client before restarting the authentication process.

Note You should change the default value of this command only to adjust for unusual circumstances
such as unreliable links or speci c behavioral problems with certain clients and authentication
servers.

Beginning in privileged EXEC mode, follow these steps to set the switch-to-client frame-retransmission
number. This procedure is optional.

  Command Purpose
Step 1  con gure Enter global con guration mode.
terminal

Step 2  interface Specify the port to be con gured, and enter interface con guration mode.
interface-id

Step 3  dot1x max- Set the number of times that the switch sends an EAP-request/identity
reauth-req count frame to the client before restarting the authentication process. The range
is 1 to 10; the default is 2.

Step 4  end Return to privileged EXEC mode.

Step 5  show Verify your entries.

authentication
interface
interface-id
or
show dot1x
interface
interface-id

Step 6  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

To return to the default retransmission number, use the no dot1x max-req interface con guration
command.

This example shows how to set 5 as the number of times that the switch sends an EAP-request/identity
request before restarting the authentication process:

Switch(config-if)# dot1x max-req 5

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 45/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Setting the Re-Authentication Number

You can also change the number of times that the switch restarts the authentication process before the
port changes to the unauthorized state.

Note You should change the default value of this command only to adjust for unusual circumstances
such as unreliable links or speci c behavioral problems with certain clients and authentication
servers.

Beginning in privileged EXEC mode, follow these steps to set the re-authentication number. This
procedure is optional.

  Command Purpose
Step 1  con gure Enter global con guration mode.
terminal

Step 2  interface Specify the port to be con gured, and enter interface con guration
interface-id mode.

Step 3  dot1x max- Set the number of times that the switch restarts the authentication
reauth-req count process before the port changes to the unauthorized state. The range is
0 to 10; the default is 2.

Step 4  end Return to privileged EXEC mode.

Step 5  show Verify your entries.

authentication
interface
interface-id
or
show dot1x
interface
interface-id

Step 6  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

To return to the default re-authentication number, use the no dot1x max-reauth-req interface
con guration command.

This example shows how to set 4 as the number of times that the switch restarts the authentication
process before the port changes to the unauthorized state:

Switch(config-if)# dot1x max-reauth-req 4

Enabling MAC Move

MAC move allows an authenticated host to move from one port on the switch to another.

Beginning in privileged EXEC mode, follow these steps to globally enable MAC move on the switch. This
procedure is optional.

Command Purpose

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 46/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

con gure terminal Enter global con guration mode.

authentication mac-move permit Enable

end Return to privileged EXEC mode.

show run Verify your entries.

copy running-con g startup-con g (Optional) Save your entries in the con guration le.

This example shows how to globally enable MAC move on a switch:

Switch(config)# authentication mac-move permit

Con guring 802.1x Accounting

Enabling AAA system accounting with 802.1x accounting allows system reload events to be sent to the
accounting RADIUS server for logging. The server can then infer that all active 802.1x sessions are
closed.

Because RADIUS uses the unreliable UDP transport protocol, accounting messages might be lost due to
poor network conditions. If the switch does not receive the accounting response message from the
RADIUS server after a con gurable number of retransmissions of an accounting request, this system
message appears:

Accounting message %s for session %s failed to receive Accounting Response.

When the stop message is not sent successfully, this message appears:

00:09:55: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.201:1645,1646 is not responding.

Note You must con gure the RADIUS server to perform accounting tasks, such as logging start, stop,
and interim-update messages and time stamps. To turn on these functions, enable logging of
"Update/Watchdog packets from this AAA client" in your RADIUS server Network Con guration
tab. Next, enable "CVS RADIUS Accounting" in your RADIUS server System Con guration tab.

Beginning in privileged EXEC mode, follow these steps to con gure 802.1x accounting after AAA is
enabled on your switch. This procedure is optional.

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  interface interface-id Specify the port to be con gured, and enter interface con guration
mode.

Step 3  aaa accounting dot1x Enable 802.1x accounting using the list of all RADIUS servers.
default start-stop
group radius

Step 4  aaa accounting (Optional) Enables system accounting (using the list of all RADIUS
system default start- servers) and generates system accounting reload event messages
stop group radius when the switch reloads.

Step 5  end Return to privileged EXEc mode.

Step 6  show running-con g Verify your entries.

Step 7  (Optional) Saves your entries in the con guration le.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 47/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

copy running-con g
startup-con g

Use the show radius statistics privileged EXEC command to display the number of RADIUS messages
that do not receive the accounting response message.

This example shows how to con gure 802.1x accounting. The rst command con gures the RADIUS
server, specifying 1813 as the UDP port for accounting:

Switch(config)# radius-server host 172.120.39.46 auth-port 1812 acct-port 1813 key rad123
Switch(config)# aaa accounting dot1x default start-stop group radius
Switch(config)# aaa accounting system default start-stop group radius

Con guring a Guest VLAN

When you con gure a guest VLAN, clients that are not 802.1x-capable are put into the guest VLAN when
the server does not receive a response to its EAP request/identity frame. Clients that are 802.1x-capable
but that fail authentication are not granted network access. The switch supports guest VLANs in single-
host or multiple-hosts mode.

Beginning in privileged EXEC mode, follow these steps to con gure a guest VLAN. This procedure is
optional.

  Command Purpose
Step 1  con gure Enter global con guration mode.
terminal

Step 2  interface Specify the port to be con gured, and enter interface con guration mode.
interface-id For the supported port types, see the "802.1x Authentication Con guration
Guidelines" section.

Step 3  switchport Set the port to access mode

mode access or
or Con gure the Layer 2 port as a private-VLAN host port.
switchport
mode private-
vlan host

Step 4  authentication Enable 802.1x authentication on the port.

port-control
auto
or
dot1x port-
control auto

Step 5  dot1x guest- Specify an active VLAN as an 802.1x guest VLAN. The range is 1 to 4094.
vlan vlan-id You can con gure any active VLAN except an internal VLAN (routed port), an
RSPAN VLAN, a primary private VLAN, or a voice VLAN as an 802.1x guest
VLAN.

Step 6  end Return to privileged EXEC mode.

Step 7  show Verify your entries.

authentication
interface-id

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 48/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

or
show dot1x
interface
interface-id

Step 8  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

To disable and remove the guest VLAN, use the no dot1x guest-vlan interface con guration command.
The port returns to the unauthorized state.

This example shows how to enable VLAN 2 as an 802.1x guest VLAN:

Switch(config)# interface gigabitethernet0/2

Switch(config-if)# dot1x guest-vlan 2

This example shows how to set 3 as the quiet time on the switch, to set 15 as the number of seconds
that the switch waits for a response to an EAP-request/identity frame from the client before re-sending
the request, and to enable VLAN 2 as an 802.1x guest VLAN when an 802.1x port is connected to a
DHCP client:

Switch(config-if)# dot1x timeout quiet-period 3

Switch(config-if)# dot1x timeout tx-period 15
Switch(config-if)# dot1x guest-vlan 2

Con guring a Restricted VLAN

When you con gure a restricted VLAN on a switch, clients that are 802.1x-compliant are moved into the
restricted VLAN when the authentication server does not receive a valid username and password. The
switch supports restricted VLANs only in single-host mode.

Beginning in privileged EXEC mode, follow these steps to con gure a restricted VLAN. This procedure is
optional.

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  interface interface- Specify the port to be con gured, and enter interface con guration
id mode. For the supported port types, see the "802.1x Authentication
Con guration Guidelines" section.

Step 3  switchport mode Set the port to access mode,

access or
or Con gure the Layer 2 port as a private-VLAN host port.
switchport mode
private-vlan host

Step 4  authentication Enable 802.1x authentication on the port.

port-control auto
or
dot1x port-control
auto

Step 5  authentication Specify an active VLAN as an 802.1x restricted VLAN. The range is 1
event fail action to 4094.
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 49/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

authorize vlan-id You can con gure any active VLAN except an internal VLAN (routed
port), an RSPAN VLAN, a primary private VLAN, or a voice VLAN as an
802.1x restricted VLAN.

Step 6  end Return to privileged EXEC mode.

Step 7  show (Optional) Verify your entries.

authentication
interface-id
or
show dot1x
interface interface-
id

Step 8  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

To disable and remove the restricted VLAN, use the no dot1x auth-fail vlan interface con guration
command. The port returns to the unauthorized state.

This example shows how to enable VLAN 2 as an 802.1x restricted VLAN:

-if)# dot1x auth-fail vlan 2

You can con gure the maximum number of authentication attempts allowed before a user is assigned to
the restricted VLAN by using the dot1x auth-fail max-attempts interface con guration command. The
range of allowable authentication attempts is 1 to 3. The default is 3 attempts.

Beginning in privileged EXEC mode, follow these steps to con gure the maximum number of allowed
authentication attempts. This procedure is optional.

  Command Purpose
Step 1  con gure Enter global con guration mode.
terminal

Step 2  interface Specify the port to be con gured, and enter interface con guration mode.
interface-id For the supported port types, see the "802.1x Authentication
Con guration Guidelines" section.

Step 3  switchport mode Set the port to access mode,

access or
or Con gure the Layer 2 port as a private-VLAN host port.
switchport mode
private-vlan host

Step 4  authentication Enable 802.1x authentication on the port.

port-control auto
or
dot1x port-
control auto

Step 5  dot1x auth-fail Specify an active VLAN as an 802.1x restricted VLAN. The range is 1
vlan vlan-id to 4094.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 50/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

You can con gure any active VLAN except an internal VLAN (routed port),
an RSPAN VLAN, a primary private VLAN, or a voice VLAN as an 802.1x
restricted VLAN.

Step 6  dot1x auth-fail Specify a number of authentication attempts to allow before a port moves
max-attempts to the restricted VLAN. The range is 1 to 3, and the default is 3.
max attempts

Step 7  end Return to privileged EXEC mode.

Step 8  show (Optional) Verify your entries.

authentication
interface-id
or
show dot1x
interface
interface-id

Step 9  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

To return to the default value, use the no dot1x auth-fail max-attempts interface con guration
command.

This example shows how to set 2 as the number of authentication attempts allowed before the port
moves to the restricted VLAN:

Switch(config-if)# dot1x auth-fail max-attempts 2

Con guring the Inaccessible Authentication Bypass Feature

You can con gure the inaccessible bypass feature, also referred to as critical authentication or the AAA
fail policy.

Beginning in privileged EXEC mode, follow these steps to con gure the port as a critical port and enable
the inaccessible authentication bypass feature. This procedure is optional.

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  radius-server dead- (Optional) Set the conditions that are used to decide when a
criteria time time tries tries RADIUS server is considered unavailable or dead.
The range for time is from 1 to 120 seconds. The switch
dynamically determines the default seconds value that is 10 to
60 seconds.
The range for tries is from 1 to 100. The switch dynamically
determines the default tries parameter that is 10 to 100.

Step 3  radius-server deadtime (Optional) Set the number of minutes that a RADIUS server is
minutes not sent requests. The range is from 0 to 1440 minutes (24
hours). The default is 0 minutes.

Step 4  radius-server host ip- (Optional) Con gure the RADIUS server parameters by using
address [acct-port udp- these keywords:
port] [auth-port udp-port]

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 51/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

[test username name • acct-port udp-port—Specify the UDP port for the RADIUS
[idle-time time] [ignore- accounting server. The range for the UDP port number is from
acct-port] [ignore-auth- 0 to 65536. The default is 1646.
port]] [key string] • auth-port udp-port—Specify the UDP port for the RADIUS
authentication server. The range for the UDP port number is
from 0 to 65536. The default is 1645.
Note You should con gure the UDP port for the RADIUS
accounting server and the UDP port for the RADIUS
authentication server to nondefault values.
• test username name—Enable automated testing of the
RADIUS server status, and specify the username to be used.
• idle-time time—Set the interval of time in minutes after which
the switch sends test packets to the server. The range is from
1 to 35791 minutes. The default is 60 minutes (1 hour).
• ignore-acct-port—Disable testing on the RADIUS-server
accounting port.
• ignore-auth-port—Disable testing on the RADIUS-server
authentication port.
• key string—Specify the authentication and encryption key for
all RADIUS communication between the switch and the
RADIUS daemon.
Note Always con gure the key as the last item in the radius-
server host command syntax because leading spaces are
ignored, but spaces within and at the end of the key are
used. If you use spaces in the key, do not enclose the key
in quotation marks unless the quotation marks are part of
the key. This key must match the encryption used on the
RADIUS daemon.
You can also con gure the authentication and encryption key
by using the radius-server key {0 string | 7 string | string}
global con guration command.

Step 5  dot1x critical {eapol | (Optional) Con gure the parameters for inaccessible
recovery delay authentication bypass:
milliseconds} eapol—Specify that the switch sends an EAPOL-Success
message when the switch successfully authenticates the
critical port.
recovery delay milliseconds—Set the recovery delay period
during which the switch waits to re-initialize a critical port
when a RADIUS server that was unavailable becomes available.
The range is from 1 to 10000 milliseconds. The default is 1000
milliseconds (a port can be re-initialized every second).

Step 6  interface interface-id Specify the port to be con gured, and enter interface
con guration mode. For the supported port types, see the
"802.1x Authentication Con guration Guidelines" section.

Step 7  authentication event Use these keywords to move hosts on the port if the RADIUS
server dead action server is unreachable:
[authorize | reinitialize] • authorize-Move any new hosts trying to authenticate to the
vlan vlan-id user-speci ed critical VLAN.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 52/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

• reinitialize-Move all authorized hosts on the port to the user-

speci ed critical VLAN.

Step 8  dot1x critical [recovery Enable the inaccessible authentication bypass feature, and use
action reinitialize | vlan these keywords to con gure the feature:
vlan-id] • recovery action reinitialize—Enable the recovery feature, and
specify that the recovery action is to authenticate the port
when an authentication server is available.
• vlan vlan-id—Specify the access VLAN to which the switch
can assign a critical port. The range is from 1 to 4094.

Step 9  end Return to privileged EXEC mode.

Step 10  show authentication (Optional) Verify your entries.

interface interface-id
or
show dot1x interface
interface-id

Step 11  copy running-con g (Optional) Save your entries in the con guration le.
startup-con g

To return to the RADIUS server default settings, use the no radius-server dead-criteria, the no radius-
server deadtime, and the no radius-server host global con guration commands. To return to the
default settings of inaccessible authentication bypass, use the no dot1x critical {eapol | recovery delay}
global con guration command. To disable inaccessible authentication bypass, use the no dot1x critical
interface con guration command.

This example shows how to con gure the inaccessible authentication bypass feature:

Switch(config)# radius-server dead-criteria time 30 tries 20

Switch(config)# radius-server deadtime 60
Switch(config)# radius-server host 1.1.1.2 acct-port 1550 auth-port 1560 test username
user1 idle-time 30 key abc1234
Switch(config)# dot1x critical eapol
Switch(config)# dot1x critical recovery delay 2000
Switch(config)# interface gigabitethernet0/2
Switch(config)# radius-server deadtime 60
Switch(config-if)# dot1x critical
Switch(config-if)# dot1x critical recovery action reinitialize
Switch(config-if)# dot1x critical vlan 20
Switch(config-if)# end

Con guring 802.1x Authentication with WoL

Beginning in privileged EXEC mode, follow these steps to enable 802.1x authentication with WoL. This
procedure is optional.

  Command Purpose
Step 1  con gure Enter global con guration mode.
terminal

Step 2  interface Specify the port to be con gured, and enter interface con guration mode.
interface-id For the supported port types, see the "802.1x Authentication
Con guration Guidelines" section.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 53/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Step 3  authentication Enable 802.1x authentication with WoL on the port, and use these
control-direction keywords to con gure the port as bidirectional or unidirectional.
{both | in} • both—Sets the port as bidirectional. The port cannot receive packets
or from or send packets to the host. By default, the port is bidirectional.
dot1x control- • in—Sets the port as unidirectional. The port can send packets to the host
direction {both | but cannot receive packets from the host.
in}

Step 4  end Return to privileged EXEC mode.

Step 5  show Verify your entries.

authentication
interface
interface-id
or
show dot1x
interface
interface-id

Step 6  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

To disable 802.1x authentication with WoL, use the no authentication control-direction or no dot1x
control-direction interface con guration command.

These examples show how to enable 802.1x authentication with WoL and set the port as bidirectional:

Switch(config-if)# authentication control-direction both

or

Switch(config-if)# dot1x control-direction both

Con guring MAC Authentication Bypass

Beginning in privileged EXEC mode, follow these steps to enable MAC authentication bypass. This
procedure is optional.

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  interface interface- Specify the port to be con gured, and enter interface con guration
id mode. For the supported port types, see the "802.1x Authentication
Con guration Guidelines" section.

Step 3  authentication Enable 802.1x authentication on the port.

port-control auto
or
dot1x port-control
auto

Step 4  dot1x mac-auth- Enable MAC authentication bypass.

bypass [eap | (Optional) Use the eap keyword to con gure the switch to use EAP for
authorization.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 54/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

timeout activity (Optional) Use the timeout activity keywords to con gured the number
{value}] of seconds that a connected host can be inactive before it is placed in
an unauthorized state. The range is 1 to 65535.
You must enable port security before con guring a timeout value. For
more information, see the "Con guring Port Security" section.

Step 5  end Return to privileged EXEC mode.

Step 6  show Verify your entries.

authentication
interface-id
or
show dot1x
interface interface-
id

Step 7  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

To disable MAC authentication bypass, use the no dot1x mac-auth-bypass interface con guration
command.

This example shows how to enable MAC authentication bypass:

Switch(config-if)# dot1x mac-auth-bypass

Con guring 802.1x User Distribution

Beginning in global con guration, follow these steps to con gure a VLAN group and to map a VLAN to it:

  Command Purpose
Step 1  vlan group vlan-group-name Con gure a VLAN group, and map a single VLAN or a
vlan-list vlan-list range of VLANs to it.

Step 2  show vlan group all vlan-group- Verify the con guration.
name

Step 3  no vlan group vlan-group-name Clear the VLAN group con guration or elements of the
vlan-list vlan-list VLAN group con guration.

This example shows how to con gure the VLAN groups, to map the VLANs to the groups, to and verify
the VLAN group con gurations and mapping to the speci ed VLANs:

switch(config)# vlan group eng-dept vlan-list 10

switch(config)# show vlan group group-name eng-dept
Group Name Vlans Mapped
------------- --------------
eng-dept 10
switch# show dot1x vlan-group all
Group Name Vlans Mapped
------------- --------------
eng-dept 10
hr-dept 20

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 55/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

This example shows how to add a VLAN to an existing VLAN group and to verify that the VLAN was
added:

switch(config)# vlan group eng-dept vlan-list 30

switch(config)# show vlan group eng-dept
Group Name Vlans Mapped
------------- --------------
eng-dept 10,30

This example shows how to remove a VLAN from a VLAN group:

switch# no vlan group eng-dept vlan-list 10

This example shows that when all the VLANs are cleared from a VLAN group, the VLAN group is cleared:

switch(config)# no vlan group eng-dept vlan-list 30

Vlan 30 is successfully cleared from vlan group eng-dept.
switch(config)# show vlan group group-name eng-dept

This example shows how to clear all the VLAN groups:

switch(config)# no vlan group end-dept vlan-list all

switch(config)# show vlan-group all

For more information about these commands, see the Cisco IOS Security Command Reference.

Con guring NAC Layer 2 802.1x Validation

You can con gure NAC Layer 2 802.1x validation, which is also referred to as 802.1x authentication with
a RADIUS server.

Beginning in privileged EXEC mode, follow these steps to con gure NAC Layer 2 802.1x validation. The
procedure is optional.

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  interface Specify the port to be con gured, and enter interface con guration
interface-id mode.

Step 3  dot1x guest-vlan Specify an active VLAN as an 802.1x guest VLAN. The range is 1
vlan-id to 4094.
You can con gure any active VLAN except an internal VLAN (routed
port), an RSPAN VLAN, or a voice VLAN as an 802.1x guest VLAN.

Step 4  authentication Enable periodic re-authentication of the client, which is disabled by

periodic default.
or
dot1x
reauthentication

Step 5  dot1x timeout Set the number of seconds between re-authentication attempts.
reauth-period The keywords have these meanings:
{seconds | server}
• seconds—Sets the number of seconds from 1 to 65535. The default
is 3600 seconds.
• server—Sets the number of seconds based on the value of the
Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 56/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Action RADIUS attribute (Attribute [29]).

This command a ects the behavior of the switch only if periodic re-
authentication is enabled.

Step 6  end Return to privileged EXEC mode.

Step 7  show Verify your 802.1x authentication con guration.

authentication
interface
interface-id
or
show dot1x
interface
interface-id

Step 8  copy running- (Optional) Save your entries in the con guration le.
con g startup-
con g

This example shows how to con gure NAC Layer 2 802.1x validation:

Switch# configure terminal

Switch(config)# interface gigabitethernet0/1
Switch(config-if)# dot1x reauthentication
Switch(config-if)# dot1x timeout reauth-period server

Con guring an Authenticator and a Supplicant Switch with NEAT

Con guring this feature requires that one switch outside a wiring closet is con gured as a supplicant and
is connected to an authenticator switch.

For overview information, see the "802.1x Supplicant and Authenticator Switches with Network Edge
Access Topology (NEAT)" section.

Note The cisco-av-pairs must be con gured as device-tra c-class=switch on the ACS, which sets the
interface as a trunk after the supplicant is successfully authenticated.

Beginning in privileged EXEC mode, follow these steps to con gure a switch as an authenticator:

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  cisp enable Enable CISP.

Step 3  interface interface-id Specify the port to be con gured, and enter interface
con guration mode.

Step 4  switchport mode access Set the port mode to access.

Step 5  authentication port-control auto Set the port-authentication mode to auto.

Step 6  dot1x pae authenticator Con gure the interface as a port access entity (PAE)
authenticator.

Step 7  spanning-tree portfast

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 57/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Enable Port Fast on an access port connected to a single

workstation or server..

Step 8  end Return to privileged EXEC mode.

Step 9  show running-con g interface Verify your con guration.

interface-id

Step 10  copy running-con g startup- (Optional) Save your entries in the con guration le.
con g

This example shows how to con gure a switch as an 802.1x authenticator:

Switch# configure terminal

Switch(config)# cisp enable
Switch(config-if)# switchport mode access
Switch(config-if)# authentication port-control auto
Switch(config-if)# dot1x pae authenticator
Switch(config-if)# spanning-tree portfast trunk

Beginning in privileged EXEC mode, follow these steps to con gure a switch as a supplicant:

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  cisp enable Enable CISP.

Step 3  dot1x credentials pro le Create 802.1x credentials pro le. This must be attached to the
port that is con gured as supplicant.

Step 4  username suppswitch Create a username.

Step 5  password password Create a password for the new username.

Step 6  dot1x supplicant force- Force the switch to send only multicast EAPOL packets when it
multicast receives either unicast or multicast packets.
This also allows NEAT to work on the supplicant switch in all host
modes.

Step 7  interface interface-id Specify the port to be con gured, and enter interface
con guration mode.

Step 8  switchport trunk Set the port to trunk mode.

encapsulation dot1q

Step 9  switchport mode trunk Con gure the interface as a VLAN trunk port.

Step 10  dot1x pae supplicant Con gure the interface as a port access entity (PAE) supplicant.

Step 11  dot1x credentials pro le- Attach the 802.1x credentials pro le to the interface.
name

Step 12  end Return to privileged EXEC mode.

Step 13  show running-con g Verify your con guration.

interface interface-id

Step 14  copy running-con g (Optional) Save your entries in the con guration le.
startup-con g

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 58/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

This example shows how to con gure a switch as a supplicant:

Switch# configure terminal

Switch(config)# cisp enable
Switch(config)# dot1x credentials test
Switch(config)# username suppswitch
Switch(config)# password myswitch
Switch(config)# dot1x supplicant force-multicast
Switch(config-if)# switchport trunk encapsulation dot1q
Switch(config-if)# switchport mode trunk

Switch(con g-if)# dot1x pae supplicant

Switch(con g-if)# dot1x credentials test
Switch(con g-if)# end

Con guring NEAT with ASP

You can also use an AutoSmart Ports user-de ned macro instead of the switch VSA to con gure the
authenticator switch. For more information, see the Chapter 12 "Con guring Auto Smartports Macros.""

Con guring 802.1x Authentication with Downloadable ACLs and

Redirect URLs
In addition to con guring 802.1x authentication on the switch, you need to con gure the ACS. For more
information, see the Cisco Secure ACS con guration guides.

Note You must con gure a downloadable ACL on the ACS before downloading it to the switch.

After authentication on the port, you can use the show ip access-list privileged EXEC command to
display the downloaded ACLs on the port.

Con guring Downloadable ACLs

The policies take e ect after client authentication and the client IP address addition to the IP device
tracking table. The switch then applies the downloadable ACL to the port.

Beginning in privileged EXEC mode:

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  ip device tracking Con gure the ip device tracking table.

Step 3  aaa new-model Enables AAA.

Step 4  aaa authorization Sets the authorization method to local. To remove the authorization
network default method, use the no aaa authorization network default group radius
group radius command.

Step 5  radius-server vsa Con gure the radius vsa send authentication.
send authentication

Step 6  interface interface-id Specify the port to be con gured, and enter interface con guration
mode.

Step 7  Con gure the default ACL on the port in the input direction.
https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 59/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

ip access-group acl- Note The acl-id is an access list name or number.

id in

Step 8  show running-con g Verify your con guration.

interface interface-id

Step 9  copy running-con g (Optional) Save your entries in the con guration le.
startup-con g

Con guring a Downloadable Policy

Beginning in privileged EXEC mode:

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  access-list access- De nes the default port ACL by using a source address and
list-number deny wildcard.
source source- The access-list-number is a decimal number from 1 to 99 or 1300
wildcard log to 1999.
Enter deny or permit to specify whether to deny or permit access if
conditions are matched.
The source is the source address of the network or host that sends
a packet, such as this:
• The 32-bit quantity in dotted-decimal format.
• The keyword any as an abbreviation for source and source-
wildcard value of 0.0.0.0 255.255.255.255. You do not need to
enter a source-wildcard value.
• The keyword host as an abbreviation for source and source-
wildcard of source 0.0.0.0.
(Optional) Applies the source-wildcard wildcard bits to the source.
(Optional) Enters log to cause an informational logging message
about the packet that matches the entry to be sent to the console.

Step 3  interface interface-id Enter interface con guration mode.

Step 4  ip access-group acl-id Con gure the default ACL on the port in the input direction.
in Note The acl-id is an access list name or number.

Step 5  exit Returns to global con guration mode.

Step 6  aaa new-model Enables AAA.

Step 7  aaa authorization Sets the authorization method to local. To remove the authorization
network default group method, use the no aaa authorization network default group
radius radius command.

Step 8  ip device tracking Enables the IP device tracking table.

To disable the IP device tracking table, use the no ip device
tracking global con guration commands.

Step 9  ip device tracking (Optional) Con gures the IP device tracking table:
probe count count

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 60/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

• count count-Sets the number of times that the switch sends the
ARP probe. The range is from 1 to 5. The default is 3.
• interval interval-Sets the number of seconds that the switch waits
for a response before resending the ARP probe. The range is
from 30 to 300 seconds. The default is 30 seconds.

Step 10  radius-server vsa Con gures the network access server to recognize and use
send authentication vendor-speci c attributes.
Note The downloadable ACL must be operational.

Step 11  end Returns to privileged EXEC mode.

Step 12  show ip device Displays information about the entries in the IP device tracking
tracking all table.

Step 13  copy running-con g (Optional) Saves your entries in the con guration le.
startup-con g

This example shows how to con gure a switch for a downloadable policy:

Switch# config terminal

Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# aaa new-model
Switch(config)# aaa authorization network default group radius
Switch(config)# ip device tracking
Switch(config)# ip access-list extended default_acl
Switch(config-ext-nacl)# permit ip any any
Switch(config-ext-nacl)# exit
Switch(config)# radius-server vsa send authentication
Switch(config)# interface gigabitethernet0/1
Switch(config-if)# ip access-group default_acl in
Switch(config-if)# exit

Con guring VLAN ID-based MAC Authentication

Beginning in privileged EXEC mode, follow these steps:

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  mab request format attribute 32 vlan Enable VLAN ID-based MAC authentication.
access-vlan

Step 3  copy running-con g startup-con g (Optional) Save your entries in the

con guration le.

There is no show command to con rm the status of VLAN ID-based MAC authentication. You can use the
debug radius accounting privileged EXEC command to con rm the RADIUS attribute 32. For more
information about this command, see the Cisco IOS Debug Command Reference, Release 12.2 at this
URL:

http://www.cisco.com/en/US/docs/ios/debug/command/reference/db_q1.html#wp1123741

This example shows how to globally enable VLAN ID-based MAC authentication on a switch:

Switch# config terminal

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 61/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Enter configuration commands, one per line. End with CNTL/Z.

Switch(config)# mab request format attribute 32 vlan access-vlan
Switch(config-if)# exit

Con guring Flexible Authentication Ordering

Beginning in privileged EXEC mode, follow these steps:

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  interface interface-id Specify the port to be con gured, and enter interface
con guration mode.

Step 3  authentication order [dot1x | mab] | (Optional) Set the order of authentication methods
{webauth} used on a port.

Step 4  authentication priority [dot1x | (Optional) Add an authentication method to the port-
mab] | {webauth} priority list.

Step 5  show authentication (Optional) Verify your entries.

Step 6  copy running-con g startup-con g (Optional) Save your entries in the con guration le.

This example shows how to con gure a port attempt 802.1x authentication rst, followed by web
authentication as fallback method:

Switch# configure terminal

Switch(config)# interface gigabitethernet0/1
Switch(config)# authentication order dot1x webauth

Con guring Open1x

Beginning in privileged EXEC mode:

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  interface interface-id Specify the port to be con gured, and enter interface
con guration mode.

Step 3  authentication control-direction (Optional) Con gure the port control as unidirectional
{both | in} or bidirectional.

Step 4  authentication fallback name (Optional) Con gure a port to use web authentication
as a fallback method for clients that do not support
802.1x authentication.

Step 5  authentication host-mode [multi- (Optional) Set the authorization manager mode on a
auth | multi-domain | multi-host | port.
single-host]

Step 6  authentication open (Optional) Enable or disable open access on a port.

Step 7  authentication order [dot1x | mab] (Optional) Set the order of authentication methods
| {webauth} used on a port.

Step 8  authentication periodic (Optional) Enable or disable reauthentication on a port.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 62/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Step 9  authentication port-control {auto | (Optional) Enable manual control of the port
force-authorized | force-un authorization state.
authorized}

Step 10  show authentication (Optional) Verify your entries.

Step 11  copy running-con g startup- (Optional) Save your entries in the con guration le.
con g

This example shows how to con gure open 1x on a port:

Switch# configure terminal

Switch(config)# interface gigabitethernet0/1
Switch(config)# authentication control-direction both
Switch(config)# au ten tic at ion fallback profile1
Switch(config)# authentication host-mode multi-auth
Switch(config)# authentication open
Switch(config)# authentication order dot1x webauth
Switch(config)# authentication periodic
Switch(config)# authentication port-control auto

Disabling 802.1x Authentication on the Port

You can disable 802.1x authentication on the port by using the no dot1x pae interface con guration
command.

Beginning in privileged EXEC mode, follow these steps to disable 802.1x authentication on the port. This
procedure is optional.

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  interface interface-id Specify the port to be con gured, and enter interface
con guration mode.

Step 3  no dot1x pae Disable 802.1x authentication on the port.

Step 4  end Return to privileged EXEC mode.

Step 5  show authentication Verify your entries.

interface-id
or
show dot1x interface
interface-id

Step 6  copy running-con g startup- (Optional) Save your entries in the con guration le.
con g

To con gure the port as an 802.1x port access entity (PAE) authenticator, which enables 802.1x on the
port but does not allow clients connected to the port to be authorized, use the dot1x pae authenticator
interface con guration command.

This example shows how to disable 802.1x authentication on the port:

Switch(config)# interface gigabitethernet0/1

Switch(config-if)# no dot1x pae authenticator

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 63/64
11/2/2018 Catalyst 3560 Software Configuration Guide, Release 12.2(52)SE - Configuring IEEE 802.1x Port-Based Authentication [Cisco Catal…

Resetting the 802.1x Authentication Con guration to the Default

Values
Beginning in privileged EXEC mode, follow these steps to reset the 802.1x authentication con guration
to the default values. This procedure is optional.

  Command Purpose
Step 1  con gure terminal Enter global con guration mode.

Step 2  interface interface-id Enter interface con guration mode, and specify the port
to be con gured.

Step 3  dot1x default Reset the 802.1x parameters to the default values.

Step 4  end Return to privileged EXEC mode.

Step 5  show authentication interface Verify your entries.

interface-id
or
show dot1x interface interface-
id

Step 6  copy running-con g startup- (Optional) Save your entries in the con guration le.
con g

Displaying 802.1x Statistics and Status

To display 802.1x statistics for all ports, use the show dot1x all statistics privileged EXEC command. To
display 802.1x statistics for a speci c port, use the show dot1x statistics interface interface-id
privileged EXEC command.

To display the 802.1x administrative and operational status for the switch, use the show dot1x all
[details | statistics | summary] privileged EXEC command. To display the 802.1x administrative and
operational status for a speci c port, use the show dot1x interface interface-id privileged EXEC
command.

For detailed information about the elds in these displays, see the command reference for this release.

© 2018 Cisco and/or its a liates. All rights reserved.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3560/software/release/12-2_52_se/configuration/guide/3560scg/sw8021x.html 64/64