Cisco Virtual Wireless Controller FAQ 2016

Cisco Virtual Wireless Controller, as its name described “Virtual”, is a controller in a virtual form factor. It enables flexible and cost-effective deployment for small, medium-sized, or large service provider deployments. Andit can be deployed on any x86 server that supports VMware ESXi 4.x, 5.x, or 6.x and Linux KVM systems.

The Cisco Virtual Wireless LAN Controller (vWLC) is available with two types of software images starting with the 8.2 release: small-scale image (supports up to 200 access points and 6000 clients) and large-scale image (supports up to 3000 access points and 32,000 clients).

A Cisco Virtual Wireless Controller can be positioned:

Small and midsized deployments with a virtual infrastructure that requires an on-premises controller

Distributed branch environments with a centralized controller supporting a maximum of 200 branches

In the following Part there are many fast questions and answers to help you know what the Cisco Virtual Wireless Controller is, know its capability and its bright features.

Cisco Virtual Wireless Controller FAQ 2016

Q. Does the Cisco Virtual Wireless Controller support local mode?

A. The Cisco Virtual Wireless Controller offers FlexConnect features in both central and local switching. FlexConnect central switching provides a feature set similar to that of local mode.

Q. Does the Cisco Virtual Wireless Controller support bring-your-own-device (BYOD) enhancements in conjunction with the Cisco Identity Services Engine (ISE)?

Q. When do I position a Cisco Flex7500 Series Controller versus a Virtual Wireless Controller?

A. Position a virtual controller if the customer’s deployment meets the following requirements and specifications:

Virtual footprint based on VMware hypervisor ESXi 4.x, 5.x or 6.x and Linux KVM system

Does not require Data Transport Layer Security (DTLS) support

Maximum number of sites limited to 200

Performance limited to 500 Mbps per controller

Q. How is the Cisco Virtual Wireless Controller purchased?

A. The Cisco Wireless Virtual Controller can be purchased directly from Cisco or from a reseller.

After purchase of a license, a product activation key (PAK) is delivered to the purchaser. The PAK needs to be provided to a Cisco License Server along with a unique device identifier (that is generated when the virtual controller VM boots up) in order for the server to provide the virtual controller with a license file. The license file then needs to be installed in the virtual controller and activated.

Starting with the 8.2 release, Cisco Virtual Wireless Controllers also provide an option to enable licensing using Cisco Smart Software Licensing, designed for easy monitoring and consumption of licenses.

Manage license deployments with real-time visibility to ownership and consumption.

Pools license entitlements in a single account. Licenses can be moved freely through the network to wherever they are needed.

Q. How is the Cisco Virtual Wireless Controller deployed?

A. The virtual controller software will be posted as a .ovf package in the Cisco software center. Customers can download the .ovf package and install it similarly to any other virtual application. Software comes with a free 60-day evaluation license. After the VM is started, the evaluation license can be activated, and later a purchased license can be automatically installed and activated.

Q. How is the Cisco Virtual Controller managed?

A. Similar to other Cisco Wireless Controllers, the virtual controller can be managed using the controller device GUI or using Cisco Prime infrastructure.

Q. Does the Cisco Virtual Controller support serial console for out-of-band access?

A. Yes. The administrator can use the vSphere client to configure the Cisco Virtual Controller. An alternate recommended option is to configure either a physical or virtual serial console. A physical console is bound to the physical ESXi server and can be connected to a terminal console server. A virtual serial port is accessible over the network and can be assigned to each virtual controller; more than one virtual serial console can be set up as required by the number of virtual controllers in each ESXi server. Only one console option (physical or virtual serial) can be used.

Q. What are the requirements for access points to join a virtual controller?

The access points must be upgraded to 7.3 software before joining a virtual controller.

Router-switch.com is the World's Leading Cisco Supplier, founded in 2002. We provide network equipments that reduce the cost of network infrastructure, and is renowned for their customer service and huge supply of robust, cost-effective products. Read More>>