Suggested Hardware Recommendations for Hosting Cisco Virtual Controllers
∙UCS R210−2121605W Rack Mount Server (2 RU):
♦2 * Intel Xeon CPU X5670 @ 2.93 GHz
♦16 G memory
∙IBM x3550 M3 Server:
♦2 * Intel Xeon 5600 series processors with 4 cores each and each core capable of doing hyper threading which gives you 16 CPUs in total @3.6 GHz
♦12G memory
∙ISR G2 Services Ready Engine (SRE) using UCS Express (Stretch goal):
♦SRE 700: Single Core Intel Core Duo 1.86 GHz with 4 GB memory
♦SRE 900: Dual Core Intel Core Duo 1.86 GHz with 4 GB memory (upgradable to 8 GB)
AP Requirement
∙All 802.11n APs with required software version 7.3 are supported.
∙APs will be operating in FlexConnect mode only.
∙AP autoconvert to FlexConnect is supported on controller.
∙New APs ordered will ship with 7.3 software from manufacturing.
∙Existing APs must be upgraded to 7.3 software before joining a virtual controller.
Note: The Virtual Controller in release 7.3 uses Self Signed Certificates (SSC) as against the Manufacturing Installed Certificates (MIC) in the traditional controller. The AP will be able to validate the SSC certificate provided by the virtual controller before joining. See AP Considerations in the Troubleshooting section for more details.
Components Used
The information in this document is based on these software and hardware versions:
∙Cisco Catalyst Switch
∙Wireless LAN Controllers Virtual Appliance
∙Wireless LAN Controller 7.3 Software
∙Cisco Prime Infrastructure 1.2
∙802.11n Access Points in FlexConnect Mode
∙DHCP server
∙DNS Server
∙NTP
∙Wireless Client Laptop, Smartphone, and Tablets (Apple iOS, Android, Windows, and Mac)
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