Managing APs

Converting Autonomous Access Points to Lightweight Mode

You can convert any autonomous mode Cisco Aironet access point, to lightweight mode. When you upgrade one of these access points to lightweight mode, the access point communicates with a controller and receives a configuration and software image from the controller.

See the Upgrading Autonomous Cisco Aironet Access Points to Lightweight Mode document for instructions to upgrade an autonomous access point to lightweight mode:

http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_01101010.html

The following are some guidelines for converting autonomous APs to lightweight mode APs:

  • All Cisco lightweight access points support 16 BSSIDs per radio and a total of 16 wireless LANs per access point. When a converted access point associates with a controller, wireless LANs with IDs 1 through 16 are pushed to the access point if the AP is part of the default AP group on the controller. You can use other AP group configurations to push other wireless LANs to the new AP.

    When a 802.11ac module (the RM3000AC) is added to a 3600 AP, you can have only 8 wireless LANs on the 802.11a/n/ac radio.

  • Access points converted to lightweight mode must get an IP address and discover the controller using DHCP, DNS, or IP subnet broadcast.

  • It is not possible to perform archive download while CAPWAP image download is in progress or CAPWAP DTLS is flipping. (CSCvn74377)

This section contains the following subsections:

Restrictions for Converting Autonomous Access Points 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 that is equivalent to WDS when the access point associates to it.

  • After you convert an access point to lightweight mode, the console port provides read-only access to the unit.

Converting Autonomous Access Points to Lightweight Mode

  1. Download the CAPWAP file matching your access point model from Cisco.com. Two types of CAPWAP files are available:

    • Fully functional CAPWAP files, identified by the k9w8 string in their name. When booting this image, the AP is fully functional and can join a controller to obtain its configuration.

    • Recovery mode CAPWAP files, identified by the rcvk9w8 string in their name. These files are smaller than the fully functional k9w8 CAPWAP files. When booting rcvk9w8 files, the AP can join a controller to download a fully functional image. The AP will then reboot, use the fully functional image and rejoin a controller to obtain its configuration.

  2. position the image on an FTP server

  3. Configure the AP to connect to the FTP server as a FTP client. This is done under global configuration mode, with the command ip ftp username , and ip ftp password . For example: 

    Ap#configure terminal
ap(config)#ip ftp username cisco
ap(config)#ip ftp password Cisco123
ap(config)#exit

  4. Once the parameters are configured, you can start the download process on the AP. Use the archive download-sw command, with the /force-reload argument to have the AP reboot at the end of the cycle, and /overwrite to replace the autonomous code with the CAPWAP code. See the following example: 

    ap#archive download-sw /force-reload /overwrite ftp://10.100.1.31/ap3g2-rcvk9w8-tar.152-4.JB6.tar
examining image...
Loading ap3g2-rcvk9w8-tar.152-4.JB6.tar
extracting info (273 bytes)!
Image info:
    Version Suffix: rcvk9w8-
    Image Name: ap3g2-rcvk9w8-mx
    Version Directory: ap3g2-rcvk9w8-mx
    Ios Image Size: 2335232
    Total Image Size: 2335232
    Image Feature: WIRELESS LAN|CAPWAP|RECOVERY
    Image Family: ap3g2
    Wireless Switch Management Version: 3.0.51.0
Extracting files...
ap3g2-rcvk9w8-mx/ (directory) 0 (bytes)
extracting ap3g2-rcvk9w8-mx/ap3g2-rcvk9w8-mx (2327653 bytes)!!!!!!!!!
extracting ap3g2-rcvk9w8-mx/info (273 bytes)

    The AP reboots into lightweight mode and looks for a controller.

Reverting from Lightweight Mode to Autonomous Mode

After you 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. 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.

Reverting to a Previous Release (CLI)

Procedure
Step 1

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

Revert from lightweight mode, by entering 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.

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

Procedure
Step 1

Configure the PC on which your TFTP server software runs 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 ap3g2-k9w7-tar.152-4.JB4.tar for a 2700 or 3700 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 ap3g2-k9w7-tar.default for a 2700 or a 3700 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.

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 the 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.

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 APs.

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.


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, enter the show ap config general Cisco_AP CLI command to show 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.

Configuring a Static IP Address (GUI)

Procedure
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.

Step 3

Under IP Config, select the Static IP (IPv4/IPv6) check box if you want to assign a static IP address to this access point. The default value is unselected.

Note 
The static IP configured on the AP will take precedence over the preferred mode configured on the AP. For example: If AP has static IPV6 address and prefer-mode is set to IPV4, then the AP will join over IPv6.
Step 4

Enter the static IPv4/IPv6 address of the access point, subnet mask/ prefix length assigned to the access point IPv4/IPv6 address, and the IPv4/IPv6 gateway of the access point in the corresponding text boxes.

Step 5

Click Apply to commit your changes. The access point reboots and rejoins the controller, and the static IPv4/IPv6 address that you specified in Step 4 is sent to the access point.

Step 6

After the static IPv4/IPv6 address has been sent to the access point, you can configure the DNS server IP address and domain name as follows:

  1. In the DNS IP Address text box, enter the IPv4/IPv6 address of the DNS server.

  2. In the Domain Name text box, enter the name of the domain to which the access point belongs.

  3. Click Apply to commit your changes.

  4. Click Save Configuration to save your changes.

Configuring a Static IP Address (CLI)

Procedure
Step 1

Configure a static IP address on the access point by entering this command:

For IPv4—config ap static-ip enable Cisco_AP ip_address mask gateway

For IPv6—config ap static-ip enable Cisco_AP ip_address prefix_length gateway

Note 
To disable static IP for the access point, enter the config ap static-ip disable Cisco_AP command.
Note 
The static IP configured on the AP takes precedence over the preferred mode that is configured on the AP. For example: If AP has static IPv6 address and prefer-mode is set to IPv4, then the AP will join over IPv6.
Step 2

Enter the save config command to save your changes.

The access point reboots and rejoins the controller, and the static IP address that you specified in Step 1 is pushed to the access point.

Step 3

After the static IPv4/IPv6 address has been sent to the access point, you can configure the DNSv4/DNSv6 server IP address and domain name as follows:

  1. To specify a DNSv4/DNSv6 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 DNSv4/DNSv6 server for a specific access point or all access points, enter the config ap static-ip delete nameserver {Cisco_AP | all} command.

  2. 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} .

  3. Enter the save config command to save your changes.

Step 4

See the IPv4/IPv6 address configuration for the access point by entering this command:

  • For IPv4:

    show ap config general Cisco_AP

    Information similar to the following appears: 

    show ap config general <Cisco_AP>

Cisco AP Identifier.............................. 4
Cisco AP Name................................. AP6
...
IP Address Configuration......................... Static IP assigned
IP Address....................................... 10.10.10.118
IP NetMask....................................... 255.255.255.0
Gateway IP Addr............................... 10.10.10.1

Domain........................................... Domain1
Name Server................................... 10.10.10.205
...

  • For IPv6:

    show ap config general Cisco_AP

    Information similar to the following appears: 

    
show ap config general <Cisco_AP>

Cisco AP Identifier.............................. 16
Cisco AP Name.................................... AP2602I-A-K9-1
...
IPv6 Address Configuration....................... DHCPv6
IPv6 Address..................................... 2001:9:2:16:1ae:a1da:c2c7:44b
IPv6 Prefix Length............................... 128
Gateway IPv6 Addr................................ fe80::c60a:cbff:fe79:53c4
NAT External IP Address.......................... None

...
IPv6 Capwap UDP Lite............................. Enabled
Capwap Prefer Mode............................... Ipv6 (ApGroup Config)
Hotspot Venue Group.............................. Unspecified
Hotspot Venue Type............................... Unspecified
DNS server IP ............................. Not Available

Supporting Oversized Access Point Images

Controller software release 5.0 or later releases allow you to upgrade to an oversized access point image by automatically deleting the recovery image to create sufficient space.

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.

Recovering the Access Point—Using the TFTP Recovery Procedure

Procedure
Step 1

Download the required recovery image from Cisco.com (for example, ap3g2-rcvk9w8-tar.152-4.JB6.tar for 2700 or 3700 APs) 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.

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 WLC 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, select or unselect Telnet and SSH check boxes.

    When you enable Telnet or SSH for all APs, the functionality is allowed on APs that are yet to associate with the Cisco WLC 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 select the check box to enable the functionality for the AP.

  5. From the SSH drop-down list, choose AP Specific and select 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

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:

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 Cisco WLC GUI at Wireless > Access Points > Access Point name > Inventory.

  • Supported on the following Cisco Wireless Controller models:

    • Cisco 3504 WLC

    • Cisco 5520 WLC

    • Cisco 8540 WLC

    • Cisco Virtual Controller

  • Supported on the following Cisco Access Point models:

    • 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 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 Cisco WLC or directly specify the Ethernet MAC address of the AP that is associated with the Cisco WLC.

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

Select 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

Select 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

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

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

Configuring Mesh Leaf Node

Access points within a mesh network operate in one of the following two ways:

  1. Root access point (RAP)

  2. Mesh access point (MAP)

While the RAPs have wired connections to their controller (WLC), the MAPs have wireless connections to their controller. MAPs communicate among themselves and back to the RAP using wireless connections over the 802.11a/n/g radio backhaul. MAPs use the Cisco Adaptive Wireless Path Protocol (AWPP) to determine the best path through the other mesh access points to the controller.

Relationships among mesh access points are as a parent, child, or neighbor.

  • A parent access point offers the best route back to the RAP. A parent can be either the RAP itself or another MAP.

  • A child access point selects the parent access point as its best route back to the RAP.

  • A neighbor access point is within RF range of another access point but is not selected as its parent or a child.

You can configure the MAP with lower performance to work only as a leaf node. When the mesh network is formed and converged, the leaf node can only work as a child MAP, and cannot be selected by other MAPs as a parent MAP, so that the wireless backhaul performance will not be downgraded.


Note

The mesh leaf node feature is supported only for the IR829 AP803 and the IW3700 Series access points.

Use the following command to configure an MAP as a leaf node: 


(Cisco Controller) >config mesh block-child <ap_name> {enable|disable} 

enable         Enable blocking child for an MAP
disable        Disable blocking child for an MAP

Use the following commands to display the details of the leaf node configuration: 

(Cisco Controller) >show mesh block-child {summary|<ap_name>}

Examples


(Cisco Controller) >show mesh block-child summary 

AP Name       AP Model             BVI MAC Hop  Bridge Group Name  Block Child Set
----------  -------------------  -----------------  ---  -----------------  -------------
AP3        AIR-CAP3602I-C-K9    4c:00:82:07:64:6b  1    mesh               True

Number of Mesh APs Block Child Set............................... 1

(Cisco Controller) >show mesh block-child AP3 

AP Name        AP Model             BVI MAC Hop  Bridge Group Name  Block Child Set
----------  -------------------  -----------------  ---  -----------------  -------------
AP3        AIR-CAP3602I-C-K9    4c:00:82:07:64:6b  1    mesh               True