Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

AP reboot issue w/ WLC4400 and LAP1020

Hello,

I have a WiFi network based on WLC4400 (SW version 4.2.130.0) and 14 LAP1040s (SW ver. 4.2.130.0, boot ver. 2.1.78.0).

I'm experimenting AP reboots with no apparent reason (no evident correlated event which triggers the reboot).

From WLC4400 log I see messages like the following when reboots happen:

Jun 14 09:21:08.931 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:9a:2e:30 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     ECHO_REQUEST)

Jun 14 09:20:57.478 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:9a:77:d0 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     ECHO_REQUEST)

Jun 14 09:20:38.709 spam_apf.c:314 LWAPP-3-AP_DB_ERR1: Unable to find AP 00:0b:85:9a:77:d0 entry in the database, could not process delete WLAN ALL MNs message

Jun 14 09:20:38.708 spam_l2.c:760 LWAPP-3-TX_ERR3: Max retransmissions for LWAPP control message reached on AP 00:0b:85:9a:77:d0 for CONFIGURE_COMMAND (number of pending messages is 1)

Jun 14 09:19:54.694 spam_lrad.c:2630 LWAPP-3-RX_ERR9: Received a bad sequenced RRM data request message from AP 00:0b:85:9a:77:d0

Jun 14 09:19:54.109 spam_l2.c:387 LWAPP-3-RX_ERR: Received an unexpected LWAPP packet from AP 00:0b:85:9a:77:d0

Jun 14 09:15:35.261 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:9a:2e:30 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     ECHO_REQUEST)

Jun 14 09:15:23.806 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:9a:77:d0 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     ECHO_REQUEST)

Jun 14 09:15:02.698 spam_l2.c:760 LWAPP-3-TX_ERR3: Max retransmissions for LWAPP control message reached on AP 00:0b:85:9a:77:d0 for CONFIGURE_COMMAND (number of pending messages is 2)

Jun 14 09:10:00.735 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:9a:2e:30 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     ECHO_REQUEST)

Jun 14 09:09:50.089 spam_l2.c:404 LWAPP-3-RX_ERR3: Received LWAPP packet with invalid sequence number (got 1expected 2) - from AP 00:0b:85:9a:77:d0

Jun 14 09:09:50.089 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:9a:77:d0 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     ECHO_REQUEST)

Jun 14 09:09:48.369 spam_apf.c:314 LWAPP-3-AP_DB_ERR1: Unable to find AP 00:0b:85:9a:2e:30 entry in the database, could not process delete WLAN ALL MNs message

Jun 14 09:09:48.367 spam_l2.c:760 LWAPP-3-TX_ERR3: Max retransmissions for LWAPP control message reached on AP 00:0b:85:9a:2e:30 for CONFIGURE_COMMAND (number of pending messages is 1)

Jun 14 09:04:25.557 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:80:a3:c0 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     RRM_DATA_REQ)

Jun 14 09:04:25.414 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:80:a0:10 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     ECHO_REQUEST)

Jun 14 09:04:24.039 apf_rogue.c:736 APF-1-UNABLE_TO_KEEP_ROUGE_CONTAIN: Unable to keep rogue f4:ec:38:cd:a1:9e in contained state - no available AP to contain.

Jun 14 09:04:16.528 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:9a:77:d0 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     ECHO_REQUEST)

Jun 14 09:04:15.011 apf_rogue.c:736 APF-1-UNABLE_TO_KEEP_ROUGE_CONTAIN: Unable to keep rogue 54:e6:fc:e6:a2:3c in contained state - no available AP to contain.

Jun 14 09:04:03.634 spam_apf.c:314 LWAPP-3-AP_DB_ERR1: Unable to find AP 00:0b:85:80:a3:c0 entry in the database, could not process delete WLAN ALL MNs message

Jun 14 09:04:03.632 spam_l2.c:760 LWAPP-3-TX_ERR3: Max retransmissions for LWAPP control message reached on AP 00:0b:85:80:a3:c0 for CONFIGURE_COMMAND

(number of pending messages is 1)

Previous message occurred 2 times.

Jun 14 09:03:56.221 spam_lrad.c:2630 LWAPP-3-RX_ERR9: Received a bad sequenced RRM data request message from AP 00:0b:85:80:a3:c0

Jun 14 09:03:55.160 spam_lrad.c:2630 LWAPP-3-RX_ERR9: Received a bad sequenced RRM data request message from AP 00:0b:85:80:a3:c0

Jun 14 09:03:55.159 spam_lrad.c:2630 LWAPP-3-RX_ERR9: Received a bad sequenced RRM data request message from AP 00:0b:85:80:a3:c0

Previous message occurred 2 times.

Jun 14 09:03:54.174 spam_lrad.c:2630 LWAPP-3-RX_ERR9: Received a bad sequenced RRM data request message from AP 00:0b:85:80:a3:c0

Jun 14 09:03:53.151 spam_lrad.c:2630 LWAPP-3-RX_ERR9: Received a bad sequenced RRM data request message from AP 00:0b:85:80:a3:c0

Jun 14 09:03:53.150 spam_lrad.c:2630 LWAPP-3-RX_ERR9: Received a bad sequenced RRM data request message from AP 00:0b:85:80:a3:c0

Previous message occurred 2 times.

Jun 14 09:03:52.093 spam_lrad.c:2630 LWAPP-3-RX_ERR9: Received a bad sequenced RRM data request message from AP 00:0b:85:80:a3:c0

Jun 14 09:03:51.094 spam_lrad.c:2630 LWAPP-3-RX_ERR9: Received a bad sequenced RRM data request message from AP 00:0b:85:80:a3:c0

Jun 14 08:58:41.884 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:9a:77:d0 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     ECHO_REQUEST)

Jun 14 08:58:23.832 spam_l2.c:760 LWAPP-3-TX_ERR3: Max retransmissions for LWAPP control message reached on AP 00:0b:85:9a:77:d0 for CONFIGURE_COMMAND (number of pending messages is 1)

Jun 14 08:58:03.541 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:9a:81:00 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     ECHO_REQUEST)

Jun 14 08:57:57.390 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:9a:2e:30 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     RRM_DATA_REQ)

Jun 14 08:57:56.460 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:80:a3:c0 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     RRM_DATA_REQ)

Jun 14 08:57:51.925 spam_lrad.c:2286 LWAPP-3-REBOOT_ERR2: AP 00:0b:85:80:a0:10 joined to the controller currently experienced a reboot earlier - (Link Failure Reason:     RRM_DATA_REQ)

Just before the AP reboots, a wifi client connected to that AP looses wifi connection for about 20 secs (wifi connection is ok, just no IP traffic can go through).

Can anybody help me on troubleshooting the issue?

Thanks,

Marco

Everyone's tags (3)
715
Views
0
Helpful
0
Replies
CreatePlease to create content