LWAPP's losing names and showing up as default MAC address's

[Steven Williams]

I have been having random LWAPP's that have been configured previously showing up as the original names as if they were just installed (APxxx:xxxx:xxxx). I know this becasue the location field is the location of where they are, and AP group name is also set to the location they are. What would cause this?

WLC = 7.0.98.0

AP = 1142n 12.4(23c)JA

This problem is here and there...it is happening to about 5 percent of my overall AP's.

[Surendra BG]

Guess the AP is losing the private config and rejoining the WLC, so the MAC diplays instead os name!! AFAIK, no bugs in the WLC code that we are running.. (7.0.98)

Regards

Surendra

[Steven Williams]

How does it just lose its config? At what point does an AP write its config? I had an AP lose its config after 7 months....and the AP has been powered on and off numerous times due to energywise and never lost its config.

[Leo Laohoo]

I've used 7.0.98.0 since it was published and I've never seen this behaviour before.  I have the following suggestion:

1.  Disable EnergyWise on this AP alone; or

2.  Upgrade your firmware to the new 7.0.116.0.

[weterry · Accepted solution]

Just my $.02

If your AP is retaining its AP Group and Location parameters, it is not losing its configuration.....

Have you tried to reboot an AP that shows the Mac address format, and see if it joins with the correct name again?

I bet it comes up with the correct name.....

If so, my money is on your APs are dropping from the WLC and joining before the WLC has cleared the previous entry.

There is logic on the WLC to temporarily reset an APs name if two APs join with the same name (since you can't have two APs with the same name).

I could be wrong, it may permeanently reset the name, but I still bet it has to do with your AP dropping and joining too quickly....

[Steven Williams]

AWESOME!!!  GREAT KNOWLEDGE!!!  Man, to think I wasted a whole couple of days digging through my cardboard of MAC addresses and renaming them when all I had to do was reboot!!!  ARG!!! So I assume I need to start looking into connectivity issues.

[weterry]

My statement above may not match 100% to your scenario, but I've seen it happen, heard a few reports of similar events, and it generally sounds plausible to me....

Regarding the AP Disconnect concerns.....

I would consider you look at the Wireless TAB in the GUI.  APs are listed there in order of when they joined the WLC.   I believe that screen will shows you AP UP Time, but you can click on the AP and then see the parameter for AP Associated Time, this is how long it as been joined to the WLC.

I normally go to the end of list on the Wireless TAB, and look at the APs at the end which are the most recent to join.

Generally speaking, if you have APs with an UP Time like you expected,  but a Join Time that is signficantly shorter, you could conclude that some event caused those APs to drop from the WLC...    I assume your APs a missing name must have either rebooted (up time short) or disconnected (up time same as others, join time short).

Hoiw many APs did this happen to anyhow?   You said there were power outages though, so you know they had rebooted, so looking for association times may not matter....

[Steven Williams]

This happened to about 30 AP's throughout different locations. All the AP's are on energywise shcedules so the shutdown at night and come up in the AM so they reboot daily. Almost a year of having this system, this is the first instance of this problem I have had. How long does it take the WLC to clear the AP info? I mean are we talking about AP's dropping from the WLC and joining within seconds? Or minutes? Or hours? I assume the WLC clears the AP info fairly quickly.

[weterry]

Do all the APs power up at the exact same time?

Because maybe you had some kind of join congestion or something where APs were trying to join and some of the APs just didn't get what they wanted so they tried to join again (but maybe WLC thought they were joined)....

WLC has a heartbeat to the AP and generally an AP will be gone from the list within a minute or two....

So you're likely dealing with a scenario of APs trying to join and maybe having to re-join due to some network event...

The only times I've ever seen this reported are with a rush of APs to join a controller, and usually only a handful have the problem.

Maybe there is some kind of "bug" here, but the few times I've seen this a reboot of the AP provided the AP a correct name again....

If they reboot daily, did any of them lose the name again last night? 

[Steven Williams]

Yes I had 2 of them lose their names last night.

Yes all of the AP's come up at the same time. There are about 1300 in production right now so your thoughts on a "rush to join" could have some weight.

[weterry]

So did those two join again with the right name after a 2nd reboot? or did you already fix the names before reading this thread?

Could you pull off the eventlog from those APs?   I think it might be something like "show ap eventlog " from the wlc...

or you could enable telnet/ssh to the AP and do a "show log"  and a "more eventlog"  and capture the output....

I'm curious if the log shows the AP comes up with one name and then gets told to change names.....

[Steven Williams]

From the AP, nothing stands out to me on this log output:

Syslog logging: enabled (1 messages dropped, 12 messages rate-limited,
                0 flushes, 0 overruns, xml disabled, filtering disabled)
    Console logging: level debugging, 43 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging: level debugging, 53 messages logged, xml disabled,
                    filtering disabled
    Logging Exception size (4096 bytes)
    Count and timestamp logging messages: disabled
    Trap logging: level errors, 35 message lines logged
        Logging to 255.255.255.255(global) (udp port 514, audit disabled,  link up), 12 message lines logged, xml disabled,
               filtering disabled

Log Buffer (1048576 bytes):

*Mar  1 00:00:07.947: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar  1 00:00:07.957: *** CRASH_LOG = YES
Security Core found.
Base Ethernet MAC address: D0:D0:FD:2E:2F:0E

*Mar  1 00:00:09.327: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar  1 00:00:09.895: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar  1 00:00:09.934: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 124 messages)

*Mar  1 00:00:09.953:  status of voice_diag_test from WLC is false
*Mar  1 00:00:10.994: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar  1 00:00:12.073: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar  1 00:00:12.114: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1140 Software (C1140-K9W8-M), Version 12.4(23c)JA, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Tue 01-Jun-10 12:29 by prod_rel_team
*Mar  1 00:00:12.114: %SNMP-5-COLDSTART: SNMP agent on host RESAD115 is undergoing a cold start
*Mar  1 00:15:33.040: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar  1 00:15:33.105: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar  1 00:15:33.105: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar  1 00:15:33.606: %DOT11-2-TX_PWR_TIMO: Interface Dot11Radio0, Timed out waiting for fw to clear txp_pndg flag
*Mar  1 00:15:34.104: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar  1 00:15:34.104: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar  1 00:15:34.106: %DOT11-2-TX_PWR_TIMO: Interface Dot11Radio1, Timed out waiting for fw to clear txp_pndg flag
*Mar  1 00:15:34.306: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar  1 00:15:42.226: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.103.100.63, mask 255.255.0.0, hostname RESAD115

*Mar  1 00:15:51.900:  status of voice_diag_test from WLC is false
*Mar  1 00:15:51.939: Logging LWAPP message to 255.255.255.255.

*Mar  1 00:15:54.038: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar  1 00:15:54.068: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar  1 00:15:54.081: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar  1 00:15:55.045: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar  1 00:15:55.046: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
*Mar  1 00:15:55.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar  1 00:16:02.970: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar  1 00:16:12.973: %CAPWAP-3-ERRORLOG: Selected MWAR 'RPS-5508-2'(index 0).
*Mar  1 00:16:12.973: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 20 13:11:59.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.200.1.21 peer_port: 5246
*Apr 20 13:11:59.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Apr 20 13:11:59.835: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.200.1.21 peer_port: 5246
*Apr 20 13:11:59.835: %CAPWAP-5-SENDJOIN: sending Join Request to 10.200.1.21
*Apr 20 13:11:59.835: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Apr 20 13:11:59.965: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Apr 20 13:12:00.083: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 20 13:12:00.091: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Apr 20 13:12:00.095: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 20 13:12:00.136: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller RPS-5508-2
*Apr 20 13:12:00.184: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Apr 20 13:12:00.185: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[0]
*Apr 20 13:12:00.190: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[0]
*Apr 20 13:12:00.192: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[1]
*Apr 20 13:12:00.193: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[1]
*Apr 20 13:12:00.202: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 1 due to not using AES encryption or encryption is not disabled
*Apr 20 13:12:00.207: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 1 due to not using AES encryption or encryption is not disabled
*Apr 20 13:12:00.212: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 20 13:12:00.212: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 20 13:12:00.221: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
*Apr 20 13:12:00.229: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

[Steven Williams]

AP event log from controller:

AP event log download completed.
======================= AP Event log Contents =====================
*Mar 1 00:15:54.702: %CDP_PD-2-POWER_LOW: All radios disabled - NEGOTIATED WS-C4506-E (5475.d01d.8052)
*Mar 1 00:16:02.966: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Aug 30 19:37:23.001: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Aug 30 19:37:23.001: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.200.1.10 peer_port: 5246
*Aug 30 19:37:23.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Aug 30 19:37:23.734: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.200.1.10 peer_port: 5246
*Aug 30 19:37:23.734: %CAPWAP-5-SENDJOIN: sending Join Request to 10.200.1.10
*Aug 30 19:37:23.734: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Aug 30 19:37:23.751: %CAPWAP-5-CHANGED: CAPWAP changed state to IMAGE
*Aug 30 19:38:04.730: %CDP_PD-2-POWER_LOW: All radios disabled - NEGOTIATED WS-C4506-E (5475.d01d.8052)
*Aug 30 19:38:12.291: *** Access point reloading. Reason: NEW IMAGE DOWNLOAD ***
*Aug 30 19:38:12.292: %SYS-4-PUPDATECLOCK: Periodic Clock update with ROMMON failed, because size left in ROMMON (4294967295),
*Mar 1 00:15:54.161: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:15:54.184: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:15:54.191: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:15:55.155: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

--More-- or (q)uit
*Mar 1 00:15:55.176: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:16:02.982: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Aug 30 19:39:56.001: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Aug 30 19:39:56.001: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.200.1.10 peer_port: 5246
*Aug 30 19:39:56.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Aug 30 19:39:56.744: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.200.1.10 peer_port: 5246
*Aug 30 19:39:56.744: %CAPWAP-5-SENDJOIN: sending Join Request to 10.200.1.10
*Aug 30 19:39:56.744: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Aug 30 19:39:56.940: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Aug 30 19:39:57.047: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug 30 19:39:57.051: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Aug 30 19:39:57.052: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 30 19:39:57.252: %LWAPP-3-CLIENTEVENTLOG: Received AP Syslog IP Address(255.255.255.255) configuration.
*Aug 30 19:39:57.258: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller Wism-Slot1Proc1
*Aug 30 19:39:57.263: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Aug 30 19:39:57.263: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[0]
*Aug 30 19:39:57.264: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[0]
*Aug 30 19:39:57.264: %LWAPP-3-CLIENTEVENTLOG: SSID ILOVEDOGS added to the slot[0]
*Aug 30 19:39:57.265: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[1]
*Aug 30 19:39:57.284: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 2 due to not using AES encryption or en
*Aug 30 19:39:57.287: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 2 due to not using AES encryption or en
*Aug 30 19:39:57.287: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Aug 30 19:39:57.287: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

--More-- or (q)uit
*Aug 30 19:39:57.287: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[1]
*Aug 30 19:39:57.287: %LWAPP-3-CLIENTEVENTLOG: SSID ILOVEDOGS added to the slot[1]
*Aug 30 19:39:57.297: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 31 02:29:15.271: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Aug 31 02:29:15.324: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Aug 31 02:29:15.327: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug 31 02:29:15.411: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 31 03:34:40.892: *** Access point reloading. Reason: Recvd RESET req from Controller ***
*Mar 1 00:15:55.598: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:15:55.622: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:15:55.630: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:15:56.594: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:15:56.616: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:16:02.969: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Aug 31 03:33:11.001: %CAPWAP-3-ERRORLOG: Selected MWAR 'RPS-5508-2'(index 0).
*Aug 31 03:33:11.001: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Aug 31 03:33:11.001: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.200.1.21 peer_port: 5246
*Aug 31 03:33:11.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Aug 31 03:33:11.842: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.200.1.21 peer_port: 5246
*Aug 31 03:33:11.842: %CAPWAP-5-SENDJOIN: sending Join Request to 10.200.1.21
*Aug 31 03:33:11.842: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Aug 31 03:33:11.975: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Aug 31 03:33:12.100: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

--More-- or (q)uit
*Aug 31 03:33:12.104: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Aug 31 03:33:12.105: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 31 03:33:12.312: %LWAPP-3-CLIENTEVENTLOG: Received AP Syslog IP Address(255.255.255.255) configuration.
*Aug 31 03:33:12.318: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller RPS-5508-2
*Aug 31 03:33:12.322: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Aug 31 03:33:12.322: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[0]
*Aug 31 03:33:12.324: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[0]
*Aug 31 03:33:12.324: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[1]
*Aug 31 03:33:12.324: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[1]
*Aug 31 03:33:12.342: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 1 due to not using AES encryption or en
*Aug 31 03:33:12.346: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 1 due to not using AES encryption or en
*Aug 31 03:33:12.346: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Aug 31 03:33:12.346: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug 31 03:33:12.354: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 31 03:36:11.493: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Aug 31 03:36:11.503: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Aug 31 03:51:52.242: %CAPWAP-5-CHANGED: CAPWAP changed state to DOWN
*Aug 31 03:51:52.336: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Aug 31 03:51:52.342: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Aug 31 03:51:52.345: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Aug 31 03:51:52.346: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 31 03:51:52.346: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Aug 31 03:51:52.346: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[0]

--More-- or (q)uit
*Aug 31 03:51:52.346: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[1]
*Aug 31 03:51:52.347: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Aug 31 03:51:52.347: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[0]
*Aug 31 03:51:52.347: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[1]
*Aug 31 03:51:52.370: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Aug 31 03:51:52.370: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug 31 03:51:52.379: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 31 03:52:02.470: *** Access point reloading. Reason: Recvd RESET req from Controller ***
*Mar 1 00:15:52.829: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:15:52.853: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:15:52.860: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:15:52.960: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:15:52.963: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:16:02.966: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Apr 20 11:02:16.001: %CAPWAP-3-ERRORLOG: Selected MWAR 'RPS-5508-2'(index 0).
*Apr 20 11:02:16.001: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 20 11:02:16.001: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.200.1.21 peer_port: 5246
*Apr 20 11:02:16.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Apr 20 11:02:16.991: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.200.1.21 peer_port: 5246
*Apr 20 11:02:16.991: %CAPWAP-5-SENDJOIN: sending Join Request to 10.200.1.21
*Apr 20 11:02:16.991: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Apr 20 11:02:17.279: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Apr 20 11:02:17.459: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

--More-- or (q)uit
*Apr 20 11:02:17.463: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Apr 20 11:02:17.463: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 20 11:02:17.549: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller RPS-5508-2
*Apr 20 11:02:17.556: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Apr 20 11:02:17.556: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[0]
*Apr 20 11:02:17.582: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 1 due to not using AES encryption or en
*Apr 20 11:02:17.583: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 20 11:02:17.583: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 20 11:02:17.583: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[0]
*Apr 20 11:02:17.583: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[1]
*Apr 20 11:02:17.583: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[1]
*Apr 20 11:02:17.591: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 1 due to not using AES encryption or en
*Apr 20 11:02:17.591: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 20 13:10:23.885: *** Access point reloading. Reason: Recvd RESET req from Controller ***
*Mar 1 00:15:54.051: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:15:54.075: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:15:54.082: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:15:55.045: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:15:55.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:16:02.971: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Apr 20 13:11:59.001: %CAPWAP-3-ERRORLOG: Selected MWAR 'RPS-5508-2'(index 0).
*Apr 20 13:11:59.001: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 20 13:11:59.001: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.200.1.21 peer_port: 5246

--More-- or (q)uit
*Apr 20 13:11:59.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Apr 20 13:11:59.836: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.200.1.21 peer_port: 5246
*Apr 20 13:11:59.836: %CAPWAP-5-SENDJOIN: sending Join Request to 10.200.1.21
*Apr 20 13:11:59.836: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Apr 20 13:11:59.965: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Apr 20 13:12:00.090: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 20 13:12:00.095: %CAPWAP-5-CHANGED: CAPWAP changed state to UP
*Apr 20 13:12:00.095: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 20 13:12:00.183: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller RPS-5508-2
*Apr 20 13:12:00.196: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Apr 20 13:12:00.196: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[0]
*Apr 20 13:12:00.196: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[0]
*Apr 20 13:12:00.196: %LWAPP-3-CLIENTEVENTLOG: SSID RPS added to the slot[1]
*Apr 20 13:12:00.196: %LWAPP-3-CLIENTEVENTLOG: SSID RPS-GUEST added to the slot[1]
*Apr 20 13:12:00.217: %DOT11-4-NO_HT: Interface Dot11Radio1, Mcs rates disabled on vlan 1 due to not using AES encryption or en
*Apr 20 13:12:00.223: %DOT11-4-NO_HT: Interface Dot11Radio0, Mcs rates disabled on vlan 1 due to not using AES encryption or en
*Apr 20 13:12:00.223: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Apr 20 13:12:00.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 20 13:12:00.229: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 20 14:20:10.592: %CAPWAP-3-ERRORLOG: Received a upload request from controller for event log buffer

[weterry]

You're right, not nearly as helpful as I was hoping for.

*Mar  1 00:15:42.226: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.103.100.63, mask 255.255.0.0, hostname RESAD115

Is RESAD115 the AP name?

The logs don't show the AP joining and dropping or anything, so that sort of disproves my theory.

I see this is a 5508....  the other customers I've seen are all 5508s (which can handle like 100 joins at once or something)....    so maybe something really is going on the WLC side where it thinks the AP has joined already so it resets the name...

Either way, I think you confirmed the AP isn't actually losing its configuration, it is just getting its name set to default temporarily....

I'd be real curious to see the output of an AP that is in this state....   maybe if we could see the show log from it, we could at least confirm the DHCP stuff has the hostname (that is the AP hostname)....

[Steven Williams]

Well if the 1000 joins is correct that is not the issue then because I have 3 controllers and a WiSM and all AP's are spread across all devices. What do you mean when you say:

I'd be real curious to see the output of an AP that is in this state....   maybe if we could see the show log from it, we could at least confirm the DHCP stuff has the hostname (that is the AP hostname)....