Getting Started
The Virtual Controller Deployment Guide is the best reference for installing and initially configuring a vWLC:
Cisco Virtual Wireless Controller Deployment Guide
Cisco Virtual Wireless Controller Data Sheet
Key Points
The vWLC only supports AP’s in Flexconnect mode
+ All or some Wlans may still be centrally switched if preferred
+ If local mode (default) AP’s join the vWLC, they will appear to be functional, but will not beacon and service clients
The following enhancement bug has been opened to proactively alert administrators of unsupported AP modes:
CSCub46293 7500 and Virtual WLC: need to alert non support of non flexconnect ap's
+ AP’s may be automatically converted to flexconnect mode via the AP autoconvert cli command:
(vWLC) >show ap autoconvert AP Autoconvert .................................. Disabled (vWLC) >config ap autoconvert flexconnect (vWLC) >show ap autoconvert AP Autoconvert .................................. FlexConnect
AP’s must be running 7.3 (15.2(2)JA) or later code to join a vWLC
7.3.101.0 = 15.2(2)JA
Refer to the following document for IOS to WLC code version cross reference:
Table 1 Cisco WLC Software Releases, AP IOS Releases, and Supported Access Points
+ AP’s migrating from legacy controllers (eg 4400, 2100, WiSM, last code support 7.0) to vWLC’s must either first be moved to a 7.3 or later physical controller, or manually upgraded.
License not active upon initial installation
+ A common point overlooked is that once a vWLC is initially installed, ‘0 Access Points Supported’ will be displayed on the vWLC’s Monitor page. A license (evaluation or permanent) must be activated before AP’s will be able to join.
7.4 Configuration Guide – Managing Licenses
Common Issues
VM Port Mapping
It is critical, during VM configuration, that the vWLC’s service port (VM Network Adapter
1) and the vWLC’s Data Port (VM Network Adapter
2) not be mapped to the same virtual switch. This is documented in the vWLC deployment guide, but often overlooked or misunderstood.
Issues such as ap join stability, inconsistent access to external hosts (such as Radius or NMS servers) and degraded vWLC management interface response may be encountered.
The following log message typically indicates this configuration state:
*osapiReaper: Sep 10 16:57:24.575: #LOG-3-Q_IND: dhcp_proxy.c:3754 Received a DHCP packet sent by the controller itself possible network loop![...It occurred 5 times.!]Additional information
CSCuj14843 vWLC: prevent service/data port confusion
VMware configuration correction screenshots:
Commonly encountered bugs
CSCuf38985 AP can't join a second vWLC - trouble validating vWLC Self-Signed Cert
CSCuf74326 valid vWLC license misinterpreted by vWLC : no AP count
Additional Info
vWLC license loading but not allowing ap's to join
CSCuj14843 vWLC: prevent service/data port confusion
CSCub46293 7500 and Virtual WLC: need to alert non support of non flexconnect ap's
CSCul29834 AP not join vWLC due to SSC certificate validation failed
CSCud56753 vMotion of vWLC causes extended loss of communication to management
