Buy or Renew
Buy or Renew
Cisco Virtual Engineer generative AI bot now active in Wireless Discussion Forum. Learn more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2134
Views
0
Helpful
14
Replies

Cisco AP 1042N Can not join a controller

Go to solution
fgasimzade
Level 4
Level 4

‎02-08-2012 11:47 PM - edited ‎07-03-2021 09:32 PM

We have purchased new 1042 Access-points, and we already have a cisco 3750 integrated wireless controller with 7.0.220.0 software

An access point have received the IP address, has found the controller, downloaded firmware and now fails to register with this messages is concole

*Feb  9 07:43:23.351: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb  9 07:43:23.351: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb  9 07:43:23.443:  status of voice_diag_test from WLC is false

*Feb  9 07:43:33.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i

p: 192.168.110.82 peer_port: 5246

*Feb  9 07:43:33.001: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb  9 07:43:34.158: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully

peer_ip: 192.168.110.82 peer_port: 5246

*Feb  9 07:43:34.159: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.110.82

*Feb  9 07:43:34.159: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb  9 07:43:34.298: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Feb  9 07:43:34.302: %DTLS-5-ALERT: Received WARNING : Close notify alert from

192.168.110.82

*Feb  9 07:43:34.302: %DTLS-5-PEER_DISCONNECT: Peer 192.168.110.82 has closed co

nnection.

*Feb  9 07:43:34.303: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192

.168.110.82:5246

Can it be due to incompatible regulatory domain? Controller is -A, access point is -E

Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Leo Laohoo
Hall of Fame
Hall of Fame

‎02-08-2012 11:49 PM 

Can it be due to incompatible regulatory domain? Controller is -A, access point is -E

That's correct.

View solution in original post

0 Helpful
14 Replies 14

Go to solution
Leo Laohoo
Hall of Fame
Hall of Fame

‎02-08-2012 11:49 PM 

Can it be due to incompatible regulatory domain? Controller is -A, access point is -E

That's correct.

0 Helpful

Go to solution
fgasimzade
Level 4
Level 4

‎02-09-2012 12:08 AM

Ok, I have changed Contry config on the Controller, now seems like AP has joined it, but Admin Status is DISABLED

Any ideas?

0 Helpful

Go to solution
Leo Laohoo
Hall of Fame
Hall of Fame
In response to fgasimzade

‎02-09-2012 12:14 AM

Check if your radios are disabled or not.

Are you using PoE?

0 Helpful

Go to solution
fgasimzade
Level 4
Level 4
In response to Leo Laohoo

‎02-09-2012 12:27 AM

Yes, I am using PoE

0 Helpful

Go to solution
fgasimzade
Level 4
Level 4
In response to fgasimzade

‎02-09-2012 12:26 AM

I have manually enabled interfaces on AP, seems like they are UP now, a can see SSID are broadcasted, but I can not associate with them anyway. An after restart interfaces on AP are still down

0 Helpful

Go to solution
Leo Laohoo
Hall of Fame
Hall of Fame
In response to fgasimzade

‎02-09-2012 12:32 AM

Can you please try with OPEN authentication?

0 Helpful

Go to solution
fgasimzade
Level 4
Level 4
In response to Leo Laohoo

‎02-09-2012 12:41 AM

Yes, I am trying with an OPEN authentication, my Blackberry fails to associate.

And what about shutted down radio interfaces? Any thoughts?

Thank you for your help!

0 Helpful

Go to solution
nikhilcherian
Level 5
Level 5
In response to Leo Laohoo

‎02-09-2012 12:43 AM

Please paste the following outputs

WLC

Show country

AP

show ip int brief

show controllers d1

show controller d0

more flash:event.log

Thanks

NikhiL

0 Helpful

Go to solution
fgasimzade
Level 4
Level 4
In response to nikhilcherian

‎02-09-2012 12:56 AM

Regulatory Domain on WLC is -AER

AP2894.0fd6.c264#sh ip interface brief

Interface                  IP-Address      OK? Method Status                Prot

ocol

Dot11Radio0                unassigned      NO  unset  administratively down down

Dot11Radio1                unassigned      NO  unset  administratively down down

GigabitEthernet0           192.168.110.8   YES DHCP   up                    up

AP2894.0fd6.c264#sh controllers d1

!

interface Dot11Radio1

Radio AIR-AP1140A, Base Address 1caa.0770.2aa0, BBlock version 0.00, Software ve

rsion 3.00.81

Serial number: FOC15123GN8

Number of supported simultaneous BSSID on Dot11Radio1: 16

Carrier Set: ETSI (OFDM) (EU) (-E)

Uniform Spreading Required: Yes

Configured Frequency: 5700 MHz  Channel 140 (DFS enabled)

Allowed Frequencies: 5180(36) 5200(40) 5220(44) 5240(48) 5260(52) 5280(56) 5300(

60) 5320(64) 5500(100) 5520(104) 5540(108) 5560(112) 5580(116) 5660(132) 5680(13

6) 5700(140)

Listen Frequencies: 5180(36) 5200(40) 5220(44) 5240(48) 5260(52) 5280(56) 5300(6

0) 5320(64) 5500(100) 5520(104) 5540(108) 5560(112) 5580(116) 5600(120) 5620(124

) 5640(128) 5660(132) 5680(136) 5700(140) 5745(149) 5765(153) 5785(157) 5805(161

) 5825(165)

Beacon Flags: 0, Interface Flags 60109, Interface Events 0, Mode 9; Beacons are

disabled; Probes are disabled

Configured Power: 17 dBm (level 1)

AP2894.0fd6.c264#sh controllers d0

!

interface Dot11Radio0

Radio AIR-AP1140G, Base Address 1caa.0743.f160, BBlock version 0.00, Software ve

rsion 3.00.81

Serial number: FOC15123GN8

Number of supported simultaneous BSSID on Dot11Radio0: 16

Carrier Set: EMEA (EU) (-E)

Uniform Spreading Required: No

Configured Frequency: 2462 MHz  Channel 11

Allowed Frequencies: 2412(1) 2417(2) 2422(3) 2427(4) 2432(5) 2437(6) 2442(7) 244

7(8) 2452(9) 2457(10) 2462(11) 2467(12) 2472(13)

Listen Frequencies: 2412(1) 2417(2) 2422(3) 2427(4) 2432(5) 2437(6) 2442(7) 2447

(8) 2452(9) 2457(10) 2462(11) 2467(12) 2472(13) 2484(14)

Beacon Flags: 0, Interface Flags 60109, Interface Events 0, Mode 9; Beacons are

disabled; Probes are disabled

Configured Power: 5 dBm (level 5)

Active power levels by rate

     1.0 to 54.0-d, 5   dBm

  OffChnl Power: 16, Rate 1.0

Allowed Power Levels:  -1 2 5 8 11 14 17

Allowed Client Power Levels: 2 5 8 11 14 17

Receive Antennas : right-a left-b

Transmit Antennas : right-a left-b, cck single, ofdm all

Antenna: internal, Gain: Allowed 8, Reported 0, Configured 0, In Use 8

AP2894.0fd6.c264#more flash:event.log

*Feb 9 08:00:48.001: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xC0

A86E52, load = 7..

*Feb 9 08:00:48.001: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Feb 9 08:00:48.002: %CAPWAP-3-EVENTLOG: Setting time to 08:00:48 UTC Feb 9 2012

*Feb 9 08:00:48.002: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip

: 192.168.110.82 peer_port: 5246

*Feb 9 08:00:48.002: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Feb 9 08:00:48.002: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb 9 08:00:49.162: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully

peer_ip: 192.168.110.82 peer_port: 5246

*Feb 9 08:00:49.163: %CAPWAP-3-EVENTLOG: Dtls Session Established with the AC 19

2.168.110.82,port= 5246

*Feb 9 08:00:49.163: %CAPWAP-3-EVENTLOG: CAPWAP State: Join.

*Feb 9 08:00:49.163: %CAPWAP-3-EVENTLOG: Join request: version=117496832

*Feb 9 08:00:49.163: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117496832

*Feb 9 08:00:49.163: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payloa

d

*Feb 9 08:00:49.163: %CAPWAP-3-EVENTLOG: Sending Join Request Path MTU payload,

Length 1376

*Feb 9 08:00:49.163: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.110.82

*Feb 9 08:00:49.163: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb 9 08:00:49.303: %CAPWAP-3-EVENTLOG: Join Response from 192.168.110.82

*Feb 9 08:00:49.303: %CAPWAP-3-EVENTLOG: PTMU : Setting MTU to : 1485

*Feb 9 08:00:49.303: %CAPWAP-3-EVENTLOG: Starting Post Join timer

*Feb 9 08:00:49.303: %CAPWAP-3-EVENTLOG: CAPWAP State: Configure.

*Feb 9 08:00:49.303: %CAPWAP-3-EVENTLOG: reboot reason flag 21

*Feb 9 08:00:49.303: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb 9 08:00:49.303: %CAPWAP-3-EVENTLOG: Configuration Status sent to 192.168.11

0.82

*Feb 9 08:00:49.303: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Feb 9 08:00:49.303: %CAPWAP-3-EVENTLOG: Current image is good. Connecting to th

e controller.

*Feb 9 08:00:49.309: %DTLS-5-ALERT: Received WARNING : Close notify alert from 1

92.168.110.82

*Feb 9 08:00:49.404: %CAPWAP-3-EVENTLOG: Ignoring callback message Close alert r

eceived..

*Feb 9 08:00:49.411: %DTLS-5-PEER_DISCONNECT: Peer 192.168.110.82 has closed con

nection.

*Feb 9 08:00:49.413: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.

168.110.82:5246

*Feb 9 08:00:49.449: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restart

ing capwap state machine.

*Feb 9 08:00:49.449: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 9 08:00:49.449: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 9 08:00:49.450: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to ad

ministratively down

*Feb 9 08:00:49.450: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to ad

ministratively down

*Feb 9 08:00:49.450: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending cha

nnel and power levels info.192:168:110:82

*Feb 9 08:00:49.450: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Feb 9 08:00:49.450: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to re

set

*Feb 9 08:00:49.451: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending cha

nnel and power levels info.192:168:110:82

*Feb 9 08:00:49.451: %CAPWAP-3-EVENTLOG: Starting Discovery.Initializing discove

ry latency in discovery responses

*Feb 9 08:00:49.451: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Feb 9 08:00:49.451: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117496832

*Feb 9 08:00:49.451: %CAPWAP-3-EVENTLOG: Discovery Request sent to 192.168.254.8

1 with discovery type set to 3

*Feb 9 08:00:49.451: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117496832

*Feb 9 08:00:49.451: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.2

55 with discovery type set to 0

*Feb 9 08:00:49.451: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 9 08:00:49.451: %CAPWAP-3-EVENTLOG: Discovery Response from 192.168.254.81

*Feb 9 08:00:49.457: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending cha

nnel and power levels info.192:168:110:82

*Feb 9 08:00:49.458: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Feb 9 08:00:49.470: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to re

set

*Feb 9 08:00:49.483: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending cha

nnel and power levels info.192:168:110:82

*Feb 9 08:00:49.484: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 9 08:01:00.002: %CAPWAP-3-EVENTLOG: Selected MWAR 'Cisco_68:60:c7' (index 0

).

*Feb 9 08:01:00.002: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Feb 9 08:01:00.002: %CAPWAP-3-EVENTLOG: Go join a capwap controller

*Feb 9 08:01:00.002: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xC0

A86E52, load = 7..

*Feb 9 08:01:00.002: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Feb 9 08:01:00.002: %CAPWAP-3-EVENTLOG: Setting time to 08:01:00 UTC Feb 9 2012

*Feb 9 08:01:00.002: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip

: 192.168.110.82 peer_port: 5246

*Feb 9 08:01:00.002: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Feb 9 08:01:00.002: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb 9 08:01:01.159: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully

peer_ip: 192.168.110.82 peer_port: 5246

*Feb 9 08:01:01.159: %CAPWAP-3-EVENTLOG: Dtls Session Established with the AC 19

2.168.110.82,port= 5246

*Feb 9 08:01:01.159: %CAPWAP-3-EVENTLOG: CAPWAP State: Join.

*Feb 9 08:01:01.159: %CAPWAP-3-EVENTLOG: Join request: version=117496832

*Feb 9 08:01:01.159: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117496832

*Feb 9 08:01:01.159: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payloa

d

*Feb 9 08:01:01.159: %CAPWAP-3-EVENTLOG: Sending Join Request Path MTU payload,

Length 1376

*Feb 9 08:01:01.159: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.110.82

*Feb 9 08:01:01.159: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb 9 08:01:01.298: %CAPWAP-3-EVENTLOG: Join Response from 192.168.110.82

*Feb 9 08:01:01.298: %CAPWAP-3-EVENTLOG: PTMU : Setting MTU to : 1485

*Feb 9 08:01:01.298: %CAPWAP-3-EVENTLOG: Starting Post Join timer

*Feb 9 08:01:01.298: %CAPWAP-3-EVENTLOG: CAPWAP State: Configure.

*Feb 9 08:01:01.298: %CAPWAP-3-EVENTLOG: reboot reason flag 21

*Feb 9 08:01:01.298: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb 9 08:01:01.298: %CAPWAP-3-EVENTLOG: Configuration Status sent to 192.168.11

0.82

*Feb 9 08:01:01.298: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Feb 9 08:01:01.298: %CAPWAP-3-EVENTLOG: Current image is good. Connecting to th

e controller.

*Feb 9 08:01:01.304: %DTLS-5-ALERT: Received WARNING : Close notify alert from 1

92.168.110.82

*Feb 9 08:01:01.399: %CAPWAP-3-EVENTLOG: Ignoring callback message Close alert r

eceived..

*Feb 9 08:01:01.406: %DTLS-5-PEER_DISCONNECT: Peer 192.168.110.82 has closed con

nection.

*Feb 9 08:01:01.407: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.

168.110.82:5246

*Feb 9 08:01:01.443: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restart

ing capwap state machine.

*Feb 9 08:01:01.443: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 9 08:01:01.443: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 9 08:01:01.443: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to ad

ministratively down

*Feb 9 08:01:01.443: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to ad

ministratively down

*Feb 9 08:01:01.444: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending cha

nnel and power levels info.192:168:110:82

*Feb 9 08:01:01.444: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to re

set

*Feb 9 08:01:01.444: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending cha

nnel and power levels info.192:168:110:82

*Feb 9 08:01:01.444: %CAPWAP-3-EVENTLOG: Starting Discovery.Initializing discove

ry latency in discovery responses

*Feb 9 08:01:01.444: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Feb 9 08:01:01.444: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117496832

*Feb 9 08:01:01.444: %CAPWAP-3-EVENTLOG: Discovery Request sent to 192.168.254.8

1 with discovery type set to 3

*Feb 9 08:01:01.445: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117496832

*Feb 9 08:01:01.445: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.2

55 with discovery type set to 0

*Feb 9 08:01:01.445: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 9 08:01:01.445: %CAPWAP-3-EVENTLOG: Discovery Response from 192.168.254.81

*Feb 9 08:01:01.450: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending cha

nnel and power levels info.192:168:110:82

*Feb 9 08:01:01.451: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Feb 9 08:01:01.463: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to re

set

*Feb 9 08:01:01.476: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending cha

nnel and power levels info.192:168:110:82

*Feb 9 08:01:01.477: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Feb 9 08:01:12.001: %CAPWAP-3-EVENTLOG: Selected MWAR 'Cisco_68:60:c7' (index 0

).

*Feb 9 08:01:12.001: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Feb 9 08:01:12.001: %CAPWAP-3-EVENTLOG: Go join a capwap controller

*Feb 9 08:01:12.001: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xC0

A86E52, load = 7..

*Feb 9 08:01:12.001: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Feb 9 08:01:12.002: %CAPWAP-3-EVENTLOG: Setting time to 08:01:12 UTC Feb 9 2012

*Feb 9 08:01:12.002: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip

: 192.168.110.82 peer_port: 5246

*Feb 9 08:01:12.002: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Feb 9 08:01:12.002: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Feb 9 08:01:13.162: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully

peer_ip: 192.168.110.82 peer_port: 5246

*Feb 9 08:01:13.162: %CAPWAP-3-EVENTLOG: Dtls Session Established with the AC 19

2.168.110.82,port= 5246

*Feb 9 08:01:13.162: %CAPWAP-3-EVENTLOG: CAPWAP State: Join.

*Feb 9 08:01:13.162: %CAPWAP-3-EVENTLOG: Join request: version=117496832

*Feb 9 08:01:13.163: %CAPWAP-3-EVENTLOG: WTP descriptor: version=117496832

*Feb 9 08:01:13.163: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payloa

d

*Feb 9 08:01:13.163: %CAPWAP-3-EVENTLOG: Sending Join Request Path MTU payload,

Length 1376

*Feb 9 08:01:13.163: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.110.82

*Feb 9 08:01:13.163: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Feb 9 08:01:13.302: %CAPWAP-3-EVENTLOG: Join Response from 192.168.110.82

*Feb 9 08:01:13.302: %CAPWAP-3-EVENTLOG: PTMU : Setting MTU to : 1485

*Feb 9 08:01:13.302: %CAPWAP-3-EVENTLOG: Starting Post Join timer

*Feb 9 08:01:13.302: %CAPWAP-3-EVENTLOG: CAPWAP State: Configure.

*Feb 9 08:01:13.302: %CAPWAP-3-EVENTLOG: reboot reason flag 21

*Feb 9 08:01:13.302: %CAPWAP-3-EVENTLOG: Sending packet to AC

*Feb 9 08:01:13.302: %CAPWAP-3-EVENTLOG: Configuration Status sent to 192.168.11

0.82

*Feb 9 08:01:13.302: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Feb 9 08:01:13.303: %CAPWAP-3-EVENTLOG: Current image is good. Connecting to th

e controller.

*Feb 9 08:01:13.308: %DTLS-5-ALERT: Received WARNING : Close notify alert from 1

92.168.110.82

*Feb 9 08:01:13.403: %CAPWAP-3-EVENTLOG: Ignoring callback message Close alert r

eceived..

*Feb 9 08:01:13.409: %DTLS-5-PEER_DISCONNECT: Peer 192.168.110.82 has closed con

nection.

*Feb 9 08:01:13.410: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.

168.110.82:5246

*Feb 9 08:01:13.447: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restart

ing capwap state machine.

*Feb 9 08:01:13.447: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 9 08:01:13.447: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Feb 9 08:01:13.447: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to ad

ministratively down

*Feb 9 08:01:13.447: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to ad

ministratively down

*Feb 9 08:01:13.447: %CAPWAP-3-EVENTLOG: CAPWAP state not up.  Abort sending cha

nnel and power levels info.192:168:110:82

*Feb 9 08:01:13.447: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to re

set

AP2894.0fd6.c264#

0 Helpful

Go to solution
nikhilcherian
Level 5
Level 5
In response to fgasimzade

‎02-09-2012 12:59 AM

Can you disable the A and R domains in the wireless controller, if not required

0 Helpful

Go to solution
fgasimzade
Level 4
Level 4
In response to nikhilcherian

‎02-09-2012 01:04 AM

I can disable R, but we've got A for other APs

One more thing, when I manually no shutdown interfaces on AP, I still get Admin Status Disabled on Controller

0 Helpful

Go to solution
fgasimzade
Level 4
Level 4
In response to fgasimzade

‎02-09-2012 01:00 AM

I also get

NVRAM Verification Failed

when I try to save config

0 Helpful

Go to solution
fgasimzade
Level 4
Level 4
In response to fgasimzade

‎02-09-2012 01:06 AM

Thank you guys for your help, I enabled Admin Status from the WLC, everything works fine now!

0 Helpful

Go to solution
nikhilcherian
Level 5
Level 5
In response to fgasimzade

‎02-09-2012 01:08 AM

Happy to see that the issue was resolved

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card