HP procurve 2500 Manuale Utente

    58

Enhancements in Release F.05.05 through F.05.60

•

If, after the supplicant port sends the configured number of start request packets, it does 
not receive a response, it assumes that switch “B” is not 802.1X-aware, and transitions 
to the authenticated state. If switch “B” is operating properly and is not 802.1X-aware, 
then the link should begin functioning normally, but without 802.1X security. 

•

If, after sending one or more start request packets, port 1 receives a request packet from 
port 5, then switch “B” is operating as an 802.1X authenticator. The supplicant port then 
sends a response/ID packet. If switch “B” is configured for RADIUS authentication, it 
forwards this request to a RADIUS server. If switch “B” is configured for Local 802.1X 
authentication (page 42), the authenticator compares the switch “A” response to its local 
username and password.

2.

The RADIUS server then responds with an access challenge that switch “B” forwards to port 1 
on switch “A”.

3.

Port 1 replies with a hash response based on its unique credentials. Switch “B” forwards this 
response to the RADIUS server. 

4.

The RADIUS server then analyzes the response and sends either a “success” or “failure” packet 
back through switch “B” to port 1. 

•

A “success” response unblocks port 5 to normal traffic from port 1.

•

A “failure” response continues the block on port 5 and causes port 1 to wait for the “held-
time” period before trying again to achieve authentication through port 5. 

You can configure a switch port to operate as both a supplicant and an authenticator at the same time. 

You can configure one or more switch 

ports to operate as supplicants for point-to-point links to 802.1X-aware ports on other switches. You 
must configure a port as a supplicant before you can configure any supplicant-related parameters

.

Syntax: [no] aaa port-access supplicant [ethernet] < port-list >

no” form of the command disables supplicant operation on