![cisco virtual controller pricebit cisco virtual controller pricebit](https://i.ebayimg.com/images/g/PvUAAOSw2zpfvAcZ/s-l1600.jpg)
But do also look at the logs on the controller. The logs on the AP are often a better source of info than the logs on the controller. You can console in to the AP and have a look at the logs on the CLI. For Mobility Express (controller-less) and (I'm guessing) vWLC deployments, the AP firmware will need to be loaded to a TFTP server AND the location of that server will have to be part of the DHCP server options and it is usually Option 66. On a hardware controller the AP firmware is built in. The AP's get their firmware from the controller. Make sure the switch, DHCP server and vWLC are showing the same time.
![cisco virtual controller pricebit cisco virtual controller pricebit](https://i.pinimg.com/originals/f2/1e/fd/f21efd8365bac44807b80d2e16668035.png)
It's the thing I forget to do the most when I set up a controller (but don't tell anyone.). So plan to have a management network for the APS and controller and use a different vlan for the wireless networks.ĩ9 times out of 100 (licensing aside) the reason an AP can't see a controller on the same subnet is because the clocks are not sync'd. Infact it is actually difficult to enable an SSID on the same connection as management and controller. It does not have to be the same subnet and vlan as that used for SSIDs (the actual wireless networks). One other starting tip is that the AP needs to communicate with the controller using IP and in a non tagged vlan (switch port should be access vlan x) - but this is for management only. If the APs need to all cover the same area then planning and adjusting setup to accommodate this is much harder. If you are just looking for simple SSID deployment with APs not near each other covering different areas, it will be ok. Overall this could be a good fun learning project, but do not expect it to be simple. Also the controller has to have AP management enabled on the applicable interface.Īlso console cable to the AP, it will output log messages that tell you what is going on.
![cisco virtual controller pricebit cisco virtual controller pricebit](https://i.ebayimg.com/images/g/jhcAAOSwku9fvAci/s-l640.jpg)
For both the above the AP needs to be getting an ip address etc from dhcp. Otherwise layer3 can be done via dhcp option or DNS entry.
#Cisco virtual controller pricebit how to
The AP needs to know how to contact a controller - one method is layer 2 discovery so connect the virtual controller and AP in the same vlan. Have you read any documentation and checked the configuration? I've retsrted both the AP and the virtual controller but it makes no difference.īefore I pull out what is left of my hair is the opinion that this should be a working combination and I'm simply doing it wrong or is this never going to work at all as they are not compatible? At no point can I see the AP in the virtual controlller. The status light spends a long time at solid green (10 minutes or so) and then flashes green/red for 30 seconds before going back to solid greed. I've unboxed one and connected it to a PoE port which brings it to life. That's as far as it went - the APs are all in boxes and have never been powered on until today. To get around this he has downloaded and setup a virtual wireless controller - an AIR-CTVM-K9 to be accurate.
#Cisco virtual controller pricebit install
By the time he went to install them there was no budget to purchase one as Covid had happened and budgets are very tight.
![cisco virtual controller pricebit cisco virtual controller pricebit](https://www.cisco.com/c/dam/en/us/td/i/300001-400000/350001-360000/351001-352000/351626.tif/_jcr_content/renditions/351626.jpg)
He purchased 4*Cisco C9115 APs but no controller as he wasn't aware that a controller would be needed. One of the projects the outgoing IT person had started was to install wireless APs at each office - 4 in total. I have just started a new job as the lone IT person working for a small company.