operationsIT
asked on
Cisco AP 2600 not joining Wireless Controller
Hello EE,
We have some APs that are not joining the WLC.
They are getting a DHCP address and I can ping them.
The AP themselves says:
Controller address x.x.x.x obtained through DHCP
Did not get log server settings from DHCP
Could not resolve Cisco-CAPWAP-Controller.x.
We have some APs that are not joining the WLC.
They are getting a DHCP address and I can ping them.
The AP themselves says:
Controller address x.x.x.x obtained through DHCP
Did not get log server settings from DHCP
Could not resolve Cisco-CAPWAP-Controller.x.
ASKER
Yes
Yes
7.3.112.0 but just installed APs at another location last month and worked.
Yes
7.3.112.0 but just installed APs at another location last month and worked.
Yep that's fine then - 7.2.110 is the minimum for the 2600 AP.
Are they on the same subnet/VLAN as the WLC?
Is the time/date correct on the WLC?
On the WLC, do you get anything in the log on the monitor page under recent traps?
Are they on the same subnet/VLAN as the WLC?
Is the time/date correct on the WLC?
On the WLC, do you get anything in the log on the monitor page under recent traps?
ASKER
I can ping from controller to AP and from AP to controller however when I debug I get nothing on the WLC like nothing is hitting it. It is on a different subnet.
Are there any firewalls or ACLs between the APs and WLC blocking TCP/UDP ports 5246 and 5247?
ASKER
There is but if I telnet to the controller from the branch site on port 5246 it opens to a blank screen. Does this mean it's open?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I was happened before and finally found that the new AP country code is not matching...
That's a good point, Joey.
ASKER
It was not seeing the MAC so I ran wireshark and saw the request, but not the reply so was able to go to ISP and show there was a block to which they resolved.. Thanks!
What version of code do you have on the WLC?