\u2022![\"\"](\"https:\/\/www.cisco.com\/c\/dam\/en\/us\/td\/i\/000001-100000\/90001-95000\/94001-95000\/94158.ps\/_jcr_content\/renditions\/94158.jpg\")
Client\u2014The workstation that requests access to the LAN, and responds to requests from the switch. The workstation must be running 802.1X-compliant client software.<\/p>\n\n\n\n
\n\n\n\n
Note\u00a0<\/strong> \u2022 When the switch receives EAPOL frames and relays them to the authentication server, the Ethernet header is stripped and the remaining EAP frame is reencapsulated in the RADIUS format. The EAP frames are not modified or examined during encapsulation, and the authentication server must support EAP within the native frame format. When the switch receives frames from the authentication server, the frame header is removed from the server, leaving the EAP frame, which is then encapsulated for Ethernet and sent to the client.<\/p>\n\n\n\n Cisco devices that are capable of functioning as an 802.1X network access point include Catalyst 4500 series switches, the Catalyst 3550 multilayer switch, the Catalyst 2950 switch, and a Cisco Airnet series wireless access point. These devices must be running software that supports the RADIUS client and 802.1X.<\/p>\n\n\n\n \u2022 The switch or the client can initiate authentication. If you enable authentication on a port by using the dot1x port-control auto<\/strong> interface configuration command, the switch must initiate authentication when it determines that the port link state has changed. It then sends an EAP-request\/identity frame to the client to request its identity (typically, the switch sends an initial identity\/request frame followed by one or more requests for authentication information). Upon receipt of the frame, the client responds with an EAP-response\/identity frame.<\/p>\n\n\n\n However, if during bootup, 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.<\/p>\n\n\n\n If 802.1X 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 transmits frames as if the port is in the authorized state. A port in the authorized state means that the client has been successfully authenticated.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.<\/p>\n\n\n\n The specific exchange of EAP frames depends on the authentication method being used.\u00a0Figure\u00a031-2\u00a0shows a message exchange that is initiated by the client using the One-Time Password (OTP) authentication method with an authentication server.<\/p>\n\n\n\n Figure 31-2 Message Exchange<\/a><\/p>\n\n\n\n The switch port state determines whether or not the client is granted access to the network. The port starts in the unauthorized state. While in this state, the port disallows all ingress and egress traffic except for 802.1X protocol packets. When a client is successfully authenticated, the port transitions to the authorized state, allowing all traffic for the client to flow normally.<\/p>\n\n\n\n If a client that does not support 802.1X is connected 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. If the guest VLAN is configured for a port that connects to a client that does not support 802.1X, the port is placed in the configured guest VLAN and in the authorized state. For more information, see the\u00a0“Using 802.1X Authentication for Guest VLANs” section.<\/p>\n\n\n\n In contrast, when an 802.1X-enabled client connects to a port that is not running the 802.1X protocol, the client initiates the authentication process by sending the EAPOL-start frame. When no response is received, the client sends the request a fixed number of times. Because no response is received, the client begins sending frames as if the port is in the authorized state.<\/p>\n\n\n\n You can control the port authorization state with the dot1x port-control<\/strong> interface configuration command and these keywords:<\/p>\n\n\n\n \u2022 \u2022 \u2022 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 authentication fails, the port remains in the unauthorized state, but authentication can be retried. If the authentication server cannot be reached, the switch can retransmit the request. If no response is received from the server after the specified number of attempts, authentication fails and network access is not granted.<\/p>\n\n\n\n If the link state of a port transitions from up to down, or if an EAPOL-logoff frame is received by the port, the port returns to the unauthorized state.<\/p>\n\n\n\n You can use the VLAN assignment to limit network access for certain users. With the VLAN assignment, 802.1X-authenticated ports are assigned to a VLAN based on the username of the client connected to that port. The RADIUS server database maintains the username-to-VLAN mappings. After successful 802.1X authentication of the port, the RADIUS server sends the VLAN assignment to the switch. Note <\/strong>To enable the guest VLAN feature in Release 12.1(19)EW and later releases, the port must be statically configured as an access port.<\/p>\n\n\n\n When configured on the switch and the RADIUS server, 802.1X with VLAN assignment has these characteristics:<\/p>\n\n\n\n \u2022 \u2022 Configuration errors might occur if you specify a VLAN for a routed port, a malformed VLAN ID, or a nonexistent or internal (routed port) VLAN ID. Similarly, an error might occur if you make an assignment to a voice VLAN ID.<\/p>\n\n\n\n \u2022 \u2022 \u2022 To configure VLAN assignment you need to perform these tasks:<\/p>\n\n\n\n \u2022 \u2022 \u2022 \u2013 \u2013 \u2013 You can use guest VLANs to enable non-802.1X capable hosts to access networks that use 802.1X authentication. For example, you can use guest VLANs while you are upgrading your system to support 802.1X authentication.<\/p>\n\n\n\n Guest VLANs are supported on a per-port basis, and you can use any VLAN (except a private VLAN) as a guest VLAN. If a port is already forwarding on the guest VLAN and you enable 802.1X support on the network interface of the host, the port is immediately moved out of the guest VLAN and the authenticator waits for authentication to occur.<\/p>\n\n\n\n Enabling 802.1X authentication on a port starts the 802.1X protocol. If the host fails to respond to the packets from the authenticator within a certain amount of time, the authenticator puts the port in the guest VLAN.<\/p>\n\n\n\n The usage guidelines for using 802.1X authentication with guest VLANs on Windows-XP hosts are as follows:<\/p>\n\n\n\n \u2022 \u2022 You can enable port security on an 802.1X port in either single- or multiple-host mode. (To do so, you must configure port security with the switchport port-security<\/strong> interface configuration command. Refer to the “Configuring Port Security” chapter in this guide.) When you enable port security and 802.1X on a port, 802.1X authenticates the port, and port security manages the number of MAC addresses allowed on that port, including that of the client. Hence an 802.1X port with port security enabled can be used to limit the number or group of clients that can access the network.<\/p>\n\n\n\n These examples describe the interaction between 802.1X and port security on the switch:<\/p>\n\n\n\n \u2022 When a client is authenticated and manually configured for port security, it is guaranteed an entry in the secure host table (unless port security static aging has been enabled).<\/p>\n\n\n\n A security violation occurs if an additional host is learned on the port. The action taken depends on which feature (802.1X or port security) detects the security violation:<\/p>\n\n\n\n \u2013 \u2013 The following describes when port security and 802.1X security violations occur:<\/p>\n\n\n\n \u2013 \u2013 \u2013 \u2022 \u2022 \u2022 \u2022 \u2022 802.1X RADIUS accounting relays important events to the RADIUS server (such as the client’s connection session). This session is defined as the difference in time from when client is authorized to use the port and when the client stops using the port.<\/p>\n\n\n\n Figure\u00a031-3\u00a0shows the 802.1X device roles.<\/p>\n\n\n\n Figure 31-3 Radius Accounting<\/a> Note <\/strong>You must configure the 802.1X client to send an EAP-logoff (Stop) message to the switch when the user logs off. If you do not configure the 802.1X client, an EAP-logoff message is not sent to the switch and the accompanying accounting Stop message will not be sent to the authentication server. Refer to the Microsoft Knowledge Base article at the URL: http:\/\/support.microsoft.com<\/a>. Also refer to the Microsoft article at the URL: http:\/\/www.microsoft.com\/technet\/treeview\/default.asp?url=\/technet\/columns\/cableguy\/cg0703.asp<\/a>, and set the SupplicantMode registry to 3 and the AuthMode registry to 1.<\/p>\n\n\n\n The client uses EAP to authenticate itself with the RADIUS server. The switch relays EAP packets between the client and the RADIUS server.<\/p>\n\n\n\n After the client is authenticated, the switch sends accounting-request packets to the RADIUS server, which responds with accounting-response packets to acknowledge the receipt of the request.<\/p>\n\n\n\n A RADIUS accounting-request packet contains one or more Attribute-Value pairs to report various events and related information to the RADIUS server. The following events are tracked:<\/p>\n\n\n\n \u2022 \u2022 \u2022 \u2022 \u2022 When the port state transitions between authorized and unauthorized, the RADIUS messages are transmitted to the RADIUS server.<\/p>\n\n\n\n The switch does not log any accounting information. Instead, it sends such information to the RADIUS server, which must be configured to log accounting messages.<\/p>\n\n\n\n The 802.1X authentication, authorization and accounting process is as follows:<\/p>\n\n\n\n Step 1 <\/strong> Step 2 <\/strong> Step 3 <\/strong> Step 4 <\/strong> Step 5 <\/strong> Step 6 <\/strong> Step 7 <\/strong> Step 8 <\/strong> To configure 802.1X accounting, you need to do the following tasks:<\/p>\n\n\n\n \u2022 \u2022 \u2022 \u2022 Enabling AAA system accounting along with 802.1X accounting allows system reload events to be sent to the accounting RADIUS server for logging. By doing this, the accounting RADIUS server can infer that all active 802.1X sessions are appropriately closed.<\/p>\n\n\n\n Because RADIUS uses the unreliable transport protocol UDP, accounting messages may be lost due to poor network conditions. If the switch does not receive the accounting response message from the RADIUS server after a configurable number of retransmissions of an accounting request, the following system message appears:<\/p>\n\n\n\n When the stop message is not transmitted successfully, the following message appears:<\/p>\n\n\n\n Use the show radius statistics command to display the number of RADIUS messages that do not receive the accounting response message.<\/p>\n\n\n\n A voice VLAN port is a special access port associated with two VLAN identifiers:<\/p>\n\n\n\n \u2022 \u2022 Each port that you configure for a voice VLAN is associated with a VVID and a PVID. This configuration allows voice traffic and data traffic to be separated onto different VLANs.<\/p>\n\n\n\n When you enable the single-host mode, only one 802.1X client is allowed on the primary VLAN; other workstations are blocked. When you enable the multiple-hosts mode and an 802.1X client is authenticated on the primary VLAN, additional clients on the voice VLAN are unrestricted after 802.1X authentication succeeds on the primary VLAN.<\/p>\n\n\n\n A voice VLAN port becomes active when there is link, and the device MAC address appears in the MAC-address table after the first CDP message from the IP phone. Cisco IP phones do not relay CDP messages from other devices. As a result, if several Cisco IP phones are connected in series, the switch recognizes only the one directly connected to it. When 802.1X is enabled on a voice VLAN port, the switch drops packets from unrecognized Cisco IP phones more than one hop away.<\/p>\n\n\n\n When 802.1X is enabled on a port, you cannot configure a PVID that is equal to a VVID. For more information about voice VLANs, see\u00a0“Configuring Voice Interfaces.”<\/p>\n\n\n\n Be aware of the following feature interactions:<\/p>\n\n\n\n \u2022 \u2022 \u2022 However, you cannot use the 802.1X voice VLAN port feature with 802.1X port security’s sticky MAC address configuration and 802.1X port-security’s statically configured MAC address configuration.<\/p>\n\n\n\n \u2022 \u2022 The 802.1X port-based authentication supports two topologies:<\/p>\n\n\n\n \u2022 \u2022 In a point-to-point configuration (see\u00a0Figure\u00a031-1), only one client can be connected to the 802.1X-enabled switch port when the multi-host mode is not enabled (the default). The switch detects the client 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.<\/p>\n\n\n\n Figure\u00a031-4\u00a0illustrates 802.1X port-based authentication in a wireless LAN. You must configure the 802.1X port as a multiple-host port that is authorized as a wireless access point once the client is authenticated. (See the\u00a0“Enabling Multiple Hosts” section.) When the port is authorized, all other hosts that are indirectly attached to the port are granted access to the network. If the port becomes unauthorized (reauthentication fails or an EAPOL-logoff message is received), the switch denies access to the network for all wireless access point-attached clients. In this topology, the wireless access point is responsible for authenticating clients attached to it, and the wireless access point acts as a client to the switch.<\/p>\n\n\n\n Figure 31-4 Wireless LAN Example<\/a><\/p>\n\n\n\n These sections describe how to configure 802.1X:<\/p>\n\n\n\n \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 Table\u00a031-1\u00a0shows the default 802.1X configuration.<\/p>\n\n\n\n This section describes the guidelines for configuring 802.1X authentication:<\/p>\n\n\n\n \u2022 \u2013 \u2013 \u2013 \u2013 \u2013 If you are planning to use either 802.1X accounting or VLAN assignment, be aware that both features utilize general AAA commands. For information how to configure AAA, refer to “Enabling 802.1X Authentication” on page 13<\/a> and “Enabling 802.1X Accounting” on page 16<\/a>. Alternatively, you can refer to the Cisco IOS security documentation.<\/p>\n\n\n\n Refer to the following Cisco IOS security documentation for information on how to configure AAA system accounting:<\/p>\n\n\n\nFor more information on 802.1X-compliant client application software such as Microsoft Windows 2000 Professional or Windows XP, refer to the Microsoft Knowledge Base.<\/p>\n\n\n\n
\n\n\n\nAuthenticator\u2014Controls physical access to the network based on the authentication status of the client. The switch acts as an intermediary 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 encapsulates and decapsulates the Extensible Authentication Protocol (EAP) frames and interacts with the RADIUS authentication server.<\/p>\n\n\n\nAuthentication server\u2014Performs the actual authentication of the client. The authentication server validates the identity of the client and notifies the switch that the client is authorized to access the LAN and switch services. (The only supported authentication server is the RADIUS authentication server with EAP extensions; it is available in Cisco Secure Access Control Server version 3.2 and later.)<\/p>\n\n\n\nAuthentication Initiation and Message Exchange<\/h3>\n\n\n\n
Ports in Authorized and Unauthorized States<\/h3>\n\n\n\n
force-authorized<\/strong>\u2014Disables 802.1X authentication and causes the port to transition to the authorized state without any authentication exchange required. The port transmits and receives normal traffic without 802.1X-based authentication of the client. This setting is the default.<\/p>\n\n\n\nforce-unauthorized<\/strong>\u2014Causes 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 interface.<\/p>\n\n\n\nauto<\/strong>\u2014Enables 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 transitions 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. The switch can uniquely identify each client attempting to access the network by the client’s MAC address.<\/p>\n\n\n\nUsing 802.1X with VLAN Assignment<\/h3>\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\n
\n\n\n\nIf no VLAN is supplied by the RADIUS server, the port is configured in its access VLAN when authentication succeeds.<\/p>\n\n\n\nIf the authentication server provides invalid VLAN information, the port remains unauthorized. This situation prevents ports from appearing unexpectedly in an inappropriate VLAN due to a configuration error.<\/p>\n\n\n\nIf the authentication server provides valid VLAN information, the port is authorized and placed in the specified VLAN when authentication succeeds.<\/p>\n\n\n\nIf the multiple-hosts mode is enabled, all hosts are in the same VLAN as the first authenticated user.<\/p>\n\n\n\nIf 802.1X is disabled on the port, the port is returned to the configured access VLAN.<\/p>\n\n\n\nEnable AAA authorization with the\u00a0network<\/strong>\u00a0keyword to allow interface configuration from the RADIUS server. For an illustration of how to apply the aaa authorization network group radius command, refer to the section\u00a0“Enabling 802.1X Authentication” on page\u00a013.<\/p>\n\n\n\nEnable 802.1X. (The VLAN assignment feature is automatically enabled when you configure 802.1X on an access port.)<\/p>\n\n\n\nAssign vendor-specific tunnel attributes in the RADIUS server. To ensure proper VLAN assignment, the RADIUS server must return these attributes to the switch:<\/p>\n\n\n\nTunnel-Type = VLAN<\/p>\n\n\n\nTunnel-Medium-Type = 802<\/p>\n\n\n\nTunnel-Private-Group-ID = VLAN NAME<\/p>\n\n\n\nUsing 802.1X Authentication for Guest VLANs<\/h3>\n\n\n\n
Usage Guidelines for Using 802.1X Authentication with Guest VLANs on Windows-XP Hosts<\/h3>\n\n\n\n
If the host fails to respond to the authenticator, the port attempts to connect three times (with a 30 second timeout between each attempt). After this time, the login\/password window does not appear on the host, so you must unplug and reconnect the network interface cable.<\/p>\n\n\n\nHosts responding with an incorrect login\/password fail authentication. Hosts failing authentication are not put in the guest VLAN. The first time that a host fails authentication, the quiet-period timer starts, and no activity occurs for the duration of the quiet-period timer. When the quiet-period timer expires, the host is presented with the login\/password window. If the host fails authentication for the second time, the quiet-period timer starts again, and no activity will occur for the duration of the quiet-period timer. The host is presented with the login\/password window a third time. If the host fails authentication the third time, the port is placed in the unauthorized state, and you must disconnect and reconnect the network interface cable.<\/p>\n\n\n\nUsing 802.1X with Port Security<\/h3>\n\n\n\n
When a client is authenticated, and the port security table is not full, the client’s MAC address is added to the port security list of secure hosts. The port then proceeds to come up normally.<\/p>\n\n\n\nIf 802.1X detects the violation, the action is to err-disable the port.<\/p>\n\n\n\nIf port security detects the violation, the action is to shutdown or restrict the port (the action is configurable).<\/p>\n\n\n\nIn single host mode, after the port is authorized, any MAC address received other than the client’s will cause a 802.1X security violation.<\/p>\n\n\n\nIn single host mode, if installation of an 802.1X client’s MAC address fails because port security has already reached its limit (due to a configured secure MAC addresses), a port security violation is triggered.<\/p>\n\n\n\nIn multi host mode, once the port is authorized, any additional MAC addresses that cannot be installed because the port security has reached its limit will trigger a port security violation.<\/p>\n\n\n\nWhen an 802.1X client logs off, the port transitions back to an unauthenticated state, and all dynamic entries in the secure host table are cleared, including the entry for the client. Normal authentication then ensues.<\/p>\n\n\n\nIf you administratively shut down the port, the port becomes unauthenticated, and all dynamic entries are removed from the secure host table.<\/p>\n\n\n\nOnly 802.1X can remove the client’s MAC address from the port security table. Note that in multi host mode, with the exception of the client’s MAC address, all MAC addresses that are learned by port security can be deleted using port security CLIs.<\/p>\n\n\n\nWhenever port security ages out a 802.1X client’s MAC address, 802.1X attempts to reauthenticate the client. Only if the reauthentication succeeds will the client’s MAC address be retained in the port security table.<\/p>\n\n\n\nAll of the 802.1X client’s MAC addresses are tagged with (dot1x) when you display the port security table by using CLI.<\/p>\n\n\n\n802.1X RADIUS Accounting<\/h3>\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\n
\n\n\n\nUser successfully authenticates<\/p>\n\n\n\nUser logs-off<\/p>\n\n\n\nLink-down occurs on a 802.1X port<\/p>\n\n\n\nReauthentication succeeds<\/p>\n\n\n\nReauthentication fails<\/p>\n\n\n\n
\n\n\n\nA user connects to a port on the switch.<\/p>\n\n\n\nAuthentication is performed, for example, using the username\/password method.<\/p>\n\n\n\nVLAN assignment is enabled, as appropriate, per RADIUS server configuration.<\/p>\n\n\n\nThe switch sends a start message to an accounting server.<\/p>\n\n\n\nReauthentication is performed, as necessary.<\/p>\n\n\n\nThe switch sends an interim accounting update to the accounting server that is based on the result of reauthentication.<\/p>\n\n\n\nThe user disconnects from the port.<\/p>\n\n\n\nThe switch sends a stop message to the accounting server.<\/p>\n\n\n\n
\n\n\n\nEnable logging of “Update\/Watchdog packets from this AAA client” in your RADIUS server’s Network Configuration tab.<\/p>\n\n\n\nEnable “Logging>CVS RADIUS Accounting” in your RADIUS server System Configuration tab.<\/p>\n\n\n\nEnable 802.1X accounting on your switch.<\/p>\n\n\n\nEnable AAA accounting by using the aaa system accounting command. Refer to the\u00a0“Enabling 802.1X Accounting” section.<\/p>\n\n\n\nAccounting message %s for session %s failed to receive Accounting Response.\n<\/pre>\n\n\n\n
<\/pre>\n\n\n\n
00:09:55: %RADIUS-3-NOACCOUNTINGRESPONSE: Accounting message Start for session \n172.20.50.145 sam 11\/06\/03 07:01:16 11000002 failed to receive Accounting Response.\n<\/pre>\n\n\n\n
<\/pre>\n\n\n\n
Using 802.1X with Voice VLAN Ports<\/h3>\n\n\n\n
Voice VLAN ID (VVID) to carry voice traffic to and from the IP phone. The VVID is used to configure the IP phone connected to the port.<\/p>\n\n\n\nPort VLAN ID (PVID) to carry the data traffic to and from the workstation connected to the switch through the IP phone. The PVID is the native VLAN of the port.<\/p>\n\n\n\n802.1X VLAN assignment cannot assign to the port the same VLAN as the voice VLAN; otherwise, the 802.1X authentication will fail.<\/p>\n\n\n\n802.1X guest VLAN works with the 802.1X voice VLAN port feature. However, the guest VLAN cannot be the same as the voice VLAN.<\/p>\n\n\n\n802.1X port security works with the 802.1X voice VLAN port feature and is configured per port. Three secure addresses must be configured: one for the Cisco IP phone MAC address on the VVID, one for the PC MAC-address on PVID, and a third to allow the Cisco IP phone MAC address on the PVID.<\/p>\n\n\n\n802.1X accounting is unaffected by the 802.1X voice VLAN port feature.<\/p>\n\n\n\nWhen 802.1X is configured on a port, you cannot connect multiple IP-phones to a Catalyst 4500 series switch through a hub.<\/p>\n\n\n\nSupported Topologies<\/h3>\n\n\n\n
Point to point<\/p>\n\n\n\nWireless LAN<\/p>\n\n\n\nHow to Configure 802.1X<\/h2>\n\n\n\n
Default 802.1X Configuration<\/p>\n\n\n\n802.1X Configuration Guidelines<\/p>\n\n\n\nEnabling 802.1X Authentication\u00a0(required)<\/p>\n\n\n\nConfiguring Switch-to-RADIUS-Server Communication\u00a0(required)<\/p>\n\n\n\nEnabling 802.1X Accounting<\/p>\n\n\n\nConfiguring 802.1X with Guest VLANs<\/p>\n\n\n\nConfiguring 802.1X with Voice VLAN<\/p>\n\n\n\nEnabling Periodic Reauthentication\u00a0(optional)<\/p>\n\n\n\nManually Reauthenticating a Client Connected to a Port\u00a0(optional)<\/p>\n\n\n\nChanging the Quiet Period\u00a0(optional)<\/p>\n\n\n\nChanging the Switch-to-Client Retransmission Time\u00a0(optional)<\/p>\n\n\n\nSetting the Switch-to-Client Frame-Retransmission Number\u00a0(optional)<\/p>\n\n\n\nEnabling Multiple Hosts\u00a0(optional)<\/p>\n\n\n\nResetting the 802.1X Configuration to the Default Values\u00a0(optional)<\/p>\n\n\n\nDefault 802.1X Configuration<\/h3>\n\n\n\n
Feature<\/th> Default Setting<\/th><\/tr> Authentication, authorization, and accounting (AAA)<\/td> Disabled<\/td><\/tr> RADIUS server\u2022 IP address\u2022UDP authentication port\u2022Key<\/td>\u2022 None specified\u20221812\u2022None specified<\/td><\/tr>Per-interface 802.1X protocol enable state<\/td> Disabled (force-authorized)The port transmits and receives normal traffic without 802.1X-based authentication of the client.<\/td><\/tr> Periodic reauthentication<\/td> Disabled<\/td><\/tr> Time between reauthentication attempts<\/td> 3600 sec<\/td><\/tr> Quiet period<\/td> 60 secNumber of seconds that the switch remains in the quiet state following a failed authentication exchange with the client.<\/td><\/tr> Retransmission time<\/td> 30 secNumber of seconds that the switch should wait for a response to an EAP request\/identity frame from the client before retransmitting the request.<\/td><\/tr> Maximum retransmission number<\/td> 2Number of times that the switch will send an EAP-request\/identity frame before restarting the authentication process.<\/td><\/tr> Multiple host support<\/td> Disabled<\/td><\/tr> Client timeout period<\/td> 30 secWhen relaying a request from the authentication server to the client, the amount of time that the switch waits for a response before retransmitting the request to the client.<\/td><\/tr> Authentication server timeout period<\/td> 30 secWhen relaying a response from the client to the authentication server, the amount of time that the switch waits for a reply before retransmitting the response to the server. This setting is not configurable.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n 802.1X Configuration Guidelines<\/h3>\n\n\n\n
The 802.1X protocol is supported on both Layer 2 static-access ports and Layer 3 routed ports, but it is not supported on the following port types:<\/p>\n\n\n\nTrunk port\u2014If you try to enable 802.1X on a trunk port, an error message appears, and 802.1X is not enabled. If you try to change the mode of an 802.1X-enabled port to trunk, the port mode is not changed.<\/p>\n\n\n\nDefault ports\u2014All ports default as dynamic-access ports (auto). Use the no switchport<\/strong> command to access a router port.<\/p>\n\n\n\nDynamic ports\u2014A port in dynamic mode can negotiate with its neighbor to become a trunk port. If you try to enable 802.1X on a dynamic port, an error message appears, and 802.1X is not enabled. If you try to change the mode of an 802.1X-enabled port to dynamic, the port mode is not changed.<\/p>\n\n\n\nEtherChannel port\u2014Before enabling 802.1X on the port, you must first remove it from the EtherChannel. If you try to enable 802.1X on an EtherChannel or on an active port in an EtherChannel, an error message appears, and 802.1X is not enabled. If you enable 802.1X on a not-yet active port of an EtherChannel, the port does not join the EtherChannel.<\/p>\n\n\n\nSwitched Port Analyzer (SPAN) destination port\u2014You can enable 802.1X on a port that is a SPAN destination port; however, 802.1X is disabled until the port is removed as a SPAN destination. You can enable 802.1X on a SPAN source port.<\/p>\n\n\n\n