AP1832 always in discovery

[mgerguis]

I received 2x Cisco AP1832 , one managed to discover & connect to the AP Controller, while the other one is continually in discovery & won't allow any configuration or as it keeps on discovery retry.

please advise if its faulty to return or I am missing something here

show version - output

AP Running Image     : 8.2.111.0
Primary Boot Image   : 8.2.111.0
Backup Boot Image    : 0.0.0.0
2 Gigabit Ethernet interfaces
2 802.11 Radios
Radio FW version : 21e6bdcdd6b8c8a2e3830b2f6ddab9b5
NSS FW version : NSS.AK.1.0.c10-00017-E_custC-1

any help is apperciated

[Philip D'Ath]

Please post the output from the console port.

[mgerguis]

thanks for your reply here is

[*06/21/2016 04:01:05.7304] device capwap0 entered promiscuous mode
[*06/21/2016 04:01:05.7604] device capwap1 entered promiscuous mode
[*06/21/2016 04:01:14.1478] CAPWAP State: Discovery
[*06/21/2016 04:01:23.6548] CAPWAP State: Discovery
[*06/21/2016 04:01:33.1518] CAPWAP State: Discovery
[*06/21/2016 04:01:42.6689] CAPWAP State: Discovery
[*06/21/2016 04:01:52.1659] CAPWAP State: Discovery
[*06/21/2016 04:02:01.6729] CAPWAP State: Discovery
[*06/21/2016 04:02:11.1699] CAPWAP State: Discovery
[*06/21/2016 04:02:20.6870] CAPWAP State: Discovery
[*06/21/2016 04:02:30.1940] CAPWAP State: Discovery
[*06/21/2016 04:02:39.6910] CAPWAP State: Discovery
[*06/21/2016 04:02:49.2081] CAPWAP State: Discovery
[*06/21/2016 04:02:58.7051] CAPWAP State: Discovery
[*06/21/2016 04:03:08.2121] CAPWAP State: Discovery
[*06/21/2016 04:03:17.7191] CAPWAP State: Discovery
[*06/21/2016 04:03:27.2262] CAPWAP State: Discovery

and it keeps like that for a period then restarts & its again to same cycle

[Philip D'Ath]

Are these devices definitely all in the same VLAN?

[mgerguis]

they are newly bought no configuration has been done yet

[mgerguis]

thanks a lot for trying to assist here the problem turned to be that the supplier while testing put static IP for the controller & caused it to cycle trying to connect to that controller & as to be expected not finding it

a rest removed offending configuration & I am glad to say its working okay now.