Dell PowerConnect B-RX BigIron RX Series Configuration Guide v02.8.00 - Page 1039

Chapter Configuring 802.1x Port Security 33 Overview of 802.1x port security BigIron RX supports the IEEE 802.1x standard for authenticating devices attached to LAN ports. Using 802.1x port security, you can configure a BigIron RX to grant access to a port based on information supplied by a client to an authentication server. When a user logs on to a network that uses 802.1x port security, the device grants (or does not grant) access to network services after the user is authenticated by an authentication server. The user-based authentication in 802.1x port security provides an alternative to granting network access based on a user's IP address, MAC address, or subnetwork. BigIron RX Series supports 802.1x authentication on untagged ports only. IETF RFC support Brocade's implementation of 802.1x port security supports the following RFCs: • RFC 2284 PPP Extensible Authentication Protocol (EAP) • RFC 2865 Remote Authentication Dial In User Service (RADIUS) • RFC 2869 RADIUS Extensions How 802.1x port security works This section explains the basic concepts behind 802.1x port security, including device roles, how the devices communicate, and the procedure used for authenticating clients. Device roles in an 802.1x configuration The 802.1x standard defines the roles of Client/Supplicant, Authenticator, and Authentication Server in a network. The Client (known as a Supplicant in the 802.1x standard) provides username/password information to the Authenticator. The Authenticator sends this information to the Authentication Server. Based on the Client's information, the Authentication Server determines whether the Client can use services provided by the Authenticator. The Authentication Server passes this information to the Authenticator, which then provides services to the Client, based on the authentication result. Figure 124 illustrates these roles. BigIron RX Series Configuration Guide 963 53-1002253-01