Cisco Cisco Aironet 1310 Access Point Bridge Information Guide
the primary, secondary, and tertiary fields to increase the odds on AP connections to your
preference.
preference.
Q. With LWAPP, is it possible to determine the SSIDs an AP has on an
individual AP basis? What is required to be able to have specific APs in
a zone that use a unique SSID, and all the rest that use another set of
SSIDs?
individual AP basis? What is required to be able to have specific APs in
a zone that use a unique SSID, and all the rest that use another set of
SSIDs?
A. With the WLAN override option, you can choose which SSIDs an AP offers. Controllers
support only up to 16 SSIDs each, so you can only choose from among the supported 16. This
is done on a per−AP basis.
support only up to 16 SSIDs each, so you can only choose from among the supported 16. This
is done on a per−AP basis.
Q. When I enable some LWAPP commands on my LAP, I get an error that
says the command is disabled. Why is this?
says the command is disabled. Why is this?
AccessPoint#clear lwapp ap controller ip address ERROR!!! Command is disabled.
A. Once your AP has successfully joined a controller, the LWAPP commands are disabled. In
order to enable LWAPP commands again, you must set the username/password of the AP
from the controller CLI with the config ap username <name> password <pwd>
<cisco−ap>/all command. Once that is done, you can do a clear lwapp private−config in the
AP CLI to allow you to manually re−issue the AP LWAPP configuration commands.
order to enable LWAPP commands again, you must set the username/password of the AP
from the controller CLI with the config ap username <name> password <pwd>
<cisco−ap>/all command. Once that is done, you can do a clear lwapp private−config in the
AP CLI to allow you to manually re−issue the AP LWAPP configuration commands.
Note: If you are running WLC version 5.0 and later, use this command to set the username
and password on the AP:
and password on the AP:
config ap mgmtuser add username AP_username
password AP_password secret secret {all | Cisco_AP}
Q. When two APs are on the same channel and can see each other, what
are the implications (for roaming throughput, etc.) over the use of four
channels instead of three? How do the APs react in such a situation and
how does a client react?
are the implications (for roaming throughput, etc.) over the use of four
channels instead of three? How do the APs react in such a situation and
how does a client react?
A. Whether APs are on the same channel or not, it does not particularly impact client
roaming. What does matter is sufficient cell overlap such that clients can make smooth
transitions from the coverage area of one AP to the next. The intent of a move from a
three−channel design to a four−channel design is to increase design flexibility (because of the
extra channel). This approach is shortsighted because, while you add a bit of deployment
flexibility (since you have another channel), you actually increase the amount of co−channel
interference. What you might gain in design flexibility with the four−channel approach, you
lose in the added co−channel interference. Bottom line: do not use a four−channel design.
roaming. What does matter is sufficient cell overlap such that clients can make smooth
transitions from the coverage area of one AP to the next. The intent of a move from a
three−channel design to a four−channel design is to increase design flexibility (because of the
extra channel). This approach is shortsighted because, while you add a bit of deployment
flexibility (since you have another channel), you actually increase the amount of co−channel
interference. What you might gain in design flexibility with the four−channel approach, you
lose in the added co−channel interference. Bottom line: do not use a four−channel design.
Q. Can we control when clients roam? Can we let the client roam solely
based on the signal strength on an individual AP basis and for all client
adapters?
based on the signal strength on an individual AP basis and for all client
adapters?
A. Today, roaming is always a function of the client, and the choice to roam or not is
implemented differently in various clients. Directed Roaming is a part of CCX, but it is an
optional feature and is not used today.
implemented differently in various clients. Directed Roaming is a part of CCX, but it is an
optional feature and is not used today.