Ports in authorized and unauthorized states – Dell POWEREDGE M1000E User Manual

Page 272

Advertising
background image

10-10

Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide

OL-13270-03

Chapter 10 Configuring IEEE 802.1x Port-Based Authentication

Understanding IEEE 802.1x Port-Based Authentication

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

Ports in Authorized and Unauthorized States

During IEEE 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
configured as a voice VLAN port disallows all ingress and egress traffic except for IEEE 802.1x
authentication, CDP, and STP packets. When a client is successfully authenticated, the port changes to
the authorized state, allowing all traffic for the client to flow normally. If the port is configured as a voice
VLAN port, the port allows VoIP traffic and IEEE 802.1x protocol packets before the client is
successfully authenticated.

If a client that does not support IEEE 802.1x authentication connects to an unauthorized IEEE 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 IEEE 802.1x-enabled client connects to a port that is not running the IEEE 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 fixed 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 dot1x port-control interface configuration
command and these keywords:

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

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 IEEE 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 identified 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

authentication violation {protect |
restrict | shutdown}

dot1x violation-mode {shutdown
| restrict | protect}

Configure the violation modes that occur when a
new device connects to a port or when a new
device connects to a port after the maximum
number of devices are connected to that port.

show authentication

show dot1x

Display 802.1x statistics, administrative status,
and operational status for the switch or for the
specified port.

Table 10-2

Authentication Manager Commands and Earlier 802.1x Commands (continued)

The authentication manager
commands in Cisco IOS
Release 12.2(50)SE or later

The equivalent 802.1x commands in
Cisco IOS Release 12.2(46)SE and
earlier

Description

Advertising