Cisco Cisco 2504 Wireless Controller 문제 해결 가이드

Refer to Cisco Technical Tips Conventions for more information on document conventions.

In a new installation, when a LAP is unable to find a WLC using the discovery algorithms, you can statically
configure the information necessary to join a controller via the console port and the APs CLI. Refer to
Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC) for more information on the WLC
discovery algorithms and the LAP registration process.

In order to manually configure static information on a LAP using the AP CLI interface, you can use these
EXEC mode CLI commands:

AP#capwap ap ip address <IP address> <subnet mask>

AP#capwap ap ip default−gateway <IP−address>

AP#capwap ap controller ip address <IP−address>

AP#capwap ap hostname <name>

  (optional)

Note: For LAPs that run LWAPP, replace capwap with lwapp in the previous commands.

You must issue these commands while in enable mode. The default enable password is Cisco.

The static information configured with the CLI commands is used by the AP to join a controller. After joining
the controller, the user can configure new settings on the LAP via the controller.

When you move your AP to a different location in your network and the LAP cannot join the previous WLC,
or if you want to manually reconfigure the AP to join another WLC, you have to enter the new controller
information in order to allow your AP to associate with a different controller.

In WLC releases prior to 6.0.188.0, once your LAP successfully registers with the WLC, the static LWAPP
configuration commands (discussed in the previous section) are locked out and are no longer accessible.

If you enter the clear lwapp private−config command, you might see this error message:

AP0017.5922.f384#clear lwapp private−config

This error message indicates that the static configuration commands are locked out because either:

This command was entered while the LAP is registered to a controller.

• 

The LAP was previously registered to a WLC, but the username/password was not changed from the
default.

• 

In order to re−enable the commands, you must have set the username and password while the LAP was joined
to the previous controller.