![]() ![]() Will try to see what triggered the bump back to 0 (if this happens again). ![]() For our deployment I am going to use virtual Wireless LAN Controller version 8.0.140. Will leave my machine shut down tonight / till tomorrow (wait for the date to roll over) and see what tomorrow brings 0 or 200 APs supported :)ĮDIT: The license seems to stick for now, still 200 APs supported. Cisco updates the virtual Wireless LAN Controller versions pretty regularly so you may have a newer version of virtual Wireless LAN Controller than what I am using in this lab series. Shutting down my local Windows 7 machine and booting up again 200 APs supported. Shutting down (and starting) the VM Workstation and the ESXi boot the vWLC via vSphere will still not trigger the issue, 200 APs supported. Note A zero value for the VLAN identifier (on the Controller > Interfaces page) means that the interface is untagged. ![]() I thought i would be able to add more boosters and antennas as time went. Shutting down (and starting) vSphere and booting the vWLC will still have the 200 APs supported. If you configure an interface to use the native VLAN on a neighboring Cisco switch, make sure you configure the interface on the controller to be untagged. I am looking at deploying a Cisco Virtual Wireless LAN Controller (vWLC 7.3). Managed from vSphere 6.0.0 (2502222), all local on my Windows 7 machine.īooting this morning (after shutting down yesterday with 200 APs supported) I start the vWLC from powerdown the license is returned to 0 APs.Ī reboot (of the vWLC) after agree with the EULA will save the config and the 200 APs are still supported.
0 Comments
Leave a Reply. |