I quickly fixed this one and then took a look at log messages on the controller. That was the first hint and by the way I fixed another issue not related to AP join but rather to NAT for return traffic. Then quickly logged to gui of vWLC and pinged the AP. I sat behind the console, checked the option 43 decimal to hex translation. At first glance this could be certificate or asymmetric routing issue
This is normal behaviour when option 43 is not properly set in DHCP or there is no connectivity between AP and controller. The problem was that AP was not able to join the vWLC changing the address in cycles.
#CISCO VWLC KEYGEN SOFTWARE#
In turn, AP is able to establish Capwap tunnel to controller, download updated software and specific configuration.
Normally after connecting AP to PoE powered Catalyst, the AP receives IP address from DHCP with option 43 that specifies the controller IP address. Between the office and DC there is an IPSec VPN tunnel created on Cisco ASA (5506x and 5520, the older one) in EzVPN hardware client mode.
The vWLC was located in Grandmetric DC Testing Labs whereas Cisco CAP-2700 was located at Grandmetric HQ Office. A colleague asked me to take a look and explained the topology. Cisco 2700 AP could not join to newly installed Cisco vWLC controller. I recently faced the issue with AP join to vWLC.
0 kommentar(er)
