Troubleshooting
Unusual Network Activity
There can be several reasons for not receiving a response to an authentication
request. Do the following:
■
Use
ping
to ensure that the switch has access to the configured RADIUS
servers.
■
Verify that the switch is using the correct encryption key (RADIUS secret
key) for each server.
■
Verify that the switch has the correct IP address for each RADIUS server.
■
Ensure that the
radius-server timeout
period is long enough for network
conditions.
The switch does not authenticate a client even though the RADIUS
server is properly configured and providing a response to the
authentication request.
If the RADIUS server configuration for authenti
cating the client includes a VLAN assignment, ensure that the VLAN exists as
a static VLAN on the switch. See “How 802.1X Authentication Affects VLAN
Operation” in the
Access Security Guide
for your switch.
During RADIUS-authenticated client sessions, access to a VLAN on the
port used for the client sessions is lost.
If the affected VLAN is config
ured as untagged on the port, it may be temporarily blocked on that port during
an 802.1X session. This is because the switch has temporarily assigned another
VLAN as untagged on the port to support the client access, as specified in the
response from the RADIUS server. See “How 802.1X Authentication Affects
VLAN Operation” in the
Access Security Guide
for your switch.
The switch appears to be properly configured as a supplicant, but
cannot gain access to the intended authenticator port on the switch
to which it is connected.
If
aaa authentication port-access
is configured for
Local, ensure that you have entered the local
login
(operator-level) username
and password of the authenticator switch into the
identity
and
secret
parame
ters of the supplicant configuration. If instead, you enter the enable (manager
level) username and password, access will be denied.
The supplicant statistics listing shows multiple ports with the same
authenticator MAC address.
The link to the authenticator may have been
moved from one port to another without the supplicant statistics having been
cleared from the first port. Refer to the “Note on Supplicant Statistics” in the
Access Security Guide
for your switch.
The
show port-access authenticator <
port-list
>
command shows one or more
ports remain open after they have been configured with
control
C-10
Summary of Contents for ProCurve 2610-24
Page 1: ...Management and Configuration Guide 2610 2610 PWR ProCurve Switches R 11 XX www procurve com ...
Page 2: ......
Page 18: ...xvi ...
Page 24: ...Product Documentation xxii ...
Page 54: ...Using the Menu Interface Where To Go From Here 3 16 ...
Page 94: ...Using the Web Browser Interface Status Reporting Features 5 24 ...
Page 132: ...Switch Memory and Configuration Multiple Configuration Files 6 38 ...
Page 148: ...Interface Access and System Information System Information 7 16 ...
Page 192: ...Time Protocols SNTP Messages in the Event Log 9 24 ...
Page 256: ...Power Over Ethernet PoE Operation PoE Event Log Messages 11 18 ...
Page 280: ...Port Trunking Port Status and Configuration 12 24 ...
Page 362: ...File Transfers Copying Diagnostic Data to a Remote Host PC or Unix Workstation A 24 ...
Page 438: ...Troubleshooting Restoring a Flash Image C 48 ...
Page 446: ...MAC Address Management Viewing the MAC Addresses of Connected Devices D 8 ...
Page 450: ...Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time E 4 ...
Page 462: ...12 Index ...
Page 463: ......