The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following topics:
Prior to release 7.3, Wireless LAN (WLAN) controller software ran on dedicated hardware you were expected to purchase. The Virtual Wireless LAN Controller (vWLC) runs on general hardware under an industry standard virtualization infrastructure. The vWLC is ideal for small and mid-size deployments with a virtual infrastructure and require an on-premises controller. Distributed branch environments can also benefit with a centralized virtual controller with fewer branches required (up to 200).
vWLCs are not a replacement of shipping hardware controllers. The function and features of the vWLC offer deployment advantages and benefits of controller services where data centers with virtualization infrastructure exist or are considered.
The new features in 8.1 are:
This document is an update for vWLC based on the CUWN 8.1 software release and the support for Linux Kernel-based Virtual Machine (KVM). KVM is supported in Cisco Wireless Release 8.1.102.0 and later releases.
Note | After KVM is deployed, it is recommended that you do not downgrade to a Cisco Wireless release that is older than Release 8.1.102.0. |
VMware support is discussed in separate document and is not relevant in this document.
Following are some of the features not supported on Cisco vWLC:
Note | FlexConnect local-switched multicast traffic is bridged transparently for both wired and wireless on the same VLAN. FlexConnect access points do not limit traffic based on IGMP or MLD snooping. |
High Availability
PMIPv6
Workgroup Bridges
Mesh (use Flex + Bridge mode for mesh-enabled FlexConnect deployments)
Note | Outdoor APs in the FlexConnect mode are supported. |
Following are the KVM prerequisites for hosting vWLC:
Minimum of 2 G memory
Minimum of 1 vCPU
Minimum of 2 network interfaces
Required storage of 8 G
Network device model is "virtio"
The physical devices connected to Open vswitch bridge should not have any IP addresses configured on it.
For more information, refer to KVM resource.