Cisco Wireless LAN Controller Configuration Guide, Release 6.0

Guidelines for Using CAPWAP

Follow these guidelines when using CAPWAP:

• If your firewall is currently configured to allow traffic only from access points using LWAPP, you must change the rules of the firewall to allow traffic from access points using CAPWAP.
• Make sure that the CAPWAP UDP ports 5246 and 5247 (similar to the LWAPP UDP ports 12222 and 12223) are enabled and are not blocked by an intermediate device that could prevent an access point from joining the controller.
• If access control lists (ACLs) are in the control path between the controller and its access points, you need to open new protocol ports to prevent access points from being stranded.

Configuring Data Encryption

Cisco 5500 series controllers enable you to encrypt CAPWAP control packets (and optionally CAPWAP data packets) that are sent between the access point and the controller using Datagram Transport Layer Security (DTLS). DTLS is a standards-track Internet Engineering Task Force (IETF) protocol based on TLS. CAPWAP control packets are management packets exchanged between a controller and an access point while CAPWAP data packets encapsulate forwarded wireless frames. CAPWAP control and data packets are sent over separate UDP ports: 5246 (control) and 5247 (data). If an access point does not support DTLS data encryption, DTLS is enabled only for the control plane, and a DTLS session for the data plane is not established.

Note Only 5500 series controllers support data encryption. This feature is not available on other controller platforms. If an access point with data encryption enabled tries to join any other controller, the access point joins the controller, but data packets are sent unencrypted.

Note Cisco 1130 and 1240 series access points support DTLS data encryption with software-based encryption, and 1140 and 1250 series access points support DTLS data encryption with hardware-based encryption. Data-encrypted access points can join a 5500 series controller only if the wplus license is installed on the controller. If the wplus license is not installed, the access points cannot join the controller.

DTLS data encryption is enabled automatically for OfficeExtend access points but disabled by default for all other access points. Most access points are deployed in a secure network within a company building, so data encryption is not necessary. In contrast, the traffic between an OfficeExtend access point and the controller travels through an unsecure public network, so data encryption is more important for these access points. When data encryption is enabled, traffic is encrypted at the access point before it is sent to the controller and at the controller before it is sent to the client.

Note Encryption limits throughput at both the controller and the access point, and maximum throughput is desired for most enterprise networks.

Note Refer to the “OfficeExtend Access Points” section for more information on OfficeExtend access points.

You can use the controller GUI or CLI to enable or disable DTLS data encryption for a specific access point or for all access points.

Using the GUI to Configure Data Encryption

Using the controller GUI, follow these steps to enable DTLS data encryption for access points on the controller.

Step 1 Make sure that the wplus license is installed on the 5500 series controller. Once the license is installed, you can enable data encryption for the access points.

Note Note Refer to the Configuring Controller Settings chapter for information on obtaining and installing licenses.

Step 2 Choose Wireless > Access Points > All APs to open the All APs page.

Step 3 Click the name of the access point for which you want to enable data encryption.

Step 4 Choose the Advanced tab to open the All APs > Details for (Advanced) page (see Figure 1).

Figure 1 All APs > Details for (Advanced) Page

Step 5 Check the Data Encryption check box to enable data encryption for this access point or uncheck it to disable this feature. The default value is unchecked.

Note Changing the data encryption mode requires the access points to rejoin the controller.

Step 6 Click Apply to commit your changes.

Step 7 Click Save Configuration to save your changes.

Using the CLI to Configure Data Encryption

Using the controller CLI, follow these steps to enable DTLS data encryption for access points on the controller.

Step 1 To enable or disable data encryption for all access points or a specific access point, enter this command:

config ap link-encryption { enable | disable } { all | Cisco_AP}

The default value is disabled.

Note Changing the data encryption mode requires the access points to rejoin the controller.

Step 2 When prompted to confirm that you want to disconnect the access point(s) and attached client(s), enter Y .

Step 3 To save your changes, enter this command:

save config

Step 4 To see the encryption state of all access points or a specific access point, enter this command:

show ap link-encryption { all | Cisco_AP}

Information similar to the following appears:

This command also shows authentication errors, which tracks the number of integrity check failures, and replay errors, which tracks the number of times that the access point receives the same packet.

Step 5 To see a summary of all active DTLS connections, enter this command:

show dtls connections

Information similar to the following appears:

Note If you experience any problems with DTLS data encryption, enter this command to debug all DTLS messages, events, traces, or packets: debug dtls {all | event | trace | packet} {enable | disable}.

Viewing CAPWAP MTU Information

To view the maximum transmission unit (MTU) for the CAPWAP path on the controller, enter this command. The MTU specifies the maximum size of any packet (in bytes) in a transmission.

show ap config general Cisco_AP

Information similar to the following appears:

Debugging CAPWAP

Use these CLI commands to obtain CAPWAP debug information:

• debug capwap events {enable | disable}—Enables or disables debugging of CAPWAP events.
• debug capwap errors {enable | disable}—Enables or disables debugging of CAPWAP errors.
• debug capwap detail {enable | disable}—Enables or disables debugging of CAPWAP details.
• debug capwap info {enable | disable}—Enables or disables debugging of CAPWAP information.
• debug capwap packet {enable | disable}—Enables or disables debugging of CAPWAP packets.
• debug capwap payload {enable | disable}—Enables or disables debugging of CAPWAP payloads.
• debug capwap hexdump {enable | disable}—Enables or disables debugging of the CAPWAP hexadecimal dump.
• debug capwap dtls-keepalive {enable | disable}—Enables or disables debugging of CAPWAP DTLS data keepalive packets.

The Controller Discovery Process

In a CAPWAP environment, a lightweight access point discovers a controller by using CAPWAP discovery mechanisms and then sends the controller a CAPWAP join request. The controller sends the access point a CAPWAP join response allowing the access point to join the controller. When the access point joins the controller, the controller manages its configuration, firmware, control transactions, and data transactions.

Upgrade and downgrade paths from LWAPP to CAPWAP or from CAPWAP to LWAPP are supported. An access point with an LWAPP image starts the discovery process in LWAPP. If it finds an LWAPP controller, it starts the LWAPP discovery process to join the controller. If it does not find a LWAPP controller, it starts the discovery in CAPWAP. If the number of times that the discovery process starts with one discovery type (CAPWAP or LWAPP) exceeds the maximum discovery count and the access point does not receive a discovery response, the discovery type changes to the other type. For example, if the access point does not discover the controller in LWAPP, it starts the discovery process in CAPWAP.

Note If an access point is in the UP state and its IP address changes, the access point tears down the existing CAPWAP tunnel and rejoins the controller. In previous software releases, the access point notifies the controller, and the session continues with the changed IP address without tearing down the session.

Note You must install software release 4.0.155.0 or later on the controller before connecting 1100 and 1300 series access points to the controller. The 1120 and 1310 access points were not supported prior to software release 4.0.155.0.

Note During the discovery process, the 1140 series access point will only query for Cisco CAPWAP Controllers. It will not query for LWAPP controllers. If you want this access point to query for both LWAPP and CAPWAP controllers then you need to update the DNS.

Note The Cisco controllers cannot edit or query any access point information using the CLI if the name of the access point contains a space.

Note Make sure that the controller is set to the current time. If the controller is set to a time that has already occurred, the access point might not join the controller because its certificate may not be valid for that time.

Access points must be discovered by a controller before they can become an active part of the network. The lightweight access points support these controller discovery processes:

• Layer 3 CAPWAP or LWAPP discovery—Can occur on different subnets from the access point and uses IP addresses and UDP packets rather the MAC addresses used by Layer 2 discovery.
• Over-the-air provisioning (OTAP)—This feature is supported by Cisco 5500 and 4400 series controllers. If this feature is enabled on the controller (on the controller General page or through the config network otap-mode { enable | disable } CLI command), all associated access points transmit wireless CAPWAP or LWAPP neighbor messages, and new access points receive the controller IP address from these messages. This feature is disabled by default and should remain disabled when all access points are installed.

Note Disabling OTAP on the controller does not disable it on the access point. OTAP cannot be disabled on the access point.

Note For more information about OTAP, see
http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/100516-ustnd-otap.html

• Locally stored controller IP address discovery—If the access point was previously associated to a controller, the IP addresses of the primary, secondary, and tertiary controllers are stored in the access point’s non-volatile memory. This process of storing controller IP addresses on an access point for later deployment is called priming the access point.
• DHCP server discovery—This feature uses DHCP option 43 to provide controller IP addresses to the access points. Cisco switches support a DHCP server option that is typically used for this capability. For more information about DHCP option 43, see the “Using DHCP Option 43 and DHCP Option 60” section.
• DNS discovery—The access point can discover controllers through your domain name server (DNS). For the access point to do so, you must configure your DNS to return controller IP addresses in response to CISCO-LWAPP-CONTROLLER.localdomain, where localdomain is the access point domain name. When an access point receives an IP address and DNS information from a DHCP server, it contacts the DNS to resolve CISCO-LWAPP-CONTROLLER.localdomain. When the DNS sends a list of controller IP addresses, the access point sends discovery requests to the controllers.

Verifying that Access Points Join the Controller

When replacing a controller, you need to make sure that access points join the new controller.

Using the GUI to Verify that Access Points Join the Controller

Follow these steps to ensure that access points join the new controller.

Step 1 Follow these steps to configure the new controller as a master controller.

a. Choose Controller > Advanced > Master Controller Mode to open the Master Controller Configuration page.

b. Check the Master Controller Mode check box.

c. Click Apply to commit your changes.

d. Click Save Configuration to save your changes.

Step 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure. Ask your network administrator for more information about this step.

Step 3 Restart the access points.

Step 4 Once all the access points have joined the new controller, configure the controller not to be a master controller by unchecking the Master Controller Mode check box on the Master Controller Configuration page.

Using the CLI to Verify that Access Points Join the Controller

Follow these steps to ensure that access points join the new controller.

Step 1 To configure the new controller as a master controller, enter this command:

config network master-base enable

Step 2 (Optional) Flush the ARP and MAC address tables within the network infrastructure. Ask your network administrator for more information about this step.

Step 3 Restart the access points.

Step 4 To configure the controller not to be a master controller once all the access points have joined the new controller, enter this command:

config network master-base disable

Using the GUI to Search the AP Filter

To search for access points using the controller GUI, follow these steps:

Step 1 Choose Monitor > Access Point Summary> All APs > Details to open the All APs page (see Figure 2).

Figure 2 All APs Page

This page lists all of the access points joined to the controller. For each access point, you can see its name, MAC address, uptime, status, operating mode, certificates, OfficeExtend access point status, and access point submode.

The total number of access points appears in the upper right-hand corner of the page. If the list of access points spans multiple pages, you can access these pages by clicking the page number links. Each page shows up to 20 access points.

Step 2 Click Change Filter to open the Search AP dialog box (see Figure 3).

Figure 3 Search AP Dialog Box

Step 3 Select one or more of the following check boxes to specify the criteria used when displaying access points:

• MAC Address —Enter the MAC address of an access point.

Note When you enable the MAC Address filter, the other filters are disabled automatically. When you enable any of the other filters, the MAC Address filter is disabled automatically.

• AP Name —Enter the name of an access point.
• AP Model—Enter the model name of an access point.
• Operating Status —Select one or more of the following check boxes to specify the operating status of the access points:

– UP —The access point is up and running.

– DOWN —The access point is not operational.

– REG —The access point is registered to the controller.

– DEREG —The access point is not registered to the controller.

– DOWNLOAD —The controller is downloading its software image to the access point.

• Port Number—Enter the controller port number to which the access point is connected.
• Admin Status —Choose Enabled or Disabled to specify whether the access points are enabled or disabled on the controller.
• AP Mode —Select one or more of the following options to specify the operating mode of the access points:

– Local—The default option.

Note The 600 OEAP series access point uses only local mode.

When an access point in local mode connects to a Cisco Flex 7500 Series Controller, it does not serve clients. The access point details are available in the controller. To enable an access point to serve clients or perform monitoring-related tasks when connected to the Cisco Flex 7500 Series Controller, the access point mode must be in hybrid-REAP or monitor mode. Use the following command to automatically convert access points to a hybrid-REAP mode or monitor mode on joining the controller:

config ap autoconvert {hreap | monitor | disable}

All access points that connect to the controller will either be converted to hybrid-REAP mode or monitor mode depending on the configuration provided.

– HREAP (hybrid Remote Edge lightweight Access Point) — This mode is used for 1040, 1130AG, 1140, 1240AG, 1250, 1260, 3500, AP801, and AP802 access points.

– REAP—This mode is the remote edge lightweight access point.

– Monitor—This mode is the monitor-only mode.

– Rogue Detector—This mode monitors the rogue APs on wire. It does not transmit or receive frames over the air or contain rogue APs.

For more information on Rogue detection, see
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/70987-rogue-detect.html

– Sniffer—The access point starts sniffing the air on a given channel. It captures and forwards all the packets from the clients on that channel to a remote machine that runs Airopeek or Wireshark (packet analyzers for IEEE 802.11 wireless LANs). It includes information on the time stamp, signal strength, packet size, and so on.

Note The Bridge option is displayed only if the AP is bridge capable.

Note If the AP mode is set to “Bridge” and the AP is not REAP capable, an error appears.

– Bridge—This mode sets the AP mode to “Bridge” if you are connecting a Root AP.

– SE-Connect—This mode allows you to connect to spectrum expert and it allows the access point to perform spectrum intelligence.

Note The AP3500 supports the spectrum intelligence and AP1260 does not support the spectrum intelligence.

Note When an access point is configured in SE-Connect mode, the access point reboots and rejoins the controller. Access points that are configured in this mode do not serve the client.

• Certificate Type —Select one or more of the following check boxes to specify the types of certificates installed on the access points:

– MIC —Manufactured-installed certificate

– SSC —Self-signed certificate

– LSC —Local significant certificate

Note See the “Authorizing Access Points” section for more information on these certificate types.

• Primary S/W Version—Select this check box to enter the primary software version number
• Backup S/W Version—Select this check box to enter the secondary software version number.

Step 4 Click Apply to commit your changes. Only the access points that match your search criteria appear on the All APs page, and the Current Filter parameter at the top of the page specifies the filter used to generate the list (for example, MAC Address:00:1d:e5:54:0e:e6, AP Name:pmsk-ap, Operational Status: UP, Status: Enabled, and so on).

Note If you want to remove the filters and display the entire access point list, click Clear Filter.

Using the GUI to Configure Global Credentials for Access Points

Using the controller GUI, follow these steps to configure global credentials for access points that join the controller.

Step 1 Choose Wireless > Access Points > Global Configuration to open the Global Configuration page (see Figure 7).

Figure 7 Global Configuration Page

Step 2 In the Username field, enter the username that is to be inherited by all access points that join the controller.

Step 3 In the Password field, enter the password that is to be inherited by all access points that join the controller.

Step 4 In the Enable Password field, enter the enable password that is to be inherited by all access points that join the controller.

Step 5 Click Apply to send the global username, password, and enable password to all access points that are currently joined to the controller or that join the controller in the future.

Step 6 Click Save Configuration to save your changes.

Step 7 If desired, you can choose to override the global credentials for a specific access point and assign a unique username, password, and enable password to this access point. Follow these steps to do so:

a. Choose Access Points > All APs to open the All APs page.

b. Click the name of the access point for which you want to override the global credentials.

c. Choose the Credentials tab. The All APs > Details for (Credentials) page appears (see Figure 8).

Figure 8 All APs > Details for (Credentials) Page

d. Check the Over-ride Global Credentials check box to prevent this access point from inheriting the global username, password, and enable password from the controller. The default value is unchecked.

e. In the Username, Password, and Enable Password fields, enter the unique username, password, and enable password that you want to assign to this access point.

Note The information that you enter is retained across controller and access point reboots and if the access point joins a new controller.

f. Click Apply to commit your changes.

g. Click Save Configuration to save your changes.

Note If you ever want to force this access point to use the controller’s global credentials, simply uncheck the Over-ride Global Credentials check box.

Using the CLI to Configure Global Credentials for Access Points

Using the controller CLI, follow these steps to configure global credentials for access points that join the controller.

Step 1 To configure the global username, password, and enable password for all access points currently joined to the controller as well as any access points that join the controller in the future, enter this command:

config ap mgmtuser add username user password password enablesecret enable_password all

Step 2 If desired, you can choose to override the global credentials for a specific access point and assign a unique username, password, and enable password to this access point. To do so, enter this command:

config ap mgmtuser add username user password password enablesecret enable_password Cisco_AP

The credentials that you enter in this command are retained across controller and access point reboots and if the access point joins a new controller.

Note If you ever want to force this access point to use the controller’s global credentials, enter this command: config ap mgmtuser delete Cisco_AP. The following message appears after you execute this command: “AP reverted to global username configuration.”

Step 3 To save your changes, enter this command:

save config

Step 4 To verify that global credentials are configured for all access points that join the controller, enter this command:

show ap summary

Information similar to the following appears:

Note If global credentials are not configured, the Global AP User Name field shows “Not Configured.”

Step 5 To see the global credentials configuration for a specific access point, enter this command:

show ap config general Cisco_AP

Note The name of the access point is case sensitive.

Information similar to the following appears:

Note If this access point is configured for global credentials, the AP User Mode fields shows “Automatic.” If the global credentials have been overwritten for this access point, the AP User Mode field shows “Customized.”

Using the GUI to Configure Authentication for Access Points

Using the controller GUI, follow these steps to configure authentication for access points that join the controller.

Step 1 Choose Wireless > Access Points > Global Configuration to open the Global Configuration page (see Figure 9).

Figure 9 Global Configuration Page

Step 2 Under 802.1x Supplicant Credentials, check the 802.1x Authentication check box.

Step 3 In the Username field, enter the username that is to be inherited by all access points that join the controller.

Step 4 In the Password and Confirm Password fields, enter the password that is to be inherited by all access points that join the controller.

Note You must enter a strong password in these fields. Strong passwords have the following characteristics:
- They are at least eight characters long.
- They contain a combination of upper- and lowercase letters, numbers, and symbols.
- They are not a word in any language.

Step 5 Click Apply to send the global authentication username and password to all access points that are currently joined to the controller and to any that join the controller in the future.

Step 6 Click Save Configuration to save your changes.

Step 7 If desired, you can choose to override the global authentication settings and assign a unique username and password to a specific access point. Follow these steps to do so:

a. Choose Access Points > All APs to open the All APs page.

b. Click the name of the access point for which you want to override the authentication settings.

c. Choose the Credentials tab to open the All APs > Details for (Credentials) page (see Figure 10).

Figure 10 All APs > Details for (Credentials) Page

d. Under 802.1x Supplicant Credentials, check the Over-ride Global Credentials check box to prevent this access point from inheriting the global authentication username and password from the controller. The default value is unchecked.

e. In the Username, Password, and Confirm Password fields, enter the unique username and password that you want to assign to this access point.

Note The information that you enter is retained across controller and access point reboots and whenever the access point joins a new controller.

f. Click Apply to commit your changes.

g. Click Save Configuration to save your changes.

Note If you ever want to force this access point to use the controller’s global authentication settings, simply uncheck the Over-ride Global Credentials check box.

Using the CLI to Configure Authentication for Access Points

Using the controller CLI, follow these steps to configure authentication for access points that join the controller.

Step 1 To configure the global authentication username and password for all access points currently joined to the controller as well as any access points that join the controller in the future, enter this command:

config ap dot1xuser add username user password password all

Note You must enter a strong password for the password parameter. Strong passwords have the following characteristics:
- They are at least eight characters long.
- They contain a combination of upper- and lowercase letters, numbers, and symbols.
- They are not a word in any language.

Step 2 If desired, you can choose to override the global authentication settings and assign a unique username and password to a specific access point. To do so, enter this command:

config ap dot1xuser add username user password password Cisco_AP

Note You must enter a strong password for the password parameter. See the note in To configure the global authentication username and password for all access points currently joined to the controller as well as any access points that join the controller in the future, enter this command: for the characteristics of strong passwords.

The authentication settings that you enter in this command are retained across controller and access point reboots and whenever the access point joins a new controller.

Note If you ever want to force this access point to use the controller’s global authentication settings, enter this command: config ap dot1xuser delete Cisco_AP. The following message appears after you execute this command: “AP reverted to global username configuration.”

Step 3 To save your changes, enter this command:

save config

Step 4 If you ever want to disable 802.1X authentication for all access points or for a specific access point, enter this command:

config ap dot1xuser disable { all | Cisco_AP }

Note You can disable 802.1X authentication for a specific access point only if global 802.1X authentication is not enabled. If global 802.1X authentication is enabled, you can disable 802.1X for all access points only.

Step 5 To view the authentication settings for all access points that join the controller, enter this command:

show ap summary

Information similar to the following appears:

Note If global authentication settings are not configured, the Global AP Dot1x User Name field shows “Not Configured.”

Step 6 To view the authentication settings for a specific access point, enter this command:

show ap config general Cisco_AP

Note The name of the access point is case sensitive.

Information similar to the following appears:

Note If this access point is configured for global authentication, the AP Dot1x User Mode fields shows “Automatic.” If the global authentication settings have been overwritten for this access point, the AP Dot1x User Mode field shows “Customized.”

Configuring the Switch for Authentication

On the switch CLI, enter these commands to enable 802.1X authentication on a switch port:

Switch# configure terminal

Switch(config)# dot1x system-auth-control

Switch(config)# aaa new-model

Switch(config)# aaa authentication dot1x default group radius

Switch(config)# radius-server host ip_addr auth-port port acct-port port key key

Switch(config)# interface fastethernet2/1

Switch(config-if)# switchport mode access

Switch(config-if)# dot1x pae authenticator

Switch(config-if)# dot1x port-control auto

Switch(config-if)# end

Guidelines for Using Access Points Converted to Lightweight Mode

Keep these guidelines in mind when you use autonomous access points that have been converted to lightweight mode:

• Access points converted to lightweight mode do not support Wireless Domain Services (WDS). Converted access points communicate only with Cisco wireless LAN controllers and cannot communicate with WDS devices. However, the controller provides functionality equivalent to WDS when the access point associates to it.
• In controller software release 4.2 or later, all Cisco lightweight access points support 16 BSSIDs per radio and a total of 16 wireless LANs per access point. In previous releases, they supported only 8 BSSIDs per radio and a total of 8 wireless LANs per access point. When a converted access point associates to a controller, only wireless LANs with IDs 1 through 16 are pushed to the access point.
• Access points converted to lightweight mode must get an IP address and discover the controller using DHCP, DNS, or IP subnet broadcast.
• After you convert an access point to lightweight mode, the console port provides read-only access to the unit.
• The 1130AG and 1240AG access points support hybrid-REAP mode. See the Configuring Hybrid REAP chapter for details.
• The upgrade conversion tool adds the self-signed certificate (SSC) key-hash to only one of the controllers on the Cisco WiSM. After the conversion has been completed, add the SSC key-hash to the second controller on the Cisco WiSM by copying the SSC key-hash from the first controller to the second controller. To copy the SSC key-hash, open the AP Policies page of the controller GUI ( Security > AAA > AP Policies ) and copy the SSC key-hash from the SHA1 Key Hash column under AP Authorization List (see Figure 13). Then, using the second controller’s GUI, open the same page and paste the key-hash into the SHA1 Key Hash field under Add AP to Authorization List. If you have more than one Cisco WiSM, use WCS to push the SSC key-hash to all the other controllers.

Reverting from Lightweight Mode to Autonomous Mode

After you use the upgrade tool to convert an autonomous access point to lightweight mode, you can convert the access point from a lightweight unit back to an autonomous unit by loading a Cisco IOS release that supports autonomous mode (Cisco IOS release 12.3(7)JA or earlier). If the access point is associated to a controller, you can use the controller to load the Cisco IOS release. If the access point is not associated to a controller, you can load the Cisco IOS release using TFTP. In either method, the access point must be able to access a TFTP server that contains the Cisco IOS release to be loaded.

Using a Controller to Return to a Previous Release

Follow these steps to revert from lightweight mode to autonomous mode using a wireless LAN controller:

Step 1 Log into the CLI on the controller to which the access point is associated.

Step 2 Enter this command:

config ap tftp-downgrade tftp-server-ip-address filename access-point-name

Step 3 Wait until the access point reboots and reconfigure the access point using the CLI or GUI.

Using the MODE Button and a TFTP Server to Return to a Previous Release

Follow these steps to revert from lightweight mode to autonomous mode by using the access point MODE (reset) button to load a Cisco IOS release from a TFTP server:

Step 1 The PC on which your TFTP server software runs must be configured with a static IP address in the range of 10.0.0.2 to 10.0.0.30.

Step 2 Make sure that the PC contains the access point image file (such as c1200-k9w7-tar.123-7.JA.tar for a 1200 series access point) in the TFTP server folder and that the TFTP server is activated.

Step 3 Rename the access point image file in the TFTP server folder to c1200-k9w7-tar.default for a 1200 series access point.

Step 4 Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable.

Step 5 Disconnect power from the access point.

Step 6 Press and hold the MODE button while you reconnect power to the access point.

Note The MODE button on the access point must be enabled. Follow the steps in the “Disabling the Reset Button on Access Points Converted to Lightweight Mode” section to check the status of the access point MODE button.

Step 7 Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds), and release the MODE button.

Step 8 Wait until the access point reboots as indicated by all LEDs turning green followed by the Status LED blinking green.

Step 9 After the access point reboots, reconfigure the access point using the GUI or the CLI.

Authorizing Access Points

In controller software releases prior to 5.2, the controller may either use self-signed certificates (SSCs) to authenticate access points or send the authorization information to a RADIUS server (if access points have manufactured-installed certificates [MICs]). In controller software release 5.2 or later, you can configure the controller to use a local significant certificate (LSC).

Authorizing Access Points Using SSCs

The Control and Provisioning of Wireless Access Points protocol (CAPWAP) secures the control communication between the access point and controller by means of a secure key distribution requiring X.509 certificates on both the access point and controller. CAPWAP relies on a priori provisioning of the X.509 certificates. Cisco Aironet access points shipped before July 18, 2005 do not have a MIC, so these access points create an SSC when upgraded to operate in lightweight mode. Controllers are programmed to accept local SSCs for authentication of specific access points and do not forward those authentication requests to a RADIUS server. This behavior is acceptable and secure.

Authorizing Access Points Using MICs

You can configure controllers to use RADIUS servers to authorize access points using MICs. The controller uses an access point’s MAC address as both the username and password when sending the information to a RADIUS server. For example, if the MAC address of the access point is 000b85229a70, both the username and password used by the controller to authorize the access point are 000b85229a70.

Note The lack of a strong password by the use of the access point’s MAC address should not be an issue because the controller uses MIC to authenticate the access point prior to authorizing the access point through the RADIUS server. Using MIC provides strong authentication.

Note If you use the MAC address as the username and password for access point authentication on a RADIUS AAA server, do not use the same AAA server for client authentication.

Authorizing Access Points Using LSCs

You can use an LSC if you want your own public key infrastructure (PKI) to provide better security, to have control of your certificate authority (CA), and to define policies, restrictions, and usages on the generated certificates.

The LSC CA certificate is installed on access points and controllers. You need to provision the device certificate on the access point. The access point gets a signed X.509 certificate by sending a certRequest to the controller. The controller acts as a CA proxy and receives the certRequest signed by the CA for the access point.

Note Access points that are configured for bridge mode are not supported.

Using the GUI to Configure LSC

Using the controller GUI, follow these steps to enable the use of LSC on the controller.

Step 1 Choose Security > Certificate > LSC to open the Local Significant Certificates (LSC) - General page (see Figure 11).

Figure 11 Local Significant Certificates (LSC) - General Page

Step 2 To enable LSC on the system, check the Enable LSC on Controller check box.

Step 3 In the CA Server URL field, enter the URL to the CA server. You can enter either a domain name or an IP address.

Step 4 In the Params fields, enter the parameters for the device certificate. The key size is a value from 384 to 2048 (in bits), and the default value is 2048.

Step 5 Click Apply to commit your changes.

Step 6 To add the CA certificate into the controller’s CA certificate database, hover your cursor over the blue drop-down arrow for the certificate type and choose Add .

Step 7 Choose the AP Provisioning tab to open the Local Significant Certificates (LSC) - AP Provisioning page (see Figure 12).

Figure 12 Local Significant Certificates (LSC) - AP Provisioning Page

Step 8 To provision the LSC on the access point, check the Enable check box and click Update .

Step 9 When a message appears indicating that the access points will be rebooted, click OK .

Step 10 In the Number of Attempts to LSC field, enter the number of times that the access point attempts to join the controller using an LSC before the access point reverts to the default certificate (MIC or SSC). The range is 0 to 255 (inclusive), and the default value is 3.

Note If you set the number of retries to a non-zero value and the access point fails to join the controller using an LSC after the configured number of retries, the access point reverts to the default certificate. If you set the number of retries to 0 and the access point fails to join the controller using an LSC, the access point does not attempt to join the controller using the default certificate.

Note If you are configuring LSC for the first time, Cisco recommends that you configure a non-zero value.

Step 11 To add access points to the provision list, enter the access point MAC address in the AP Ethernet MAC Addresses field and click Add .

Note To remove an access point from the provision list, hover your cursor over the blue drop-down arrow for the access point and choose Remove.

Note If you configure an access point provision list, only the access points in the provision list are provisioned when you enable AP provisioning. If you do not configure an access point provision list, all access points with a MIC or SSC certificate that join the controller are LSC provisioned.

Step 12 Click Apply to commit your changes.

Step 13 Click Save Configuration to save your changes.

Using the CLI to Configure LSC

Using the controller CLI, follow these steps to enable the use of LSC on the controller.

Step 1 To enable LSC on the system, enter this command:

config certificate lsc { enable | disable }

Step 2 To configure the URL to the CA server, enter this command:

config certificate lsc ca-server http: //url:port/path

where url can be either a domain name or IP address.

Note You can configure only one CA server. To configure a different CA server, delete the configured CA server using the config certificate lsc ca-server delete command; then configure a different CA server.

Step 3 To add the LSC CA certificate into the controller’s CA certificate database, enter this command:

config certificate lsc ca-cert { add | delete }

Step 4 To configure the parameters for the device certificate, enter this command:

config certificate lsc subject-params country state city orgn dept email

Note The common name (CN) is generated automatically on the access point using the current MIC/SSC format Cxxxx-MacAddr, where xxxx is the product number.

Step 5 To configure a key size, enter this command:

config certificate lsc other-params keysize

The keysize is a value from 384 to 2048 (in bits), and the default value is 2048.

Step 6 To add access points to the provision list, enter this command:

config certificate lsc ap-provision auth-list add AP_mac_addr

Note To remove access points from the provision list, enter this command: config certificate lsc ap-provision auth-list delete AP_mac_addr.

Note If you configure an access point provision list, only the access points in the provision list are provisioned when you enable AP provisioning (in To provision the LSC on the access point, enter this command:). If you do not configure an access point provision list, all access points with a MIC or SSC certificate that join the controller are LSC provisioned.

Step 7 To configure the number of times that the access point attempts to join the controller using an LSC before the access point reverts to the default certificate (MIC or SSC), enter this command:

config certificate lsc ap-provision revert-cert retries

where retries is a value from 0 to 255, and the default value is 3.

Note If you set the number of retries to a non-zero value and the access point fails to join the controller using an LSC after the configured number of retries, the access point reverts to the default certificate. If you set the number of retries to 0 and the access point fails to join the controller using an LSC, the access point does not attempt to join the controller using the default certificate.

Note If you are configuring LSC for the first time, Cisco recommends that you configure a non-zero value.

Step 8 To provision the LSC on the access point, enter this command:

config certificate lsc ap-provision { enable | disable }

Step 9 To view the LSC summary, enter this command:

show certificate lsc summary

Information similar to the following appears:

Step 10 To view details about the access points that are provisioned using LSC, enter this command:

show certificate lsc ap-provision

Information similar to the following appears:

Using the GUI to Authorize Access Points

Using the controller GUI, follow these steps to authorize access points.

Step 1 Choose Security > AAA > AP Policies to open the AP Policies page (see Figure 13).

Figure 13 AP Policies Page

Step 2 If you want the access point to accept self-signed certificates (SSCs), manufactured-installed certificates (MICs), or local significant certificates (LSCs), check the appropriate check box.

Step 3 If you want the access points to be authorized using a AAA RADIUS server, check the Authorize MIC APs against auth-list or AAA check box.

Step 4 If you want the access points to be authorized using an LSC, check the Authorize LSC APs against auth-list check box.

Step 5 Click Apply to commit your changes.

Step 6 Follow these steps to add an access point to the controller’s authorization list:

a. Click Add to access the Add AP to Authorization List area.

b. In the MAC Address field, enter the MAC address of the access point.

c. From the Certificate Type drop-down box, choose MIC , SSC , or LSC .

d. Click Add . The access point appears in the access point authorization list.

Note To remove an access point from the authorization list, hover your cursor over the blue drop-down arrow for the access point and choose Remove.

Note To search for a specific access point in the authorization list, enter the MAC address of the access point in the Search by MAC field and click Search.

Using the CLI to Authorize Access Points

Using the controller CLI, follow these steps to authorize access points.

Step 1 To configure an access point authorization policy, enter this command:

config auth-list ap-policy { authorize-ap { enable | disable } | authorize-lsc-ap { enable | disable }}

Step 2 To configure an access point to accept manufactured-installed certificates (MICs), self-signed certificates (SSCs), or local significant certificates (LSCs), enter this command:

config auth-list ap-policy { mic | ssc | lsc { enable | disable }}

Step 3 To add an access point to the authorization list, enter this command:

config auth-list add { mic | ssc | lsc } ap_mac [ ap_key ]

where ap_key is an optional key hash value equal to 20 bytes or 40 digits.

Note To delete an access point from the authorization list, enter this command:
config auth-list delete ap_mac.

Step 4 To view the access point authorization list, enter this command:

show auth-list

Information similar to the following appears:

Using DHCP Option 43 and DHCP Option 60

Cisco Aironet access points use the type-length-value (TLV) format for DHCP option 43. DHCP servers must be programmed to return the option based on the access point’s DHCP Vendor Class Identifier (VCI) string (DHCP option 60). Table 1 lists the VCI strings for Cisco access points capable of operating in lightweight mode.

This is the format of the TLV block:

• Type: 0xf1 (decimal 241)
• Length: Number of controller IP addresses * 4
• Value: List of the IP addresses of controller management interfaces

Refer to the product documentation for your DHCP server for instructions on configuring DHCP option 43. The Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode document contains example steps for configuring option 43 on a DHCP server.

Troubleshooting the Access Point Join Process

Access points can fail to join a controller for many reasons: a RADIUS authorization is pending, self-signed certificates are not enabled on the controller, the access point and controller’s regulatory domains do not match, and so on.

Note For join information specific to an OfficeExtend access point, refer to the “OfficeExtend Access Points” section.

Controller software release 5.2 or later enables you to configure the access points to send all CAPWAP-related errors to a syslog server. You do not need to enable any debug commands on the controller because all of the CAPWAP error messages can be viewed from the syslog server itself.

The state of the access point is not maintained on the controller until it receives a CAPWAP join request from the access point. Therefore, it can be difficult to determine why the CAPWAP discovery request from a certain access point was rejected. In order to troubleshoot such joining issues without enabling CAPWAP debug commands on the controller, the controller collects information for all access points that send a discovery message to this controller and maintains information for any access points that have successfully joined this controller.

The controller collects all join-related information for each access point that sends a CAPWAP discovery request to the controller. Collection begins with the first discovery message received from the access point and ends with the last configuration payload sent from the controller to the access point.

You can view join-related information for the following numbers of access points:

• Up to 250 access points for 5500 series controllers
• Up to 300 access points for 4400 series controllers, the Cisco WiSM, and the Catalyst 3750G Integrated Wireless LAN Controller Switch
• Up to three times the maximum number of access points supported by the platform for the 2100 series controllers and the Controller Network Module within the Cisco 28/37/38xx Series Integrated Services Routers

When the controller is maintaining join-related information for the maximum number of access points, it does not collect information for any more access points.

An access point sends all syslog messages to IP address 255.255.255.255 by default when any of the following conditions are met:

• An access point running software release 4.2 or later has been newly deployed.
• An existing access point running a software release prior to 4.2 has been upgraded to 4.2 or a later release.
• An existing access point running software release 4.2 or later has been reset after clearing the configuration.

If any of these conditions are met and the access point has not yet joined a controller, you can also configure a DHCP server to return a syslog server IP address to the access point using option 7 on the server. The access point then starts sending all syslog messages to this IP address.

You can also configure the syslog server IP address through the access point CLI, provided the access point is currently not connected to the controller. The relevant command is lwapp ap log-server syslog_server_IP_address.

When the access point joins a controller for the first time, the controller pushes the global syslog server IP address (the default is 255.255.255.255) to the access point. After that, the access point sends all syslog messages to this IP address, until it is overridden by one of the following scenarios:

• The access point is still connected to the same controller, and the global syslog server IP address configuration on the controller has been changed using the config ap syslog host global syslog_server_IP_address command. In this case, the controller pushes the new global syslog server IP address to the access point.
• The access point is still connected to the same controller, and a specific syslog server IP address has been configured for the access point on the controller using the config ap syslog host specific Cisco_AP syslog_server_IP_address command. In this case, the controller pushes the new specific syslog server IP address to the access point.
• The access point gets disconnected from the controller, and the syslog server IP address has been configured from the access point CLI using the lwapp ap log-server syslog_server_IP_address command. This command works only if the access point is not connected to any controller.
• The access point gets disconnected from the controller and joins another controller. In this case, the new controller pushes its global syslog server IP address to the access point.

Whenever a new syslog server IP address overrides the existing syslog server IP address, the old address is erased from persistent storage, and the new address is stored in its place. The access point also starts sending all syslog messages to the new IP address, provided the access point can reach the syslog server IP address.

You can configure the syslog server for access points using the controller GUI and view the access point join information using the controller GUI or CLI.

Configuring the Syslog Server for Access Points

Follow these steps to configure the syslog server for access points using the controller CLI.

Step 1 Perform one of the following:

• To configure a global syslog server for all access points that join this controller, enter this command:

config ap syslog host global syslog_server_IP_address

Note By default, the global syslog server IP address for all access points is 255.255.255.255. Make sure that the access points can reach the subnet on which the syslog server resides before configuring the syslog server on the controller. If the access points cannot reach this subnet, the access points are unable to send out syslog messages.

• To configure a syslog server for a specific access point, enter this command:

config ap syslog host specific Cisco_AP syslog_server_IP_address

Note By default, the syslog server IP address for each access point is 0.0.0.0, indicating that it is not yet set. When the default value is used, the global access point syslog server IP address is pushed to the access point.

Step 2 To save your changes, enter this command:

save config

Step 3 To see the global syslog server settings for all access points that join the controller, enter this command:

show ap config global

Information similar to the following appears:

Step 4 To see the syslog server settings for a specific access point, enter this command:

show ap config general Cisco_AP

Viewing Access Point Join Information

Join statistics for an access point that sends a CAPWAP discovery request to the controller at least once are maintained on the controller even if the access point is rebooted or disconnected. These statistics are removed only when the controller is rebooted or when you choose to clear the statistics.

Using the GUI to View Access Point Join Information

Using the controller GUI, follow these steps to view access point join information.

Step 1 Choose Monitor > Statistics > AP Join to open the AP Join Stats page (see Figure 14).

Figure 14 AP Join Stats Page

This page lists all of the access points that are joined to the controller or that have tried to join. It shows the radio MAC address, access point name, current join status, Ethernet MAC address, IP address, and last join time for each access point.

The total number of access points appears in the upper right-hand corner of the page. If the list of access points spans multiple pages, you can view these pages by clicking the page number links. Each page shows the join statistics for up to 25 access points.

Note If you ever want to remove an access point from the list, hover your cursor over the blue drop-down arrow for that access point and click Remove.

Note If you ever want to clear the statistics for all access points and start over, click Clear Stats on All APs.

Step 2 If you want to search for specific access points in the list of access points on the AP Join Stats page, follow these steps to create a filter to display only access points that meet certain criteria (such as MAC address or access point name).

Note This feature is especially useful if your list of access points spans multiple pages, preventing you from viewing them all at once.

a. Click Change Filter to open the Search AP window (see Figure 15).

Figure 15 Search AP Window

b. Check one of the following check boxes to specify the criteria used when displaying access points:

• MAC Address —Enter the base radio MAC address of an access point.
• AP Name —Enter the name of an access point.

Note When you enable one of these filters, the other filter is disabled automatically.

c. Click Find to commit your changes. Only the access points that match your search criteria appear on the AP Join Stats page, and the Current Filter parameter at the top of the page specifies the filter used to generate the list (for example, MAC Address:00:1e:f7:75:0a:a0 or AP Name:pmsk-ap).

Note If you want to remove the filter and display the entire access point list, click Clear Filter.

Step 3 To see detailed join statistics for a specific access point, click the radio MAC address of the access point. The AP Join Stats Detail page appears (see Figure 16).

Figure 16 AP Join Stats Detail Page

This page provides information from the controller’s perspective on each phase of the join process and shows any errors that have occurred.

Using the CLI to View Access Point Join Information

Use these CLI commands to view access point join information:

• To see the MAC addresses of all the access points that are joined to the controller or that have tried to join, enter this command:

show ap join stats summary all

Information similar to the following appears:

• To see the last join error detail for a specific access point, enter this command:

show ap join stats summary ap_mac

where ap_mac is the MAC address of the 802.11 radio interface.

Note To obtain the MAC address of the 802.11 radio interface, enter this command on the access point CLI: show interfaces Dot11Radio 0

Information similar to the following appears:

• To see all join-related statistics collected for a specific access point, enter this command:

show ap join stats detailed ap_mac

Information similar to the following appears:

• To clear the join statistics for all access points or for a specific access point, enter this command:

clear ap join stats { all | ap_mac }

Using a Controller to Send Debug Commands to Access Points Converted to Lightweight Mode

Enter this command to enable the controller to send debug commands to an access point converted to lightweight mode:

debug ap {enable | disable | command cmd } Cisco_AP

When this feature is enabled, the controller sends debug commands to the converted access point as character strings. You can send any debug command supported by Cisco Aironet access points that run Cisco IOS software in lightweight mode.

Converted Access Points Send Crash Information to Controller

When a converted access point unexpectedly reboots, the access point stores a crash file on its local flash memory at the time of the crash. After the unit reboots, it sends the reason for the reboot to the controller. If the unit rebooted because of a crash, the controller pulls up the crash file using existing CAPWAP messages and stores it in the controller flash memory. The crash info copy is removed from the access point flash memory when the controller pulls it from the access point.

Converted Access Points Send Radio Core Dumps to Controller

When a radio module in a converted access point generates a core dump, the access point stores the core dump file of the radio on its local flash memory at the time of the radio crash. It sends a notification message to the controller indicating which radio generated a core dump file. The controller sends a trap alerting the network administrator, and the administrator can retrieve the radio core file from the access point.

The retrieved core file is stored in the controller flash and can subsequently be uploaded through TFTP or FTP to an external server for analysis. The core file is removed from the access point flash memory when the controller pulls it from the access point.

Using the CLI to Retrieve Radio Core Dumps

Using the controller CLI, follow these steps to retrieve the radio core dump file.

Step 1 To transfer the radio core dump file from the access point to the controller, enter this command:

config ap crash-file get-radio-core-dump slot Cisco_AP

For the slot parameter, enter the slot ID of the radio that crashed.

Step 2 To verify that the file was downloaded to the controller, enter this command:

show ap crash-file

Information similar to the following appears:

lrad_AP1130.rdump0 ( 156 )

The number in parentheses indicates the size of the file. The size should be greater than zero if a core dump file is available.

Using the GUI to Upload Radio Core Dumps

Using the controller GUI, follow these steps to upload the radio core dump file to a TFTP or FTP server.

Step 1 Choose Commands > Upload File to open the Upload File from Controller page (see Figure 17).

Figure 17 Upload File from Controller Page

Step 2 From the File Type drop-down box, choose Radio Core Dump .

Step 3 From the Transfer Mode drop-down box, choose TFTP or FTP .

Step 4 In the IP Address field, enter the IP address of the TFTP or FTP server.

Step 5 In the File Path field, enter the directory path of the file.

Step 6 In the File Name field, enter the name of the radio core dump file.

Note The filename that you enter should match the filename generated on the controller. You can determine the filename on the controller by entering the show ap crash-file command.

Step 7 If you chose FTP as the Transfer Mode, follow these steps:

a. In the Server Login Username field, enter the FTP server login name.

b. In the Server Login Password field, enter the FTP server login password.

c. In the Server Port Number field, enter the port number of the FTP server. The default value for the server port is 21.

Step 8 Click Upload to upload the radio core dump file from the controller. A message appears indicating the status of the upload.

Using the CLI to Upload Radio Core Dumps

Using the controller CLI, follow these steps to upload the radio core dump file to a TFTP or FTP server.

Step 1 To transfer the file from the controller to a TFTP or FTP server, enter these commands:

• transfer upload mode { tftp | ftp }
• transfer upload datatype radio-core-dump
• transfer upload serverip server_ip_address
• transfer upload path server_path_to_file
• transfer upload filename filename

Note The filename that you enter should match the filename generated on the controller. You can determine the filename on the controller by entering the show ap crash-file command.

Step 2 If you are using an FTP server, also enter these commands:

• transfer upload username username
• transfer upload password password
• transfer upload port port

Note The default value for the port parameter is 21.

Step 3 To view the updated settings, enter this command:

transfer upload start

Step 4 When prompted to confirm the current settings and start the software upload, answer y.

Uploading Memory Core Dumps from Converted Access Points

By default, access points converted to lightweight mode do not send memory core dumps to the controller. This section provides instructions to upload access point core dumps using the controller GUI or CLI.

Using the GUI to Upload Access Point Core Dumps

Using the controller GUI, follow these steps to upload a core dump file of the access point.

Step 1 Choose Wireless > Access Points > All APs > access point name > the Advanced tab to open the All APs > Details for (Advanced) page (see Figure 18).

Figure 18 All APs > Details for (Advanced) Page

Step 2 To upload a core dump of the access point, check the AP Core Dump check box.

Step 3 In the TFTP Server IP field, enter the IP address of the TFTP server.

Step 4 In the File Name field, enter a name of the access point core dump file (such as dump.log ).

Step 5 To compress the access point core dump file, check the File Compression check box. When you enable this option, the file is saved with a .gz extension (such as dump.log.gz ). This file can be opened with WinZip.

Step 6 Click Apply to commit your changes.

Step 7 Click Save Configuration to save your changes.

Using the CLI to Upload Access Point Core Dumps

Using the controller CLI, follow these steps to upload a core dump file of the access point.

Step 1 To upload a core dump of the access point, enter this command on the controller:

config ap core-dump enable tftp_server_ip_address filename {compress | uncompress} {ap_name | all}

where

• tftp_server_ip_address is the IP address of the TFTP server to which the access point sends core dump files,

Note The access point must be able to reach the TFTP server.

• filename is the name that the access points uses to label the core file,
• compress configures the access point to send compressed core files whereas uncompress configures the access point to send uncompressed core files, and

Note When you choose compress, the file is saved with a .gz extension (for example, dump.log.gz). This file can be opened with WinZip.

• ap_name is the name of a specific access point for which core dumps are uploaded whereas all is all access points converted to lightweight mode.

Step 2 To save your changes, enter this command:

save config

Display of MAC Addresses for Converted Access Points

There are some differences in the way that controllers display the MAC addresses of converted access points on information pages in the controller GUI:

• On the AP Summary page, the controller lists the Ethernet MAC addresses of converted access points.
• On the AP Detail page, the controller lists the BSS MAC addresses and Ethernet MAC addresses of converted access points.
• On the Radio Summary page, the controller lists converted access points by radio MAC address.

Disabling the Reset Button on Access Points Converted to Lightweight Mode

You can disable the reset button on access points converted to lightweight mode. The reset button is labeled MODE on the outside of the access point.

Use this command to disable or enable the reset button on one or all converted access points associated to a controller:

config ap reset-button {enable | disable} {ap-name | all}

The reset button on converted access points is enabled by default.

Configuring a Static IP Address on a Lightweight Access Point

If you want to specify an IP address for an access point rather than having one assigned automatically by a DHCP server, you can use the controller GUI or CLI to configure a static IP address for the access point. Static IP addresses are generally used only for deployments with a limited number of users.

Note Refer to the “Configuring DHCP” section for information on assigning IP addresses using DHCP.

An access point cannot discover the controller using domain name system (DNS) resolution if a static IP address is configured for the access point, unless you specify a DNS server and the domain to which the access point belongs. Previously, these parameters could be configured only using the CLI, but controller software release 6.0 expands this functionality to the GUI.

Note If you configure an access point to use a static IP address that is not on the same subnet on which the access point’s previous DHCP address was, the access point falls back to a DHCP address after the access point reboots. If the access point falls back to a DHCP address, the show ap config general Cisco_AP CLI command correctly shows that the access point is using a fallback IP address. However, the GUI shows both the static IP address and the DHCP address, but it does not identify the DHCP address as a fallback address.

Using the GUI to Configure a Static IP Address

Using the controller GUI, follow these steps to configure a static IP address for a lightweight access point.

Step 1 Choose Wireless > Access Points > All APs to open the All APs page.

Step 2 Click the name of the access point for which you want to configure a static IP address. The All APs > Details for (General) page appears (see Figure 19).

Figure 19 All APs > Details for (General) Page

Step 3 Under IP Config, check the Static IP check box if you want to assign a static IP address to this access point. The default value is unchecked.

Step 4 Enter the static IP address, netmask, and default gateway in the corresponding fields.

Step 5 Click Apply to commit your changes. The access point reboots and rejoins the controller, and the static IP address that you specified in Enter the static IP address, netmask, and default gateway in the corresponding fields. is sent to the access point.

Step 6 After the static IP address has been sent to the access point, you can configure the DNS server IP address and domain name. To do so, follow these steps:

a. In the DNS IP Address field, enter the IP address of the DNS server.

b. In the Domain Name field, enter the name of the domain to which the access point belongs.

c. Click Apply to commit your changes.

d. Click Save Configuration to save your changes.

Using the CLI to Configure a Static IP Address

Using the controller CLI, follow these steps to configure a static IP address for a lightweight access point.

Step 1 To configure a static IP address on the access point, enter this command:

config ap static-ip enable Cisco_AP ip_address mask gateway

Note To disable static IP for the access point, enter this command: config ap static-ip disable Cisco_AP.

Step 2 To save your changes, enter this command:

save config

The access point reboots and rejoins the controller, and the static IP address that you specified in To configure a static IP address on the access point, enter this command: is pushed to the access point.

Step 3 After the static IP address has been sent to the access point, you can configure the DNS server IP address and domain name. To do so, follow these steps:

a. To specify a DNS server so that a specific access point or all access points can discover the controller using DNS resolution, enter this command:

config ap static-ip add nameserver {Cisco_AP | all } ip_address

Note To delete a DNS server for a specific access point or all access points, enter this command: config ap static-ip delete nameserver {Cisco_AP | all}.

b. To specify the domain to which a specific access point or all access points belong, enter this command:

config ap static-ip add domain {Cisco_AP | all } domain_name

Note To delete a domain for a specific access point or all access points, enter this command: config ap static-ip delete domain {Cisco_AP | all}.

c. To save your changes, enter this command:

save config

Step 4 To see the IP address configuration for the access point, enter this command:

show ap config general Cisco_AP

Information similar to the following appears:

Supporting Oversized Access Point Images

Controller software release 5.0 or later allows you to upgrade to an oversized access point image by automatically deleting the recovery image to create sufficient space. This feature affects only access points with 8 MB of flash (the 1100, 1200, and 1310 series access points). All newer access points have a larger flash size than 8 MB.

Note As of August 2007, there are no oversized access point images, but as new features are added, the access point image size will continue to grow.

The recovery image provides a backup image that can be used if an access point power-cycles during an image upgrade. The best way to avoid the need for access point recovery is to prevent an access point from power-cycling during a system upgrade. If a power-cycle occurs during an upgrade to an oversized access point image, you can recover the access point using the TFTP recovery procedure.

Follow these steps to perform the TFTP recovery procedure.

Step 1 Download the required recovery image from Cisco.com (c1100-rcvk9w8-mx, c1200-rcvk9w8-mx, or c1310-rcvk9w8-mx) and install it in the root directory of your TFTP server.

Step 2 Connect the TFTP server to the same subnet as the target access point and power-cycle the access point. The access point boots from the TFTP image and then joins the controller to download the oversized access point image and complete the upgrade procedure.

Step 3 After the access point has been recovered, you may remove the TFTP server.

Implementing Security

Follow these steps to ensure that only valid OfficeExtend access points join the company network.

Step 1 To use local significant certificates (LSCs) to authorize your OfficeExtend access points, follow the instructions in the “Authorizing Access Points Using LSCs” section.

Note Configuring LSC is optional.

Step 2 To implement AAA server validation using the access point’s MAC address, name, or both as the username in authorization requests, enter this command:

config auth-list ap-policy authorize-ap username { ap_mac | Cisco_AP | both }

Using the access point name for validation can ensure that only the OfficeExtend access points of valid employees can join the controller. To implement this security policy, make sure to name each OfficeExtend access point with an employee ID or employee number. When an employee is terminated, you can then run a script to remove this user from the AAA server database, thereby preventing that employee’s OfficeExtend access point from joining the network.

Step 3 To save your changes, enter this command:

save config

Licensing for an OfficeExtend Access Point

In order to use OfficeExtend access points, a wplus license must be installed and in use on the 5500 series controller. After the license is installed, you can enable the OfficeExtend mode on an 1130 series or 1140 series access point.

If an OfficeExtend access point attempts to join a controller that is using only a base license (and not the wplus license), the following message appears in the controller trap log: “License Not Available for feature: OfficeExtendAP.” To view the controller trap log, choose Monitor and click View All under “Most Recent Traps” on the controller GUI.

Note Refer to the Configuring Controller Settings chapter for information on obtaining and installing licenses.

Configuring OfficeExtend Access Points

After the 1130 series or 1140 series access point has joined the controller, you can configure it as an OfficeExtend access point using the controller GUI or CLI.

Using the GUI to Configure OfficeExtend Access Points

Using the controller GUI, follow these steps to configure an OfficeExtend access point.

Step 1 Follow these steps to enable hybrid REAP on the access point:

a. Choose Wireless to open the All APs page.

b. Click the name of the desired access point. The All APs > Details for (General) page appears.

c. Choose H-REAP from the AP Mode drop-down box to enable hybrid REAP for this access point.

Step 2 Follow these steps to configure one or more controllers for the access point:

a. Choose the High Availability tab to open the All APs > Details for (High Availability) page.

b. Enter the name and IP address of the primary controller for this access point in the Primary Controller Name and Management IP Address fields.

Note You must enter both the name and IP address of the controller. Otherwise, the access point cannot join this controller.

c. If desired, enter the name and IP address of a secondary or tertiary controller (or both) in the corresponding Controller Name and Management IP Address fields.

d. Click Apply to commit your changes. The access point reboots and then rejoins the controller.

Note OfficeExtend access points do not use the generic broadcast or over-the air (OTAP) discovery process to locate a controller. You must configure one or more controllers because OfficeExtend access points try to connect only to their configured controllers.

Note The names and IP addresses must be unique for the primary, secondary, and tertiary controllers.

Note Make sure that you configure only 5500 series controllers with a wplus license. If you configure a non-5500 series controller or a 5500 series controller without a wplus license, the OfficeExtend access point cannot join the controller.

Step 3 Follow these steps to enable OfficeExtend access point settings:

a. Re-click the access point name on the All APs page.

b. Choose the H-REAP tab to open the All APs > Details for (H-REAP) page (see Figure 21).

Figure 21 All APs > Details for (H-REAP) Page

c. Check the Enable OfficeExtend AP check box to enable the OfficeExtend mode for this access point. The default value is checked.

Unchecking this check box simply disables OfficeExtend mode for this access point. It does not undo all of the configuration settings on the access point. If you want to clear the access point’s configuration and return it to factory default settings, enter clear ap config Cisco_AP on the controller CLI . If you want to clear only the access point’s personal SSID, click Reset Personal SSID .

Note Rogue detection is disabled automatically when you enable the OfficeExtend mode for an access point. However, you can enable or disable rogue detection for a specific access point by checking the Rogue Detection check box on the All APs > Details for (Advanced) page. Rogue detection is disabled by default for OfficeExtend access points because these access points, which are deployed in a home environment, are likely to detect a large number of rogue devices. Refer to the “Managing Rogue Devices” section for more information on rogue detection.

Note DTLS data encryption is enabled automatically when you enable the OfficeExtend mode for an access point. However, you can enable or disable DTLS data encryption for a specific access point by checking the Data Encryption check box on the All APs > Details for (Advanced) page. Refer to the “Configuring Data Encryption” section for more information on DTLS data encryption.

Note Telnet and SSH access are disabled automatically when you enable the OfficeExtend mode for an access point. However, you can enable or disable Telnet or SSH access for a specific access point by checking the Telnet or SSH check box on the All APs > Details for (Advanced) page. Refer to the “Troubleshooting Access Points Using Telnet or SSH” section for more information on Telnet and SSH.

Note Link latency is enabled automatically when you enable the OfficeExtend mode for an access point. However, you can enable or disable link latency for a specific access point by checking the Enable Link Latency check box on the All APs > Details for (Advanced) page. Refer to the “Configuring Link Latency” section for more information on this feature.

d. Check the Enable Least Latency Controller Join check box if you want the access point to choose the controller with the least latency when joining. Otherwise, leave this check box unchecked, which is the default value. When you enable this feature, the access point calculates the time between discovery request and discovery response and joins the 5500 series controller that responds first.

e. Click Apply to commit your changes.

The OfficeExtend AP field on the All APs page shows which access points are configured as OfficeExtend access points.

Step 4 Follow these steps if you want to configure a specific username and password for the OfficeExtend access point. The teleworker can use these credentials to log into the GUI of the OfficeExtend access point.

a. Re-click the access point name on the All APs page.

b. Choose the Credentials tab to open the All APs > Details for (Credentials) page.

c. Check the Over-ride Global Credentials check box to prevent this access point from inheriting the global username, password, and enable password from the controller. The default value is unchecked.

d. In the Username, Password, and Enable Password fields, enter the unique username, password, and enable password that you want to assign to this access point.

Note The information that you enter is retained across controller and access point reboots and if the access point joins a new controller.

e. Click Apply to commit your changes.

f. Click Save Configuration to save your changes.

Note If you ever want to force this access point to use the controller’s global credentials, simply uncheck the Over-ride Global Credentials check box.

Step 5 If your controller supports only OfficeExtend access points, refer to the “Configuring RRM” section for instructions on setting the recommended values for DCA interval, channel scan duration, and neighbor packet frequency.

Using the CLI to Configure OfficeExtend Access Points

Using the controller CLI, follow these steps to configure an OfficeExtend access point.

Step 1 To enable hybrid-REAP on the access point, enter this command:

config ap mode h-reap Cisco_AP

Step 2 To configure one or more controllers for the access point, enter one or all of these commands:

config ap primary-base controller_name Cisco_AP controller_ip_address

config ap secondary-base controller_name Cisco_AP controller_ip_address

config ap tertiary-base controller_name Cisco_AP controller_ip_address

Note You must enter both the name and IP address of the controller. Otherwise, the access point cannot join this controller.

Note OfficeExtend access points do not use the generic broadcast or over-the air (OTAP) discovery process to find a controller. You must configure one or more controllers because OfficeExtend access points try to connect only to their configured controllers.

Note The names and IP addresses must be unique for the primary, secondary, and tertiary controllers.

Note Make sure that you configure only 5500 series controllers with a wplus license. If you configure a non-5500 series controller or a 5500 series controller without a wplus license, the OfficeExtend access point cannot join the controller.

Step 3 To enable the OfficeExtend mode for this access point, enter this command:

config hreap office-extend { enable | disable } Cisco_AP

The default value is enabled. The disable parameter simply disables OfficeExtend mode for this access point. It does not undo all of the configuration settings on the access point. If you want to clear the access point’s configuration and return it to factory default settings, enter this command:

clear ap config Cisco_AP

If you want to clear only the access point’s personal SSID, enter this command:

config hreap office-extend clear-personalssid-config Cisco_AP.

Note Rogue detection is disabled automatically when you enable the OfficeExtend mode for an access point. However, you can enable or disable rogue detection for a specific access point or for all access points using this command: config rogue detection {enable | disable} {Cisco_AP | all}. Rogue detection is disabled by default for OfficeExtend access points because these access points, which are deployed in a home environment, are likely to detect a large number of rogue devices. Refer to the “Managing Rogue Devices” section for more information on rogue detection.

Note DTLS data encryption is enabled automatically when you enable the OfficeExtend mode for an access point. However, you can enable or disable DTLS data encryption for a specific access point or for all access points using this command: config ap link-encryption {enable | disable} {Cisco_AP | all}. Refer to the “Configuring Data Encryption” section for more information on DTLS data encryption.

Note Telnet and SSH access are disabled automatically when you enable the OfficeExtend mode for an access point. However, you can enable or disable Telnet or SSH access for a specific access point using this command: config ap {telnet | ssh} {enable | disable} Cisco_AP. Refer to the “Troubleshooting Access Points Using Telnet or SSH” section for more information on Telnet and SSH.

Note Link latency is enabled automatically when you enable the OfficeExtend mode for an access point. However, you can enable or disable link latency for a specific access point or for all access points currently associated to the controller using this command: config ap link-latency {enable | disable} {Cisco_AP | all}. Refer to the “Configuring Link Latency” section for more information on this feature.

Step 4 To enable the access point to choose the controller with the least latency when joining, enter this command:

config hreap join min-latency { enable | disable } Cisco_AP

The default value is disabled. When you enable this feature, the access point calculates the time between discovery request and discovery response and joins the 5500 series controller that responds first.

Step 5 To configure a specific username and password that teleworkers can enter to log into the GUI of the OfficeExtend access point, enter this command:

config ap mgmtuser add username user password password enablesecret enable_password Cisco_AP

The credentials that you enter in this command are retained across controller and access point reboots and if the access point joins a new controller.

Note If you ever want to force this access point to use the controller’s global credentials, enter this command: config ap mgmtuser delete Cisco_AP. The following message appears after you execute this command: “AP reverted to global username configuration.”

Step 6 To save your changes, enter this command:

save config

Step 7 If your controller supports only OfficeExtend access points, refer to the “Configuring RRM” section for instructions on setting the recommended value for the DCA interval.

Configuring a Personal SSID on an OfficeExtend Access Point

Instruct teleworkers to follow these steps to log into the GUI of their OfficeExtend access point and configure a personal SSID.

Step 1 Find the IP address of your OfficeExtend access point by doing one of the following:

• Log into your home router and look for the IP address of your OfficeExtend access point.
• Ask your company’s IT professional for the IP address of your OfficeExtend access point.
• Use an application such as Network Magic (a Linksys product) to detect devices on your network and their IP addresses.

Step 2 With the OfficeExtend access point connected to your home router, enter the IP address of the OfficeExtend access point in the Address field of your Internet browser and click Go .

Note Make sure you are not connected to your company’s network using a virtual private network (VPN) connection.

Step 3 When prompted, enter the username and password to log into the access point.

Step 4 On the OfficeExtend Access Point Welcome page, click Enter . The OfficeExtend Access Point Home page appears (see Figure 22).

Figure 22 OfficeExtend Access Point Home Page

This page shows the access point name, IP address, MAC address, software version, status, channel, transmit power, and client traffic.

Step 5 Choose Configuration to open the Configuration page (see Figure 23).

Figure 23 OfficeExtend Access Point Configuration Page

Step 6 Check the Personal SSID check box to enable this wireless connection. The default value is disabled.

Step 7 In the SSID field, enter the personal SSID that you want to assign to this access point. This SSID will be locally switched.

Note A controller with an OfficeExtend access point publishes only up to 15 WLANs to each connected access point because it reserves one WLAN for the personal SSID.

Step 8 From the Security drop-down box, choose Open , WPA2/PSK (AES) , or 104 bit WEP to set the security type to be used by this access point.

Note If you choose WPA2/PSK (AES), make sure that the client is configured for WPA2/PSK and AES encryption.

Step 9 If you chose WPA2/PSK (AES) in From the Security drop-down box, choose Open, WPA2/PSK (AES), or 104 bit WEP to set the security type to be used by this access point. , enter an 8- to 38-character WPA2 passphrase in the Secret field. If you chose 104 bit WEP, enter a 13-character ASCII key in the Key field.

Step 10 Click Apply to commit your changes.

Note If you ever want to use the OfficeExtend access point for another application, you can clear this configuration and return the access point to factory default settings by clicking Clear Config. You can also clear the access point’s configuration from the controller CLI by entering this command: clear ap config Cisco_AP.

Viewing OfficeExtend Access Point Statistics

Use these controller CLI commands to view information about the OfficeExtend access points on your network.

• To see a list of all OfficeExtend access points, enter this command:

show hreap office-extend summary

Information similar to the following appears:

• To see the link delay for OfficeExtend access points, enter this command:

show hreap office-extend latency

Information similar to the following appears:

• To see the encryption state of all access points or a specific access point, enter this command:

show ap link-encryption { all | Cisco_AP}

Information similar to the following appears:

This command also shows authentication errors, which track the number of integrity check failures, and replay errors, which track the number of times that the access point receives the same packet.

• To see the data plane status for all access points or a specific access point, enter this command:

show ap data-plane { all | Cisco_AP}

Information similar to the following appears:

• To see the join statistics for the OfficeExtend access points, refer to the “Using the CLI to View Access Point Join Information” section.

Guidelines for Using WGBs

Follow these guidelines for using WGBs on your network:

• The WGB can be any autonomous access point that supports the workgroup bridge mode and is running Cisco IOS Release 12.4(3g)JA or later (on 32-MB access points) or Cisco IOS Release 12.3(8)JEB or later (on 16-MB access points). These access points include the AP1120, AP1121, AP1130, AP1140, AP1231, AP1240, AP1250, and AP1310. Cisco IOS Releases prior to 12.4(3g)JA and 12.3(8)JEB are not supported.

Note If your access point has two radios, you can configure only one for workgroup bridge mode. This radio is used to connect to the lightweight access point. Cisco recommends that you disable the second radio.

Note The controller supports only Cisco WGB products. Linksys and OEM WGB devices are not supported. Although the Cisco Wireless Unified Solution does not support the Linksys WET54G and WET11B Ethernet Bridges, you can use these devices in a Wireless Unified Solution configuration if you follow these guidelines:
1. Connect only one device to the WET54G or WET11B.
2. Enable the MAC cloning feature on the WET54G or WET11B to clone the connected device.
3. Install the latest drivers and firmware on devices connected to the WET54G or WET11B. This guideline is especially important for JetDirect printers because early firmware versions might cause problems with DHCP.
Note: Because these devices are not supported in the Cisco Wireless Unified Solution, Cisco Technical Support cannot help you troubleshoot any problems associated with them.

Perform one of the following to enable the workgroup bridge mode on the WGB:

– On the WGB access point GUI, choose Workgroup Bridge for the role in radio network on the Settings > Network Interfaces page.

– On the WGB access point CLI, enter this command: station-role workgroup-bridge

Note See the sample WGB access point configuration in the “Sample WGB Configuration” section.

• The WGB can associate only to lightweight access points.
• Only WGBs in client mode (which is the default value) are supported. Those in infrastructure mode are not supported. Perform one of the following to enable client mode on the WGB:

– On the WGB access point GUI, choose Disabled for the Reliable Multicast to WGB parameter.

– On the WGB access point CLI, enter this command: no infrastructure client .

Note VLANs are not supported for use with WGBs.

Note See the sample WGB access point configuration in the “Sample WGB Configuration” section.

• These features are supported for use with a WGB:

– Guest N+1 redundancy

– Local EAP

– Open, WEP 40, WEP 128, CKIP, WPA+TKIP, WPA2+AES, LEAP, EAP-FAST, and EAP-TLS authentication modes

• These features are not supported for use with a WGB:

– Cisco Centralized Key Management (CCKM)

– Hybrid REAP

– Idle timeout

– Web authentication

Note If a WGB associates to a web-authentication WLAN, the WGB is added to the exclusion list, and all of the WGB wired clients are deleted.

• The WGB supports a maximum of 20 wired clients. If you have more than 20 wired clients, use a bridge or another device.
• Wired clients connected to the WGB are not authenticated for security. Instead, the WGB is authenticated against the access point to which it associates. Therefore, Cisco recommends that you physically secure the wired side of the WGB.
• With Layer 3 roaming, if you plug a wired client into the WGB network after the WGB has roamed to another controller (for example, to a foreign controller), the wired client’s IP address displays only on the anchor controller, not on the foreign controller.
• If a wired client does not send traffic for an extended period of time, the WGB removes the client from its bridge table, even if traffic is continuously being sent to the wired client. As a result, the traffic flow to the wired client fails. To avoid the traffic loss, prevent the wired client from being removed from the bridge table by configuring the aging-out timer on the WGB to a large value using the following IOS commands on the WGB:

where bridge-group-number is a value between 1 and 255, and seconds is a value between 10 and 1,000,000 seconds. Cisco recommends configuring the seconds parameter to a value greater than the wired client’s idle period.

• When you delete a WGB record from the controller, all of the WGB wired clients’ records are also deleted.
• Wired clients connected to a WGB inherit the WGB’s QoS and AAA override attributes.
• These features are not supported for wired clients connected to a WGB:

– MAC filtering

– Link tests

– Idle timeout

• To enable the WGB to communicate with the lightweight access point, create a WLAN and make sure that Aironet IE is enabled.

Sample WGB Configuration

Here is a sample configuration of a WGB access point using static WEP with a 40-bit WEP key:

To verify that the WGB is associated to an access point, enter this command on the WGB:

show dot11 association

Information similar to the following appears:

Using the GUI to View the Status of Workgroup Bridges

Follow these steps to view the status of WGBs on your network using the controller GUI.

Step 1 Choose Monitor > Clients to open the Clients page (see Figure 25).

Figure 25 Clients Page

The WGB field on the right side of the page indicates whether any of the clients on your network are workgroup bridges.

Step 2 Click the MAC address of the desired client. The Clients > Detail page appears (see Figure 26).

Figure 26 Clients > Detail Page

The Client Type field under Client Properties shows “WGB” if this client is a workgroup bridge, and the Number of Wired Client(s) field shows the number of wired clients that are connected to this WGB.

Step 3 To see the details of any wired clients that are connected to a particular WGB, follow these steps:

a. Click Back on the Clients > Detail page to return to the Clients page.

b. Hover your cursor over the blue drop-down arrow for the desired WGB and choose Show Wired Clients . The WGB Wired Clients page appears (see Figure 27).

Figure 27 WGB Wired Clients Page

Note If you ever want to disable or remove a particular client, hover your cursor over the blue drop-down arrow for the desired client and choose Remove or Disable, respectively.

c. Click the MAC address of the desired client to see more details for this particular client. The Clients > Detail page appears (see Figure 28).

Figure 28 Clients > Detail Page

The Client Type field under Client Properties shows “WGB Client,” and the rest of the fields on this page provide additional information for this client.

Using the CLI to View the Status of Workgroup Bridges

Follow these steps to view the status of WGBs on your network using the controller CLI.

Step 1 To see any WGBs on your network, enter this command:

show wgb summary

Information similar to the following appears:

Step 2 To see the details of any wired clients that are connected to a particular WGB, enter this command:

show wgb detail wgb _ mac_address

Information similar to the following appears:

Using the CLI to Debug WGB Issues

Use the commands in this section if you experience any problems with the WGB.

1. To enable debugging for IAPP messages, errors, and packets, enter these commands:

• debug iapp all enable —Enables debugging for IAPP messages.
• debug iapp error enable —Enables debugging for IAPP error events.
• debug iapp packet enable —Enables debugging for IAPP packets.

2. If you experience a roaming issue, enter this command:

debug mobility handoff enable

3. If you experience an IP assignment issue and DHCP is used, enter these commands:

• debug dhcp message enable
• debug dhcp packet enable

4. If you experience an IP assignment issue and static IP is used, enter these commands:

• debug dot11 mobile enable
• debug dot11 state enable

Using the GUI to Configure Backup Controllers

Using the controller GUI, follow these steps to configure primary, secondary, and tertiary controllers for a specific access point and to configure primary and secondary backup controllers for all access points.

Step 1 Choose Wireless > Access Points > Global Configuration to open the Global Configuration page (see Figure 29).

Figure 29 Global Configuration Page

Step 2 From the Local Mode AP Fast Heartbeat Timer State drop-down box, choose Enable to enable the fast heartbeat timer for access points in local mode or Disable to disable this timer. The default value is Disable.

Step 3 If you chose Enable in From the Local Mode AP Fast Heartbeat Timer State drop-down box, choose Enable to enable the fast heartbeat timer for access points in local mode or Disable to disable this timer. The default value is Disable. , enter a number between 10 and 15 seconds (inclusive) in the Local Mode AP Fast Heartbeat Timeout field to configure the fast heartbeat timer for access points in local mode. Specifying a small heartbeat interval reduces the amount of time it takes to detect a controller failure. The default value is 0 seconds, which disables the timer.

Step 4 From the H-REAP Mode AP Fast Heartbeat Timer State drop-down box, choose Enable to enable the fast heartbeat timer for hybrid-REAP access points or Disable to disable this timer. The default value is Disable.

Step 5 If you chose Enable in From the H-REAP Mode AP Fast Heartbeat Timer State drop-down box, choose Enable to enable the fast heartbeat timer for hybrid-REAP access points or Disable to disable this timer. The default value is Disable. , enter a value between 10 and 15 seconds (inclusive) in the H-REAP Mode AP Fast Heartbeat Timeout field to configure the fast heartbeat timer for hybrid-REAP access points. Specifying a small heartbeat interval reduces the amount of time it takes to detect a controller failure. The default value is 0 seconds, which disables the timer.

Step 6 In the AP Primary Discovery Timeout field, a value between 30 and 3600 seconds (inclusive) to configure the access point primary discovery request timer. The default value is 120 seconds.

Step 7 If you want to specify a primary backup controller for all access points, enter the IP address of the primary backup controller in the Back-up Primary Controller IP Address field and the name of the controller in the Back-up Primary Controller Name field.

Note The default value for the IP address is 0.0.0.0, which disables the primary backup controller.

Step 8 If you want to specify a secondary backup controller for all access points, enter the IP address of the secondary backup controller in the Back-up Secondary Controller IP Address field and the name of the controller in the Back-up Secondary Controller Name field.

Note The default value for the IP address is 0.0.0.0, which disables the secondary backup controller.

Step 9 Click Apply to commit your changes.

Step 10 If you want to configure primary, secondary, and tertiary backup controllers for a specific access point, follow these steps:

a. Choose Access Points > All APs to open the All APs page.

b. Click the name of the access point for which you want to configure primary, secondary, and tertiary backup controllers.

c. Choose the High Availability tab to open the All APs > Details for (High Availability) page (see Figure 30).

Figure 30 All APs > Details for (High Availability) Page

d. If desired, enter the name and IP address of the primary backup controller for this access point in the Primary Controller fields.

Note Entering an IP address for the backup controller is optional in this step and the next two steps. If the backup controller is outside the mobility group to which the access point is connected (the primary controller), then you need to provide the IP address of the primary, secondary, or tertiary controller, respectively. The controller name and IP address must belong to the same primary, secondary, or tertiary controller. Otherwise, the access point cannot join the backup controller.

e. If desired, enter the name and IP address of the secondary backup controller for this access point in the Secondary Controller fields.

f. If desired, enter the name and IP address of the tertiary backup controller for this access point in the Tertiary Controller fields.

g. Click Apply to commit your changes.

Step 11 Click Save Configuration to save your changes.

Using the CLI to Configure Backup Controllers

Using the controller CLI, follow these steps to configure primary, secondary, and tertiary controllers for a specific access point and to configure primary and secondary backup controllers for all access points.

Step 1 To configure a primary controller for a specific access point, enter this command:

config ap primary-base controller_name Cisco_AP [ controller_ip_address ]

Note The controller_ip_address parameter in this command and the next two commands is optional. If the backup controller is outside the mobility group to which the access point is connected (the primary controller), then you need to provide the IP address of the primary, secondary, or tertiary controller, respectively. In each command, the controller_name and controller_ip_address must belong to the same primary, secondary, or tertiary controller. Otherwise, the access point cannot join the backup controller.

Step 2 To configure a secondary controller for a specific access point, enter this command:

config ap secondary-base controller_name Cisco_AP [ controller_ip_address ]

Step 3 To configure a tertiary controller for a specific access point, enter this command:

config ap tertiary-base controller_name Cisco_AP [ controller_ip_address ]

Step 4 To configure a primary backup controller for all access points, enter this command:

config advanced backup-controller primary backup_controller_name backup_controller_ip_address

Step 5 To configure a secondary backup controller for all access points, enter this command:

config advanced backup-controller secondary backup_controller_name backup_controller_ip_address

Note To delete a primary or secondary backup controller entry, enter 0.0.0.0 for the controller IP address.

Step 6 To enable or disable the fast heartbeat timer for local or hybrid-REAP access points, enter this command:

config advanced timers ap-fast-heartbeat { local | hreap | all } { enable | disable} interval

where all is both local and hybrid-REAP access points, and interval is a value between 1 and 10 seconds (inclusive). Specifying a small heartbeat interval reduces the amount of time it takes to detect a controller failure. The default value is disabled.

Step 7 To configure the access point heartbeat timer, enter this command:

config advanced timers ap-heartbeat-timeout interval

where interval is a value between 1 and 30 seconds (inclusive). This value should be at least three times larger than the fast heartbeat timer. The default value is 30 seconds.

Step 8 To configure the access point primary discovery request timer, enter this command:

config advanced timers ap-primary-discovery-timeout interval

where interval is a value between 30 and 3600 seconds. The default value is 120 seconds.

Step 9 To configure the access point discovery timer, enter this command:

config advanced timers ap-discovery-timeout interval

where interval is a value between 1 and 10 seconds (inclusive). The default value is 10 seconds.

Step 10 To configure the 802.11 authentication response timer, enter this command:

config advanced timers auth-timeout interval

where interval is a value between 10 and 600 seconds (inclusive). The default value is 10 seconds.

Step 11 To save your changes, enter this command:

save config

Step 12 To view an access point’s configuration, enter these commands:

• show ap config general Cisco_AP
• show advanced backup-controller
• show advanced timers

Information similar to the following appears for the show ap config general Cisco_AP command :

Information similar to the following appears for the show advanced backup-controller command :

Information similar to the following appears for the show advanced timers command :

Using the GUI to Configure Failover Priority for Access Points

Using the controller GUI, follow these steps to configure failover priority for access points that join the controller.

Step 1 Choose Wireless > Access Points > Global Configuration to open the Global Configuration page (see Figure 31).

Figure 31 Global Configuration Page

Step 2 From the Global AP Failover Priority drop-down box, choose Enable to enable access point failover priority or Disable to disable this feature and turn off any access point priority assignments. The default value is Disable.

Step 3 Click Apply to commit your changes.

Step 4 Click Save Configuration to save your changes.

Step 5 Choose Wireless > Access Points > All APs to open the All APs page.

Step 6 Click the name of the access point for which you want to configure failover priority.

Step 7 Choose the High Availability tab. The All APs > Details for (High Availability) page appears (see Figure 32).

Figure 32 All APs > Details for (High Availability) Page

Step 8 From the AP Failover Priority drop-down box, choose one of the following options to specify the priority of the access point:

• Low —Assigns the access point to the level 1 priority, which is the lowest priority level. This is the default value.
• Medium —Assigns the access point to the level 2 priority.
• High —Assigns the access point to the level 3 priority.
• Critical —Assigns the access point to the level 4 priority, which is the highest priority level.

Step 9 Click Apply to commit your changes.

Step 10 Click Save Configuration to save your changes.

Using the CLI to Configure Failover Priority for Access Points

Using the controller CLI, follow these steps to configure failover priority for access points that join the controller.

Step 1 To enable or disable access point failover priority, enter this command:

config network ap-priority {enable | disable }

Step 2 To specify the priority of an access point, enter this command:

config ap priority {1 | 2 | 3 | 4 } Cisco_AP

where 1 is the lowest priority level and 4 is the highest priority level. The default value is 1.

Step 3 To save your changes, enter this command:

save config

Using the CLI to View Failover Priority Settings

Use these commands to view the failover priority configuration settings on your network:

• To confirm whether access point failover priority is enabled on your network, enter this command:

show network summary

Information similar to the following appears:

• To see the failover priority for each access point, enter this command:

show ap summary

Information similar to the following appears:

Guidelines for Configuring Multiple Country Codes

Follow these guidelines when configuring multiple country codes:

• When the multiple-country feature is being used, all controllers intended to join the same RF group must be configured with the same set of countries, configured in the same order.
• When multiple countries are configured and the radio resource management (RRM) auto-RF feature is enabled, the auto-RF feature is limited to only the channels that are legal in all configured countries and to the lowest power level common to all configured countries. The access points are always able to use all legal frequencies, but non-common channels can only be assigned manually.

Note If an access point was already set to a higher legal power level or is configured manually, the power level is limited only by the particular country to which that access point is assigned.

You can configure country codes through the controller GUI or CLI.

Using the GUI to Configure Country Codes

Follow these steps to configure country codes using the GUI.

Step 1 Follow these steps to disable the 802.11a and 802.11b/g networks:

a. Choose Wireless > 802.11a/n > Network.

b. Uncheck the 802.11a Network Status check box.

c. Click Apply to commit your changes.

d. Choose Wireless > 802.11b/g/n > Network.

e. Uncheck the 802.11b/g Network Status check box.

f. Click Apply to commit your changes.

Step 2 Choose Wireless > Country to open the Country page (see Figure 33).

Figure 33 Country Page

Step 3 Check the check box for each country where your access points are installed.

Step 4 If you checked more than one check box in Check the check box for each country where your access points are installed., a message appears indicating that RRM channels and power levels are limited to common channels and power levels. Click OK to continue or Cancel to cancel the operation.

Step 5 Click Apply to commit your changes.

Step 6 If you selected multiple country codes in Check the check box for each country where your access points are installed., each access point is assigned to a country. Follow these steps to see the default country chosen for each access point and to choose a different country if necessary.

Note If you ever remove a country code from the configuration, any access points currently assigned to the deleted country reboot and when they rejoin the controller, they get re-assigned to one of the remaining countries if possible.

a. Perform one of the following:

– Leave the 802.11a and 802.11b/g networks disabled.

– Re-enable the 802.11a and 802.11b/g networks and then disable only the access points for which you are configuring a country code. To disable an access point, choose Wireless > Access Points > All APs, click the link of the desired access point, choose Disable from the Status drop-down box, and click Apply.

b. Choose Wireless > Access Points > All APs to open the All APs page.

c. Click the link for the desired access point.

d. Choose the Advanced tab to open the All APs > Details for (Advanced) page (see Figure 34).

Figure 34 All APs > Details for (Advanced) Page

e. The default country for this access point appears in the Country Code drop-down box. If the access point is installed in a country other than the one shown, choose the correct country from the drop-down box. The box contains only those country codes that are compatible with the regulatory domain of at least one of the access point’s radios.

f. Click Apply to commit your changes.

g. Repeat these steps to assign all access points joined to the controller to a specific country.

h. Re-enable any access points that you disabled in Perform one of the following:.

Step 7 Re-enable the 802.11a and 802.11b/g networks, provided you did not re-enable them in If you selected multiple country codes in Step 3, each access point is assigned to a country. Follow these steps to see the default country chosen for each access point and to choose a different country if necessary..

Step 8 Click Save Configuration to save your settings.

Using the CLI to Configure Country Codes

Follow these steps to configure country codes using the CLI.

Step 1 To see a list of all available country codes, enter this command:

show country supported

Step 2 Enter these commands to disable the 802.11a and 802.11b/g networks:

config 802.11a disable network

config 802.11b disable network

Step 3 To configure the country codes for the countries where your access points are installed, enter this command:

config country code1[,code2,code3,...]

If you are entering more than one country code, separate each by a comma (for example, config country US,CA,MX). Information similar to the following appears:

Step 4 Enter Y when prompted to confirm your decision. Information similar to the following appears:

Step 5 To verify your country code configuration, enter this command:

show country

Step 6 To see the list of available channels for the country codes configured on your controller, enter this command:

show country channels

Information similar to the following appears:

Step 7 To save your settings, enter this command:

save config

Step 8 To see the countries to which your access points have been assigned, enter this command:

show ap summary

Information similar to the following appears:

Step 9 If you entered multiple country codes in To configure the country codes for the countries where your access points are installed, enter this command:, follow these steps to assign each access point to a specific country:

a. Perform one of the following:

– Leave the 802.11a and 802.11b/g networks disabled.

– Re-enable the 802.11a and 802.11b/g networks and then disable only the access points for which you are configuring a country code. To re-enable the networks, enter these commands:

config 802.11a enable network

config 802.11b enable network

To disable an access point, enter this command:

config ap disable ap_name

b. To assign an access point to a specific country, enter this command:

config ap country code {ap_name | all}

Make sure that the country code you choose is compatible with the regulatory domain of at least one of the access point’s radios.

Note If you enabled the networks and disabled some access points and then run the config ap country code all command, the specified country code is configured on only the disabled access points. All other access points are ignored.

For example, if you enter config ap country mx all, information similar to the following appears:

c. To re-enable any access points that you disabled in Perform one of the following:, enter this command:

config ap enable ap_name

Step 10 If you did not re-enable the 802.11a and 802.11b/g networks in If you entered multiple country codes in Step 3, follow these steps to assign each access point to a specific country:, enter these commands to re-enable them now:

config 802.11a enable network

config 802.11b enable network

Step 11 To save your settings, enter this command:

save config

Guidelines for Migration

Follow these guidelines before migrating your access points to the -U regulatory domain:

• You can migrate only Cisco Aironet 1130, 1200, and 1240 lightweight access points that support the -J regulatory domain and Airespace AS1200 access points. Other access points cannot be migrated.
• Your controller and all access points must be running software release 4.1 or greater or software release 3.2.193.0.

Note Software release 4.0 is not supported. If you migrate your access points using software release 3.2.193.0, you cannot upgrade to software release 4.0. You can upgrade only to software release 4.1 or later or to a later release of the 3.2 software.

• You must have had one or more Japan country codes (JP, J2, or J3) configured on your controller at the time you last booted your controller.
• You must have at least one access point with a -J regulatory domain joined to your controller.
• You cannot migrate your access points from the -U regulatory domain back to the -J domain. The Japanese government has made reverse migration illegal.

Note You cannot undo an access point migration. Once an access point has been migrated, you cannot return to software release 4.0. Migrated access points will have non-functioning 802.11a radios under software release 4.0.

Migrating Access Points to the -U Regulatory Domain

Follow these steps to migrate your access points from the -J regulatory domain to the -U regulatory domain using the controller CLI. This process cannot be performed using the controller GUI.

Step 1 To determine which access points in your network are eligible for migration, enter this command:

show ap migrate

Information similar to the following appears:

Step 2 Enter these commands to disable the 802.11a and 802.11b/g networks:

config 802.11a disable network

config 802.11b disable network

Step 3 Enter this command to change the country code of the access points to be migrated to J3:

config country J3

Step 4 Wait for any access points that may have rebooted to rejoin the controller.

Step 5 Enter this command to migrate the access points from the -J regulatory domain to the -U regulatory domain:

config ap migrate j52w52 {all | ap_name}

Information similar to the following appears:

Step 6 Enter Y when prompted to confirm your decision to migrate.

Step 7 Wait for all access points to reboot and rejoin the controller. This process may take up to 15 minutes, depending on access point. The AP1130, AP1200, and AP1240 reboot twice; all other access points reboot once.

Step 8 Enter this command to verify migration for all access points:

show ap migrate

Information similar to the following appears:

Step 9 Enter these commands to re-enable the 802.11a and 802.11b/g networks:

config 802.11a enable network

config 802.11b enable network

Step 10 Send an email with your company name and the list of access points that have been migrated to this email address: migrateapj52w52@cisco.com. Cisco recommends that you cut and paste the output from the show ap migrate command in Enter this command to verify migration for all access points: into the email.

Using the GUI to Optimize RFID Tracking on Access Points

Using the controller GUI, follow these steps to optimize RFID tracking.

Step 1 Choose Wireless > Access Points > All APs to open the All APs page.

Step 2 Click the name of the access point for which you want to configure monitor mode. The All APs > Details for page appears.

Step 3 From the AP Mode drop-down box, choose Monitor .

Step 4 Click Apply to commit your changes.

Step 5 Click OK when warned that the access point will be rebooted.

Step 6 Click Save Configuration to save your changes.

Step 7 Choose Wireless > Access Points > Radios > 802.11b/g/n to open the 802.11b/g/n Radios page.

Step 8 Hover your cursor over the blue drop-down arrow for the desired access point and choose Configure . The 802.11b/g/n Cisco APs > Configure page appears (see Figure 35).

Figure 35 802.11b/g/n Cisco APs > Configure Page

Step 9 To disable the access point radio, choose Disable from the Admin Status drop-down box and click Apply .

Step 10 To enable tracking optimization on the radio, choose Enable from the Enable Tracking Optimization drop-down box.

Step 11 From the four Channel drop-down boxes, choose the channels on which you want to monitor RFID tags.

Note You must configure at least one channel on which the tags will be monitored.

Step 12 Click Apply to commit your changes.

Step 13 Click Save Configuration to save your changes.

Step 14 To re-enable the access point radio, choose Enable from the Admin Status drop-down box and click Apply .

Step 15 Click Save Configuration to save your changes.

Using the CLI to Optimize RFID Tracking on Access Points

Using the controller CLI, follow these steps to optimize RFID tracking.

Step 1 To configure an access point for monitor mode, enter this command:

config ap mode monitor Cisco_AP

Step 2 When warned that the access point will be rebooted and asked if you want to continue, enter Y .

Step 3 To save your changes, enter this command:

save config

Step 4 To disable the access point radio, enter this command:

config 802.11b disable Cisco_AP

Step 5 To configure the access point to scan only the DCA channels supported by its country of operation, enter this command:

config ap monitor-mode tracking-opt Cisco_AP

Note To specify the exact channels to be scanned, enter this command and the command in After you have entered the command in Step 5, you can enter this command to choose up to four specific 802.11b channels to be scanned by the access point:.

Note To disable tracking optimization for this access point, enter this command: config ap monitor-mode no-optimization Cisco_AP.

Step 6 After you have entered the command in To configure the access point to scan only the DCA channels supported by its country of operation, enter this command: , you can enter this command to choose up to four specific 802.11b channels to be scanned by the access point:

config ap monitor-mode 802.11b fast-channel Cisco_AP channel1 channel2 channel3 channel4

Note In the United States, you can assign any value between 1 and 11 (inclusive) to the channel variable. Other countries support additional channels. You must assign at least one channel.

Step 7 To re-enable the access point radio, enter this command:

config 802.11b enable Cisco_AP

Step 8 To save your changes, enter this command:

save config

Step 9 To see a summary of all access points in monitor mode, enter this command:

show ap monitor-mode summary

Information similar to the following appears:

Using the GUI to Retrieve the Unique Device Identifier on Controllers and Access Points

Follow these steps to retrieve the UDI on controllers and access points using the GUI.

Step 1 Choose Controller > Inventory to open the Inventory page (see Figure 36).

Figure 36 Inventory Page

This page shows the five data elements of the controller UDI.

Step 2 Choose Wireless > Access Points > All APs to open the All APs page.

Step 3 Click the name of the desired access point.

Step 4 Choose the Inventory tab to open the All APs > Details for (Inventory) page (see Figure 37).

Figure 37 All APs > Details for (Inventory) Page

This page shows the inventory information for the access point.

Using the CLI to Retrieve the Unique Device Identifier on Controllers and Access Points

Enter these commands to retrieve the UDI on controllers and access points using the CLI:

• show inventory—Shows the UDI string of the controller. Information similar to the following appears:

• show inventory ap ap_id—Shows the UDI string of the access point specified.

Using the GUI to Perform a Link Test

Follow these steps to run a link test using the GUI.

Step 1 Choose Monitor > Clients to open the Clients page (see Figure 38).

Figure 38 Clients Page

Step 2 Hover your cursor over the blue drop-down arrow for the desired client and choose LinkTest. A link test page appears (see Figure 39).

Note You can also access this page by clicking the MAC address of the desired client and then clicking the Link Test button on the top of the Clients > Detail page.

Figure 39 Link Test Page

This page shows the results of the CCX link test.

Note If the client and/or controller does not support CCX v4 or later, the controller performs a ping link test on the client instead, and a much more limited link test page appears.

Step 3 Click OK to exit the link test page.

Using the CLI to Perform a Link Test

Use these commands to run a link test using the CLI.

1. To run a link test, enter this command:

linktest client_mac

When CCX v4 or later is enabled on both the controller and the client being tested, information similar to the following appears:

When CCX v4 or later is not enabled on either the controller or the client being tested, fewer details appear:

2. To adjust the link-test parameters that are applicable to both the CCX link test and the ping test, enter these commands from config mode:

config > linktest frame-size size_of_link-test_frames

config > linktest number-of-frames number_of_link-test_request_frames_per_test

Using the GUI to Configure Link Latency

Using the controller GUI, follow these steps to configure link latency.

Step 1 Choose Wireless > Access Points > All APs to open the All APs page.

Step 2 Click the name of the access point for which you want to configure link latency.

Step 3 Choose the Advanced tab to open the All APs > Details for (Advanced) page (see Figure 40).

Figure 40 All APs > Details for (Advanced) Page

Step 4 Check the Enable Link Latency check box to enable link latency for this access point or uncheck it to prevent the access point from sending the round-trip time to the controller after every echo response is received. The default value is unchecked.

Step 5 Click Apply to commit your changes.

Step 6 Click Save Configuration to save your changes.

Step 7 When the All APs page reappears, click the name of the access point again.

Step 8 When the All APs > Details for page reappears, choose the Advanced tab again. The link latency and data latency results appear below the Enable Link Latency check box:

• Current —The current round-trip time (in milliseconds) of CAPWAP heartbeat packets or data packets from the access point to the controller and back.
• Minimum —Since link latency has been enabled or reset, the minimum round-trip time (in milliseconds) of CAPWAP heartbeat packets or data packets from the access point to the controller and back.
• Maximum —Since link latency has been enabled or reset, the maximum round-trip time (in milliseconds) of CAPWAP heartbeat packets or data packets from the access point to the controller and back.

Step 9 To clear the current, minimum, and maximum link latency and data latency statistics on the controller for this access point, click Reset Link Latency .

Step 10 After the page refreshes and the All APs > Details for page reappears, choose the Advanced tab. The updated statistics appear in the Minimum and Maximum fields.

Using the CLI to Configure Link Latency

Using the controller CLI, follow these steps to configure link latency.

Step 1 To enable or disable link latency for a specific access point or for all access points currently associated to the controller, enter this command:

config ap link-latency { enable | disable } { Cisco_AP | all }

The default value is disabled.

Note The config ap link-latency {enable | disable} all command enables or disables link latency only for access points that are currently joined to the controller. It does not apply to access points that join in the future.

Step 2 To view the link latency results for a specific access point, enter this command:

show ap config general Cisco_AP

Information similar to the following appears:

The output of this command contains the following link latency results:

• Current Delay —The current round-trip time (in milliseconds) of CAPWAP heartbeat packets from the access point to the controller and back.
• Maximum Delay —Since link latency has been enabled or reset, the maximum round-trip time (in milliseconds) of CAPWAP heartbeat packets from the access point to the controller and back.
• Minimum Delay —Since link latency has been enabled or reset, the minimum round-trip time (in milliseconds) of CAPWAP heartbeat packets from the access point to the controller and back.

Step 3 To clear the current, minimum, and maximum link latency statistics on the controller for a specific access point, enter this command:

config ap link-latency reset Cisco_AP

Step 4 To view the results of the reset, enter this command:

show ap config general Cisco_AP

Using the GUI to Configure Power over Ethernet

Using the controller GUI, follow these steps to configure PoE.

Step 1 Choose Wireless > Access Points > All APs and then the name of the desired access point.

Step 2 Choose the Advanced tab to open the All APs > Details for (Advanced) page (see Figure 41).

Figure 41 All APs > Details for (Advanced) Page

The PoE Status field shows the power level at which the access point is operating: High (20 W), Medium (16.8 W), or Medium (15.4 W). This field is not configurable. The controller auto-detects the access point’s power source and displays the power level here.

Note This field applies only to 1250 series access points that are powered using PoE. There are two other ways to determine if the access point is operating at a lower power level. First, the “Due to low PoE, radio is transmitting at degraded power” message appears under the Tx Power Level Assignment section on the 802.11a/n (or 802.11b/g/n) Cisco APs > Configure page. Second, the “PoE Status: degraded operation” message appears in the controller’s trap log on the Trap Logs page.

Step 3 Perform one of the following:

• Check the Pre-Standard State check box if the access point is being powered by a high-power Cisco switch. These switches provide more than the traditional 6 Watts of power but do not support the intelligent power management (IPM) feature. These switches include:

– 2106 controller,

– WS-C3550, WS-C3560, WS-C3750,

– C1880,

– 2600, 2610, 2611, 2621, 2650, 2651,

– 2610XM, 2611XM, 2621XM, 2650XM, 2651XM, 2691,

– 2811, 2821, 2851,

– 3620, 3631-telco, 3640, 3660,

– 3725, 3745,

– 3825, and 3845.

• Uncheck the Pre-Standard State check box if power is being provided by a power injector or by a switch not on the above list. This is the default value.

Step 4 Check the Power Injector State check box if the attached switch does not support IPM and a power injector is being used. If the attached switch supports IPM, you do not need to check this check box.

Step 5 If you checked the Power Injector State check box in the previous step, the Power Injector Selection and Injector Switch MAC Address parameters appear. The Power Injector Selection parameter enables you to protect your switch port from an accidental overload if the power injector is inadvertently bypassed. Choose one of these options from the drop-down box to specify the desired level of protection:

• Installed—This option examines and remembers the MAC address of the currently connected switch port and assumes that a power injector is connected. Choose this option if your network contains older Cisco 6-Watt switches and you want to avoid possible overloads by forcing a double-check of any relocated access points.

If you want to configure the switch MAC address, enter the MAC address in the Injector Switch MAC Address field. If you want the access point to find the switch MAC address, leave the Injector Switch MAC Address field blank.

Note Each time an access point is relocated, the MAC address of the new switch port fails to match the remembered MAC address, and the access point remains in low-power mode. You must then physically verify the existence of a power injector and reselect this option to cause the new MAC address to be remembered.

• Override—This option allows the access point to operate in high-power mode without first verifying a matching MAC address. It is acceptable to use this option if your network does not contain any older Cisco 6-Watt switches that could be overloaded if connected directly to a 12-Watt access point. The advantage of this option is that if you relocate the access point, it continues to operate in high-power mode without any further configuration. The disadvantage of this option is that if the access point is connected directly to a 6-Watt switch, an overload occurs.

Step 6 Click Apply to commit your changes.

Step 7 If you have a dual-radio 1250 series access point and want to disable one of its radios in order to enable the other radio to receive full power, follow these steps:

a. Choose Wireless > Access Points > Radios > 802.11a/n or 802.11b/g/n to open the 802.11a/n (or 802.11b/g/n) Radios page .

b. Hover your cursor over the blue drop-down arrow for the radio that you want to disable and choose Configure .

c. On the 802.11a/n (or 802.11b/g/n) Cisco APs > Configure page, choose Disable from the Admin Status drop-down box.

d. Click Apply to commit your changes.

e. Manually reset the access point in order for the change to take effect.

Step 8 Click Save Configuration to save your settings.

Using the CLI to Configure Power over Ethernet

Using the controller CLI, enter these commands to configure and view PoE settings.

• If your network contains any older Cisco 6-Watt switches that could be accidentally overloaded if connected directly to a 12-Watt access point, enter this command:

config ap power injector enable { Cisco_AP | all} installed

The access point remembers that a power injector is connected to this particular switch port. If you relocate the access point, you must reissue this command after the presence of a new power injector is verified.

Note Make sure CDP is enabled before issuing this command. Otherwise, this command will fail. See the “Configuring Cisco Discovery Protocol” section for information on enabling CDP.

• To remove the safety checks and allow the access point to be connected to any switch port, enter this command:

config ap power injector enable { Cisco_AP | all} override

It is acceptable to use this command if your network does not contain any older Cisco 6-Watt switches that could be overloaded if connected directly to a 12-Watt access point. The access point assumes that a power injector is always connected. If you relocate the access point, it continues to assume that a power injector is present.

• If you know the MAC address of the connected switch port and do not wish to automatically detect it using the installed option, enter this command:

config ap power injector enable { Cisco_AP | all} switch_port_mac_address

• If you have a dual-radio 1250 series access point and want to disable one of its radios in order to enable the other radio to receive full power, enter this command:

config {802.11a | 802.11b} disable Cisco_AP

Note You must manually reset the access point in order for the change to take effect.

• To view the PoE settings for a specific access point, enter this command:

show ap config general Cisco_AP

Information similar to the following appears:

The Power Type/Mode field shows “degraded mode” if the access point is not operating at full power.

• To view the controller’s trap log, enter this command:

show traplog

If the access point is not operating at full power, the trap contains “PoE Status: degraded operation.”

Using the GUI to View Clients

Using the GUI, follow these steps to view client information.

Step 1 Choose Monitor > Clients to open the Clients page (see Figure 42).

Figure 42 Clients Page

This page lists all of the clients that are associated to the controller’s access points. It provides the following information for each client:

• The MAC address of the client
• The name of the access point to which the client is associated
• The name of the WLAN used by the client
• The type of client (802.11a, 802.11b, 802.11g, or 802.11n)

Note If the 802.11n client associates to an 802.11a radio that has 802.11n enabled, then the client type shows as 802.11n(5). If the 802.11n client associates to an 802.11b/g radio with 802.11n enabled, then the client type shows as 802.11n (2.4).

• The status of the client connection
• The authorization status of the client
• The port number of the access point to which the client is associated
• An indication of whether the client is a WGB

Note Refer to the “Cisco Workgroup Bridges” section for more information on the WGB status.

Note If you want to remove or disable a client, hover your cursor over the blue drop-down arrow for that client and choose Remove or Disable, respectively. If you want to test the connection between the client and the access point, hover your cursor over the blue drop-down arrow for that client and choose Link Test.

Step 2 To create a filter to display only clients that meet certain criteria (such as MAC address, status, or radio type), follow these steps:

a. Click Change Filter to open the Search Clients page (see Figure 43).

Figure 43 Search Clients Page

b. Check one or more of the following check boxes to specify the criteria used when displaying clients:

• MAC Address —Enter a client MAC address.

Note When you enable the MAC Address filter, the other filters are disabled automatically. When you enable any of the other filters, the MAC Address filter is disabled automatically.

• AP Name —Enter the name of an access point.
• WLAN Profile —Enter the name of a WLAN.
• Status —Check the Associated , Authenticated , Excluded , Idle , and/or Probing check boxes.
• Radio Type —Choose 802.11a , 802.11b , 802.11g , 802.11n , or Mobile .
• WGB —Shows WGB clients associated to the controller’s access points.

c. Click Apply to commit your changes. The Current Filter parameter at the top of the Clients page shows the filters that are currently applied.

Note If you want to remove the filters and display the entire client list, click Clear Filter.

Step 3 To view detailed information for a specific client, click the MAC address of the client. The Clients > Detail page appears (see Figure 44).

Figure 44 Clients > Detail Page

This page shows the following information:

• The general properties of the client
• The security settings of the client
• The QoS properties of the client
• Client statistics
• The properties of the access point to which the client is associated

Using the CLI to View Clients