1131 not initiating join process

Unanswered Question
Jul 13th, 2009

Hello It's Me Again ...

I just configured a 4402 WLC and decided to plug in 2 APs to see if they would come up ... I got the following messages after I debugged the lwapp events ...

(Cisco Controller) >Mon Jul 13 17:02:38 2009: 00:23:33:bc:73:10 Received LWAPP DISCOVERY REQUEST from AP 00:23:33:bc:73:10 to ff:ff:ff:ff:ff:ff on port '29'

Mon Jul 13 17:02:38 2009: LWAPP header parsing for packet from AP ff:ff:ff:ff:ff:ff, next Hop 00:23:33:bc:73:10

Mon Jul 13 17:02:38 2009: ApNextHop - AP ff:ff:ff:ff:ff:ff, next Hop 00:23:33:bc:73:10

Mon Jul 13 17:02:38 2009: 00:23:33:bc:73:10 LWAPP Discovery Request AP Software Version: 0x3003300

Mon Jul 13 17:02:38 2009: 00:23:33:bc:73:10 Successful transmission of LWAPP Discovery Response to AP 00:23:33:bc:73:10 on port 29

Mon Jul 13 17:02:56 2009: 00:23:04:b7:87:96 Received LWAPP DISCOVERY REQUEST from AP 00:23:04:b7:87:96 to ff:ff:ff:ff:ff:ff on port '29'

Mon Jul 13 17:02:56 2009: LWAPP header parsing for packet from AP ff:ff:ff:ff:ff:ff, next Hop 00:23:04:b7:87:96

Mon Jul 13 17:02:56 2009: ApNextHop - AP ff:ff:ff:ff:ff:ff, next Hop 00:23:04:b7:87:96

Mon Jul 13 17:02:56 2009: 00:23:04:b7:87:96 LWAPP Discovery Request AP Software Version: 0x3003300

Mon Jul 13 17:02:56 2009: 00:23:04:b7:87:96 Successful transmission of LWAPP Discovery Response to AP 00:23:04:b7:87:96 on port 29

To me appears that they are finding the controller but the join process isn't being initiated. The APs and WLC are in the same subnet and vlan so I have configured the WLC as Layer 2. The only thing that is different from other installs I have done is that this customer has HP Switches.

Any thoughts would be great ... Thanks!!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 2.3 (3 ratings)
Loading.
Leo Laohoo Mon, 07/13/2009 - 16:21

1. Has the LAP been used in a previous deployment before?

2. Can the LAP ping the WLC Managmenet IP Address?

If "Yes" to #2 question, console into the LAP and in enable mode, type the command "lwap ap controller ip address "

Hope this helps.

mjohnson1914 Mon, 07/13/2009 - 18:52

The LAP's have not be previously deployed as this is a complete new install.

I am not sure if the LAP can ping the Management IP but I will check that in the morning ... but my question is why no errors ... I did a debug on errors and got nothing ... I did a sh ap join stats detailed on the 2 MAC Addresses that I connected and got no errors so I am truly puzzled as too why the APs are not attempting to initiate the join process ... I am thinking that is may be a DHCP issue so I am starting there tomorrow

garrsmith Tue, 07/14/2009 - 01:44

How are the switchports configured on the HP switches? I have known the HP switches to be different to cisco with VLAN tagging/trunking. It might be worth trying a few different combinations on the switchports.. Also, have you tried priming the AP with an IP address and a Controller?

mjohnson1914 Tue, 07/14/2009 - 03:52

As far as I know the HP Switches are tagged with the same vlan the WLC is in. I don't have access to them but is it something else I should be asking the customer to check or do in regard to the HP Switches ... again I have only worked with Cisco Switches when it has came to Wireless

mat.edwards Tue, 07/14/2009 - 04:22

Cisco 1131 does not support Layer 2 mode. Change your WLC to Layer 3, reboot and the 1131 will join.

Cheers

Mat

mjohnson1914 Tue, 07/14/2009 - 05:21

Thanks for that tidbit ... I didn't know that so luckily when I reconfigured the WLC because I thought it may be an XML issue from me downgrading to 4.2.205 I left the mode as LAYER 3.

But, the problem was that the Tech here didn't exclude the Mang Interface and AP Mang Interface from the DHCP scope so the APs were grabbing those IPs hence causing them to error once a duplicate IP was found.

Thanks for all the suggestions

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