cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1914
Views
0
Helpful
10
Replies

1142 N series AP is not registering in the controller

dinesh1977
Level 1
Level 1

Hi ,

I am trying to connect few 1142 N series AP to my existing controller 4404. I have upgrade the code of the WLC (AIR-WLC4400-K9-6-0-182-0.aes) . But iam getting the following error messages .

*Oct 6 15:28:47.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.97.3 peer_port: 5246

*Oct 6 15:28:47.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Oct 6 15:28:47.765: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.97.3 peer_port: 5246

*Oct 6 15:28:47.765: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.97.3

*Oct 6 15:28:47.765: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Oct 6 15:28:47.845: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Oct 6 15:28:47.845: %CAPWAP-3-ERRORLOG: Starting config timer

*Oct 6 15:28:47.957: %LWAPP-3-CLIENTERRORLOG: Operator changed mode for 802.11g. Rebooting.

*Could somebody help me to solve the issue ?

Rgds

Dinesh

10 Replies 10

Leo Laohoo
Hall of Fame
Hall of Fame

%Error opening lwapp:/c1140 (Incorrect Login/Password)

Console into the LWAP and in enable mode use the command "clear lwapp private" and reload the LWAP.

Hi Thanks for the reply .But iam not able to execute the command

I am continously getting the messages . Ap prompt is not comming .

Rgds

Dinesh

Try disconnecting the AP from the network. Assuming you are using PoE, then you'll need to find a power source for the AP (perhaps a standalone switch not connected to the network).

You'll need to hit the enter key to get the prompt to show up.

The 4400 controller is running code that supports the 1140 (and CAPWAP), right?

Hi Robert

I upgradrd the image to 6.0.182.0 .

I have disconnected the Ap from the network connected using power adapter. But still I am getting the error messages logs and is not showing the Ap prompt:

Rgds

Dinesh

Before trying the stuff below, you might want to connect your AP back to the network, go to the controller CLI and issue the following command:

debug capwap detail enable

Watch watch messages are displayed when the AP fails to join.

--------------------------------

I can't my docs on how to do this, so I can't be sure these instructions are corrent...

You may want to try and clear all the LWAPP/CAPWAP configuration that the AP has learned. While holding in the mode button, apply power to the AP (release the mode button after about 5 seconds). Via the console port, you should be able to get to a command prompt. Go to enable mode (password should be "Cisco" or "cisco" [without the quotes]. Once in enable mode, try issuing a "clear lwapp private-config" command. If that doesn't work, try working through the CLI help to see what clear options you have. You then might want to try and manually set up the AP. Sample commands to give it an IP address and point it towards a WLC are below.

#clear lwapp private-config

#lwapp ap hostname mynewap

#lwapp ap ip address 10.77.244.199 255.255.255.224

#lwapp ap ip default-gateway 10.77.244.220

#lwapp ap controller ip address 172.16.1.50

Hi Rob,

"But iam not able to execute the command"

This got me stumped. How come it's possible to console into the AP but can't type any commands. Bizarre.

Yeah, that's a new one for me. I hope that either the steps above fix the problem, the hardware is bad, or we hear a loud "Doh!".

Hi Robert,

The issue is resolved .. I have done 3 -4 times factory reset and finally it goy asscociated to one of the controller ...

Thanks

Dinesh

That's great news - nice work!

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: