Managing APs

Access Point Modes

Each lightweight AP is configured to operate in one of several different AP modes. In some modes, the AP provides network service to clients; in other modes, the AP operates as a dedicated network management tool.

Not all AP models support all AP modes.

Client-Serving AP Modes

  • Local: This is the default mode. A local mode AP tunnels all client traffic, for all WLANs, in CAPWAP, to the controller. In this mode, the AP’s radios are operational only when the AP is connected to its controller. Local mode APs do not support mesh operation. All AP models support Local mode.

  • FlexConnect: In this mode, client traffic can either be tunneled in CAPWAP to the controller, or egress at the AP’s LAN port, depending on the WLAN configuration. FlexConnect mode APs do not support mesh operation. All models support FlexConnect mode.

  • Bridge and Flex+Bridge: These modes are used in mesh deployments, where wireless rather than wired backhaul is used for CAPWAP connectivity. Not all AP models support these modes; see the relevant mesh documentation for information about support for mesh operation.

Network Management AP Modes

  • Monitor: In this mode, the AP radios are dedicated to monitoring the Wi-Fi channel for RRM and rogue detection. All AP models support this mode.

  • Rogue Detector: In this mode, the AP radios are disabled; the AP monitors the LAN to detect on-wire rogue activity. This mode is not supported on Cisco Wave 2 or 802.11ax APs and is deprecated.

  • Sniffer: In this mode, the AP radio operates in promiscuous mode and captures all Wi-Fi traffic on a channel. These packets are tunneled in CAPWAP to the controller, which forwards them to a machine running OmniPeek or Wireshark for storage and analysis.

  • SE-Connect: In this mode, the AP provides a dedicated connection to CleanAir for spectrum analysis by software such as Spectrum Expert or Chanalyzer. SE-Connect mode is supported only on SE models with CleanAir.

Global Credentials for Access Points

Cisco IOS access points are shipped from the factory with Cisco as the default enable password. This password allows users to log on to the nonprivileged mode and enter show and debug commands, which poses a security threat. The default enable password must be changed to prevent unauthorized users from accessing to the access point's console port and entering configurable commands.

The following are some guidelines to configure global credentials for access points:

  • You can set a global username, password, and enable password that all access points that are currently joined to the controller and any that join in the future inherit as they join the controller. If desired, you can override the global credentials and assign a unique username, password, and enable password for a specific access point.

  • After an access point joins the controller, the access point enables console port security, and you are prompted for your username and password whenever you log in to the access point’s console port. When you log on, you are in nonprivileged mode, and you must enter the enable password in order to use the privileged mode.

  • The global credentials that you configure on the controller are retained across controller and access point reboots. They are overwritten only if the access point joins a new controller that is configured with a global username and password. If the new controller is not configured with global credentials, the access point retains the global username and password configured for the first controller.

  • You must keep track of the credentials used by the access points. Otherwise, you might not be able to log onto the console port of the access point. If you need to return the access points to the default Cisco /Cisco username and password, you must clear the controller’s configuration and the access point’s configuration to return them to factory-default settings. To clear the controller’s configuration, choose Commands > Reset to Factory Default > Reset on the controller GUI, or enter the clear config command on the controller CLI. To clear the access point’s configuration, choose Wireless > Access Points > All APs, click the AP name and click Clear All Config on the controller GUI, or enter the clear ap config Cisco_AP command on the controller CLI. To clear the access point's configuration except its static IP address, choose Wireless > Access Points > All APs, click the AP name and click Clear Config Except Static IP, or enter the clear ap config ap-name keep-ip-config command on the controller CLI. After the access point rejoins a controller, it adopts the default Cisco/Cisco username and password.


    Note

    If the AP is in Bridge mode, then the same Bridge mode is retained after the factory reset of the AP; if the AP is in FlexConnect, Local, Sniffer, or any other mode, then the AP mode is set to Local mode after the factory reset of the AP. If you press the Reset button on the AP and perform a true factory reset, then the AP moves to a cookie configured mode.


    Note
    Suppose you configure an indoor Cisco AP to go into the mesh mode. If you want to reset the Cisco AP to the local mode, use the test mesh mode local command.

  • To reset the AP hardware, choose Wireless > Access Points > All APs, click the AP name and click Reset AP Now.

This section contains the following subsections:

Restrictions for Global Credentials for Access Points

  • The controller software features are supported on all access points that have been converted to lightweight mode except the 1100 series. VxWorks access points are not supported.

  • Telnet is not supported on Cisco Aironet 1810 OEAP, 1810W, 1830, 1850, 2800, and 3800 Series APs.

  • A global Access Point login credentials once configured in controller cannot be removed.

Configuring Global Credentials for Access Points

Configuring Global Credentials for Access Points (GUI)

Procedure

Step 1

Choose Wireless > Access Points > Global Configuration to open the 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.

You can set a global username, password, and enable password that all access points inherit as they join the controller including access points that are currently joined to the controller and any that join in the future. You can override the global credentials and assign a unique username, password, and enable password for a specific access point. The following are requirements enforced on the password:

  • The password should contain characters from at least three of the following classes: lowercase letters, uppercase letters, digits, and special characters.

  • No character in the password can be repeated more than three times consecutively.

  • The password should not contain the management username or the reverse of the username.

  • The password should not contain words like Cisco, oscic, admin, nimda or any variant obtained by changing the capitalization of letters by substituting 1, |, or ! or substituting 0 for o or substituting $ for s.

  • The AP passwords or secret passwords should not contain the following characters:

    &, <, >, ", and '

Step 4

In the Enable Password text box, 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

(Optional) Override the global credentials for a specific access point and assign a unique username, password, and enable password to this access point as follows:

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

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

  3. Choose the Credentials tab. The All APs > Details for (Credentials) page appears.

  4. Select 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 unselected.

  5. In the Username, Password, and Enable Password text boxes, 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.

  6. Click Apply to commit your changes.

  7. Click Save Configuration to save your changes.

    Note

     

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

Configuring Global Credentials for Access Points (CLI)

Procedure

Step 1

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 by entering this command:

config ap mgmtuser add username user password password enablesecret enable_password all

Step 2

(Optional) Override the global credentials for a specific access point and assign a unique username, password, and enable password to this access point by entering 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 want to force this access point to use the controller’s global credentials, enter the config ap mgmtuser delete Cisco_AP command. The following message appears after you execute this command: “AP reverted to global username configuration.”

Step 3

Enter the save config command to save your changes.

Step 4

Verify that global credentials are configured for all access points that join the controller by entering this command:

show ap summary

Note

 

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

To view summary of specific access point you can specify the access point name. You can also use wildcard searches when filtering for access points.

Step 5

See the global credentials configuration for a specific access point by entering this command:

show ap config general Cisco_AP

Note

 

The name of the access point is case sensitive.

Note

 

If this access point is configured for global credentials, the AP User Mode text boxes shows “Automatic.” If the global credentials have been overwritten for this access point, the AP User Mode text box shows “Customized.”

Configuring Telnet and SSH for Access Points

Configuring Telnet and SSH for APs (GUI)

Procedure

Step 1

Global configuration:

  1. Choose Wireless > Access Points > Global Configuration.

  2. In the Global Telnet SSH area, check or uncheck Telnet and SSH check boxes.

    When you enable Telnet or SSH for all APs, the functionality is allowed on APs that are yet to join the controller regardless of their mode.

  3. Click Apply.

  4. Click Save Configuration.

Step 2

Configuration for a specific AP:

  1. Choose Wireless > Access Points > All APs.

  2. Click an AP name.

  3. Click the Advanced tab.

  4. From the Telnet drop-down list, choose AP Specific and check the check box to enable the functionality for the AP.

  5. From the SSH drop-down list, choose AP Specific and check the check box to enable the functionality.

  6. Click Apply.

  7. Click Save Configuration.

Configuring Telnet and SSH for APs (CLI)

Procedure

  • Configure Telnet or SSH for all APs or a specific AP by entering this command:

    config ap {telnet | ssH} {enable | disable} {ap-name | all}

  • Replace the Telnet or SSH configuration for a specific AP with the global configuration by entering this command:

    config ap {telnet | ssH} default ap-name

Embedded Access Points

Controller software release 7.0.116.0 or later releases support the embedded access points: AP801 and AP802, which are the integrated access points on the Cisco 880 Series Integrated Services Routers (ISRs). This access points use a Cisco IOS software image that is separate from the router Cisco IOS software image. The access points can operate as autonomous access points configured and managed locally, or they can operate as centrally managed access points that utilize the CAPWAP or LWAPP protocol. The AP801 and AP802 access points are preloaded with both an autonomous Cisco IOS release and a recovery image for the unified mode.

The following are some guidelines for embedded access points:

  • Before you use an AP801 or AP802 Series Lightweight Access Point with controller software release 7.0.116.0 or later releases, you must upgrade the software in the Next Generation Cisco 880 Series Integrated Services Routers (ISRs) to Cisco IOS 151-4.M or later.


    Note
    In Release 7.4, all AP modes except bridging (required for mesh) are supported for both AP801 and AP802. In Release 7.5 and later, all AP modes are supported on AP802; however, bridging is not supported on AP801.

  • When you want to use the AP801 or AP802 with a controller, you must enable the recovery image for the unified mode on the access point by entering the service-module wlan-ap 0 bootimage unified command on the router in privileged EXEC mode.

  • If the service-module wlan-ap 0 bootimage unified command does not work, make sure that the software license is still eligible.

  • After enabling the recovery image, enter the service-module wlan-ap 0 reload command on the router to shut down and reboot the access point. After the access point reboots, it discovers the controller, downloads the full CAPWAP or LWAPP software release from the controller, and acts as a lightweight access point.


    Note

    To use the CLI commands mentioned above, the router must be running Cisco IOS Release 12.4(20)T or later releases.

  • To support CAPWAP or LWAPP, the router must be activated with at least the Cisco Advanced IP Services IOS license-grade image. A license is required to upgrade to this Cisco IOS image on the router. For licensing information, see http://www.cisco.com/c/en/us/td/docs/routers/access/sw_activation/SA_on_ISR.html.

  • After the AP801 or AP802 boots up with the recovery image for the unified mode, it requires an IP address to communicate with the controller and to download its unified image and configuration from the controller. The router can provide DHCP server functionality, the DHCP pool to reach the controller, and setup option 43 for the controller IP address in the DHCP pool configuration. Use the following configuration to perform this task:

    ip dhcp pool pool_name

    network ip_address subnet_mask

    dns-server ip_address

    default-router ip_address

    option 43 hex controller_ip_address_in_hex

    Example: 

    
ip dhcp pool embedded-ap-pool
	network 60.0.0.0 255.255.255.0
   dns-server 171.70.168.183
   default-router 60.0.0.1
   option 43 hex  f104.0a0a.0a0f   /* single WLC IP address(10.10.10.15) in hex format  */

  • The AP801 and AP802 802.11n radio supports lower power levels than the 802.11n radio in the Cisco Aironet 1250 series access points. The AP801 and AP802 access points store the radio power levels and passes them to the controller when the access point joins the controller. The controller uses the supplied values to limit the user’s configuration.

  • The AP801 and AP802 access points can be used in FlexConnect mode.

For more information about the AP801, see the documentation for the Cisco 800 Series ISRs at http://www.cisco.com/c/en/us/support/routers/800-series-routers/tsd-products-support-series-home.html.

For more information about the AP802, see the documentation for the Next generation Cisco 880 Series ISRs at http://www.cisco.com/c/dam/en/us/td/docs/routers/access/800/860-880-890/software/configuration/guide/SCG_880_series.pdf.

Spectrum Expert Connection

To obtain detailed spectrum data that can be used to generate RF analysis plots similar to those provided by a spectrum analyzer, you can configure a Cisco CleanAir-enabled access point to connect directly to a Microsoft Windows XP or Vista PC running the Spectrum Expert application (referred to as a Spectrum Expert console). You can initiate the Spectrum Expert connection semi-automatically from Prime Infrastructure or by manually launching it from the controller. This section provides instructions for the latter.

Note

The Cisco Aironet Access Point Module for Wireless Security and Spectrum Intelligence (WSSI) for the Cisco Aironet 3600 Series Access Point tightly couples data connectivity, spectrum analysis, and security threat detection and mitigation into a single, multipurpose access point. With WSSI you have to use Metageek Chanalyzer Pro with CleanAir support and not Spectrum expert for wIPS, CleanAir and spectrum analysis.

This section contains the following subsections:

Guidelines and Limitations for Spectrum Expert Connection

You may encounter the error message Unable to contact the remote sensor while connecting to the Cisco Catalyst 9120 AP. This error message appears due to a difference in the AP architecture compared to the Cisco Wave 2 APs. You can view the 5G data by switching the Spectrum Expert panel to sensord using Slot #0.

Configuring Spectrum Expert (GUI)

Before you begin

Prior to establishing a connection between the Spectrum Expert console and the access point, make sure that IP address routing is properly configured and the network spectrum interface (NSI) ports are open in any intervening firewalls.

Procedure

Step 1

Ensure that Cisco CleanAir functionality is enabled for the access point that will be connected to the Spectrum Expert console.

Step 2

Configure the access point for SE-Connect mode using the controller GUI or CLI.

Note

 
The SE-Connect mode is set for the entire access point, not just a single radio. However, the Spectrum Expert console connects to a single radio at a time.

If you are using the controller GUI, follow these steps:

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

  2. Click the name of the desired access point to open the All APs > Details for page.

  3. Choose SE-Connect from the AP Mode drop-down list. This mode is available only for access points that are capable of supporting Cisco CleanAir functionality. For the SE-Connect mode to appear as an available option, the access point must have at least one spectrum-capable radio in the Enable state.

  4. Click Apply to commit your changes.

  5. Click OK when prompted to reboot the access point.

If you are using the CLI, follow these steps:

  1. To configure the access point for SE-Connect mode, enter this command:

    config ap mode se-connect Cisco_AP

  2. When prompted to reboot the access point, enter Y.

  3. To verify the SE-Connect configuration status for the access point, enter this command:

    show ap config {802.11a | 802.11b} Cisco_AP

    Information similar to the following appears:

    
Cisco AP Identifier.............................. 0
Cisco AP Name.................................... CISCO_AP3500
...
Spectrum Management Information
        Spectrum Management Capable.............. Yes
        Spectrum Management Admin State.......... Enabled
        Spectrum Management Operation State...... Up
        Rapid Update Mode........................ Disabled
        Spectrum Expert connection............... Enabled
	 	Spectrum Sensor State.................. Configured (Error code = 0)


Step 3

On the Windows PC, access the Cisco Software Center from this URL:

http://www.cisco.com/cisco/software/navigator.html

Step 4

Click Product > Wireless > Cisco Spectrum Intelligence > Cisco Spectrum Expert > Cisco Spectrum Expert Wi-Fi, and then download the Spectrum Expert 4.0 executable (*.exe) file.

Step 5

Run the Spectrum Expert application on the PC.

Step 6

When the Connect to Sensor dialog box appears, enter the IP address of the access point, choose the access point radio, and enter the 16-byte network spectrum interface (NSI) key to authenticate. The Spectrum Expert application opens a TCP/IP connection directly to the access point using the NSI protocol.

Note

 
The access point must be a TCP server listening on ports 37540 for 2.4 GHz and 37550 for 5 GHz frequencies. These ports must be opened for the spectrum expert application to connect to the access point using the NSI protocol.

Note

 
On the controller GUI, the NSI key appears in the Network Spectrum Interface Key field (below the Port Number field) on the All APs > Details for page. To view the NSI key from the controller CLI, enter the show ap config {802.11a | 802.11b} Cisco_AP command.

When an access point in SE-Connect mode joins a controller, it sends a Spectrum Capabilities notification message, and the controller responds with a Spectrum Configuration Request. The request contains the 16-byte random NSI key generated by the controller for use in NSI authentication. The controller generates one key per access point, which the access point stores until it is rebooted.

Note

 
You can establish up to three Spectrum Expert console connections per access point radio. The Number of Spectrum Expert Connections text box on the 802.11a/n/ac (or 802.11b/g/n) Cisco APs > Configure page of the controller GUI shows the number of Spectrum Expert applications that are currently connected to the access point radio.

Step 7

Verify that the Spectrum Expert console is connected to the access point by selecting the Slave Remote Sensor text box in the bottom right corner of the Spectrum Expert application. If the two devices are connected, the IP address of the access point appears in this text box.

Step 8

Use the Spectrum Expert application to view and analyze spectrum data from the access point.

Cisco Universal Small Cell 8x18 Dual-Mode Module

Cisco Universal Small Cell 8x18 Dual-Mode Module is an external module (4G/LTE) that can be plugged into the Cisco Aironet 3600I APs or Cisco Aironet 3700I APs. The following features are available:

  • You can configure VLAN tagging for the external module’s traffic for the following modes:

    Mode

    Native VLAN

    Non-Native VLAN

    FlexConnect Local Switching

    Supported

    Supported

    Local Mode Central Switching

    Supported

    Supported

  • The module can be powered up by the PoE+ power supply

  • Co-existence detection and warning when Wi-Fi in 2.4 GHz and 3G/4G module are enabled

  • The module's inventory details are available on the controller GUI at Wireless > Access Points > Access Point name > Inventory.

  • Supported on the following Cisco Wireless Controller models:

    • Cisco 3504 Controller

    • Cisco 5520 Controller

    • Cisco 8540 Controller

    • Cisco Virtual Controller

  • Supported on the following Cisco Access Point models:

    • Cisco Aironet 3600I AP

    • Cisco Aironet 3700I AP

Restrictions

Cisco Universal Small Cell 8x18 Dual-Mode Modules are not supported on the following Cisco Access Point models:

  • Cisco Aironet 3600E AP

  • Cisco Aironet 3700E AP

For more information about Cisco Universal Small Cell 8x18 Dual-Mode modules, see http://www.cisco.com/c/en/us/support/wireless/universal-small-cell-8000-series/tsd-products-support-series-home.html.

This section contains the following subsections:

Configuring Cisco Universal Small Cell 8x18 Dual-Mode Module

Configuring Cisco Universal Small Cell 8x18 Dual-Mode Module (GUI)

Procedure

Step 1

Choose Wireless > Access Points > All APs.

Step 2

Click the AP name.

The All APs > Details page is displayed.

Step 3

In the Advanced tab, check or uncheck the External Module Status check box.

You might be prompted with a co-existence warning when Wi-Fi in 2.4-GHz and 3G/4G module are enabled.

Configuring Cisco Universal Small Cell 8x18 Dual-Mode Module (CLI)

Procedure

  • Enable or disable the Cisco USC 8x18 Dual-Mode Module by entering this command:

    config ap module3G {enable | disable} ap-name

    You might be prompted with a co-existence warning when Wi-Fi in 2.4-GHz and 3G/4G module are enabled.

Configuring USC8x18 Dual-Mode Module in Different Scenarios

Configuring VLAN Tagging for USC8x18 Dual-Mode Module in FlexConnect Local Switching (GUI)

Procedure

Step 1

Choose Wireless > Access Points > All APs.

Step 2

Click the AP name.

The All APs > Details page is displayed.

Step 3

In the FlexConnect tab, check the VLAN Support check box and enter the number of the native VLAN on the remote network (such as 100) in the Native VLAN ID box.

Step 4

To enable FlexConnect Local Switching with VLAN ID that is other than 0:

  1. Enable FlexConnect Local Switching under External Module.

  2. Enter a value between 2 and 4096 in the VLAN ID box.

  3. Click Apply.

Step 5

To enable FlexConnect local switching with VLAN ID equal to 0:

  1. Enable FlexConnect Local Switching under External Module.

  2. Click Apply.

Step 6

To remove the FlexConnect local switching per AP configuration, click Remove AP Specific Config.

Step 7

Save the configuration.

Configuring VLAN Tagging for USC8x18 Dual-Mode Module in FlexConnect Local Switching (CLI)

Procedure

  • config ap flexconnect module-vlan enable ap-name —Enables FlexConnect local switching for external module with native VLAN

  • config ap flexconnect module-vlan remove ap-name —Removes the AP specific external module VLAN configuration

  • config ap flexconnect module-vlan enable ap-name vlan vlan-id —Enables FlexConnect local switching with non-native VLAN for the external module

  • show ap module summary {ap-name | all} —Displays detailed information about the external module.

  • show ap inventory {ap-name | all} —Displays information about the AP’s inventory and the external module, if the module is present

  • show ap flexconnect module-vlan ap-name —Displays status of FlexConnect local switching and VLAN ID value

  • show ap config general ap-name —Displays information about the external module info, if the module is present.

Configuring VLAN Tagging for USC8x18 Dual-Mode Module in FlexConnect Group Local Switching (GUI)

Procedure

Step 1

Choose Wireless > FlexConnect Groups.

Step 2

Click New, enter the FlexConnect group name, and click Apply.

Step 3

On the FlexConnect Groups > Edit page, in the FlexConnect APs area, click Add AP.

Step 4

You can either select an AP from a list of APs associated with the controller or directly specify the Ethernet MAC address of the AP that is associated with the controller.

Step 5

Click Add.

Step 6

To enable FlexConnect Local Switching with VLAN ID:

  1. Enable FlexConnect Local Switching under External Module Configuration.

  2. Enter a value between 2 and 4096 in the VLAN ID box.

  3. Click Apply.

Step 7

Save the configuration.

Configuring VLAN Tagging for USC8x18 Dual-Mode Module in FlexConnect Group Local Switching (CLI)

Procedure

  • config flexconnect group group-name module-vlan enable vlan vlan-id —Enables FlexConnect local switching for the FlexConnect group

  • config flexconnect group group-name module-vlan disable —Disables the FlexConnect local switching for the FlexConnect group

  • show flexconnect group detail group-name module-vlan —Displays status of the FlexConnect local switching and VLAN ID in the group

Configuring USC8x18 Dual-Mode Module in Local Mode Central Switching (GUI)

Procedure

Step 1

Create a Remote LAN.

For instructions to create a remote LAN, see the Configuring Remote LANs chapter under WLANs.

Step 2

On the WLANs > Edit page, click the Security tab.

Step 3

In the Layer 2 sub-tab, uncheck the MAC Filtering check box.

Note

 
Remote LAN should be configured only with open security. 802.1X security is not supported.

Step 4

To see the current state of the 3G/4G client, choose Monitor > Clients to open the Clients page.

Step 5

Save the configuration.

Configuring USC8x18 Dual-Mode Module in Local Mode Central Switching (CLI)

Procedure

  • Create a Remote LAN.

    For instructions to create a remote LAN, see the Configuring Remote LANs chapter under WLANs.

  • config interface 3g-vlan interface-name {enable | disable} —Enables or disables the 3G/4G-VLAN interface

  • show interface detailed interface-name —Displays status of the 3G/4G-VLAN flag

  • show client summary ip —Displays status of the 3G/4G clients

LED States for Access Points

In a wireless LAN network where there are a large number of access points, it is difficult to locate a specific access point associated with the controller. You can configure the controller to set the LED state of an access point so that it blinks and the access point can be located. This configuration can be done in the wireless network on a global as well as per-AP level.

The LED state configuration at the global level takes precedence over the AP level.

This section contains the following subsections:

Configuring the LED State for Access Points in a Network Globally (GUI)

Procedure

Step 1

Choose Wireless > Access Points > Global Configuration to open the Global Configuration page.

Step 2

Check the LED state check box.

Step 3

Choose Enable from the drop-down list adjacent to this check box.

Step 4

Click Apply.

Configuring the LED State for Access Point in a Network Globally (CLI)

Procedure

  • Set the LED state for all access points associated with a controller by entering this command:

    config ap led-state {enable | disable} all

Configuring LED State on a Specific Access Point (GUI)

Procedure

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.

Step 3

Check the LED state check box.

Step 4

Choose Enable from the drop-down list adjacent to this text box.

Step 5

Click Apply.

Configuring LED State on a Specific Access Point (CLI)

Procedure

Step 1

Determine the ID of the access point for which you want to configure the LED state by entering this command:

show ap summary

Step 2

Configure the LED state by entering the following command:

config ap led-state {enable | disable} Cisco_AP

Configuring Flashing LEDs

Information About Configuring Flashing LEDs

Controller software enables you to flash the LEDs on an access point in order to locate it. All Cisco IOS lightweight access points support this feature.

Configuring Flashing LEDs (CLI)

Use these commands to configure LED flashing from the privileged EXEC mode of the controller:

  1. Configure the LED flash for an AP by entering this command:

    config ap led-state flash {seconds | indefinite | disable} {Cisco_AP}

    The valid LED flash duration for the AP is 1 to 3600 seconds. You can also configure the LED to flash indefinitely or to stop flashing the LED.

  2. Disable LED flash for an AP after enabling it by entering this command:

    config ap led-state flash disable Cisco_AP

    The command disables LED flashing immediately. For example, if you run the previous command (with the seconds parameter set to 60 seconds) and then disable LED flashing after only 20 seconds, the access point’s LEDs stop flashing immediately.

  3. Save your changes by entering this command:

    save config

  4. Check the status of LED flash for the AP by entering this command:

    show ap led-flash Cisco_AP

    Information similar to the following appears:

    
(Cisco Controller)> show ap led-flash AP1040_46:b9
Led Flash........................................ Enabled for 450 secs, 425 secs left

Note

The output of these commands is sent only to the controller console, regardless of whether the commands were entered on the console or in a TELNET/SSH CLI session.

Configuring LED Flash State on a Specific Access Point (GUI)

Procedure

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.

Step 3

In the LED Flash State section, select one of the following radio buttons:

  • Click the LED flash duration for the AP option and enter the duration range from 1 to 3600 seconds.
  • Click the Indefinite option to configure the LED to flash indefinitely.
  • Click the Disable option to stop flashing the LED.

Step 4

Click Apply.

Access Points with Dual-Band Radios

This section contains the following subsections:

Configuring Access Points with Dual-Band Radios (GUI)

Procedure

Step 1

Choose Wireless > Access Points > Radios > Dual-Band Radios to open the Dual-Band Radios page.

Step 2

Hover your cursor over the blue drop-down arrow of the AP and click Configure.

Step 3

Configure the Admin Status.

Step 4

Configure CleanAir Admin Status as one of the following:

  • Enable
  • Disable
  • 5 GHz Only
  • 2.4 GHz Only

Step 5

Click Apply.

Step 6

Click Save Configuration.

What to do next

You can monitor the access points with dual-band radios by navigating to Monitor > Access Points > Radios > Dual-Band Radios.

Configuring Access Points with Dual-Band Radios (CLI)

Procedure

  • Configure an access point with dual-band radios by entering this command:

    config 802.11-abgn {enable | disable} ap-name

  • Configure the CleanAir features for an access point with dual-band radios by entering this command:

    config 802.11-abgn cleanair {enable | disable} ap-name band 2.4-or-5-GHz