use Static ip on AP, can ping to WLC but not join?

[rechard_hk]

dear all,

Please kindly see in the attach file.

i using command for AP for assign ip address and AP can ping to controller but it cannot join with Controller.

Could you help to command?

Best Regards,

Rechard

[Leo Laohoo]

Post the complete output to the following commands: 

1.  WLC:  sh sysinfo; and

2.  AP:  sh version

[rechard_hk]

Dear Leo,

Please kindly see in the attach file.

i tried to use command as below and the AP can ping to Controller but the AP cannot joint to AP

capwap ap controller ip address x.x.x.x   ( IP for controller)

capwap ap ip address x.x.x.x 255.255.255.0  (IP for AP )

Best Regards,

Rechard

[Leo Laohoo]

Post the COMPLETE output to the command "sh sysinfo".

[rbncarvalho]

If you issue the debug capwap client events/erros on the AP and debug capwap events/errors enable on the WLC what do you see?

Can you post it here?

Thank you

[rechard_hk]

Dear all,

Please kindly see log as in the attach file.

Note: ip add 192.168.7.7 i connected to internet and remote to WLC.

i don't know why AP cannot joint to WLC. but AP can ping to Controller.

After i apply command as below if the AP cannot joint with WLC the interface BVI 1 will switch to DHCP or reboot.

capwap ap ip add 50.50.50.11 255.255.255.0
capwap ap controller ip add 50.50.50.1

Best Regards,

Rechard

[Sandeep Choudhary]

Hi Rechard,

AP: 1702I model which need the min version SW on wlc: 8.0.100.0 and you are running 8.1.102.0.

As per your logs

Unknown AP type. Using Controller Version!!!

It should support this Access Point, but looks like something wrong with software , Try to Downgrade it and try again.

Regards

Don't forget to rate helpful posts

[rechard_hk]

Dear sir,

i got this log , it still cannot join to WLC.

AP80e0.1dfc.b050#ping 50.50.50.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 50.50.50.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
AP80e0.1dfc.b050#
*Sep 22 11:31:27.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
*Sep 22 11:31:27.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
*Sep 22 11:31:27.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
*Sep 22 11:31:27.095: %CAPWAP-3-EVENTLOG: Not waiting for DHCP options as resolve method on interface BVI1 is 4
*Sep 22 11:31:27.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
*Sep 22 11:31:27.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
*Sep 22 11:31:30.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 192.168.7.7 with discovery type set to 1
*Sep 22 11:31:30.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
*Sep 22 11:31:30.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup
*Sep 22 11:31:30.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 50.50.50.1 with discovery type set to 1
*Sep 22 11:31:30.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 192.168.7.7, type 1.
*Sep 22 11:31:30.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 50.50.50.1 with discovery type set to 1
*Sep 22 11:31:30.095: %CAPWAP-3-EVENTLOG: 
 SENDING DISCOVERY REQUEST wtpStartAcDiscovery:1682, Controller WLC2504: IP Address 50.50.50.1 
*Sep 22 11:31:30.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
*Sep 22 11:31:30.095: %CAPWAP-3-EVENTLOG: Send broadcast discovery request
*Sep 22 11:31:40.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
*Sep 22 11:31:40.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
*Sep 22 11:31:40.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
*Sep 22 11:31:40.095: %CAPWAP-3-EVENTLOG: Not waiting for DHCP options as resolve method on interface BVI1 is 4
*Sep 22 11:31:40.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
*Sep 22 11:31:40.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
*Sep 22 11:31:43.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 192.168.7.7 with discovery type set to 1
*Sep 22 11:31:43.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway  - gateway NOT found
*Sep 22 11:31:43.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup
*Sep 22 11:31:43.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 50.50.50.1 with discovery type set to 1
*Sep 22 11:31:43.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 192.168.7.7, type 1.
*Sep 22 11:31:43.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 50.50.50.1 with discovery type set to 1
*Sep 22 11:31:43.095: %CAPWAP-3-EVENTLOG: 
 SENDING DISCOVERY REQUEST wtpStartAcDiscovery:1682, Controller WLC2504: IP Address 50.50.50.1 
*Sep 22 11:31:43.095: %CAPWAP-3-EVENTLOG: Send IPv4 Broadcast discovery request

[Sandeep Choudhary]

Hi Rechard,

use these commands on AP to find WLC:

capwap ap ip add 50.50.50.11 255.255.255.0
capwap ap controller ip add 50.50.50.1
capwap ap ip default-gateway <IP-address>

If still failes then please paste the complete output of this command: sh sysinfo

Regards

Don't forget to rate helpful posts

[rechard_hk]

Dear Sandeep,

i was check on cisco website the version wlc: 8.0.100.0  it not available to download.

How can i go next ?

Do you have any document or step by step to implement WLC 2504 with 1702I?

Best Regards,

[Sathiyanarayanan Ravindran]

Hi,

Please check the below things.

1. Check whether below UDP ports are allowed at the firewall end for CAPWAP Communication.
Data - 5247

Control - 5246

2. NTP time sync.

3. Appropriate Country code is enabled on the WLC.

4. Install the last TAC recommended image version 8.3.143.0.  https://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn83mr4.html#concept_ejl_stn_zdb

Regards,

Sathiyanarayanan Ravindran

[Tony Ortiz]

I have a 3702i, but a controller running 7.4.121.0. I could ping the controller just fine from the AP's command line, but it would never join, no matter how many times I entered the CAPWAP and LWAPP commands defining the controller.

Then I realized, 3702i's aren't compatible with the older WLC controller software. I then pointed my AP to one of my newer WLC's running 8.0.121.0, and it associated immediately.

I realize this is a very simplistic answer, but it doesn't hurt to check the HCL in the release notes.

[ganeshjatms@gmail.com]

after rest the WLC please follow some steps 

watch the video on my you-tube channel.

https://www.youtube.com/channel/UCh5nlwJhZKFGTm_OW04bemw?view_as=subscriber 

Enter Administrative User Name (24 characters max): admin
Enter Administrative Password (3 to 24 characters): ***********
Re-enter Administrative Password : ***********

Enable Link Aggregation (LAG) [yes][NO]:

Management Interface IP Address: 192.168.10.229
Management Interface Netmask: 255.255.255.0
Management Interface Default Router: 192.168.10.1
Management Interface VLAN Identifier (0 = untagged):
Management Interface Port Num [1 to 4]:
Invalid response

Management Interface Port Num [1 to 4]: 1
Management Interface DHCP Server IP Address: 192.168.10.229

Virtual Gateway IP Address: 1.1.1.1

Multicast IP Address: 239.255.255.255

Mobility/RF Group Name: MS

Network Name (SSID): Cisco-MS

Configure DHCP Bridging Mode [yes][NO]:

Allow Static IP Addresses [YES][no]:

Configure a RADIUS Server now? [YES][no]: no
Warning! The default WLAN security policy requires a RADIUS server.
Please see documentation for more details.

Enter Country Code list (enter 'help' for a list of countries) [US]:

Enable 802.11b Network [YES][no]:
Enable 802.11a Network [YES][no]:
Enable 802.11g Network [YES][no]:
Enable Auto-RF [YES][no]:

Configure a NTP server now? [YES][no]: no
Configure the system time now? [YES][no]:
Enter the date in MM/DD/YY format: 9/10/2018
Invalid response

Enter the date in MM/DD/YY format: 09/10/2018
Invalid response

Enter the date in MM/DD/YY format: 09/10/18
Enter the time in HH:MM:SS format: 17:48:30

Configuration correct? If yes, system will save it and reset. [yes][NO]: yes
Cleaning up DHCP server configuration

Configuration saved!
Resetting system with new configuration...

Configuration saved!
Resetting system with new configuration...
Restarting system.

[raghavraghul246]

i too had this prob , check ur logs in wlc and if it states abt licensing anywhere reinstall a new license 

by going into licenses>new