Wireless deployement Project in HQ and remote Office

csco10865546 · ‎08-02-2011

Hi Guys,I am new to wireless project deployment and would like assistance on this please :

I am trying to deploy Wireless Lan Controller 5508 at the head office in Stevenage .The Stevenage Office will have about 8 access points connected to it while the other offices across Europe will have other access points in autonomous mode . I want to use the WLC in Stevenage to control all the access points including the ones remotely via the WAN link Connection to them.

I am wondering if I have to configure the Autonomous access points directly by consoling into them and setting all the parameters like dot11 radio,dhcp server ,etc or there is a way to boot them up and they locate the Controller and I manage and set everything up from it.

The WLC model is

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.98.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... N/A
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS

The Access point model and firmware version is

Product/Model Number : AIR-AP1142N-E-K9

Configuration register is 0xF.

Cisco IOS Software, C1140 Software (C1140-K9W7-M), Version 12.4(21a)JA1, RELEASE SOFTWARE (fc1).

This is a rough sketch of the drawing so it gives you an idea of what the whole project is about.

Regards,

KOlade

Surendra BG · ‎08-02-2011

Hi,

The remote APs should not be in autonomous if u wanna manage then using the WLC.. if u want so, then its called HREAP design.. the AP will join the WLC across the WAN and the time we lose the connectivity to the WLC from the remote location, the AP wil still serve the clients.. here is the deployment guide and config example guide for HREAP for same..

http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080736123.shtml

http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00807cc3b8.shtml

Please dont forget to rate the usefull posts!!

Regards

Surendra

Regards
Surendra BG

csco10865546 · ‎08-02-2011

Thanks Surendra,

I have downgraded it to the LWAP but still having troubles with errors below .

*Mar 1 01:06:26.984: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:06:36.984: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:06:36.984: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:06:36.984: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:06:46.917: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed sta te to down

*Mar 1 01:06:46.984: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:06:46.984: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:06:46.984: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:06:56.984: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:06:56.984: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:06:56.984: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:07:06.984: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:07:06.984: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:07:06.984: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:07:16.984: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:07:16.984: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:07:16.984: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:07:26.984: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:07:26.984: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:07:26.984: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:07:26.984: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:07:26.985: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:07:26.985: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:07:26.985: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:07:26.985: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:07:26.985: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:07:26.985: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:07:26.985: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:07:26.985: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:07:26.985: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:07:36.985: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:07:36.985: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:07:36.985: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:07:36.985: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:07:36.986: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:07:36.986: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:07:36.986: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:07:36.986: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:07:36.986: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:07:36.986: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:07:36.986: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:07:36.986: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:07:36.986: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:07:46.986: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:07:46.986: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:07:46.986: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:07:46.986: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:07:46.986: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:07:46.986: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:07:46.986: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:07:46.987: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:07:46.987: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:07:46.987: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:07:46.987: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:07:46.987: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:07:46.987: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:07:56.987: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:07:56.987: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:07:56.987: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:07:56.987: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:07:56.987: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:07:56.987: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:07:56.987: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:07:56.987: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:07:56.988: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:07:56.988: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:07:56.988: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:07:56.988: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:07:56.988: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:08:06.988: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:08:06.988: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:08:06.988: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:08:06.988: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:08:06.988: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:08:06.988: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:08:06.988: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:08:06.988: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:06.989: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:08:06.989: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:06.989: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:08:06.989: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:08:06.989: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:08:16.989: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:08:16.989: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:08:16.989: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:08:16.989: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:08:16.990: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:08:16.990: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:08:16.990: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:08:16.990: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:16.990: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:08:16.990: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:16.990: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:08:16.990: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:08:16.990: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:08:26.990: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:08:26.990: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:08:26.990: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:08:26.990: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar 1 01:08:26.995: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:08:26.995: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:08:26.995: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:08:26.995: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:08:26.995: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:26.995: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:08:26.995: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:26.995: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:08:26.995: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:08:26.995: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:08:36.995: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:08:36.995: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:08:36.995: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:08:36.995: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:08:36.996: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:08:36.996: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:08:36.996: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:08:36.996: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:36.996: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:08:36.996: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:36.996: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:08:36.996: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:08:36.996: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:08:46.996: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:08:46.996: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:08:46.996: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:08:46.997: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:08:46.997: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:08:46.997: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:08:46.997: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:08:46.997: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:46.997: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:08:46.997: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:46.997: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:08:46.997: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:08:46.997: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:08:56.997: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:08:56.997: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:08:56.997: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:08:56.997: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:08:56.997: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:08:56.997: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:08:56.997: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:08:56.997: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:56.998: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:08:56.998: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:08:56.998: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:08:56.998: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:08:56.998: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:09:06.998: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:09:06.998: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:09:06.998: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:09:16.998: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:09:16.998: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:09:16.998: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:09:26.998: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:09:26.998: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:09:26.998: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:09:36.998: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:09:36.998: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:09:36.998: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:09:46.998: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:09:46.998: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:09:46.998: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:09:56.998: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:09:56.998: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:09:56.998: CAPWAP_INFO: Event = 29 State = 2.

AP6400.f128.2a14#

*Mar 1 01:10:06.917: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed sta te to up

*Mar 1 01:10:06.998: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:10:06.998: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:10:06.998: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:10:16.998: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:10:16.998: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:10:16.998: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:10:26.998: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:10:26.998: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:10:26.998: CAPWAP_INFO: Event = 29 State = 2.

Not in Bound state.

*Mar 1 01:10:36.998: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:10:36.998: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:10:36.998: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:10:36.998: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar 1 01:10:47.000: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:10:47.000: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:10:47.000: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:10:47.000: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:10:47.000: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:10:47.000: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:10:47.000: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:10:47.000: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:10:47.001: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:10:47.001: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:10:47.001: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:10:47.001: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:10:47.001: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:10:57.001: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:10:57.001: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:10:57.001: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:10:57.001: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:10:57.001: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:10:57.001: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:10:57.001: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:10:57.001: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:10:57.002: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:10:57.002: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:10:57.002: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:10:57.002: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:10:57.002: CAPWAP_INFO: encodeLen = 73.

*Mar 1 01:11:07.002: CAPWAP_INFO: Discovery interval timer expired.

*Mar 1 01:11:07.002: CAPWAP_INFO: Received Capwap Timer Msg.

*Mar 1 01:11:07.002: CAPWAP_INFO: Event = 29 State = 2.

*Mar 1 01:11:07.002: CAPWAP_INFO: Discovery type: msgLength = 1.

*Mar 1 01:11:07.002: CAPWAP_INFO: Discovery Type message element len = 5.

*Mar 1 01:11:07.002: CAPWAP_INFO: msgLength = 40.

*Mar 1 01:11:07.002: CAPWAP_INFO: WTP Descriptor message element len = 49.

*Mar 1 01:11:07.002: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:11:07.003: CAPWAP_INFO: WTP Frame Tunnel Mode message element length = 54.

*Mar 1 01:11:07.003: CAPWAP_INFO: msgLength = 1.

*Mar 1 01:11:07.003: CAPWAP_INFO: WTP MAC Type message element len = 59.

*Mar 1 01:11:07.003: CAPWAP_INFO: Board data options len = 73.

*Mar 1 01:11:07.003: CAPWAP_INFO: encodeLen = 73.

Surendra BG · ‎08-02-2011

Hi,

The AP is not able to reach the WLC or not able to initiate the CAPWAP connectivity to the WLC..

*Mar 1 01:08:26.990: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

The above tells the same..

make sure from the AP ur able to reach the WLC managenent IP address..

Regards

Surendra

Regards
Surendra BG

csco10865546 · ‎08-02-2011

I connected same port io connected to it to a laptop and i can reach the WLC managemnt IP address.

I also noticed this error as well

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

*Mar 1 01:03:47.021: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER

*Mar 1 01:03:56.022: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER

eap profile lwapp_eap_profile

Any clue ?

4DigitCCIE · ‎08-02-2011

You need to give the AP a way to find the controller - DHCP option 43, DNS, etc.

http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml

-John

Surendra BG · ‎08-02-2011

run the below command on the WLC and paste it here..

debug mac addr

Debug capwap events enable

debug capwap errors enable

Lemme see whats happening!!

I guess this post was about getting the info on HREAP not on AP joining right??

Regards

Surendra

Regards
Surendra BG

csco10865546 · ‎08-02-2011

Yes it was initially for HReap before i realised i have to upgrade the autonomous access point to Lightweight.

I have done that now and just having issues with it joining the controller.

Here are the results of the debug commands

AP0007.7d65.2fed#debug capwap client event

CAPWAP Client EVENT display debugging is on

AP0007.7d65.2fed#debug capwap client error

CAPWAP Client ERROR display debugging is on

AP0007.7d65.2fed#

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

*Mar 1 00:34:37.910: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:34:37.910: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:34:43.910: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup

*Mar 1 00:34:46.910: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:34:46.910: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:34:56.910: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:34:56.910: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:35:02.910: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup

*Mar 1 00:35:05.910: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:35:05.910: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:35:15.910: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:35:15.910: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:35:21.910: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup

*Mar 1 00:35:24.910: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:35:34.910: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:35:34.910: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:35:40.910: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup

*Mar 1 00:35:43.910: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:35:53.910: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:35:53.910: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:35:59.910: %CAPWAP-3-EVENTLOG: Forcing AP to obtain IP address using DHCP

*Mar 1 00:35:59.910: %CAPWAP-5-STATIC_TO_DHCP_IP: Could not discover WLC using static IP. Forcing AP to use DHCP.

*Mar 1 00:35:59.923: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:36:09.923: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:36:09.923: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:36:09.923: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:36:19.923: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:36:19.923: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:36:19.923: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:36:29.923: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:36:29.923: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:36:29.923: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:36:39.924: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:36:39.924: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:36:39.924: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:36:49.925: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:36:49.925: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:36:49.925: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:36:59.926: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:36:59.926: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:36:59.927: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:37:09.927: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:37:09.927: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:37:09.927: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:37:19.927: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:37:19.927: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:37:19.927: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:37:19.928: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:37:29.928: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:37:29.928: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:37:29.928: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:37:29.929: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:37:39.929: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:37:39.929: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:37:39.929: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:37:39.930: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:37:49.930: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:37:49.930: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:37:49.930: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:37:49.930: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:37:59.931: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:37:59.931: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:37:59.931: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:37:59.931: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:38:09.932: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:38:09.932: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:38:09.932: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:38:09.933: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

Not in Bound state.

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

*Mar 1 00:38:19.933: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:38:19.933: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:38:19.933: %CAPWAP-5-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar 1 00:38:19.933: %CAPWAP-3-EVENTLOG: Discovery failed 12 times. Release/Renew DHCP

*Mar 1 00:38:19.938: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:38:19.938: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:38:29.938: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:38:29.938: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:38:29.938: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:38:29.939: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:38:39.939: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:38:39.939: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:38:39.939: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:38:39.940: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:38:49.940: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:38:49.940: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:38:49.940: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

*Mar 1 00:38:49.941: %CAPWAP-3-EVENTLOG: WTP descriptor: version=0

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

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

*Mar 1 00:38:59.941: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:38:59.941: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:38:59.941: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:39:09.942: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:39:09.942: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:39:09.942: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:39:19.942: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:39:19.942: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:39:19.942: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:39:29.943: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:39:29.943: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:39:29.943: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:39:39.944: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:39:39.944: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:39:39.944: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:39:49.945: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:39:49.945: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:39:49.945: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:39:59.946: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:39:59.946: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:39:59.946: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:40:09.946: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:40:09.946: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:40:09.946: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

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

*Mar 1 00:40:19.947: %CAPWAP-3-EVENTLOG: Starting Discovery.

*Mar 1 00:40:19.947: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Mar 1 00:40:19.947: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 0.0.0.0, type 1.

Surendra BG · ‎08-02-2011

Whats the WLC code?? are u sure the AP manager is configured on the WLC??

Regards

Surendra

Regards
Surendra BG

csco10865546 · ‎08-02-2011

The WLC model is

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.98.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... N/A
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS

I saw the option that you dont have to create an AP manager on the 5508 as the management interface can act as one .

So I am using the management interface and it has the option of you enabling dynamic AP management that i ticked as well

Surendra BG · ‎08-02-2011

oops.. sory, i dint know that we are using 5508!! no need to go for an AP manager Int.. Now.. from the AP are we able to ping the management interface IP address??

Regards

Surendra

Regards
Surendra BG

csco10865546 · ‎08-02-2011

Unfortunately,I am unable to ping the management interface from the AP but i can ping it from any other laptops or devices on the network

Leo Laohoo · ‎08-02-2011

Unfortunately,I am unable to ping the management interface from the AP

Maybe the AP doesn't have a valid IP address?