802.1X Authentication With Restricted Vlan - Cisco Catalyst 2960 Software Configuration Manual
Hide thumbs
Also See for Catalyst 2960:
- Configuration manual (2288 pages) ,
- Command reference manual (800 pages) ,
- Hardware installation manual (108 pages)
Table of Contents
Advertisement
Understanding IEEE 802.1x Port-Based 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 specified. For more information, see the
Authentication with MAC Authentication Bypass" section on page
For more information, see the
802.1x Authentication with Restricted VLAN
You can configure 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 configure 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.
Without this feature, the client attempts and fails authentication indefinitely, and the switch port remains
in the spanning-tree blocking state. With this feature, you can configure the switch port to be in the
restricted VLAN after a specified 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
configured 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 configured 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 configured 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 logoff 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 logoff event.
After a port moves to the restricted VLAN, a simulated EAP success message is sent to the client. This
prevents clients from indefinitely 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 configure any active VLAN except an RSPAN VLAN or a voice VLAN as an 802.1x restricted
VLAN. The restricted VLAN feature is not supported on trunk ports; it is supported only on access ports.
Other security features such as dynamic ARP Inspection, DHCP snooping, and IP source guard can be
configured independently on a restricted VLAN.
For more information, see the
Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 15.0(1)SE
10-24
Chapter 10
"Configuring a Guest VLAN" section on page
"Configuring a Restricted VLAN" section on page
Configuring IEEE 802.1x Port-Based Authentication
10-29.
10-54.
10-55.
"802.1x
OL-26520-01
Hide quick links:
Advertisement
Chapters
Table of Contents
Troubleshooting
