LWAP Join issues

Unanswered Question

Hi,

Getting the following error message when I try to join a LWAP to my controllers in california. it then joins my controller in virginia and works...

any help would be appreciated.

Set Transport Address: no more AP manager IP addresses

remain

%LWAPP-3-CLIENTERRORLOG: Join Timer: did not recieve join response (controller -

xx1-cr-wism1)

%LWAPP-3-CLIENTERRORLOG: Set Transport Address: no more AP manager IP addresses

remain

%LWAPP-5-CHANGED: LWAPP changed state to CFG

%LWAPP-5-CHANGED: LWAPP changed state to DOWN

%LWAPP-5-CHANGED: LWAPP changed state to UP

%LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

%LWAPP-3-CLIENTEVENTLOG: AP has joined controller yy-cr-wism2

%LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

%WIDS-6-ENABLED: IDS Signature is loaded and enabled

%LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
dancampb Tue, 06/23/2009 - 10:54

You could be running into a fragmentation issue. Make sure that there aren't any fragments less the 32 bytes. If there are adjust the MTU on the link so that the frags are larger.

Leo Laohoo Wed, 06/24/2009 - 15:16

Hi Jason,

Do you want the AP to join the California WLC? If this is so, you'll have to do the command in CLI (because I don't know what is your firmware version).

Go to the WLC where the AP has joined and type the command:

config ap secondary-base Virginia_controller_name Cisco_AP Management_ip_address

config ap primary-base California_controller_name Cisco_AP Management_ip_address

Give the AP about 10 seconds and it should "swing" to the California WLC with Virginia WLC acting as a secondary WLC (in case of failure).

Hope this helps.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode