Rockwell Automation 1783-WAPxxx Stratix 5100 Wireless Access Point User Manual - Manual (Page 587)

Rockwell Automation Publication 1783-UM006A-EN-P - May 2014 587
Error and Event Messages Appendix C
DOT11-2-NO_FIRMWARE: “Interface %s, no
radio firmware file (%s) was found.”
When trying to upgrade firmware, the file for the radio
was not found in the flash file system. Or, the IOS on the
access point is corrupt. The wrong image has been loaded into the
unit. Locate the correct image based on the
type of radio used. To resolve this issue you
can reload the access point with a new Cisco
IOS image.
Instructions for reloading an image are found
in
Reloading the Access Point Image on
page 566 .
If the IOS on the access point is corrupt,
reload the access point image by using the
Mode button method.
See
Using the MODE Button on page 563 .
DOT11-2-BAD_FIRMWARE: “Interface %s,
radio firmware file (%s) is invalid.”
When trying to upgrade firmware into the indicated
interface the indicated radio firmware file was found to be
invalid. Make sure the correct firmware image file is
in the place where the unit expects to find it.
DOT11-2-RADIO_FAILED: “Interface %s,
failed - %s.”
The radio driver on the indicated interface found a severe
error and is shutting down for the indicated reason. None.
DOT11-4-FLASH_RADIO_DONE: “Interface %s,
flashing radio firmware completed.”
The indicated interface radio firmware upgrade is
complete, and the radio restarts with the new firmware. None.
DOT11-4-UPLINK_LINK_DOWN: “Interface %s,
parent lost: %s.”
The connection to the parent access point on the indicated
interface was lost for the reason indicated. The unit tries
to find a new parent access point. None.
DOT11-4-CANT_ASSOC: Cannot associate: $s The unit could not establish a connection to a parent
access point for the displayed reason. Verify that the basic configuration settings
(SSID, WEP, and others) of the parent access
point and this unit match.
DOT11-4-CLIENT_NOT_FOUND: “Client was not
found.”
Client was not found while checking mic. None.
DOT11-4-MAXRETRIES: Packet to client
[mac] reached max retries, remove the
client
A packet sent to the client has not been successfully
delivered many times, and the max retries limit has been
reached. The client is deleted from the association table. None.
DOT11-4-BRIDGE_LOOP: “Bridge loop
detected between WGB %e and device %e.”
The indicated workgroup bridge reported the address of
one of its indicated Ethernet clients and the access point
already had that address marked as being somewhere
else on the network. Click Refresh on the Associations page on the
access point GUI, or enter the
clear
dot11 statistics
command on CLI.
DOT11-4-ANTENNA_INVALID: “Interface %s,
current antenna position not supported,
radio disabled.”
The Indicated AIR-RM21A radio module does not support
the high-gain position for the external antenna (the high-
gain position is folded flat against the access point). The
access point automatically disables the radio when the
antenna is in the high-gain position. Fold the antenna on the AIR-RM21A radio
module so that it is oriented 90° degrees to
the body of the access point.
DOT11-6-ANTENNA_GAIN: “Interface %s,
antenna position/gain changed, adjusting
transmitter power.”
The antenna gain has changed so the list of allowed
power levels must be adjusted. None.
DOT11-4-DIVER_USED: “Interface %s Mcs
rates 8-15 disabled due to only one
transmit or receive antenna enabled.”
The rates listed require at least 2 receive or transmit
antennas be enabled. Install and enable at least 2 receive or
transmit antennas on the access point.
DOT11-3-RF-LOOPBACK_FAILURE: “Interface
%s Radio failed to pass RF loopback
test.”
Radio loopback test failed for the interface indicated. None.
DOT11-3-RF-LOOPBACK_FREQ_FAILURE:
“Interface %s failed to pass RF loopback
test.”
Radio loopback test failed at a given frequency for the
indicated interface. None.
DOT11-7-AUTH_FAILED: “Station %e
Authentication failed”
The indicated station failed authentication. Verify that the user entered the correct
username and password, and verify that the
authentication server is online.
Table 6 - Subsystem Messages (Continued)
Message Explanation Recommended Action