cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1348
Views
4
Helpful
1
Replies

AP's fail to register after WLC upgrade

Dylan Hyndman
Level 1
Level 1

Hi All,

I've just upgraded my WLC software from 5.1.64.0 to 6.0.199.4.

The upgrade itself went fine, the system rebooted, the AP's connected and downloaded the new image and rebooted.

However after the reboot the AP's failed to join up with the WLC, below is an extract from the logs if anyone is interested.

I have a fall back WLC in a diffent location running 5.1.64.0. which I can get the AP's to join. They connect to it, download the old image and join the second controller.

The AP's are a mainly AIR-LAP1242AG-E-K9

Has anyone else had this issue?

***********************************

*Dec 01 14:34:45.534: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:34:45.534: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
Previous message occurred 2 times.
*Dec 01 14:34:35.533: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:34:25.532: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:34:25.531: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:34:15.531: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:34:15.530: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:34:05.530: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:34:05.530: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
Previous message occurred 2 times.
*Dec 01 14:33:55.528: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:33:45.528: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:33:45.527: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:33:35.527: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
*Dec 01 14:33:35.526: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10
Previous message occurred 2 times.
*Dec 01 14:33:25.525: %CAPWAP-3-DISC_INTF_ERR2: capwap_ac_sm.c:1506 Ignoring discovery request received on a wrong VLAN (14) on interface (29) from AP 00:1a:e3:ba:88:10


*Dec 01 14:32:39.717: %DTL-3-OSARP_DEL_FAILED: dtl_arp.c:1380 Unable to delete an ARP entry for 172.31.60.204 from the operating system. ioctl operation failed
*Dec 01 14:32:39.714: %LWAPP-3-ECHO_ERR: spam_tmr.c:1131 Did not receive heartbeat reply; AP: 00:1a:e3:ba:88:10


*Dec 01 14:30:08.575: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:292 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
Previous message occurred 2 times.
*Dec 01 14:29:58.356: %LWAPP-3-DISC_INTF_ERR2: spam_lrad.c:1541 Ignoring discovery request received on a wrong VLAN (14) on interface (29) in L3 LWAPP mode from AP 00:1a:e3:ba:88:10

Log System Time Trap
0 Wed Dec 1 14:32:39 2010 AP Disassociated. Base Radio MAC:00:1a:e3:ba:88:10
1 Wed Dec 1 14:32:39 2010 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1a:e3:ba:88:10 Cause=Heartbeat Timeout
2 Wed Dec 1 14:32:39 2010 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1a:e3:ba:88:10 Cause=Heartbeat Timeout

***********************************

1 Reply 1

Dylan Hyndman
Level 1
Level 1

OK, found the answer to this in another post:

I needed to open UDP ports 5246 & 5247 on our firewall.

Works a treat now.

Review Cisco Networking for a $25 gift card