Cisco Wireless LAN Controller Configuration Guide, Release 5.0
Chapter 6 - Configuring WLANs
Downloads: This chapterpdf (PDF - 1.2MB) The complete bookPDF (PDF - 14.11MB) | Feedback

Configuring WLANsWireless Device Access

Table Of Contents

Configuring WLANsWireless Device Access

WLAN Overview

Configuring WLANs

Creating WLANs

Using the GUI to Create WLANs

Using the CLI to Create WLANs

Configuring DHCP

Internal DHCP Server

External DHCP Servers

DHCP Assignment

Security Considerations

Using the GUI to Configure DHCP

Using the CLI to Configure DHCP

Configuring DHCP Scopes

Configuring MAC Filtering for WLANs

Enabling MAC Filtering

Creating a Local MAC Filter

Configuring a Timeout for Disabled Clients

Assigning WLANs to Interfaces

Configuring the DTIM Period

Using the GUI to Configure the DTIM Period

Using the CLI to Configure the DTIM Period

Configuring Peer-to-Peer Blocking

Guidelines for Using Peer-to-Peer Blocking

Using the GUI to Configure Peer-to-Peer Blocking

Using the CLI to Configure Peer-to-Peer Blocking

Configuring Layer 2 Security

Static WEP Keys

Dynamic 802.1X Keys and Authorization

Configuring a WLAN for Both Static and Dynamic WEP

WPA1 and WPA2

CKIP

Configuring a Session Timeout

Using the GUI to Configure a Session Timeout

Using the CLI to Configure a Session Timeout

Configuring Layer 3 Security

VPN Passthrough

Web Authentication

Assigning a QoS Profile to a WLAN

Using the GUI to Assign a QoS Profile to a WLAN

Using the CLI to Assign a QoS Profile to a WLAN

Configuring QoS Enhanced BSS

Guidelines for Configuring QBSS

Additional Guidelines for Using 7921 and 7920 Wireless IP Phones

Using the GUI to Configure QBSS

Using the CLI to Configure QBSS

Configuring IPv6 Bridging

Guidelines for Using IPv6 Bridging

Using the GUI to Configure IPv6 Bridging

Using the CLI to Configure IPv6 Bridging

Configuring Cisco Client Extensions

Using the GUI to Configure CCX Aironet IEs

Using the GUI to View a Client's CCX Version

Using the CLI to Configure CCX Aironet IEs

Using the CLI to View a Client's CCX Version

Configuring WLAN Override

Using the GUI to Configure WLAN Override

Using the CLI to Configure WLAN Override

Configuring Access Point Groups

Creating Access Point Groups

Assigning Access Points to Access Point Groups

Configuring Web Redirect with 802.1X Authentication

Conditional Web Redirect

Splash Page Web Redirect

Configuring the RADIUS Server

Using the GUI to Configure Web Redirect

Using the CLI to Configure Web Redirect

Disabling Accounting Servers per WLAN


Configuring WLANsWireless Device Access


This chapter describes how to configure up to 16 WLANs for your Cisco UWN Solution. It contains these sections:

WLAN Overview

Configuring WLANs

WLAN Overview

The Cisco UWN Solution can control up to 16 WLANs for lightweight access points. Each WLAN has a separate WLAN ID (1 through 16), a separate WLAN SSID (WLAN name), and can be assigned unique security policies.

Lightweight access points broadcast all active Cisco UWN Solution WLAN SSIDs and enforce the policies that you define for each WLAN.


Note Cisco recommends that you assign one set of VLANs for WLANs and a different set of VLANs for management interfaces to ensure that controllers properly route VLAN traffic.


Configuring WLANs

These sections describe how to configure WLANs:

Creating WLANs

Configuring DHCP

Configuring MAC Filtering for WLANs

Assigning WLANs to Interfaces

Configuring the DTIM Period

Configuring Peer-to-Peer Blocking

Configuring Layer 2 Security

Configuring a Session Timeout

Configuring Layer 3 Security

Assigning a QoS Profile to a WLAN

Configuring QoS Enhanced BSS

Configuring IPv6 Bridging

Configuring Cisco Client Extensions

Configuring WLAN Override

Configuring Access Point Groups

Configuring Web Redirect with 802.1X Authentication

Disabling Accounting Servers per WLAN

Creating WLANs

This section provides instructions for creating up to 16 WLANs using either the controller GUI or CLI.

You can configure WLANs with different service set identifiers (SSIDs) or with the same SSID. An SSID identifies the specific wireless network that you want the controller to access. Creating WLANs with the same SSID enables you to assign different Layer 2 security policies within the same wireless LAN. To distinguish among WLANs with the same SSID, you must create a unique profile name for each WLAN.

WLANs with the same SSID must have unique Layer 2 security policies so that clients can make a WLAN selection based on information advertised in beacon and probe responses. These are the available Layer 2 security policies:

None (open WLAN)

Static WEP or 802.1X


Note Because static WEP and 802.1X are both advertised by the same bit in beacon and probe responses, they cannot be differentiated by clients. Therefore, they cannot both be used by multiple WLANs with the same SSID.


CKIP

WPA/WPA2


Note Although WPA and WPA2 cannot both be used by multiple WLANs with the same SSID, two WLANs with the same SSID could be configured with WPA/TKIP with PSK and WPA/TKIP with 802.1X, respectively, or with WPA/TKIP with 802.1X or WPA/AES with 802.1X, respectively.



Note If a WLAN is configured to an 802.11g only radio policy and a LAP is configured to channel 14, then the WLAN clients try to associate with the LAP, which does not work as expected because of the 802.11g only policy. The workaround to the problem is one of the following:
- Disable channel 14 manually when 802.11g only policy is configured in WLANs.
- Do not select 802.11g only policy when channel 14 is configured to a LAP.


Using the GUI to Create WLANs

Follow these steps to create WLANs using the GUI.


Step 1 Click Wireless > WLANs to open the WLANs page (see Figure 6-1).

Figure 6-1 WLANs Page

This page lists all of the WLANs currently configured on the controller. Figure 6-1 illustrates multiple WLANs using the same SSID. Specifically, it shows two SSIDs named "user" but with different profile names (user1 and user2). Notice that their security policies are also different.


Note If you want to delete a WLAN, hover your cursor over the blue drop-down arrow for that WLAN and choose Remove.


Step 2 To create a new WLAN, click New. The WLANs > New page appears (see Figure 6-2).

Figure 6-2 WLANs > New Page

Step 3 From the Type drop-down box, choose WLAN to create a WLAN.


Note If you want to create a guest LAN for wired guest users, choose Guest LAN and follow the instructions in the "Configuring Wired Guest Access" section.


Step 4 In the Profile Name field, enter up to 32 alphanumeric characters for the profile name to be assigned to this WLAN. The profile name must be unique.

Step 5 In the WLAN SSID field, enter up to 32 alphanumeric characters for the SSID to be assigned to this WLAN.

Step 6 Click Apply to commit your changes. The WLANs > Edit page appears (see Figure 6-3).


Note You can also access the WLANs > Edit page from the WLANs page by clicking the name of the WLAN that you want to edit.


Figure 6-3 WLANs > Edit Page

Step 7 Use the parameters on the General, Security, QoS, and Advanced tabs to configure this WLAN. Refer to the sections in the rest of this chapter for instructions on configuring specific features for WLANs.

Step 8 On the General tab, check the Status check box to enable this WLAN. Be sure to leave it unchecked until you have finished making configuration changes to the WLAN.

Step 9 Click Apply to commit your changes.

Step 10 Click Save Configuration to save your changes.


Using the CLI to Create WLANs

Use these commands to create WLANs using the CLI.

1. To view the list of existing WLANs and to see whether they are enabled or disabled, enter this command:

show wlan summary

2. To create a new WLAN, enter this command:

config wlan create wlan_id profile_name ssid


Note If you do not specify an ssid, the profile_name parameter is used for both the profile name and the SSID.



Note When WLAN 1 is created in the configuration wizard, it is created in enabled mode. Disable it until you have finished configuring it. When you create a new WLAN using the config wlan create command, it is created in disabled mod. Leave it disabled until you have finished configuring it.



Note If you want to create a guest LAN for wired guest users, follow the instructions in the "Configuring Wired Guest Access" section.


3. To disable a WLAN (for example, before making any modifications to a WLAN), enter this command:

config wlan disable wlan_id


Note If the management and AP-manager interfaces are mapped to the same port and are members of the same VLAN, you must disable the WLAN before making a port-mapping change to either interface. If the management and AP-manager interfaces are assigned to different VLANs, you do not need to disable the WLAN.


4. To enable a WLAN (for example, after you have finished making configuration changes to the WLAN), enter this command:

config wlan enable wlan_id

5. To delete a WLAN, enter this command:

config wlan delete wlan_id

Configuring DHCP

WLANs can be configured to use the same or different Dynamic Host Configuration Protocol (DHCP) servers or no DHCP server. Two types of DHCP servers are available: internal and external.

Internal DHCP Server

The controllers contain an internal DHCP server. This server is typically used in branch offices that do not already have a DHCP server. The wireless network generally contains 10 access points or fewer, with the access points on the same IP subnet as the controller. The internal server provides DHCP addresses to wireless clients, direct-connect access points, appliance-mode access points on the management interface, and DHCP requests that are relayed from access points. Only lightweight access points are supported. When you want to use the internal DHCP server, you must set the management interface IP address of the controller as the DHCP server IP address.

DHCP option 43 is not supported on the internal server. Therefore, the access point must use an alternative method to locate the management interface IP address of the controller, such as local subnet broadcast, DNS, priming, or over-the-air discovery.


Note Refer to Chapter 7, or the Controller Deployment Guide at this URL for more information on how access points find controllers:
http://www.cisco.com/en/US/products/ps6366/prod_technical_reference_list.html


External DHCP Servers

The operating system is designed to appear as a DHCP Relay to the network and as a DHCP server to clients with industry-standard external DHCP servers that support DHCP Relay. This means that each controller appears as a DHCP Relay agent to the DHCP server. This also means that the controller appears as a DHCP server at the virtual IP Address to wireless clients.

Because the controller captures the client IP address obtained from a DHCP server, it maintains the same IP address for that client during intra-controller, inter-controller, and inter-subnet client roaming.

DHCP Assignment

You can configure DHCP on a per-interface or per-WLAN basis. The preferred method is to use the primary DHCP server address assigned to a particular interface.

Per-Interface Assignment

You can assign DHCP servers for individual interfaces. The management interface, AP-manager interface, and dynamic interfaces can be configured for a primary and secondary DHCP server, and the service-port interface can be configured to enable or disable DHCP servers.


Note Refer to Chapter 3, for information on configuring the controller's interfaces.


Per-WLAN Assignment

You can also define a DHCP server on a WLAN. This server will override the DHCP server address on the interface assigned to the WLAN.

Security Considerations

For enhanced security, Cisco recommends that you require all clients to obtain their IP addresses from a DHCP server. To enforce this requirement, all WLANs can be configured with a DHCP Addr. Assignment Required setting, which disallows client static IP addresses. If DHCP Addr. Assignment Required is selected, clients must obtain an IP address via DHCP. Any client with a static IP address is not be allowed on the network. The controller monitors DHCP traffic because it acts as a DHCP proxy for the clients.


Note WLANs that support management over wireless must allow management (device-servicing) clients to obtain an IP address from a DHCP server. See the "Using Management over Wireless" section for instructions on configuring management over wireless.


If slightly less security is tolerable, you can create WLANs with DHCP Addr. Assignment Required disabled. Clients then have the option of using a static IP address or obtaining an IP address from a designated DHCP server.

You are also allowed to create separate WLANs with DHCP Addr. Assignment Required disabled and a DHCP server IP address of 0.0.0.0. These WLANs drop all DHCP requests and force clients to use a static IP address. Note that these WLANs do not support management over wireless connections.


Note Refer to Chapter 4, for instructions on globally configuring DHCP proxy.


This section provides both GUI and CLI instructions for configuring DHCP.

Using the GUI to Configure DHCP

Follow these steps to configure DHCP using the GUI.


Step 1 Follow the instructions in the "Using the GUI to Configure the Management, AP-Manager, Virtual, and Service-Port Interfaces" section or "Using the GUI to Configure Dynamic Interfaces" section to configure a primary DHCP server for a management, AP-manager, or dynamic interface that will be assigned to the WLAN.


Note When you want to use the internal DHCP server, you must set the management interface IP address of the controller as the DHCP server IP address.


Step 2 Click WLANs to open the WLANs page.

Step 3 Click the profile name of the WLAN for which you wish to assign an interface. The WLANs > Edit (General) page appears.

Step 4 On the General tab, uncheck the Status check box and click Apply to disable the WLAN.

Step 5 Re-click the profile name of the WLAN.

Step 6 On the General tab, choose the interface for which you configured a primary DHCP server to be used with this WLAN from the Interface drop-down box.

Step 7 Click the Advanced tab to open the WLANs > Edit (Advanced) page.

Step 8 If you want to define a DHCP server on the WLAN that will override the DHCP server address on the interface assigned to the WLAN, check the DHCP Server Override check box and enter the IP address of the desired DHCP server in the DHCP Server IP Addr edit box. The default value for the check box is disabled.


Note The preferred method for configuring DHCP is to use the primary DHCP address assigned to a particular interface instead of the DHCP server override.


Step 9 If you want to require all clients to obtain their IP addresses from a DHCP server, check the DHCP Addr. Assignment Required check box. When this feature is enabled, any client with a static IP address is not allowed on the network. The default value is disabled.

Step 10 Click Apply to commit your changes.

Step 11 On the General tab, check the Status check box and click Apply to re-enable the WLAN.

Step 12 Click Save Configuration to save your changes.


Using the CLI to Configure DHCP

Follow these steps to configure DHCP using the CLI.


Step 1 Follow the instructions in the "Using the CLI to Configure the Management, AP-Manager, Virtual, and Service-Port Interfaces" section or "Using the CLI to Configure Dynamic Interfaces" section to configure a primary DHCP server for a management, AP-manager, or dynamic interface that will be assigned to the WLAN.

Step 2 To disable the WLAN, enter this command:

config wlan disable wlan_id

Step 3 To specify the interface for which you configured a primary DHCP server to be used with this WLAN, enter this command:

config wlan interface wlan_id interface_name

Step 4 If you want to define a DHCP server on the WLAN that will override the DHCP server address on the interface assigned to the WLAN, enter this command:

config wlan dhcp_server wlan_id dhcp_server_ip_address


Note The preferred method for configuring DHCP is to use the primary DHCP address assigned to a particular interface instead of the DHCP server override. If you enable the override, you can use the show wlan command to verify that the DHCP server has been assigned to the WLAN.


Step 5 To re-enable the WLAN, enter this command:

config wlan enable wlan_id


Configuring DHCP Scopes

Controllers have built-in DHCP relay agents. However, when network administrators desire network segments that do not have a separate DHCP server, the controllers can have built-in DHCP scopes that assign IP addresses and subnet masks to wireless clients. Typically, one controller can have one or more DHCP scopes that each provide a range of IP addresses.

DHCP scopes are needed for internal DHCP to work. Once DHCP is defined on the controller, we can then point the primary DHCP server IP address on the management, AP-manager, and dynamic interfaces to controller's management interface. You can configure up to 16 DHCP scopes using the controller GUI or CLI.

Using the GUI to Configure DHCP Scopes

Follow these steps to configure DHCP scopes using the GUI.


Step 1 Click Controller > Internal DHCP Server to open the DHCP Scopes page (see Figure 6-4).

Figure 6-4 DHCP Scopes Page

This page lists any DHCP scopes that have already been configured.


Note If you ever want to delete an existing DHCP scope, hover your cursor over the blue drop-down arrow for that scope and choose Remove.


Step 2 To add a new DHCP scope, click New. The DHCP Scope > New page appears.

Step 3 In the Scope Name field, enter a name for the new DHCP scope.

Step 4 Click Apply. When the DHCP Scopes page reappears, click the name of the new scope. The DHCP Scope > Edit page appears (see Figure 6-5).

Figure 6-5 DHCP Scope > Edit Page

Step 5 In the Pool Start Address field, enter the starting IP address in the range assigned to the clients.


Note This pool must be unique for each DHCP scope and must not include the static IP addresses of routers or other servers.


Step 6 In the Pool End Address field, enter the ending IP address in the range assigned to the clients.


Note This pool must be unique for each DHCP scope and must not include the static IP addresses of routers or other servers.


Step 7 In the Network field, enter the network served by this DHCP scope. This is the IP address used by the management interface with Netmask applied, as configured on the Interfaces page.

Step 8 In the Netmask field, enter the subnet mask assigned to all wireless clients.

Step 9 In the Lease Time field, enter the amount of time (from 0 to 65536 seconds) that an IP address is granted to a client.

Step 10 In the Default Routers field, enter the IP address of the optional router(s) connecting the controllers. Each router must include a DHCP forwarding agent, which allows a single controller to serve the clients of multiple controllers.

Step 11 In the DNS Domain Name field, enter the optional domain name system (DNS) domain name of this DHCP scope for use with one or more DNS servers.

Step 12 In the DNS Servers field, enter the IP address of the optional DNS server(s). Each DNS server must be able to update a client's DNS entry to match the IP address assigned by this DHCP scope.

Step 13 In the Netbios Name Servers field, enter the IP address of the optional Microsoft Network Basic Input Output System (NetBIOS) name server(s), such as a s Internet Naming Service (WINS) server.

Step 14 From the Status drop-down box, choose Enabled to enable this DHCP scope or Disabled to disable it.

Step 15 Click Apply to commit your changes.

Step 16 Click Save Configuration to save your changes.


Using the CLI to Configure DHCP Scopes

Follow these steps to configure DHCP scopes using the CLI.


Step 1 To create a new DHCP scope, enter this command:

config dhcp create-scope scope


Note If you ever want to delete a DHCP scope, enter this command: config dhcp delete-scope scope.


Step 2 To specify the starting and ending IP address in the range assigned to the clients, enter this command:

config dhcp address-pool scope start end


Note This pool must be unique for each DHCP scope and must not include the static IP addresses of routers or other servers.


Step 3 To specify the network served by this DHCP scope (the IP address used by the management interface with Netmask applied) and the subnet mask assigned to all wireless clients, enter this command:

config dhcp network scope network netmask

Step 4 To specify the amount of time (from 0 to 65536 seconds) that an IP address is granted to a client, enter this command:

config dhcp lease scope lease_duration

Step 5 To specify the IP address of the optional router(s) connecting the controllers, enter this command:

config dhcp default-router scope router_1 [router_2] [router_3]

Each router must include a DHCP forwarding agent, which allows a single controller to serve the clients of multiple controllers.

Step 6 To specify the optional domain name system (DNS) domain name of this DHCP scope for use with one or more DNS servers, enter this command:

config dhcp domain scope domain

Step 7 To specify the IP address of the optional DNS server(s), enter this command:

config dhcp dns-servers scope dns1 [dns2] [dns3]

Each DNS server must be able to update a client's DNS entry to match the IP address assigned by this DHCP scope

Step 8 To specify the IP address of the optional Microsoft Network Basic Input Output System (NetBIOS) name server(s), such as a s Internet Naming Service (WINS) server, enter this command:

config dhcp netbios-name-server scope wins1 [wins2] [wins3]

Step 9 To enable or disable this DHCP scope, enter this command:

config dhcp {enable | disable} scope

Step 10 To save your changes, enter this command:

save config

Step 11 To see the list of configured DHCP scopes, enter this command:

show dhcp summary

Information similar to the following appears:

Scope Name           Enabled           Address Range
Scope 1 						No 	 	 	 0.0.0.0 -> 0.0.0.0
Scope 2						No			 0.0.0.0 -> 0.0.0.0
 
   

Step 12 To display the DHCP information for a particular scope, enter this command:

show dhcp scope

Information similar to the following appears:

Enabled....................................... No
Lease Time.................................... 0
Pool Start.................................... 0.0.0.0
Pool End...................................... 0.0.0.0
Network....................................... 0.0.0.0
Netmask....................................... 0.0.0.0
Default Routers............................... 0.0.0.0 0.0.0.0 0.0.0.0
DNS Domain.................................... 
DNS........................................... 0.0.0.0 0.0.0.0 0.0.0.0
Netbios Name Servers.......................... 0.0.0.0 0.0.0.0 0.0.0.0
 
   

Configuring MAC Filtering for WLANs

When you use MAC filtering for client or administrator authorization, you need to enable it at the WLAN level first. If you plan to use local MAC address filtering for any WLAN, use the commands in this section to configure MAC filtering for a WLAN.

Enabling MAC Filtering

Use these commands to enable MAC filtering on a WLAN:

Enter config wlan mac-filtering enable wlan_id to enable MAC filtering.

Enter show wlan to verify that you have MAC filtering enabled for the WLAN.

When you enable MAC filtering, only the MAC addresses that you add to the WLAN are allowed to join the WLAN. MAC addresses that have not been added are not allowed to join the WLAN.

Creating a Local MAC Filter

Controllers have built-in MAC filtering capability, similar to that provided by a RADIUS authorization server.

Use these commands to add MAC addresses to a WLAN MAC filter:

Enter config macfilter add mac_addr wlan_id [interface_name] [description] [IP_addr] to create a MAC filter entry on the controller, where the following parameters are optional:

interface_name—The name of the interface.

description—A brief description of the interface in double quotes.

IP_addr—The IP address of the local MAC filter database.

Enter config macfilter ip-address mac_addr IP_addr to assign an IP address to an existing MAC filter entry, if one was not assigned in the config macfilter add command.

Enter show macfilter to verify that MAC addresses are assigned to the WLAN.

Configuring a Timeout for Disabled Clients

You can configure a timeout for disabled clients. Clients who fail to authenticate three times when attempting to associate are automatically disabled from further association attempts. After the timeout period expires, the client is allowed to retry authentication until it associates or fails authentication and is excluded again. Use these commands to configure a timeout for disabled clients:

Enter config wlan blacklist wlan_id timeout to configure the timeout for disabled clients. Enter a timeout from 1 to 65535 seconds, or enter 0 to permanently disable the client.

Use the show wlan command to verify the current timeout.

Assigning WLANs to Interfaces

Use these commands to assign a WLAN to an interface:

Enter this command to assign a WLAN to an interface:

config wlan interface {wlan_id | foreignAp} interface_id

Use the interface_id option to assign the WLAN to a specific interface.

Use the foreignAp option to use a third-party access point.

Enter show wlan summary to verify the interface assignment status.

Configuring the DTIM Period

In 802.11a/n and 802.11b/g/n networks, lightweight access points broadcast a beacon at regular intervals, which coincides with the Delivery Traffic Indication Map (DTIM). After the access point broadcasts the beacon, it transmits any buffered broadcast and multicast frames based on the value set for the DTIM period. This feature allows power-saving clients to wake up at the appropriate time if they are expecting broadcast or multicast data.

Normally, the DTIM value is set to 1 (transmit broadcast and multicast frames after every beacon) or 2 (transmit after every other beacon). For instance, if the beacon period of the 802.11a/n or 802.11b/g/n network is 100 ms and the DTIM value is set to 1, the access point transmits buffered broadcast and

multicast frames 10 times per second. If the beacon period is 100 ms and the DTIM value is set to 2, the access point transmits buffered broadcast and multicast frames 5 times per second. Either of these settings may be suitable for applications, including VoIP, that expect frequent broadcast and multicast frames.

However, the DTIM value can be set as high as 255 (transmit broadcast and multicast frames after every 255th beacon) if all 802.11a/n or 802.11b/g/n clients have power save enabled. Because the clients have to listen only when the DTIM period is reached, they can be set to listen for broadcasts and multicasts less frequently, resulting in longer battery life. For instance, if the beacon period is 100 ms and the DTIM value is set to 100, the access point transmits buffered broadcast and multicast frames once every 10 seconds, allowing the power-saving clients to sleep longer before they have to wake up and listen for broadcasts and multicasts, resulting in longer battery life.

Many applications cannot tolerate a long time between broadcast and multicast messages, resulting in poor protocol and application performance. Cisco recommends a low DTIM value for 802.11a/n and 802.11b/g/n networks that support such clients.

In controller software release 5.0, you can configure the DTIM period for the 802.11a/n and 802.11b/g/n radio networks on specific WLANs. In previous software releases, the DTIM period was configured per radio network only, not per WLAN. The benefit of this change is that now you can configure a different DTIM period for each WLAN. For example, you might want to set different DTIM values for voice and data WLANs.


Note When you upgrade the controller software to release 5.0 from a previous release, the DTIM period that was configured for a radio network is copied to all of the existing WLANs on the controller.


Using the GUI to Configure the DTIM Period

Using the GUI, follow these steps to configure the DTIM period for a WLAN.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the name of the WLAN for which you want to configure the DTIM period.

Step 3 Uncheck the Status check box to disable the WLAN.

Step 4 Click Apply to commit your changes.

Step 5 Click the Advanced tab to open the WLANs > Edit (Advanced) page (see Figure 6-6).

Figure 6-6 WLANs > Edit (Advanced) Page

Step 6 Under DTIM Period, enter a value between 1 and 255 (inclusive) in the 802.11a/n and 802.11b/g/n fields. The default value is 1 (transmit broadcast and multicast frames after every beacon).

Step 7 Click Apply to commit your changes.

Step 8 Click the General tab to open the WLANs > Edit (General) page.

Step 9 Check the Status check box to re-enable the WLAN.

Step 10 Click Save Configuration to save your changes.


Using the CLI to Configure the DTIM Period

Using the CLI, follow these steps to configure the DTIM period for a WLAN.


Step 1 To disable the WLAN, enter this command:

config wlan disable wlan_id

Step 2 To configure the DTIM period for either the 802.11a/n or 802.11b/g/n radio network on a specific WLAN, enter this command:

config wlan dtim {802.11a | 802.11b} dtim wlan_id

where dtim is a value between 1 and 255 (inclusive). The default value is 1 (transmit broadcast and multicast frames after every beacon).

Step 3 To re-enable the WLAN, enter this command:

config wlan enable wlan_id

Step 4 To save your changes, enter this command:

save config

Step 5 To verify the DTIM period, enter this command:

show wlan wlan_id

Information similar to the following appears:

WLAN Identifier.................................. 1
Profile Name..................................... employee1
Network Name (SSID).............................. employee
Status........................................... Enabled
...
DTIM period for 802.11a radio.................... 1
DTIM period for 802.11b radio.................... 1
Local EAP Authentication...................... Disabled 
...
 
   

Configuring Peer-to-Peer Blocking

In controller software releases prior to 4.2, peer-to-peer blocking is applied globally to all clients on all WLANs and causes traffic between two clients on the same VLAN to be transferred to the upstream VLAN rather than being bridged by the controller. This behavior usually results in traffic being dropped at the upstream switch because switches do not forward packets out the same port on which they are received.

In controller software release 4.2 or later, peer-to-peer blocking is applied to individual WLANs, and each client inherits the peer-to-peer blocking setting of the WLAN to which it is associated. In 4.2 or later, you also have more control over how traffic is directed. For example, you can choose to have traffic bridged locally within the controller, dropped by the controller, or forwarded to the upstream VLAN. Figure 6-7 illustrates each option.

Figure 6-7 Peer-to-Peer Blocking Examples

Guidelines for Using Peer-to-Peer Blocking

Follow these guidelines when using peer-to-peer blocking:

In controller software releases prior to 4.2, the controller forwards Address Resolution Protocol (ARP) requests upstream (just like all other traffic). In controller software release 4.2 or later, ARP requests are directed according to the behavior set for peer-to-peer blocking.

Peer-to-peer blocking does not apply to multicast traffic.

Locally switched hybrid-REAP WLANs and hybrid-REAP access points in standalone mode do not support peer-to-peer blocking.

If you upgrade to controller software release 4.2 or later from a previous release that supports global peer-to-peer blocking, each WLAN is configured with the peer-to-peer blocking action of forwarding traffic to the upstream VLAN.

Using the GUI to Configure Peer-to-Peer Blocking

Follow these steps to configure a WLAN for peer-to-peer blocking using the GUI.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the name of the WLAN for which you want to configure peer-to-peer blocking.

Step 3 Click the Advanced tab to open the WLANs > Edit (Advanced) page (see Figure 6-8).

Figure 6-8 WLANs > Edit (Advanced) Page

Step 4 Choose one of the following options from the P2P Blocking drop-down box:

Disabled—Disables peer-to-peer blocking and bridges traffic locally within the controller whenever possible. This is the default value.


Note Traffic is never bridged across VLANs in the controller.


Drop—Causes the controller to discard the packets.

Forward-UpStream—Causes the packets to be forwarded on the upstream VLAN. The device above the controller decides what action to take regarding the packets.

Step 5 Click Apply to commit your changes.

Step 6 Click Save Configuration to save your changes.


Using the CLI to Configure Peer-to-Peer Blocking

Follow these steps to configure a WLAN for peer-to-peer blocking using the CLI.


Step 1 To configure a WLAN for peer-to-peer blocking, enter this command:

config wlan peer-blocking {disable | drop | forward-upstream} wlan_id


Note See the description of each parameter in the "Using the GUI to Configure Peer-to-Peer Blocking" section above.


Step 2 To save your changes, enter this command:

save config

Step 3 To see the status of peer-to-peer blocking for a WLAN, enter this command:

show wlan wlan_id

Information similar to the following appears:

WLAN Identifier.................................. 1
Profile Name..................................... test
Network Name (SSID).............................. test
Status........................................... Enabled
...
...
...
Peer-to-Peer Blocking Action..................... Disabled
Radio Policy..................................... All
Local EAP Authentication...................... Disabled 


Configuring Layer 2 Security

This section explains how to assign Layer 2 security settings to WLANs.


Note Clients using the Microsoft Wireless Configuration Manager and 802.1X must use WLANs configured for 40- or 104-bit key length. Configuring for 128-bit key length results in clients that can associate but not authenticate.


Static WEP Keys

Controllers can control static WEP keys across access points. Use these commands to configure static WEP for WLANs:

Enter this command to disable 802.1X encryption:

config wlan security 802.1X disable wlan_id

Enter this command to configure 40/64, 104/128, or 128/152-bit WEP keys:

config wlan security static-wep-key encryption wlan_id {40 | 104 | 128} {hex | ascii} key key_index

Use the 40, 104, or 128 options to specify 40/64-bit, 104/128-bit, or 128/152-bit encryption. The default setting is 104/128.

Use the hex or ascii option to specify the character format for the WEP key.

Enter 10 hexadecimal digits (any combination of 0-9, a-f, or A-F) or five printable ASCII characters for 40-bit/64-bit WEP keys; enter 26 hexadecimal or 13 ASCII characters for 104-bit/128-bit keys; enter 32 hexadecimal or 16 ASCII characters for 128-bit/152-bit keys.

Enter a key index (sometimes called a key slot) of 1 through 4.

Dynamic 802.1X Keys and Authorization

Controllers can control 802.1X dynamic WEP keys using Extensible Authentication Protocol (EAP) across access points and support 802.1X dynamic key settings for WLANs.


Note To use LEAP with lightweight access points and wireless clients, make sure to choose Cisco-Aironet as the RADIUS server type when configuring the CiscoSecure Access Control Server (ACS).


Enter show wlan wlan_id to check the security settings of each WLAN. The default security setting for new WLANs is 802.1X with dynamic keys enabled. To maintain robust Layer 2 security, leave 802.1X configured on your WLANs.

To disable or enable the 802.1X authentication, use this command:

config wlan security 802.1X {enable | disable} wlan_id

After you enable 802.1X authentication, the controller sends EAP authentication packets between the wireless client and the authentication server. This command allows all EAP-type packets to be sent to and from the controller.

If you want to change the 802.1X encryption level for a WLAN, use this command:

config wlan security 802.1X encryption wlan_id [40 | 104 | 128]

Use the 40 option to specify 40/64-bit encryption.

Use the 104 option to specify 104/128-bit encryption. (This is the default encryption setting.)

Use the 128 option to specify 128/152-bit encryption.

Configuring a WLAN for Both Static and Dynamic WEP

You can configure up to four WLANs to support static WEP keys, and you can also configure dynamic WEP on any of these static-WEP WLANs. Follow these guidelines when configuring a WLAN for both static and dynamic WEP:

The static WEP key and the dynamic WEP key must be the same length.

When you configure both static and dynamic WEP as the Layer 2 security policy, no other security policies can be specified. That is, you cannot configure web authentication. However, when you configure either static or dynamic WEP as the Layer 2 security policy, you can configure web authentication.

WPA1 and WPA2

Wi-Fi Protected Access (WPA or WPA1) and WPA2 are standards-based security solutions from the Wi-Fi Alliance that provide data protection and access control for wireless LAN systems. WPA1 is compatible with the IEEE 802.11i standard but was implemented prior to the standard's ratification; WPA2 is the Wi-Fi Alliance's implementation of the ratified IEEE 802.11i standard.

By default, WPA1 uses Temporal Key Integrity Protocol (TKIP) and message integrity check (MIC) for data protection while WPA2 uses the stronger Advanced Encryption Standard encryption algorithm using Counter Mode with Cipher Block Chaining Message Authentication Code Protocol (AES-CCMP). Both WPA1 and WPA2 use 802.1X for authenticated key management by default. However, these options are also available: PSK, CCKM, and 802.1X+CCKM.

802.1X—The standard for wireless LAN security, as defined by IEEE, is called 802.1X for 802.11, or simply 802.1X. An access point that supports 802.1X acts as the interface between a wireless client and an authentication server, such as a RADIUS server, to which the access point communicates over the wired network. If 802.1X is selected, only 802.1X clients are supported.

PSK—When you choose PSK (also known as WPA pre-shared key or WPA passphrase), you need to configure a pre-shared key (or a passphrase). This key is used as the pairwise master key (PMK) between the clients and the authentication server.

CCKM—Cisco Centralized Key Management (CCKM) uses a fast rekeying technique that enables clients to roam from one access point to another without going through the controller, typically in under 150 milliseconds (ms). CCKM reduces the time required by the client to mutually authenticate with the new access point and derive a new session key during reassociation. CCKM fast secure roaming ensures that there is no perceptible delay in time-sensitive applications such as wireless Voice over IP (VoIP), enterprise resource planning (ERP), or Citrix-based solutions. CCKM is a CCXv4-compliant feature. If CCKM is selected, only CCKM clients are supported.


Note The 4.2 or later release of controller software supports CCX versions 1 through 5. CCX support is enabled automatically for every WLAN on the controller and cannot be disabled. The controller stores the CCX version of the client in its client database and uses it to limit client functionality. Clients must support CCXv4 or v5 in order to use CCKM. See the "Configuring Cisco Client Extensions" section for more information on CCX.


802.1X+CCKM—During normal operation, 802.1X-enabled clients mutually authenticate with a new access point by performing a complete 802.1X authentication, including communication with the main RADIUS server. However, when you configure your WLAN for 802.1X and CCKM fast secure roaming, CCKM-enabled clients securely roam from one access point to another without the need to reauthenticate to the RADIUS server. 802.1X+CCKM is considered optional CCKM because both CCKM and non-CCKM clients are supported when this option is selected.

On a single WLAN, you can allow WPA1, WPA2, and 802.1X/PSK/CCKM/802.1X+CCKM clients to join. All of the access points on such a WLAN advertise WPA1, WPA2, and 802.1X/PSK/CCKM/
802.1X+CCKM information elements in their beacons and probe responses. When you enable WPA1 and/or WPA2, you can also enable one or two ciphers, or cryptographic algorithms, designed to protect data traffic. Specifically, you can enable AES and/or TKIP data encryption for WPA1 and/or WPA2. TKIP is the default value for WPA1, and AES is the default value for WPA2.

You can configure WPA1+WPA2 through either the GUI or the CLI.

Using the GUI to Configure WPA1+WPA2

Follow these steps to configure a WLAN for WPA1+WPA2 using the controller GUI.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the profile name of the desired WLAN to open the WLANs > Edit page.

Step 3 Click the Security and Layer 2 tabs to open the WLANs > Edit (Security > Layer 2) page (see Figure 6-9).

Figure 6-9 WLANs > Edit (Security > Layer 2) Page

Step 4 Choose WPA+WPA2 from the Layer 2 Security drop-down box.

Step 5 Under WPA+WPA2 Parameters, check the WPA Policy check box to enable WPA1, check the WPA2 Policy check box to enable WPA2, or check both check boxes to enable both WPA1 and WPA2.


Note The default value is disabled for both WPA1 and WPA2. If you leave both WPA1 and WPA2 disabled, the access points advertise in their beacons and probe responses information elements only for the authentication key management method you choose in Step 7.


Step 6 Check the AES check box to enable AES data encryption or the TKIP check box to enable TKIP data encryption for WPA1, WPA2, or both. The default values are TKIP for WPA1 and AES for WPA2.

Step 7 Choose one of the following key management methods from the Auth Key Mgmt drop-down box: 802.1X, CCKM, PSK, or 802.1X+CCKM.

Step 8 If you chose PSK in Step 7, choose ASCII or HEX from the PSK Format drop-down box and then enter a pre-shared key in the blank field. WPA pre-shared keys must contain 8 to 63 ASCII text characters or 64 hexadecimal characters.

Step 9 Click Apply to commit your changes.

Step 10 Click Save Configuration to save your changes.


Using the CLI to Configure WPA1+WPA2

Follow these steps to configure a WLAN for WPA1+WPA2 using the controller CLI.


Step 1 Enter this command to disable the WLAN:

config wlan disable wlan_id

Step 2 Enter this command to enable or disable WPA for the WLAN:

config wlan security wpa {enable | disable} wlan_id

Step 3 Enter this command to enable or disable WPA1 for the WLAN:

config wlan security wpa wpa1 {enable | disable} wlan_id

Step 4 Enter this command to enable or disable WPA2 for the WLAN:

config wlan security wpa wpa2 {enable | disable} wlan_id

Step 5 Enter these commands to enable or disable AES or TKIP data encryption for WPA1 or WPA2:

config wlan security wpa wpa1 ciphers {aes | tkip} {enable | disable} wlan_id

config wlan security wpa wpa2 ciphers {aes | tkip} {enable | disable} wlan_id

The default values are TKIP for WPA1 and AES for WPA2.

Step 6 Enter this command to enable or disable 802.1X, PSK, or CCKM authenticated key management:

config wlan security wpa akm {802.1X | psk | cckm} {enable | disable} wlan_id

The default value is 802.1X.

Step 7 If you enabled PSK in Step 6, enter this command to specify a pre-shared key:

config wlan security wpa akm psk set-key {ascii | hex} psk-key wlan_id

WPA pre-shared keys must contain 8 to 63 ASCII text characters or 64 hexadecimal characters.

Step 8 If you enabled WPA2 with 802.1X authenticated key management or WPA1 or WPA2 with CCKM authenticated key management, the PMK cache lifetime timer is used to trigger reauthentication with the client when necessary. The timer is based on the timeout value received from the AAA server or the WLAN session timeout setting. To see the amount of time remaining before the timer expires, enter this command:

show pmk-cache all

Information similar to the following appears:

PMK-CCKM Cache
                            Entry
Type        Station         Lifetime   VLAN Override        IP Override
------  ------------------- --------   ------------------   ---------------
CCKM    00:07:0e:b9:3a:1b   150 		 	 	 	 	 	 	 	 	 	 	 	 	 	 0.0.0.0 

If you enabled WPA2 with 802.1X authenticated key management, the controller supports opportunistic PMKID caching but not sticky (or non-opportunistic) PMKID caching. In sticky PMKID caching, the client stores multiple PMKIDs. This approach is not practical because it requires full authentication for each new access point and is not guaranteed to work in all conditions. In contrast, opportunistic PMKID caching stores only one PMKID per client and is not subject to the limitations of sticky PMK caching.

Step 9 Enter this command to enable the WLAN:

config wlan enable wlan_id

Step 10 Enter this command to save your settings:

save config


CKIP

Cisco Key Integrity Protocol (CKIP) is a Cisco-proprietary security protocol for encrypting 802.11 media. CKIP improves 802.11 security in infrastructure mode using key permutation, message integrity check (MIC), and message sequence number. Software release 4.0 or later supports CKIP with static key. For this feature to operate correctly, you must enable Aironet information elements (IEs) for the WLAN.

A lightweight access point advertises support for CKIP in beacon and probe response packets by adding an Aironet IE and setting one or both of the CKIP negotiation bits [key permutation and multi-modular hash message integrity check (MMH MIC)]. Key permutation is a data encryption technique that uses the basic encryption key and the current initialization vector (IV) to create a new key. MMH MIC prevents bit-flip attacks on encrypted packets by using a hash function to compute message integrity code.

The CKIP settings specified in a WLAN are mandatory for any client attempting to associate. If the WLAN is configured for both CKIP key permutation and MMH MIC, the client must support both. If the WLAN is configured for only one of these features, the client must support only this CKIP feature.

CKIP requires that 5-byte and 13-byte encryption keys be expanded to 16-byte keys. The algorithm to perform key expansion happens at the access point. The key is appended to itself repeatedly until the length reaches 16 bytes. All lightweight access points support CKIP.

You can configure CKIP through either the GUI or the CLI.

Using the GUI to Configure CKIP

Follow these steps to configure a WLAN for CKIP using the controller GUI.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the profile name of the desired WLAN to open the WLANs > Edit page.

Step 3 Click the Advanced tab.

Step 4 Check the Aironet IE check box to enable Aironet IEs for this WLAN and click Apply.

Step 5 Click the General tab.

Step 6 Uncheck the Status check box, if checked, to disable this WLAN and click Apply.

Step 7 Click the Security and Layer 2 tabs to open the WLANs > Edit (Security > Layer 2) page (see Figure 6-10).

Figure 6-10 WLANs > Edit (Security > Layer 2) Page

Step 8 Choose CKIP from the Layer 2 Security drop-down box.

Step 9 Under CKIP Parameters, choose the length of the CKIP encryption key from the Key Size drop-down box.

Range: Not Set, 40 bits, or 104 bits

Default: Not Set

Step 10 Choose the number to be assigned to this key from the Key Index drop-down box. You can configure up to four keys.

Step 11 Choose ASCII or HEX from the Key Format drop-down box and then enter an encryption key in the Encryption Key field. 40-bit keys must contain 5 ASCII text characters or 10 hexadecimal characters. 104-bit keys must contain 13 ASCII text characters or 26 hexadecimal characters.

Step 12 Check the MMH Mode check box to enable MMH MIC data protection for this WLAN. The default value is disabled (or unchecked).

Step 13 Check the Key Permutation check box to enable this form of CKIP data protection. The default value is disabled (or unchecked).

Step 14 Click Apply to commit your changes.

Step 15 Click the General tab.

Step 16 Check the Status check box to enable this WLAN.

Step 17 Click Apply to commit your changes.

Step 18 Click Save Configuration to save your changes.


Using the CLI to Configure CKIP

Follow these steps to configure a WLAN for CKIP using the controller CLI.


Step 1 Enter this command to disable the WLAN:

config wlan disable wlan_id

Step 2 Enter this command to enable Aironet IEs for this WLAN:

config wlan ccx aironet-ie enable wlan_id

Step 3 Enter this command to enable or disable CKIP for the WLAN:

config wlan security ckip {enable | disable} wlan_id

Step 4 Enter this command to specify a CKIP encryption key for the WLAN:

config wlan security ckip akm psk set-key wlan_id {40 | 104} {hex | ascii} key key_index

Step 5 Enter this command to enable or disable CKIP MMH MIC for the WLAN:

config wlan security ckip mmh-mic {enable | disable} wlan_id

Step 6 Enter this command to enable or disable CKIP key permutation for the WLAN:

config wlan security ckip kp {enable | disable} wlan_id

Step 7 Enter this command to enable the WLAN:

config wlan enable wlan_id

Step 8 Enter this command to save your settings:

save config


Configuring a Session Timeout

Using the controller GUI or CLI, you can configure a session timeout for wireless clients on a WLAN. The session timeout is the maximum time for a client session to remain active before requiring reauthorization.

Using the GUI to Configure a Session Timeout

Using the controller GUI, follow these steps to configure a session timeout for wireless clients on a WLAN.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the profile name of the WLAN for which you want to assign a session timeout.

Step 3 When the WLANs > Edit page appears, click the Advanced tab. The WLANs > Edit (Advanced) page appears.

Step 4 To configure a session timeout for this WLAN, check the Enable Session Timeout check box. Otherwise, uncheck the check box. The default value is checked.

Step 5 In the Session Timeout field, enter a value between 300 and 86400 seconds to specify the duration of the client session. The default value is 1800 seconds for the following Layer 2 security types: 802.1X; Static WEP+802.1X; and WPA+WPA2 with 802.1X, CCKM, or 802.1X+CCKM authentication key management and 0 seconds for all other Layer 2 security types. A value of 0 is equivalent to no timeout.

Step 6 Click Apply to commit your changes.

Step 7 Click Save Configuration to save your changes.


Using the CLI to Configure a Session Timeout

Using the controller CLI, follow these steps to configure a session timeout for wireless clients on a WLAN.


Step 1 To configure a session timeout for wireless clients on a WLAN, enter this command:

config wlan session-timeout wlan_id timeout

The default value is 1800 seconds for the following Layer 2 security types: 802.1X; Static WEP+802.1X; and WPA+WPA2 with 802.1X, CCKM, or 802.1X+CCKM authentication key management and 0 seconds for all other Layer 2 security types. A value of 0 is equivalent to no timeout.

Step 2 To save your changes, enter this command:

save config

Step 3 To see the current session timeout value for a WLAN, enter this command:

show wlan wlan_id

Information similar to the following appears:

WLAN Identifier.................................. 9
Profile Name..................................... test12
Network Name (SSID)........................... test12 
... 
Number of Active Clients......................... 0
Exclusionlist Timeout............................ 60 seconds
Session Timeout............................... 1800 seconds 
... 


Configuring Layer 3 Security

This section explains how to configure Layer 3 security settings for a WLAN on the controller.


Note Layer 2 Tunnel Protocol (L2TP) and IPSec are not supported on controllers running software release 4.0 or later.


VPN Passthrough

Using the GUI to Configure VPN Passthrough

Follow these steps to configure a WLAN for VPN passthrough using the controller GUI.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the profile name of the WLAN for which you want to configure VPN passthrough. The WLANs > Edit page appears.

Step 3 Click the Security and Layer 3 tabs to open the WLANs > Edit (Security > Layer 3) page (see Figure 6-11).

Figure 6-11 WLANs > Edit (Security > Layer 3) Page

Step 4 Choose VPN Pass-Through from the Layer 3 Security drop-down box.

Step 5 In the VPN Gateway Address field, enter the IP address of the gateway router that is terminating the VPN tunnels initiated by the client and passed through the controller.

Step 6 Click Apply to commit your changes.

Step 7 Click Save Configuration to save your settings.


Using the CLI to Configure VPN Passthrough

Enter these commands to configure a WLAN for VPN passthrough using the controller CLI:

config wlan security passthru {enable | disable} wlan_id gateway

For gateway, enter the IP address of the router that is terminating the VPN tunnel.

Enter show wlan to verify that the passthrough is enabled.

Web Authentication

WLANs can use web authentication if IPSec or VPN passthrough is not enabled on the controller. Web authentication is simple to set up and use and can be used with SSL to improve the overall security of the WLAN.


Note Web authentication is supported only with these Layer 2 security policies: open authentication, open authentication+WEP, and WPA-PSK. It is not supported for use with 802.1X.



Note The controller supports web authentication redirects only to HTTP (HTTP over TCP) servers. It does not support web authentication redirects to HTTPS (HTTP over SSL) servers.



Note Before enabling web authentication, make sure that all proxy servers are configured for ports other than port 53.



Note When you enable web authentication for a WLAN, a message appears indicating that the controller will forward DNS traffic to and from wireless clients prior to authentication. Cisco recommends that you have a firewall or intrusion detection system (IDS) behind your guest VLAN to regulate DNS traffic and to prevent and detect any DNS tunneling attacks.


Using the GUI to Configure Web Authentication

Follow these steps to configure a WLAN for web authentication using the controller GUI.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the profile name of the WLAN for which you want to configure web authentication. The WLANs > Edit page appears.

Step 3 Click the Security and Layer 3 tabs to open the WLANs > Edit (Security > Layer 3) page.

Step 4 Check the Web Policy check box.

Step 5 Make sure that the Authentication option is selected.

Step 6 Click Apply to commit your changes.

Step 7 Click Save Configuration to save your settings.


Using the CLI to Configure Web Authentication

Enter these commands to configure a WLAN for web authentication using the controller CLI:

config wlan security web {enable | disable} wlan_id

Enter show wlan to verify that web authentication is enabled.

Assigning a QoS Profile to a WLAN

Cisco UWN Solution WLANs support four levels of QoS: Platinum/Voice, Gold/Video, Silver/Best Effort (default), and Bronze/Background. You can configure the voice traffic WLAN to use Platinum QoS, assign the low-bandwidth WLAN to use Bronze QoS, and assign all other traffic between the remaining QoS levels.

The WLAN QoS level defines a specific 802.11e user priority (UP) for over-the-air traffic. This UP is used to derive the over-the-wire priorities for non-WMM traffic, and it also acts as the ceiling when managing WMM traffic with various levels of priorities. The access point uses this QoS-profile-specific UP in accordance with the values in Table 6-1 to derive the IP DSCP value that is visible on the wired LAN.

Table 6-1 Access Point QoS Translation Values 

AVVID Traffic Type
AVVID IP DSCP
QoS Profile
AVVID 802.1p
IEEE 802.11e UP

Network control

56 (CS7)

Platinum

7

7

Inter-network control (LWAPP control, 802.11 management)

48 (CS6)

Platinum

6

7

Voice

46 (EF)

Platinum

5

6

Interactive video

34 (AF41)

Gold

4

5

Streaming video

32 (CS4)

Gold

4

5

Mission critical

26 (AF31)

Gold

3

4

Call signaling

24 (CS3)

Gold

3

4

Transactional

18 (AF21)

Silver

2

3

Network management

16 (CS2)

Silver

2

3

Bulk data

10 (AF11)

Bronze

1

2

Best effort

0 (BE)

Silver

0

0

Scavenger

8 (CS1)

Bronze

0

1



Note The IEEE 802.11e UP value for DSCP values that are not mentioned in the table is calculated by considering 3 MSB bits of DSCP. For example, the IEEE 802.11e UP value for DSCP 32 (100 000 in binary), would be the decimal converted value of the MSB (100) which is 4. The 802.11e UP value of DSCP 32 is 4.


You can assign a QoS profile to a WLAN using the controller GUI or CLI.

Using the GUI to Assign a QoS Profile to a WLAN

Using the controller GUI, follow these steps to assign a QoS profile to a WLAN.


Step 1 If you have not already done so, configure one or more QoS profiles using the instructions in the "Using the GUI to Configure QoS Profiles" section.

Step 2 Click WLANs to open the WLANs page.

Step 3 Click the name of the WLAN to which you want to assign a QoS profile.

Step 4 When the WLANs > Edit page appears, click the QoS tab.

Step 5 From the Quality of Service (QoS) drop-down box, choose one of the following:

Platinum (voice)

Gold (video)

Silver (best effort)

Bronze (background)

Silver (best effort) is the default value.

Step 6 Click Apply to commit your changes.

Step 7 Click Save Configuration to save your changes.


Using the CLI to Assign a QoS Profile to a WLAN

Using the controller CLI, follow these steps to assign a QoS profile to a WLAN.


Step 1 If you have not already done so, configure one or more QoS profiles using the instructions in the "Using the CLI to Configure QoS Profiles" section.

Step 2 To assign a QoS profile to a WLAN, enter this command:

config wlan qos wlan_id {bronze | silver | gold | platinum}

Silver is the default value.

Step 3 To save your changes, enter this command:

save config

Step 4 To verify that you have properly assigned the QoS profile to the WLAN, enter this command:

show wlan wlan_id

Information similar to the following appears:

WLAN Identifier.................................. 1
Profile Name..................................... test
Network Name (SSID).............................. test
Status........................................... Enabled
MAC Filtering.................................... Disabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Disabled
Number of Active Clients......................... 0
Exclusionlist.................................... Disabled
Session Timeout.................................. 0
Interface........................................ management
WLAN ACL......................................... unconfigured
DHCP Server...................................... 1.100.163.24
DHCP Address Assignment Required................. Disabled
Quality of Service............................... Silver (best effort)
WMM.............................................. Disabled
... 


Configuring QoS Enhanced BSS

The QoS Enhanced Basis Service Set (QBSS) information element (IE) enables the access points to communicate their channel usage to wireless devices. Because access points with high channel usage might not be able to handle real-time traffic effectively, the 7921 or 7920 phone uses the QBSS value to determine if they should associate to another access point. You can enable QBSS in these two modes:

Wi-Fi Multimedia (WMM) mode, which supports devices that meet the 802.11E QBSS standard (such as Cisco 7921 IP Phones)

7920 support mode, which supports Cisco 7920 IP Phones on your 802.11b/g network

The 7920 support mode has two options:

Support for 7920 phones that require call admission control (CAC) to be configured on and advertised by the client device (these are typically older 7920 phones)

Support for 7920 phones that require CAC to be configured on and advertised by the access point (these are typically newer 7920 phones)

When access point-controlled CAC is enabled, the access point sends out a Cisco proprietary CAC Information Element (IE) and does not send out the standard QBSS IE.

You can use the controller GUI or CLI to configure QBSS. QBSS is disabled by default.

Guidelines for Configuring QBSS

Follow these guidelines when configuring QBSS on a WLAN:

7920 phones are non-WMM phones with limited CAC functionality. The phones look at the channel utilization of the access point to which they are associated and compare that to a threshold that is beaconed by the access point. If the channel utilization is less than the threshold, the 7920 places a call. In contrast, 7921 phones are full-fledged WMM phones that use traffic specifications (TSPECs) to gain access to the voice queue before placing a phone call. The 7921 phones work well with load-based CAC, which uses the percentage of the channel set aside for voice and tries to limit the calls accordingly.

Because 7921 phones support WMM and 7920 phones do not, capacity and voice quality problems can arise if you do not properly configure both phones when they are used in a mixed environment. To enable both 7921 and 7920 phones to co-exist on the same network, make sure that load-based CAC and 7920 AP CAC are both enabled on the controller and the WMM Policy is set to Allowed. This becomes particularly important if you have many more 7920 users than 7921 users.


Note Refer to Chapter 4, for more information and configuration instructions for load-based CAC.


Additional Guidelines for Using 7921 and 7920 Wireless IP Phones

Follow these guidelines to use Cisco 7921 and 7920 Wireless IP Phones with controllers:

Aggressive load balancing must be disabled for each controller. Otherwise, the initial roam attempt by the phone may fail, causing a disruption in the audio path.

The Dynamic Transmit Power Control (DTPC) information element (IE) must be enabled using the config 802.11b dtpc enable command. The DTPC IE is a beacon and probe information element that allows the access point to broadcast information on its transmit power. The 7921 or 7920 phone uses this information to automatically adjust its transmit power to the same level as the access point to which it is associated. In this manner, both devices are transmitting at the same level.

Both the 7921 and 7920 phones and the controllers support Cisco Centralized Key Management (CCKM) fast roaming.

When configuring WEP, there is a difference in nomenclature for the controller and the 7921 or 7920 phone. Configure the controller for 104 bits when using 128-bit WEP for the 7921 or 7920.

For standalone 7921 phones, load-based CAC must be enabled, and the WMM Policy must be set to Required on the WLAN.

When using a 7921 phone with the 802.11a radio of a 1242 series access point, set the 24-Mbps data rate to Supported and choose a lower Mandatory data rate (such as 12 Mbps). Otherwise, the phone might experience poor voice quality.

Using the GUI to Configure QBSS

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


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the name of the WLAN for which you want to configure WMM mode.

Step 3 When the WLANs > Edit page appears, click the QoS tab to open the WLANs > Edit (Qos) page (see Figure 6-12).

Figure 6-12 WLANs > Edit (QoS) Page

Step 4 From the WMM Policy drop-down box, choose one of the following options, depending on whether you want to enable WMM mode for 7921 phones and other devices that meet the WMM standard:

Disabled—Disables WMM on the WLAN. This is the default value.

Allowed—Allows client devices to use WMM on the WLAN.

Required—Requires client devices to use WMM. Devices that do not support WMM cannot join the WLAN.


Note In Layer 2 LWAPP mode when WMM is enabled on any WLAN, the access point sends its priority information on the 802.1q PRI field, with VLAN ID 0 based on the WMM clients' QoS control fields. In Layer 3 LWAPP mode, this information is carried in the DSCP of the LWAPP packet's IP header. Some non-Cisco access switches to which the access point is connected might handle VLAN tag ID 0 inappropriately. For example, the switch might drop packets that are tagged with VLAN ID 0, causing the access point with WMM enabled to be unable to join the controller in Layer 2 LWAPP mode and to reboot repeatedly. Therefore, when the controller is in Layer 2 mode and WMM is enabled, you must put the access points on the trunk port of the switch to enable them to join the controller. If the access point is unable to join the controller after connecting to the trunk port of the switch, you must use the controller in Layer 3 LWAPP mode in order to use WMM.


Step 5 Check the 7920 AP CAC check box if you want to enable 7920 support mode for phones that require access point-controlled CAC. The default value is unchecked.

Step 6 Check the 7920 Client CAC check box if you want to enable 7920 support mode for phones that require client-controlled CAC. The default value is unchecked.


Note You cannot enable both WMM mode and client-controlled CAC mode on the same WLAN.


Step 7 Click Apply to commit your changes.

Step 8 Click Save Configuration to save your changes.


Using the CLI to Configure QBSS

Using the controller CLI, follow these steps to configure QBSS.


Step 1 To determine the ID number of the WLAN to which you want to add QBSS support, enter this command:

show wlan summary

Step 2 To disable the WLAN, enter this command:

config wlan disable wlan_id

Step 3 To configure WMM mode for 7921 phones and other devices that meet the WMM standard, enter this command:

config wlan wmm {disabled | allowed | required} wlan_id

where

The disabled parameter disables WMM mode on the WLAN.

The allowed parameter allows client devices to use WMM on the WLAN.

The required parameter requires client devices to use WMM. Devices that do not support WMM cannot join the WLAN.


Note In Layer 2 LWAPP mode when WMM is enabled on any WLAN, the access point sends its priority information on the 802.1q PRI field, with VLAN ID 0 based on the WMM clients' QoS control fields. In Layer 3 LWAPP mode, this information is carried in the DSCP of the LWAPP packet's IP header. Some non-Cisco access switches to which the access point is connected might handle VLAN tag ID 0 inappropriately. For example, the switch might drop packets that are tagged with VLAN ID 0, causing the access point with WMM enabled to be unable to join the controller in Layer 2 LWAPP mode and to reboot repeatedly. Therefore, when the controller is in Layer 2 mode and WMM is enabled, you must put the access points on the trunk port of the switch to enable them to join the controller. If the access point is unable to join the controller after connecting to the trunk port of the switch, you must use the controller in Layer 3 LWAPP mode in order to use WMM.


Step 4 To enable or disable 7920 support mode for phones that require client-controlled CAC, enter this command:

config wlan 7920-support client-cac-limit {enable | disable} wlan_id


Note You cannot enable both WMM mode and client-controlled CAC mode on the same WLAN.


Step 5 To enable or disable 7920 support mode for phones that require access point-controlled CAC, enter this command:

config wlan 7920-support ap-cac-limit {enable | disable} wlan_id

Step 6 To re-enable the WLAN, enter this command:

config wlan enable wlan_id

Step 7 To save your changes, enter this command:

save config

Step 8 To verify that the WLAN is enabled and the Dot11-Phone Mode (7920) field is configured for compat mode, enter this command:

show wlan wlan_id


Configuring IPv6 Bridging

Internet Protocol version 6 (IPv6) is the next-generation network layer Internet protocol intended to replace version 4 (IPv4) in the TCP/IP suite of protocols. This new version increases Internet global address space to accommodate users and applications that require unique global IP addresses. IPv6 incorporates 128-bit source and destination addresses, providing significantly more addresses than the 32-bit IPv4 addresses. Follow the instructions in this section to configure a WLAN for IPv6 bridging using either the controller GUI or CLI.

Guidelines for Using IPv6 Bridging

Follow these guidelines when using IPv6 bridging:

IPv6 bridging is supported only on the following controllers: 4400 series controllers, the Cisco WiSM, and the Catalyst 3750G Integrated Wireless LAN Controller Switch.

To enable IPv6 bridging, Layer 3 security must be set to None.

Hybrid-REAP with central switching is supported for use with IPv6 bridging. Hybrid-REAP with local switching is not supported.

Auto-anchor mobility is not supported for use with IPv6 bridging.

If symmetric mobility tunneling is enabled, all IPv4 traffic is bidirectionally tunneled to and from the client, but the IPv6 client traffic is bridged locally.

In controller software release 4.2 or later, you can enable IPv6 bridging and IPv4 web authentication on the same WLAN, a combination that previously was not supported. The controller bridges IPv6 traffic from all clients on the WLAN while IPv4 traffic goes through the normal web authentication process. The controller begins bridging IPv6 as soon as the client associates and even before web authentication for IPv4 clients is complete. No other Layer 2 or Layer 3 security policy configuration is supported on the WLAN when IPv6 bridging and web authentication are enabled. Figure 6-13 illustrates how IPv6 bridging and IPv4 web authentication can be used on the same WLAN.

Figure 6-13 IPv6 Bridging and IPv4 Web Authentication


Note The Security Policy Completed field in both the controller GUI and CLI shows "No for IPv4 (bridging allowed for IPv6)" until web authentication is completed. You can view this field from the Clients > Detail page on the GUI or from the show client detail CLI command.


Using the GUI to Configure IPv6 Bridging

Follow these steps to configure a WLAN for IPv6 bridging using the GUI.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the profile name of the desired WLAN to open the WLANs > Edit page.

Step 3 Click the Advanced tab to open the WLANs > Edit (Advanced tab) page (see Figure 6-14).

Figure 6-14 WLANs > Edit (Advanced) Page

Step 4 Check the IPv6 Enable check box if you want to enable clients that connect to this WLAN to accept IPv6 packets. Otherwise, leave the check box unchecked, which is the default value.

Step 5 Click Apply to commit your changes.

Step 6 Click Save Configuration to save your changes.


Using the CLI to Configure IPv6 Bridging

To configure a WLAN for IPv6 bridging using the CLI, enter this command:

config wlan IPv6support {enable | disable} wlan_id

The default value is disabled.

Configuring Cisco Client Extensions

Cisco Client Extensions (CCX) software is licensed to manufacturers and vendors of third-party client devices. The CCX code resident on these clients enables them to communicate wirelessly with Cisco access points and to support Cisco features that other client devices do not, including those related to increased security, enhanced performance, fast roaming, and superior power management.

The 4.2 or later release of controller software supports CCX versions 1 through 5, which enables controllers and their access points to communicate wirelessly with third-party client devices that support CCX. CCX support is enabled automatically for every WLAN on the controller and cannot be disabled. However, you can configure a specific CCX feature per WLAN. This feature is Aironet information elements (IEs).

If Aironet IE support is enabled, the access point sends an Aironet IE 0x85 (which contains the access point name, load, number of associated clients, and so on) in the beacon and probe responses of this WLAN, and the controller sends Aironet IEs 0x85 and 0x95 (which contains the management IP address of the controller and the IP address of the access point) in the reassociation response if it receives Aironet IE 0x85 in the reassociation request.

Follow the instructions in this section to configure a WLAN for the CCX Aironet IE feature and to see the CCX version supported by specific client devices using either the GUI or the CLI.


Note CCX is not supported on the AP1030.


Using the GUI to Configure CCX Aironet IEs

Follow these steps to configure a WLAN for CCX Aironet IEs using the GUI.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the profile name of the desired WLAN to open the WLANs > Edit page.

Step 3 Click the Advanced tab to open the WLANs > Edit (Advanced tab) page (see Figure 6-14).

Step 4 Check the Aironet IE check box if you want to enable support for Aironet IEs for this WLAN. Otherwise, uncheck this check box. The default value is enabled (or checked).

Step 5 Click Apply to commit your changes.

Step 6 Click Save Configuration to save your changes.


Using the GUI to View a Client's CCX Version

A client device sends its CCX version in association request packets to the access point. The controller then stores the client's CCX version in its database and uses it to limit the features for this client. For example, if a client supports CCX version 2, the controller does not allow the client to use CCX version 4 features. Follow these steps to see the CCX version supported by a particular client device using the GUI.


Step 1 Click Monitor > Clients to open the Clients page.

Step 2 Click the MAC address of the desired client device to open the Clients > Detail page (see Figure 6-15).

Figure 6-15 Clients > Detail Page

The CCX Version field shows the CCX version supported by this client device. Not Supported appears if the client does not support CCX.

Step 3 Click Back to return to the previous screen.

Step 4 Repeat this procedure to view the CCX version supported by any other client devices.


Using the CLI to Configure CCX Aironet IEs

To enable or disable support for Aironet IEs for a particular WLAN, enter this command:

config wlan ccx aironet-ie {enable | disable} wlan_id

The default value is enabled.

Using the CLI to View a Client's CCX Version

To see the CCX version supported by a particular client device, enter this command:

show client detail client_mac

Configuring WLAN Override

By default, access points transmit all defined WLANs on the controller. However, you can use the WLAN override option to select which WLANs are transmitted and which are not on a per access point basis. For example, you can use WLAN override to control where in the network the guest WLAN is transmitted, or you can use it to disable a specific WLAN in a certain area of the network.

Using the GUI to Configure WLAN Override

Follow these steps to configure the WLAN override option for a specific access point.


Step 1 Click 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.

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

Figure 6-16 802.11a/n Cisco APs > Configure Page

Step 3 Choose Enable from the WLAN Override drop-down box to enable the WLAN override feature for this access point or choose Disable to disable this feature.

Step 4 If you enabled the WLAN override feature in Step 3, check the check boxes for the WLANs that you want this access point to broadcast.

Step 5 Click Apply to commit your changes.

Step 6 Click Save Configuration to save your changes.


Using the CLI to Configure WLAN Override

Use these commands to configure the WLAN override feature for a specific access point using the controller CLI.

1. To enable or disable the WLAN override feature for a specific access point, enter this command:

config ap wlan {enable | disable} {802.11a | 802.11b} Cisco_AP

2. To define which WLANs you want to transmit, enter this command:

config ap wlan add {802.11a | 802.11b} wlan_id Cisco_AP

Configuring Access Point Groups

In a typical deployment, all users on a WLAN are mapped to a single interface on the controller. Therefore, all users associated with that WLAN are on the same subnet or VLAN. However, you can override this default WLAN setting to distribute the load among several interfaces or to group users based on specific criteria such as individual departments (for example, marketing) by creating access point groups (formerly known as site-specific VLANs). Additionally, these access point groups can be configured in separate VLANs to simplify network administration, as illustrated in the example in Figure 6-17.


Note The required access control list (ACL) must be defined on the router that serves the VLAN or subnet.



Note Multicast traffic is supported with access point group VLANs. However, if the client roams from one access point to another, the client might stop receiving multicast traffic, unless IGMP snooping is enabled.


Figure 6-17 Access Point Groups

In Figure 6-17, three configured dynamic interfaces are mapped to three different VLANs (VLAN 61, VLAN 62, and VLAN 63). Three access point groups are defined, and each is a member of a different VLAN, but all are members of the same SSID. A client within the wireless SSID is assigned an IP address from the VLAN subnet on which its access point is a member. For example, any user that associates with an access point that is a member of access point group VLAN 61 is assigned an IP address from that subnet.

In the example in Figure 6-17, the controller internally treats roaming between access points as a Layer 3 roaming event. In this way, WLAN clients maintain their original IP addresses.

To configure access point groups, follow these top-level steps:

1. Configure the appropriate dynamic interfaces and map them to the desired VLANs.

For example, to implement the network in Figure 6-17, create dynamic interfaces for VLANs 61, 62, and 63 on the controller. Refer to Chapter 3, for more information about how to configure dynamic interfaces.

2. Create the access point groups. Refer to the "Creating Access Point Groups" section.

3. Assign access points to the appropriate access point group. Refer to the "Assigning Access Points to Access Point Groups" section.

Creating Access Point Groups

Once all access points have joined the controller, you can create access point groups and assign each group to one or more WLANs. You also need to define WLAN-to-interface mapping.


Note You can create up to 150 access point groups on the controller.


Using the GUI to Create Access Point Groups

Follow these steps to create an access point group using the controller GUI.


Step 1 Click WLANs > Advanced > AP Groups VLAN to open the AP Groups VLAN page (see Figure 6-18).

Figure 6-18 AP Groups VLAN Page

Step 2 Check the AP Groups VLAN Feature Enable check box to enable this feature. The default value is unchecked.

Step 3 Enter the group's name in the AP Group Name field.

Step 4 Enter the group's description in the AP Group Description field.

Step 5 Click Create New AP-Group to create the group. The newly created access point group appears in the middle of the page.


Note If you ever want to delete this group, hover your cursor over the blue drop-down arrow for the group and choose Remove.


Step 6 To edit this new group, click the name of the group. The AP Groups VLAN page reappears with different fields (see Figure 6-19).

Figure 6-19 AP Groups VLAN Page

Step 7 To map the access point group to a WLAN, choose its ID from the WLAN SSID drop-down box.

Step 8 To map the access point group to an interface, choose the desired interface from the Interface Name drop-down box.

Step 9 Click Add Interface-Mapping to add WLAN-to-interface mappings to the group. The newly created interface mapping appears in the middle of the page.


Note If you ever want to delete this mapping, hover your cursor over the blue drop-down arrow for the mapping and choose Remove.


Step 10 Repeat Step 7 through Step 9 to add any additional interface mappings.

Step 11 Click Apply to commit your changes.

Step 12 Repeat Step 3 through Step 11 to add any additional access point groups.

Step 13 Click Save Configuration to save your changes.


Using the CLI to Create Access Point Groups

To create an access point group using the CLI, enter this command:

config ap group-name group_name

Assigning Access Points to Access Point Groups

After you have created your access point groups, use the controller GUI or CLI to assign access points to these groups.

Using the GUI to Assign Access Points to Access Point Groups

Follow these steps to assign an access point to an access point group using the GUI.


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

Step 2 Click the name of the access point that you want to assign to a group. The All APs > Details page appears.

Step 3 Click the Advanced tab to open the All APs > Details (Advanced) page (see Figure 6-20).

Figure 6-20 All APs > Details (Advanced) Page

Step 4 Choose the desired access point group from the AP Group Name drop-down box.

Step 5 Click Apply to commit your changes.

Step 6 Click Save Configuration to save your changes.


Using the CLI to Assign Access Points to Access Point Groups

To assign an access point to an access point group using the CLI, enter this command:

config ap group-name group_name ap_name

Configuring Web Redirect with 802.1X Authentication

You can configure a WLAN to redirect a user to a particular web page after 802.1X authentication has completed successfully. You can configure the web redirect to give the user partial or full access to the network.

Conditional Web Redirect

If you enable conditional web redirect, the user can be conditionally redirected to a particular web page after 802.1X authentication has completed successfully. You can specify the redirect page and the conditions under which the redirect occurs on your RADIUS server. Conditions might include the user's password reaching expiration or the user needing to pay his or her bill for continued usage.

If the RADIUS server returns the Cisco AV-pair "url-redirect," then the user is redirected to the specified URL upon opening a browser. If the server also returns the Cisco AV-pair "url-redirect-acl," the specified access control list (ACL) is installed as a preauthentication ACL for this client. The client is not considered fully authorized at this point and can only pass traffic allowed by the preauthentication ACL.

After the client completes a particular operation at the specified URL (for example, changing a password or paying a bill), the client must reauthenticate. When the RADIUS server does not return a "url-redirect," the client is considered fully authorized and allowed to pass traffic.


Note The conditional web redirect feature is available only for WLANs that are configured for 802.1X or WPA+WPA2 Layer 2 security.


After you configure the RADIUS server, you can then configure the conditional web redirect on the controller using either the controller GUI or CLI.

Splash Page Web Redirect

If you enable splash page web redirect, the user is redirected to a particular web page after 802.1X authentication has completed successfully. After the redirect, the user has full access to the network. You can specify the redirect page on your RADIUS server. If the RADIUS server returns the Cisco AV-pair "url-redirect," then the user is redirected to the specified URL upon opening a browser. The client is considered fully authorized at this point and is allowed to pass traffic, even if the RADIUS server does not return a "url-redirect."


Note The splash page web redirect feature is available only for WLANs that are configured for 802.1X or WPA+WPA2 Layer 2 security.


After you configure the RADIUS server, you can then configure the splash page web redirect on the controller using either the controller GUI or CLI.

Configuring the RADIUS Server

Follow these steps to configure your RADIUS server.


Note These instructions are specific to the CiscoSecure ACS; however, they should be similar to those for other RADIUS servers.



Step 1 From the CiscoSecure ACS main menu, click Group Setup.

Step 2 Click Edit Settings.

Step 3 From the Jump To drop-down menu, choose RADIUS (Cisco IOS/PIX 6.0). The window shown in Figure 6-21 appears.

Figure 6-21 ACS Server Configuration

Step 4 Check the [009\001] cisco-av-pair check box.

Step 5 Enter the following Cisco AV-pairs in the [009\001] cisco-av-pair edit box to specify the URL to which the user is redirected and, if configuring conditional web redirect, the conditions under which the redirect takes place, respectively:

url-redirect=http://url

url-redirect-acl=acl_name


Using the GUI to Configure Web Redirect

Using the controller GUI, follow these steps to configure conditional or splash page web redirect.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the profile name of the desired WLAN. The WLANs > Edit page appears.

Step 3 Click the Security and Layer 2 tabs to open the WLANs > Edit (Security > Layer 2) page.

Step 4 Choose 802.1X or WPA+WPA2 from the Layer 2 Security drop-down box.

Step 5 Set any additional parameters for 802.1X or WPA+WPA2.

Step 6 Click the Layer 3 tab to open the WLANs > Edit (Security > Layer 3) page (see Figure 6-22).

Figure 6-22 WLANs > Edit (Security > Layer 3) Page

Step 7 Choose None from the Layer 3 Security drop-down box

Step 8 Check the Web Policy check box.

Step 9 Choose one of the following options to enable conditional or splash page web redirect: Conditional Web Redirect or Splash Page Web Redirect. The default value is disabled for both parameters.

Step 10 If the user is to be redirected to a site external to the controller, choose the ACL that was configured on your RADIUS server from the Preauthentication ACL drop-down list.

Step 11 Click Apply to commit your changes.

Step 12 Click Save Configuration to save your changes.


Using the CLI to Configure Web Redirect

Using the controller CLI, follow these steps to configure conditional or splash page web redirect.


Step 1 To enable or disable conditional web redirect, enter this command:

config wlan security cond-web-redir {enable | disable} wlan_id

Step 2 To enable or disable splash page web redirect, enter this command:

config wlan security splash-page-web-redir {enable | disable} wlan_id

Step 3 To save your settings, enter this command:

save config

Step 4 To see the status of the web redirect features for a particular WLAN, enter this command:

show wlan wlan_id

Information similar to the following appears:

WLAN Identifier.................................. 1
Profile Name..................................... test
Network Name (SSID).............................. test
...
Web Based Authentication......................... Disabled
Web-Passthrough.................................. Disabled
Conditional Web Redirect......................... Disabled
Splash-Page Web Redirect......................... Enabled
... 


Disabling Accounting Servers per WLAN

This section provides instructions for disabling all accounting servers on a WLAN. Disabling accounting servers disables all accounting operations and prevents the controller from falling back to the default RADIUS server for the WLAN.

Follow these steps to disable all accounting servers for a RADIUS authentication server.


Step 1 Click WLANs to open the WLANs page.

Step 2 Click the profile name of the WLAN to be modified. The WLANs > Edit page appears.

Step 3 Click the Security and AAA Servers tabs to open the WLANs > Edit (Security > AAA Servers) page (see Figure 6-23).

Figure 6-23 WLANs > Edit (Security > AAA Servers) Page

Step 4 Uncheck the Enabled check box for the Accounting Servers.

Step 5 Click Apply to commit your changes.

Step 6 Click Save Configuration to save your changes.