Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

LAP 1252 can't join WLC4404

Hello,

I use dhcp option 43 on Linux dhcp server

DHCP config like Cisco recommends:

allow bootp;

option space Cisco_LWAPP_AP;

option Cisco_LWAPP_AP.server-address code 43 = string;

shared-network wifi

{

subnet 10.16.41.0 netmask 255.255.255.0 {

option routers 10.16.41.1;

option subnet-mask 255.255.255.0;

default-lease-time 14400;

max-lease-time 172800;

range dynamic-bootp 10.16.41.100 10.16.41.200;

class "Cisco AP c1250" {

match if option vendor-class-identifier = "Cisco AP c1250";

option vendor-class-identifier "Cisco AP c1250";

vendor-option-space Cisco_LWAPP_AP;

option Cisco_LWAPP_AP.server-address f1:04:0a:10:28:04; }

Controller debug output:

*Apr 10 09:40:20.572: <<<< Start of CAPWAP Packet >>>>

*Apr 10 09:40:20.572: CAPWAP Control mesg Recd from 10.16.41.185, Port 1599

*Apr 10 09:40:20.572: HLEN 4, Radio ID 0, WBID 1

*Apr 10 09:40:20.572: Msg Type : CAPWAP_DISCOVERY_REQUEST

*Apr 10 09:40:20.572: Msg Length : 29

*Apr 10 09:40:20.572: Msg SeqNum : 0

*Apr 10 09:40:20.572:

*Apr 10 09:40:20.572: Type : CAPWAP_MSGELE_DISCOVERY_TYPE, Length 1

*Apr 10 09:40:20.572: Discovery Type : CAPWAP_DISCOVERY_TYPE_UNKNOWN

*Apr 10 09:40:20.572:

*Apr 10 09:40:20.572: Type : CAPWAP_MSGELE_WTP_FRAME_TUNNEL, Length 1

*Apr 10 09:40:20.572: WTP Frame Tunnel Mode : NATIVE_FRAME_TUNNEL_MODE

*Apr 10 09:40:20.572:

*Apr 10 09:40:20.572: Type : CAPWAP_MSGELE_WTP_MAC_TYPE, Length 1

*Apr 10 09:40:20.572: WTP Mac Type : SPLIT_MAC

*Apr 10 09:40:20.572:

*Apr 10 09:40:20.572: Type : CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, Length 10

*Apr 10 09:40:20.572: Vendor Identifier : 0x00409600

*Apr 10 09:40:20.572:

IE : UNKNOWN IE 207

*Apr 10 09:40:20.572: IE Length : 4

*Apr 10 09:40:20.572: Decode routine not available, Printing Hex Dump

*Apr 10 09:40:20.572: 00000000: 03 01 00 01 ....

*Apr 10 09:40:20.572: <<<< End of CAPWAP Packet >>>>

AP debug output:

*Mar 1 00:11:49.767: <<<< Start of CAPWAP Packet >>>>

*Mar 1 00:11:49.767: CAPWAP Control mesg Sent to 255.255.255.255, Port 5246

*Mar 1 00:11:49.767: Msg Type : CAPWAP_DISCOVERY_REQUEST

*Mar 1 00:11:49.767: Msg Length : 29

*Mar 1 00:11:49.767: Msg SeqNum : 0

*Mar 1 00:11:49.767:

*Mar 1 00:11:49.767: Type : CAPWAP_MSGELE_DISCOVERY_TYPE, Length 1

*Mar 1 00:11:49.767: Discovery Type : CAPWAP_DISCOVERY_TYPE_UNKNOWN

*Mar 1 00:11:49.767:

*Mar 1 00:11:49.767: Type : CAPWAP_MSGELE_WTP_FRAME_TUNNEL, Length 1

*Mar 1 00:11:49.767: WTP Frame Tunnel Mode : NATIVE_FRAME_TUNNEL_MODE

*Mar 1 00:11:49.767:

*Mar 1 00:11:49.767: Type : CAPWAP_MSGELE_WTP_MAC_TYPE, Length 1

*Mar 1 00:11:49.767: WTP Mac Type : SPLIT_MAC

*Mar 1 00:11:49.767:

*Mar 1 00:11:49.767: Type : CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, Length 10

*Mar 1 00:11:49.767: Vendor Identifier : 0x00409600

*Mar 1 00:11:49.767:

*Mar 1 IE : UNKNOWN IE 207

*Mar 1 00:11:49.767: IE Length : 4

*Mar 1 00:11:49.767: Decode routine not available, Printing Hex Dump

*Mar 1 00:11:49.767: 03 01 00 01 00

*Mar 1 00:11:49.767: <<<< End of CAPWAP Packet >>>>

*Mar 1 00:13:59.767: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Mar 1 00:14:09.767: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Mar 1 00:14:09.767: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:14:09.767: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

When AP IP settings are configured manually everything is correct but with DCP no :(

Have you got any ideas

Thanks for help.

Regards

maniek

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Gold

Re: LAP 1252 can't join WLC4404

There's only one reason why you get "Command Disabled": The AP is running CAPWAP/LWAP Image and not the Lite or "RCV" image.

You have two options:

1. Relocate the AP and connect it to the same VLAN segment and let the AP join the WLC before re-deploying it back; or

2. Console into the AP. Do a "dir" in enable mode. Check if you have two different IOS. One IOS should have a prefix of "RCV" and the other one won't have one. If you do have both, then delete (delete /f /r flash:) the filename that DOES NOT HAVE the RCV prefix. Reload the AP and while the AP is searching for a WLC, type in the command "lwapp ap controller ip address " command again.

Hope this helps.

10 REPLIES
Hall of Fame Super Gold

Re: LAP 1252 can't join WLC4404

Hi Maniek,

My apologies but I'm trying to understand what your problem is. Is your problem:

1. AP can't get DHCP IP Address; or

2. AP can't join WLC

New Member

Re: LAP 1252 can't join WLC4404

sorry, I forgot explain:

AP get IP from DHCP Server

10.16.41.185

but can't join WLC. WLC IP address is put via DHCP option 43

option Cisco_LWAPP_AP.server-address f1:04:0a:10:28:04; (10.16.40.4)

Thanks

maniek

Hall of Fame Super Gold

Re: LAP 1252 can't join WLC4404

HI Maniek,

Can the AP ping the management IP Address of the WLC? If yes, then console into the AP and in enable mode (NOT configuration mode), type the following command "lwapp ap controller ip address ".

In the future, before deploying your AP into the "wild", prime the AP by connecting it to the same VLAN segment of the WLC. Priming an AP will allow the AP to join the WLC and create a list of joined WLC which is stored into the NVRAM of the AP.

I've deployed >150 AP's nation-wide and because I prime them, I did away with configuring the DHCP with Option 40/62.

New Member

Re: LAP 1252 can't join WLC4404

AP0021.a040.237e#lwapp ap controller ip address 10.16.40.4

ERROR!!! Command is disabled.

AP can ping WLC Mgmt int.

I try switch the AP to WLC VLAN,clear all config, and then set IP manually.

What do you think?

regards

maniek

Re: LAP 1252 can't join WLC4404

Quick question:

Do you have any other 1250's using DHCP that are able to join the controller?

Do you have other APs (1240, 1230, etc.) that are able to join the controller?

If you only have other (non-1250) AP's joining, then you may not have added the 1250-specific strings to your DHCP Option 43 settings

If you have other 1250's that are able to join via DHCP, then you may want to erase the 1250's config, manually reload the 1250 firmware (download it from Cisco.com), and try again.

Bronze

Re: LAP 1252 can't join WLC4404

It would be a little difficult to troubleshoot DHCP option 43. To me, the DNS resolution is much easier. If you just want the AP to register with the WLC, can you try with DNS resolution? If that works, it can also verify there is no communication issue between your AP and WLC. Then the issue is at DHCP option 43 part.

Hall of Fame Super Gold

Re: LAP 1252 can't join WLC4404

There's only one reason why you get "Command Disabled": The AP is running CAPWAP/LWAP Image and not the Lite or "RCV" image.

You have two options:

1. Relocate the AP and connect it to the same VLAN segment and let the AP join the WLC before re-deploying it back; or

2. Console into the AP. Do a "dir" in enable mode. Check if you have two different IOS. One IOS should have a prefix of "RCV" and the other one won't have one. If you do have both, then delete (delete /f /r flash:) the filename that DOES NOT HAVE the RCV prefix. Reload the AP and while the AP is searching for a WLC, type in the command "lwapp ap controller ip address " command again.

Hope this helps.

Re: LAP 1252 can't join WLC4404

If the snippet below is how you configured your Linux dhcp option 43, then that may be part of the problem (I am not a Linux user in any way). In our DHCP option 43 settings (Windows box), we specify the server's IP address, not MAC address.

Upload the console output from the AP as it boots and tries to find a controller to join.

class "Cisco AP c1250" {

match if option vendor-class-identifier = "Cisco AP c1250";

option vendor-class-identifier "Cisco AP c1250";

vendor-option-space Cisco_LWAPP_AP;

option Cisco_LWAPP_AP.server-address f1:04:0a:10:28:04; }

New Member

Re: LAP 1252 can't join WLC4404

I found fine explanaition about DHCP option 43 for Cisco AP on Linux server:

http://blog.pressure.net.nz/2009/01/cisco-wireless-lan-controllers-and-dhcp-option-43/

Robert,

option Cisco_LWAPP_AP.server-address f1:04:0a:10:28:04;

it's hex representation of the WLC IP address, more on this page:

http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00808714fe.shtml#backinfo

Re: LAP 1252 can't join WLC4404

Thank you for clearing that up for me.

I can't exactly tell from the messages in this thread, so forgive me if I'm asking a question that has already been asked/answered: has the AP in question, or any 1250 AP, ever joined to your controller (via DHCP or otherwise)?

You must be running a version of code the supports the 1250 (4.2.61.0 or later)

Have you followed the steps outlined in the troubleshooting document?

http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml

There are good instructions in there about working through DHCP issues.

1626
Views
0
Helpful
10
Replies
CreatePlease to create content