Buy or Renew
Buy or Renew
Cisco Virtual Engineer generative AI bot now active in Wireless Discussion Forum. Learn more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
608
Views
0
Helpful
1
Replies

Ap joins controller, but after reboot impossible to join controller

dlignier
Level 1
Level 1

‎02-10-2011 02:10 AM - edited ‎07-03-2021 07:48 PM

Hello,

First we have 8 controllers (4 Wisms), in 4 differents vlans:

503WLAN_AP_Manager-503

WLAN AP Manager
Wism_SRV-1-1 > 10.50.3.10

Wism_AUTOCOM-1-2 > 10.50.3.15

504WLAN_AP_Manager-504

WLAN AP Manager
Wism_AUTOCOM-1-1 > 10.50.4.14

Wism_SRV-1-2> 10.50.4.11

505WLAN_AP_Manager-505

WLAN AP Manager
Wism_SRV-2-1> 10.50.5.12

Wism_AUTOCOM-2-2 > 10.50.5.17

506WLAN_AP_Manager-506

WLAN AP Manager
Wism_AUTOCOM-2-1 > 10.50.6.16

Wism_SRV-2-2 > 10.50.6.13

all /24

Initially, since 8 months we didn t have any problems.

Since few weeks, if we plug an AP in VLAN X, it successfully gets its IP Address and successfully registered to its controller, depending on the Vlan.

But if we reboot the AP, or make a shut/no shut of the switchport, the AP cant join anymore its controller,

*Mar  1 00:00:10.970: %SNMP-5-COLDSTART: SNMP agent on host ap is undergoing a cold start
*Mar  1 00:11:11.040: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar  1 00:11:11.230: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar  1 00:11:11.230: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar  1 00:11:11.231: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar  1 00:11:12.230: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar  1 00:11:12.231: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar  1 00:11:20.354: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.50.3.128, mask 255.255.255.0, hostname AP0026.9986.d215
*Mar  1 00:11:30.051: Logging LWAPP message to 255.255.255.255.
*Mar  1 00:11:33.395: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar  1 00:11:33.434: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar  1 00:11:33.434: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar  1 00:11:34.434: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar  1 00:11:34.434: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar  1 00:11:34.434: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar  1 00:11:40.939: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar  1 00:11:40.942: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar  1 00:11:50.942: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Feb 10 09:45:59.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.50.3.15 peer_port: 5246
*Feb 10 09:46:00.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Feb 10 09:46:00.738: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.50.3.15 peer_port: 5246
*Feb 10 09:46:00.739: %CAPWAP-5-SENDJOIN: sending Join Request to 10.50.3.15
*Feb 10 09:46:00.739: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Feb 10 09:46:00.827: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Feb 10 09:46:01.528: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Feb 10 09:46:01.529: %LWAPP-3-CLIENTEVENTLOG: Received AP Syslog IP Address(255.255.255.255) configuration.
*Feb 10 09:46:01.638: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller Wism_AUTOCOM-1-2
*Feb 10 09:46:01.715: %LWAPP-3-CLIENTEVENTLOG: SSID CHRSO_DATA added to the slot[0]
*Feb 10 09:46:01.717: %LWAPP-3-CLIENTEVENTLOG: SSID CHRSO_TOIP added to the slot[0]
*Feb 10 09:46:01.718: %LWAPP-3-CLIENTEVENTLOG: SSID CHRSO_DATA added to the slot[1]
*Feb 10 09:46:01.720: %LWAPP-3-CLIENTEVENTLOG: SSID CHRSO_TOIP added to the slot[1]
*Feb 10 09:46:01.733: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
using  eeprom values
SHUT / NO SHUT
*Mar  1 00:00:10.987: %SNMP-5-COLDSTART: SNMP agent on host AP0026.9986.d215 is undergoing a cold start
*Mar  1 00:11:11.041: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar  1 00:11:11.234: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar  1 00:11:11.234: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar  1 00:11:11.234: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar  1 00:11:11.369: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar  1 00:11:11.369: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar  1 00:11:12.234: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar  1 00:11:12.234: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar  1 00:11:20.358: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.50.3.128, mask 255.255.255.0, hostname AP0026.9986.d215
*Mar  1 00:11:30.080: Logging LWAPP message to 255.255.255.255.
*Mar  1 00:11:33.944: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar  1 00:11:33.984: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar  1 00:11:33.985: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar  1 00:11:34.984: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar  1 00:11:34.985: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
*Mar  1 00:11:34.985: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar  1 00:11:40.926: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar  1 00:11:40.928: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar  1 00:11:50.931: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Feb 10 09:48:01.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.50.6.16 peer_port: 5246
*Feb 10 09:48:01.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Feb 10 09:48:30.999: DTLS_CLIENT_ERROR: ../dtls/dtls_connection_db.c:2015 Max retransmission count reached!
*Feb 10 09:48:30.999: %DTLS-3-HANDSHAKE_RETRANSMIT: Max retransmit count for 10.50.6.16 is reached.


We can see that after the shut / no shut, the AP tries to reach another controller.

I have to perform a clear capwap private-config, and shut/no shut, then AP can reach its controller. If I unplug the AP > same problem.

This problem occurs on all Vlan ap manager (503, 504, 505), except on the 506 !!!

Do you have an idea of what happens on the network ??

Thanks a lot.

Labels:
0 Helpful
1 Reply 1

dlignier
Level 1
Level 1

‎02-10-2011 02:46 AM

Hi,

I have found the problem: two wism were in master mode...

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card