 Feedback
|
Table Of Contents
Cisco Wireless LAN Controller Module Feature Guide
Prerequisites for the Cisco WLAN Controller Module
Information About the Cisco WLAN Controller Module
Software Features and Benefits
How to Configure the Cisco WLAN Controller Module
Overview of the Configuration Process
Accessing the CLI Through a Console Connection or Through Telnet
Understanding Interfaces on the Cisco WLAN Controller Module
Using Interface Configuration Mode
Configuring the Cisco WLAN Controller Module in the Router
Running the Configuration Wizard
Configuring and Verifying Management and AP Manager Interfaces
Configuring WLANs on the Cisco WLAN Controller Module
Upgrading the Cisco WLAN Controller Module Software
Erasing and Resetting the WLAN Controller Module Configuration
service-module wlan-controller
Open Source License Acknowledgements
Cisco Wireless LAN Controller Module Feature Guide
The Cisco wireless LAN (WLAN) controller module (WLCM) is designed to provide small and medium-sized businesses (SMBs) and enterprise branch office customers 802.11 wireless networking solutions for Cisco 2800 and Cisco 3800 series integrated services routers (ISRs) and Cisco 3700 series routers. The Cisco WLAN controller module enables Cisco ISRs and Cisco 3700 series routers to manage up to six WLAN access points (AP) and simplifies deploying and managing wireless LANs. The operating system manages all data client, communications, and system administration functions, performs Radio Resource Management (RRM) functions, manages system-wide mobility policies using the operating system security (OSS), and coordinates all security functions using the OSS framework. The Cisco WLAN controller module works in conjunction with Cisco Aironet lightweight access points, Cisco Wireless Control System (WCS), and the Cisco Wireless Location Appliance to support mission-critical wireless data, voice, and video applications.
Note
The Cisco 2801 integrated services router does not support the Cisco WLAN controller module.
Feature History for the Cisco WLAN Controller Module
3.2.78.0 (controller software)
This feature was introduced.
12.4T (router software)
This feature was introduced.
For more information about the Cisco WLAN solution, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
Contents
•
•
•
Prerequisites for the Cisco WLAN Controller Module
The Cisco WLAN controller module operating system on the Cisco WLAN controller module must be compatible with the Cisco IOS software release and feature set on the router. See the "Feature History for the Cisco WLAN Controller Module" section.
Use the following commands to view the IOS version on the router, and the OS version on the WLAN controller module.
•
•
Information About the Cisco WLAN Controller Module
This section describes the features of and some important concepts about the Cisco WLAN controller module:
•
Note
Hardware Overview
The Cisco WLAN controller module is supported on the following router platforms:
•
For information about Cisco 3700 series routers wireless support, see the following URL:
http://www.cisco.com/en/US/products/hw/routers/ps282/tsd_products_support_series_home.html
•
For information about Cisco 2800 integrated services routers wireless support, see the following URL:
http://www.cisco.com/en/US/products/ps5854/tsd_products_support_series_home.html
•
For information about Cisco 3800 integrated services routers wireless support, see the following URL:
http://www.cisco.com/en/US/products/ps5855/tsd_products_support_series_home.html
Cisco WLAN controller modules ship with and boot from an installed 256-MB CompactFlash memory card. The CompactFlash memory card contains the boot loader, Linux kernel, Cisco WLAN controller module and access points executable file, and Cisco WLAN controller module configuration.
Note
Figure 1 shows the faceplate of the Cisco WLAN controller module.
Note
Figure 1 Cisco Wireless LAN Controller Module Faceplate
Note
Note
Figure 2 shows how the Cisco WLAN controller module can be simultaneously deployed across multiple floors and buildings in a wired branch office with secure data, voice, switching, and wireless.
Figure 2 Cisco WLAN Controller Module Deployment for Converged Wireless with Secure Data, Voice, Switching, and Wireless
The Cisco Wireless Control System (WCS) allows users to design, control, and monitor enterprise wireless networks from a centralized location. The Cisco WCS is an optional network component that works in conjunction with Cisco APs and Cisco WLAN controllers.
The Cisco 2700 series location appliance is also an optional network component that enhances the high-accuracy built-in Cisco WCS location-tracking abilities by computing, collecting, and storing historical location data. This data can be displayed in the Cisco WCS. In this role, the location appliance acts as a server to one or more Cisco WCS servers, collecting, storing, and passing on data from its associated controllers. For complete information about managing the Cisco WLAN location appliance, see the following URL:
http://www.cisco.com/en/US/products/ps6386/tsd_products_support_series_home.html
Power over Ethernet
Power over Ethernet (PoE) is supported on Cisco ISR routers. When using PoE, the installer runs a single CAT-5 cable from each access point to PoE-equipped network elements, such as a PoE compliant Cisco EtherSwitch service module on the integrated services router or a Cisco Catalyst 3750 switch with PoE. When the PoE equipment determines that the access point is PoE-enabled, it sends -48 VDC over the unused pairs in the Ethernet cable to power the access point.
Connecting Access Points
Access points can be connected to a separate switch or to a Cisco EtherSwitch service module on the ISR. The ISR family supports a range of integrated Cisco EtherSwitch service modules from 4 to 48 ports supporting PoE.
Note
Software Features and Benefits
The Cisco WLAN controller module and its associated Cisco access points can be concurrently managed by these operating system user interfaces:
•
For more information about the CLI and a complete list of features available on the Cisco WLAN controller module, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
•
Note
Because the web user interface works with one Cisco wireless LAN controller at a time, the web user interface is especially useful when you wish to configure or monitor a single Cisco wireless LAN controller and its associated access points that support Lightweight Access Point Protocol (LWAPP). The web GUI is supported on Internet Explorer, version 6.0/SP1 or later.
For complete information about the GUI, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
•
The Cisco WCS includes the same configuration, performance monitoring, security, fault management, and accounting options used at the Cisco wireless LAN controller level, but adds a graphical view of multiple controllers and managed access points.
For complete information about the Cisco WCS, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
The Cisco WLAN controller module, together with the ISRs, supports IPSec security for wireless clients terminating on the ISR through the use of a VPN passthroughs on the Cisco WLAN controller module.
How to Configure the Cisco WLAN Controller Module
This section contains the following procedures:
•
•
•
•
•
•
•
•
•
•
Note
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
Before installing, configuring, or upgrading a Cisco WLAN controller module, see the Cisco Wireless LAN Solution Product Guide.
Note
Caution
Overview of the Configuration Process
Table 1 shows the configuration process for the Cisco WLAN controller module.
Table 1 Configuration Process of the Cisco WLAN Controller Module
Step 1
Configure an WLAN interface on the router.
"Configuring the Cisco WLAN Controller Module in the Router" section
Step 2
Open a session to the Cisco WLAN controller module.
"Configuring the Cisco WLAN Controller Module in the Router" section
Step 3
Run the configuration wizard on the Cisco WLAN controller module.
Step 4
Configure management and AP-manager interfaces on the Cisco WLAN controller module.
"Configuring and Verifying Management and AP Manager Interfaces" section
Step 5
Verify your connection from the router to the management and AP-manager interfaces.
"Configuring and Verifying Management and AP Manager Interfaces" section
Step 6
Configure WLANs on the Cisco WLAN controller module.
"Configuring WLANs on the Cisco WLAN Controller Module" section
Accessing the CLI Through a Console Connection or Through Telnet
Before you can access the Cisco WLAN controller module CLI, you must first use one of these methods to establish a connection from the host router:
•
Note
Note
•
The Cisco WLAN controller module supports one secure SSH session and up to 16 simultaneous Telnet sessions. Changes made by one Telnet user are reflected in all other Telnet sessions.
If your Cisco WLAN controller module is already configured, you can directly open a session to the WLAN controller and configure it through its CLI.
Understanding Interfaces on the Cisco WLAN Controller Module
Communication between the host router and the Cisco WLAN controller module is through the wlan-controller interface connection between the router and the Cisco WLAN controller module.
The Cisco WLAN controller module supports the wlan-controller interface configuration command. The interface numbering format on the Cisco WLAN controller module is slot/port.
For more detailed information about interface types on the controller module, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
Using Interface Configuration Mode
Note
The Fast Ethernet internal interface on the Cisco WLAN controller module connects internally to the wlan-controller interface 1/0 on the router (if the WLAN controller module is inserted in slot 1 of the router).
The port numbering scheme that you use in interface configuration mode is interface type/slot number/port number.
•
•
•
Configuring the Cisco WLAN Controller Module in the Router
This section describes how to perform the initial configuration of the router with a Cisco WLAN controller module installed. This section also describes the initial configuration of the Cisco WLAN controller module itself.
For advanced information about configuring the Cisco WLAN controller, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
Prerequisites
Before installing, configuring, or upgrading the Cisco WLAN controller module, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
Note
http://www.cisco.com/en/US/products/ps6308/prod_command_reference_list.html
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Step 1
enable
Example:Router# enable
Enters privileged EXEC mode.
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
interface wlan-controller slot/port
Example:Router(config)# interface wlan-controller 1/0
Enters interface configuration mode, and specifies an interface for configuration.
Step 4
ip address ip address/subnet mask
Example:Router(config-if)# ip address 192.0.2.254 255.255.255.0
Configures an IP address and subnet mask on this controller interface.
Step 5
no shutdown
Example:Router(config-if)# no shutdown
Enables the module port.
Step 6
end
Example:Router(config-if)# end
Returns you to privileged EXEC mode.
Step 7
service-module wlan-controller slot/port session
Example:Router# service-module wlan-controller 1/0 session
Opens a session to the WLAN controller module.
If the Cisco WLAN controller module has no prior configuration, the configuration wizard automatically starts. You cannot bypass the configuration wizard. Through the CLI, you must provide the information at the prompts provided. For information about the configuration wizard, see the Running the Configuration Wizard next.
Running the Configuration Wizard
When the controller boots at factory defaults, the bootup script runs the configuration wizard, which prompts the installer for initial configuration settings. Follow these steps to enter settings using the wizard on the CLI:
Step 1
Welcome to the Cisco Wizard Configuration ToolUse the '-' character to backupWLAN Controller:# anynameStep 2
Enter Administrative User Name (24 characters max): anynameEnter Administrative Password (24 characters max): *****Step 3
Management Interface IP Address: 192.0.2.24Management Interface Netmask: 255.255.255.0Management Interface Default Router: 192.0.2.254Management Interface VLAN Identifier (0 = untagged): 0Management Interface Port Num [1]: 1Step 4
Management Interface DHCP Server IP Address: 192.0.2.24Step 5
AP Manager Interface IP Address: 192.0.2.25AP-Manager is on Management subnet, using same valuesAP Manager Interface DHCP Server (192.0.2.24): 192.0.2.24Step 6
Virtual Gateway IP Address: 1.1.1.1Step 7
Mobility/RF Group Name: anyname-mgStep 8
Network Name (SSID): wlan-15Step 9
Allow Static IP Addresses [YES][no]: noStep 10
Configure a RADIUS Server now? [YES][no]: noWarning! The default WLAN security policy requires a RADIUS server.Please see documentation for more details.Enter a country code for the unit. To list the supported country codes, enter help or see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
Enter Country Code (enter 'help' for a list of countries) [US]: USStep 11
Enable 802.11b Network [YES][no]: yesEnable 802.11a Network [YES][no]: yesEnable 802.11g Network [YES][no]: yesEnable or disable Radio Resource Management (RRM) (auto RF). For a complete description of RRM, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
Enable Auto-RF [YES][no]:Configure a NTP server now? [YES][no]: yesEnter the NTP server's IP address: 192.0.2.24Enter a polling interval between 3600 and 604800 secs: 3600Configuration correct? If yes, system will save it and reset. [yes][NO]: yesWhen you answer the last prompt, the controller saves the configuration, reboots with your changes, and prompts you to log in or to enter recover-config to reset to the factory default configuration and return to the wizard.
Configuration saved!Resetting system with new configuration...When the configuration wizard has completed initial configuration, the Cisco WLAN controller module automatically reboots with the new configuration and stops at the following:
User:Step 12
Configure a NTP server now? [YES][no]: yesStep 13
Enter the NTP server's IP address: 192.0.2.254Step 14
Enter a polling interval between 3600 and 604800 secs: 7200Step 15
User: anynamePassword: *****(WLAN Controller)
Note
For more detailed information about initial configuration of the Cisco WLAN controller module, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
Configuring and Verifying Management and AP Manager Interfaces
You can create any number of static or dynamic logical interfaces on the Cisco WLAN controller module, configured as VLAN tagged interfaces or untagged interfaces. By default, two static, untagged interfaces are assigned (management interface and ap-manager interface) and used for management and communication with APs. Since these interfaces are untagged, they must be assigned on the same subnet used to configure the WLAN controller interface on the router.
The management interface must have an IP address that can be reached from the workstation managing the interface. The AP manager interface allows the WLAN controller to communicate with APs.
WLAN Controller> config interface address management 192.0.2.24 255.255.255.0 192.0.2.254WLAN Controller> config interface address ap-manager 192.0.2.25 255.255.255.0 192.0.2.254The last IP address (192.0.2.254) is the default-gateway IP address for those interfaces and the IP address of the WLAN controller module interface on the router.
Send a ping from the router to the WLAN controller module management interface and AP manager interface.
Router:# ping 192.0.2.24Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 192.0.2.24, timeout is 2 seconds:Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 msRouter:# ping 192.0.2.25Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 192.0.2.25, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 msRouter#For information about configuring VLANs on the Cisco WLAN controller module, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
Configuring WLANs on the Cisco WLAN Controller Module
The Cisco WLAN controller module can control up to 16 wireless LANs for access points. Each wireless LAN has a separate wireless LAN ID (1 through 16) and a separate wireless LAN SSID (wireless LAN name), and can be assigned unique security policies.
Note
Native VLAN is not supported on the Cisco WLAN controller module; therefore, the router should not have any functional native VLANs configured.
For additional information about configuring VLANs on the Cisco WLAN controller module, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
For complete information about configuring wireless LANs on the Cisco WLAN controller module, see the Cisco Wireless LAN Solution Product Guide at the following URL:
http://www.cisco.com/en/US/products/ps6308/products_installation_and_configuration_guides_list.html
To configure WLANs, activate them, assign the WLANs to a DHCP server, and assign WLANs to VLANs, follow the steps below.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
DETAILED STEPS
Step 1
interface type slot/port
Example:Router(config-if)# interface gigabitethernet 0/0
Configures an interface type and enters interface configuration mode.
Step 2
description string
Example:Router(config-if)# description: connected to AP
Specifies a description of the digital signal processor (DSP) interface.
Step 3
ip address ip-address mask
Example:Router(config-if)# ip address 100.100.100.1 255.255.255.0
Sets a primary or secondary IP address for an interface.
Step 4
load-interval seconds
Example:Router(config-if)# load-interval 30
Specifies the length of time to be used to calculate the average load for an interface.
Step 5
duplex speed
Example:Router(config-if)# duplex auto
Detects the transmission type of the device.
Step 6
speed speed
Example:Router(config-if)# speed auto
Detects the speed settings of the device.
Step 7
ip dhcp excluded-address low-address high-address
Example:Router(config-if)# ip dhcp excluded-address 100.100.100.1 100.100.100.100
Specifies IP addresses that a Dynamic Host Configuration Protocol (DHCP) server should not assign to DHCP clients.
Step 8
ip dhcp pool name
Example:Router(config-if)# ip dhcp pool lwapp-ap
Configures a Dynamic Host Configuration Protocol (DHCP) address pool on a DHCP server and enter DHCP pool configuration mode.
Step 9
network (dhcp) network-number mask
Example:Router(config-if)# network 100.100.100.0 255.255.255.0
Configures the subnet number and mask for a Dynamic Host Configuration Protocol (DHCP) address pool on a Cisco IOS DHCP server.
Step 10
default-router address
Example:Router(config-if)# default-router 100.100.100.1
Specifies the default router list for a Dynamic Host Configuration Protocol (DHCP) client.
Step 11
option code ascii string hex string ip address
Example:Router(config-if)# option 43 ascii 192.0.2.24
Configures Dynamic Host Configuration Protocol (DHCP) server options for the WLAN 1000 series AP.
Note
Step 12
interface wlan-controller slot/port
Example:Router(config-if)# interface wlan-controller 1/0
Enters interface configuration mode, and specifies an interface for configuration.
Step 13
ip address ip-address mask
Example:Router(config-if)# ip address 192.0.2.254 255.255.255.0
Sets a primary or secondary IP address for an interface.
Step 14
interface wlan-controller slot/port
Example:Router(config-if)# interface wlan-controller 1/0 15
Enters interface configuration mode, and specifies an interface for configuration.
Step 15
encapsulation dot1q vlan-id
Example:Router(config-if)# encapsulation dot1q 15
Enables IEEE 802.1q encapsulation of traffic on a specified subinterface in a virtual LAN (VLAN).
Step 16
ip address ip-address mask
Example:Router(config-if)# ip address 15.0.0.1 255.255.255.0
Sets a primary or secondary IP address for an interface.
Step 17
interface wlan-controller slot/port
Example:Router(config-if)# interface wlan-controller 1/0 16
Enters interface configuration mode, and specifies an interface for configuration.
Step 18
encapsulation dot1q vlan-id
Example:Router(config-if)# encapsulation dot1q 16
Enables IEEE 802.1q encapsulation of traffic on a specified subinterface in a virtual LAN (VLAN).
Step 19
ip address ip-address mask
Example:Router(config-if)# ip address 16.0.0.1 255.255.255.0
Sets a primary or secondary IP address for an interface.
Step 20
ip dhcp pool name
Example:Router(config)# ip dhcp pool client-15
Configures a Dynamic Host Configuration Protocol (DHCP) address pool on a DHCP server and enter DHCP pool configuration mode.
Step 21
network (dhcp) network-number mask
Example:Router(config)# network 15.0.0.0 255.255.255.0
Configures the subnet number and mask for a Dynamic Host Configuration Protocol (DHCP) address pool on a Cisco IOS DHCP server.
Step 22
default-router address
Example:Router(config)# default-router 15.0.0.1
Specifies the default router list for a Dynamic Host Configuration Protocol (DHCP) client.
Step 23
ip dhcp pool name
Example:Router(config)# ip dhcp pool client-16
Configures a Dynamic Host Configuration Protocol (DHCP) address pool on a DHCP server and enter DHCP pool configuration mode.
Step 24
network (dhcp) network-number mask
Example:Router(config)# network 16.0.0.0 255.255.255.0
Configures the subnet number and mask for a Dynamic Host Configuration Protocol (DHCP) address pool on a Cisco IOS DHCP server.
Step 25
default-router address
Example:Router(config)# default-router 16.0.0.1
Specifies the default router list for a Dynamic Host Configuration Protocol (DHCP) client.
Step 26
configure interface create interface_name vlan-id
Example:WLAN Controller> configure interface create Controller15 15
WLAN Controller> configure interface create Controller16 16
Adds a new dynamic interface.
Step 27
configure interface address ap-manager IP_address netmask gateway
Example:WLAN Controller> configure interface address Controller15 15.0.0.254 255.255.255.0 15.0.0.1
WLAN Controller> configure interface address Controller16 16.0.0.254 255.255.255.0 16.0.0.1
Configures the address information of an interface.
Step 28
configure wlan create wlan_id wlan_name
Example:WLAN Controller> configure wlan create 15 wlan-15
WLAN Controller> configure wlan create 16 wlan-16
Creates a wireless LAN.
Step 29
configure wlan interface wlan_id wlan_name
Example:WLAN Controller> configure wlan interface 15 Controller15
WLAN Controller> configure wlan interface 16 Controller16
Associates a wireless LAN with an existing interface.
Step 30
configure interface dhcp ap-manager server1 [server2] management server1 [server2]
Example:WLAN Controller> configure interface dhcp Controller15 15.0.0.1
WLAN Controller> configure interface dhcp Controller16 16.0.0.1
Configures DHCP options on an interface.
Example
The Wireless LAN controller module installed in the router can be logically considered equivalent to an external wireless LAN controller connected to the router through an Ethernet interface as shown in Figure 3.
Figure 3 Creating VLANs for the Cisco WLAN Controller Module
The following example assumes the network module is plugged into slot 1 of the router with these considerations:
•
•
•
•
Configure a DHCP server on the router to assign an IP address to the AP. Use the dhcp option 43 command to inform the AP contact information of the controller IP address. After performing the following steps, the AP can learn the IP address, and find the controller register.
Router(config-if)# interface GigabitEthernet0/0Description: Connected to APRouter(config-if)# ip address 100.100.100.1 255.255.255.0load-interval 30duplex autospeed auto!Router(config-if)# ip dhcp excluded-address 100.100.100.1 100.100.100.100!Router(config-if)# ip dhcp pool lwapp-apRouter(config-if)# network 100.100.100.0 255.255.255.0Router(config-if)# default-router 100.100.100.1Router(config-if)# option 43 ascii "192.0.2.24"This following example shows how two WLANs (wlan15 and wlan16) are created on the controller, mapped to the corresponding wired side vlan 15 and vlan 16, and how routing between vlan 15 and vlan 16 is done by the router through dot1Q sub-interfaces.
On the router, create one sub-interface under wlan-controller interface (in interface configuration mode) for every VLAN, assign it to the corresponding VLAN, and configure an IP address from the respective subnets.
Router(config-if)# interface wlan-controller1/0Router(config-if)# ip address 192.0.2.254 255.255.255.0!Router(config-if)# interface wlan-controller1/0.15Router(config-if)# encapsulation Dot1q 15Router(config-if)# ip address 15.0.0.1 255.255.255.0!Router(config-if)# interface wlan-controller 1/0.16Router(config-if)# encapsulation Dot1q 16Router(config-if)# ip address 16.0.0.1 255.255.255.0On the router, create two DHCP pools from subnet 15.0.0.0/24 and 16.0.0.0/24 and assign IP address information to the wireless clients in wlan 15 and 16.
Note
Router(config)# ip dhcp pool client-15Router(config)# network 15.0.0.0 255.255.255.0Router(config)# default-router 15.0.0.1Router(config)# ip dhcp pool client-16Router(config)# network 16.0.0.0 255.255.255.0Router(config)# default-router 16.0.0.1For every VLAN on the controller, create one dynamic interface to the corresponding VLAN and assign an IP address, a subnet mask, and default gateways from the above subnets.
Controller> configure interface create controller15 15Controller> configure interface create controller16 16Controller> configure interface address Controller15 15.0.0.254 255.255.255.015.0.0.1Controller> configure interface address Controller16 16.0.0.254 255.255.255.0 16.0.0.1Create wlan 15 and wlan 16 with SSID wlan-15 and wlan-16.
Controller> configure wlan create 15 wlan-15Controller> configure wlan create 16 wlan-16Map these WLANs to corresponding dynamic VLAN interfaces on the controller.
Controller> configure wlan interface 15 Controller15Controller> configure wlan interface 16 Controller16Configure DHCP server info on the controller interfaces (for wireless clients) pointing to the respective sub-interface IP addresses on the router.
Controller> configure interface dhcp controller15 15.0.0.1Controller> configure interface dhcp Controller16 16.0.0.1The traffic from wlan 15 client destined to the wlan 16 client will be routed between the sub-interfaces w1/0.15 and w1/0.16 on the router.
Note
Upgrading the Cisco WLAN Controller Module Software
Complete these steps to upgrade the controller software using the CLI.
Restrictions
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
Note
For information about module slot locations and numbering on Cisco routers, see the Cisco Network Modules Hardware Installation Guide at the following URL:
Once the WLAN controller module software is successfully upgraded, enter reset system to reboot the Cisco WLAN controller network module and run the new code.
DETAILED STEPS
Example
Sample Output for the reset system Command
This example shows what appears when you enter the reset system command:
WLAN Controller>reset systemThe system has unsaved changes. Would you like to save them now? (y/n) ySaving Configurations
Controllers contain two kinds of memory: volatile RAM and nonvolatile RAM (NVRAM). At any time, you can save the configuration changes from active volatile RAM to NVRAM.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Erasing and Resetting the WLAN Controller Module Configuration
To reboot the Cisco WLAN controller module and restore it to the factory defaults, perform the following steps.
Note
http://www.cisco.com/en/US/products/ps6308/prod_command_reference_list.html
SUMMARY STEPS
1.
2.
DETAILED STEPS
Additional References
Related Documents
Technical Assistance
service-module wlan-controller
To configure the Cisco WLAN controller network module from the router, use the service-module wlan-controller command in global configuration mode.
service-module wlan-controller slot/port {reload | reset | session [clear] | shutdown | status}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration mode.
Command History
Usage Guidelines
If the Cisco WLAN controller module is free of any prior configuration, the configuration wizard is automatically invoked. You cannot bypass the configuration wizard. Through the CLI, you must provide the information at the prompts provided.
Examples
The following example shows how to clear the existing session with the WLAN controller network module:
Router# service-module wlan-controller 1/0 session clear [confirm] [OK] boxer-bombor# Router#Router#service-module wlan-controller 1/0 sessionTrying 192.0.2.254, 2066 ... OpenUser:Open Source License Acknowledgements
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License:
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
4.
5.
6.
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4.
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco Ironport, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0907R)
