Introduction

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). This document is an update for vWLC based on the CUWN 7.5 software release.

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.

Advantages of the vWLC:

Flexibility in hardware selection based on your requirements.

Reduced cost, space requirements, and other overheads since multiple boxes can be replaced with single hardware running multiple instances of controllers, Prime Infrastructure (PI) and other servers (ISE, MSE, VSG / firewall).

Independent and mutually exclusive instances allow administrators to use multiple virtual controllers to manage different campuses (or even to manage multiple customer sites) using the same hardware.

Enable features provided by the virtualization software, including High Availability, failover protection, and ease of migration.

Virtual WLAN Controller Release 7.5 Unsupported Features

Internal DHCP server

TrustSec SXP

Access points in local mode

Mobility/guest anchor

Multicast

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 that is based on IGMP or MLD snooping.

High Availability

PMIPv6

WGB

VideoStream

Outdoor mesh access points

Note Outdoor AP in FlexConnect mode is supported.

Indoor mesh access points

Application Visibility and Control (AVC)

Client downstream rate limiting for central switching

Limitations

When multiple VM instances are rebooted simultaneously from the system, it is possible that access points may disconnect from the network even if the primary vWLC instance is active. This is a VMware limitation and not a product issue of vWLC.

– UCS E140/160 Single and Double-Wide Blade: 4-6 Cores with up to 48 GB memory.

AP Requirement

All 802.11n APs with required software version 7.5 and above are supported.

APs will be operating in FlexConnect mode only.

AP autoconvert to FlexConnect is supported on controller.

New APs ordered will ship with minimum 7.5 software from manufacturing.

Existing APs must be upgraded to 7.5 software before joining a virtual controller.

For Cisco 600 Series OEAP to associate with Cisco Virtual Wireless LAN Controller, follow these steps:

1. Configure the OEAP to associate with a physical controller that is using 7.5 or a later release and download the corresponding AP image.

2. Configure the OEAP so that the OEAP does not associate with the physical controller again; for example, you can implement an ACL in the network to block CAPWAP between the OEAP and the physical controller.

3. Configure the OEAP to associate with the Cisco Virtual Wireless LAN Controller.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Topology

In order to properly implement and test the Cisco vWLC, a minimal network setup is required, similar to the diagram shown in this section. You need to simulate a location with a FlexConnect AP in a centrally switched deployment, and/or with the addition of local and remote sites with local DHCP (better if there is also a DNS and local access to Internet).

Deploying Virtual WLC on UCS-E Modules for ISR-G2

Complete GUI and CLI configuration guides for UCS-E modules can be found on the links below. This document only provides the instructions the user needs to perform to install vWLC on a new out of the box UCS-E module.

Installation with KVM Console on UCS-E Module

The UCS-E provides a VGA connection and USB ports from the front panel for monitor display and keyboard connection; however, in this example, the CIMC will be used to launch KVM console to assist with VMware installation. Note that Java software plugin is required with compatible browsers.

Step 16 If using IE explorer and KVM console session fails to launch with an error indicating unable to connect, navigate to Tools > Internet Options > Advanced and uncheck Do not save encrypted pages to disk option.

Step 17 From CIMC > Summary > launch KVM console.

Step 18 In the KVM console, monitor the output throughout the VMware software installation.

Deploying Virtual WLC on SRE Service Modules 710/910 for ISR-G2

Complete GUI and CLI configuration guides for SRE 710/910 service modules can be found on the links below. This document only provides the instructions the user needs to perform to install vWLC on a new out of the box SRE 710/910 service modules.

Figure 2 Configuration Example for Deploying SRE Service Module for the ISR-G2

Download the Software Package for SRE Service Module

Complete the steps:

Step 1 Determine if SRE service module is 710 or 910.

Step 2 Download the UCS installation script files onto a http or ftp server from the below link and then unzip it onto a ftp or http server. The latest version is 2.0.1 on CCO. This example uses an FTP server hosting appropriate files extracted below.

Appendix

ISR-G2 Configuration with UCS-E Module Example

Note that this sample configuration intentionally contains both UCS-E and SRE SM. Both modules cannot be configured the same time, and intentionally added for reference, to show the similarity yet subtle difference in configuration between them.