964 BigIron RX Series Configuration Guide
53-1002253-01
How 802.1x port security works
33
FIGURE 124  Authenticator, Client/Supplicant, and Authentication Server in an 802.1x 
configuration
Authenticator – The device that controls access to the network. In an 802.1x configuration, the 
BigIron RX serves as the Authenticator. The Authenticator passes messages between the Client and 
the Authentication Server. Based on the identity information supplied by the Client, and the 
authentication information supplied by the Authentication Server, the Authenticator either grants or 
does not grant network access to the Client.
Client/Supplicant – The device that seeks to gain access to the network.  Clients must be running 
software that supports the 802.1x standard (for example, the Windows XP operating system).  
Clients can either be directly connected to a port on the Authenticator, or can be connected by way 
of a hub.
Authentication Server – The device that validates the Client and specifies whether or not the Client 
may access services on the device. Brocade supports Authentication Servers running RADIUS.
Communication between the devices
For communication between the devices, 802.1x port security uses the Extensible Authentication 
Protocol (EAP), defined in RFC 2284.  The 802.1x standard specifies a method for encapsulating 
EAP messages so that they can be carried over a LAN.  This encapsulated form of EAP is known as 
EAP over LAN (EAPOL).  The standard also specifies a means of transferring the EAPOL information 
between the Client/Supplicant, Authenticator, and Authentication Server.
EAPOL messages are passed between the Port Access Entity (PAE) on the Supplicant and the 
Authenticator. Figure 125 shows the relationship between the Authenticator PAE and the 
Supplicant PAE.
Client/Supplicant
RADIUS Server
(Authentication Server)
BigIron Device
(Authenticator)