WLC 5508 8.0.100 AP dropout anf fallback issue

[s.jayaram]

After WLC upgrade to 8.0.100 [ not in HA mode], the AP seem to be dropping out and reconnect using the fallback to IP-  inspite of the statically configured IP on the AP

Running Outdoor mesh AIR-CAP1552E-N-K9 on WLC 5508

(Cisco Controller) >show boot
Primary Boot Image............................... 8.0.100.0 (default) (active)
Backup Boot Image................................ 7.6.101.2
 

=========

Last AP disconnect details
- Reason for last AP connection failure.................... The AP has been reset by the controller
- Last AP disconnect reason................................ Unknown failure reason

Last join error summary
- Type of error that occurred last......................... Lwapp join request rejected
- Reason for error that occurred last...................... No Mwar payload found in join request
- Time at which the last join error occurred............... Dec 03 00:05:26.114

AP disconnect details
- Reason for last AP connection failure.................... The AP has been reset by the controller

[Rasika Nayanajith]

Hi,

You can get 8.0MR1 pre-release via TAC & see if that helps

https://supportforums.cisco.com/document/12298741/80-mr1-beta-availability

HTH

Rasika

**** Pls rate all useful responses **** 

[s.jayaram]

Thanks Rasika

I will  try that if it happens again, this has been stable after configuring the IP from the  controller cli config ap static-ip.

SJ 

[s.jayaram]

All of the AP's dropped back to DHCP , getting worse

Our monitoring tool reports 30% availability  in the past fortnight, even when the end users are working fine.

Mining client not happy with anymore upgrade till the network is stable.

Any troubleshooting tips of the AP regularly reassociating after the upgrade

Thx

[Rasika Nayanajith]

If you have TAC support that is the best avenue to proceed. Since it it 8.0 first release, there may be bugs/instabilities with this code, TAC should be able to provide fix for any known issues.

HTH
Rasika

*** Pls rate all useful responses ***

[s.jayaram]

Do we need smartnet for both WLC to log a TAC case or manage with one for now

Thx

[Rasika Nayanajith]

No, as long as you have one WLC under support, you can log the case against that product.

HTH

Rasika

[s.jayaram]

We downgraded the WLC to  7.4.121.0 and finally got rid of the DHCP problem

But encountered a new issue

The WGB once connected to the mesh AP does not reconnect to the network  , auth failure-   AIR-SAP1602E-Z-K9 running  - ap1g2-k9w7-mx.152-2.JB2

Local EAP auth configured for WGB client on the WLC

Looks more like the WGB stuck in a state , unable to negotiate its credentials

Controller log

*dot1xMsgTask: Mar 24 10:33:52.737: #DOT1X-3-WPA_SEND_STATE_ERR: 1x_kxsm.c:1404 Unable to send EAPOL-key msg  - invalid WPA state (0) - client f4:0f:1b:23:03:37

Attached is the debug and client status from WLC

Any  idea what is going on

Thanks