cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
14843
Views
0
Helpful
8
Replies

error on AP

cisco
Level 1
Level 1

  I got following on fewer APs while other APs are working fine with same OS and WLC kindly guide

capwap ap ip address 152.109.100.11 255.255.255.224
You should configure Domain and Name Server from controller CLI/GUI.
amt_pkwalls1240AP011#capwap ap ip default-gateway 152.109.100.30
amt_pkwalls1240AP011#capwap ap primary-base amt_pkKarwlc01 145.17.63.65
amt_pkwalls1240AP011#capwap ap secondary-base amt_pklhrwlc01 145.17.63.69


*Mar  1 00:02:40.409: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Mar  1 00:02:40.409: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.
*Mar  1 00:02:40.409: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Mar  1 00:02:40.409: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Mar  1 00:02:40.409: %CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.
*Mar  1 00:02:44.109: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
amt_pkwalls1240AP011#
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

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

amt_pkwalls1240AP011#
*Mar  1 00:03:15.117: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Mar  1 00:03:15.119: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

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

*Mar  1 00:03:25.121: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Mar  1 00:03:25.122: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
amt_pkwalls1240AP011#
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
amt_pkwalls1240AP011# capwap ap primary-base amt_pkKarwlc01 145.17.63.65
amt_pkwalls1240AP011# capwap ap secondary-base amt_pklhrwlc01 145.17.63.69
*Mar  1 00:03:35.124: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Mar  1 00:03:35.126: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER

amt_pkwalls1240AP011#
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

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

*Mar  1 00:03:45.129: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Mar  1 00:03:45.130: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

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

*Mar  1 00:03:55.134: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Mar  1 00:03:55.135: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
amt_pkwalls1240AP011#
amt_pkwalls1240AP011#
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

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

*Mar  1 00:04:05.138: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
*Mar  1 00:04:05.140: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
amt_pkwalls1240AP011#
amt_pkwalls1240AP011#
amt_pkwalls1240AP011#*Apr  3 16:45:45.090: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Apr  3 16:45:45.320: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Apr  3 16:46:02.954:  status of voice_diag_test from WLC is false
*Apr  3 16:46:03.027: Logging LWAPP message to 255.255.255.255.

*Apr  3 16:46:06.256: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power s
ource
*Apr  3 16:46:06.294: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Apr  3 16:46:06.333: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Apr  3 16:46:07.257: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
1, changed state to up
*Apr  3 16:46:07.258: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.
255 started - CLI initiated
*Apr  3 16:46:07.299: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio
0, changed state to up
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)

Tran

8 Replies 8

Leo Laohoo
Hall of Fame
Hall of Fame

Can the AP ping the primary and/or secondary Management IP address of the WLC?

No,

Ping from AP to AP successfully

Ping from AP to AP successfully

SO the AP can't ping either WLCs.  Here's your problem.

The AP should be connected to an access switch port.  The WLCs should be connected to a Dot1Q trunk.  Can you verify this?

yes

There is a lot of request for resolution of your WLC. I take it that your WLC is on layer 3 mode (CAPWAP). Can you confrim that there is a DNS entry in your domain controller for the WLC IP management IP address (not AP manager)?

Yes, DNS entry has been configured in WLC

Sorry, what do you by DNS entry created in WLC? Basically, you should a DHCP IP specified in the management interface config on the WLC. However, you should also create a DNS entry in the Domain controller. You would need to ask your Server Team to do that for you as I guess you're not a Server engineer. On your switch or router you should have a IP helper pointing to the DHCP server.

Can you post the config of your switch connected to your AP and your WLC?

Please post the config of the WLC too.

Review Cisco Networking products for a $25 gift card