8-13
Configuring Port-Based and Client-Based Access Control (802.1X)
General Operating Rules and Notes
port. If another client uses an 802.1X supplicant application to access
the opened port, then a re-authentication occurs using the RADIUS
configuration response for the latest client to authenticate. To control
access by all clients, use the client-based method.
■
If a port on switch “A” is configured as an 802.1X supplicant and is
connected to a port on another switch, “B”, that is not 802.1X-aware,
access to switch “B” will occur without 802.1X security protection.
■
You can configure a port as both an 802.1X authenticator
and
an
802.1X supplicant.
■
If a port on switch “A” is configured as both an 802.1X authenticator
and
supplicant and is connected to a port on another switch, “B”, that
is not 802.1X-aware, access to switch “B” will occur without 802.1X
security protection, but switch “B” will not be allowed access to
switch “A”.
■
If a client already has access to a switch port when you configure the
port for 802.1X authenticator operation, the port will block the client
from further network access until it can be authenticated.
■
On a port configured for 802.1X with RADIUS authentication, if the
RADIUS server specifies a VLAN for the supplicant and the port is a
trunk member, the port will be blocked. If the port is later removed
from the trunk, the port will try to authenticate the supplicant. If
authentication is successful, the port becomes unblocked. Similarly,
if the supplicant is authenticated and later the port becomes a trunk
member, the port will be blocked. If the port is then removed from
the trunk, it tries to re-authenticate the supplicant. If successful, the
port becomes unblocked.
■
To help maintain security, 802.1X and LACP cannot both be enabled
on the same port. If you try to configure 802.1X on a port already
configured for LACP (or the reverse) you will see a message similar
to the following:
Error configuring port
X
: LACP and 802.1X cannot be run together.
N o t e o n 8 0 2 . 1 X
a n d L A C P
To help maintain security, the switch does not allow 802.1X and LACP to both
be enabled at the same time on the same port. Refer to “802.1X Operating
Messages” on page 8-58
Summary of Contents for ProCurve 2510-24
Page 1: ...Access Security Guide 2510 www procurve com ProCurve Switches Q 11 XX 2510 24 U 11 XX 2510 48 ...
Page 2: ......
Page 3: ...ProCurve Series 2510 Switches Access Security Guide July 2008 ...
Page 26: ...1 10 Getting Started Need Only a Quick Start ...
Page 104: ...4 30 TACACS Authentication Configuring TACACS on the Switch ...
Page 144: ...5 40 RADIUS Authentication Authorization and Accounting Messages Related to RADIUS Operation ...
Page 174: ...6 30 Configuring Secure Shell SSH Messages Related to SSH Operation ...
Page 196: ...7 22 Configuring Secure Socket Layer SSL Common Errors in SSL Setup ...
Page 294: ...9 40 Configuring and Monitoring Port Security Configuring Protected Ports ...
Page 308: ...10 14 Using Authorized IP Managers Operating Notes ...
Page 316: ...8 Index ...
Page 317: ......