Allied Telesis AT-WA7501 - Manual (Page 258)

Chapter 8: Managing, Troubleshooting, and Upgrading Access Points
258
Recovering a
Failed Access
Point Note
Do not use this procedure to upgrade your access point software.
For help, see “Upgrading the Access Points” on page 261.
You should never need to use this procedure. However, if your access
point is not functioning, you may need to download an entirely new file
system. If the access point loses all its files except the boot ROM code,
you cannot ping the access point, you cannot establish a telnet session to
the access point, and the LEDs display this pattern.
You are implementing
802.1x security and you
cannot get an end device
to authenticate with a
RADIUS server. ˆ Verify that the root access point is running software
release 1.72 or later.
ˆ Verify that the RADIUS server IP address is correct.
Re-enter the RADIUS server secret key in both the
access point and the RADIUS server.
ˆ Verify that the IAPP secret key is the same in all
access points.
ˆ Verify that the access point that the end device is
communicating with has the 802.1x Authentication
field set to authenticate the radio that is in the end
device.
ˆ Verify that your end device is configured properly
for 802.1x security. For help, see the end device
user’s manual.
Table 75. General Security Troubleshooting (Continued)
Problem/Question Possible Solution/Answer
Table 76. LED Pattern of a Failed Access Point
Only Boot
ROM code
is available
on access
point. Load
new files.
(Wireless #1 and #2 blink
in unison.)
LED On LED Off
LED Flashing