04-11-2019 11:32 AM - edited 07-05-2021 10:14 AM
Trying to deploy a wireless controller.
#sh sw
Switch/Stack Mac Address : cc5a.53d5.de00 - Local Mac Address
Mac persistency wait time: Indefinite
H/W Current
Switch# Role Mac Address Priority Version State
------------------------------------------------------------
*1 Active cc5a.53d5.de00 12 V06 Ready
I has an unpredictable behavior. Reboots with no reason
#sh logging
Apr 11 05:49:05.114: %LINK-3-UPDOWN: Interface Lsmpi18/0/3, changed state to up
*Apr 11 05:49:05.115: %LINK-3-UPDOWN: Interface EOBC18/0/1, changed state to up
*Apr 11 05:49:05.117: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to down
*Apr 11 05:49:05.117: %LINK-3-UPDOWN: Interface LIIN18/0/2, changed state to up
*Apr 11 05:48:45.037: %STACKMGR-1-STACK_LINK_CHANGE:Switch 1 R0/0: stack_mgr: Stack port 1 on switch 1 is nocable
*Apr 11 05:48:45.037: %STACKMGR-1-STACK_LINK_CHANGE:Switch 1 R0/0: stack_mgr: Stack port 2 on switch 1 is down
*Apr 11 05:48:45.037: %STACKMGR-1-STACK_LINK_CHANGE:Switch 1 R0/0: stack_mgr: Stack port 2 on switch 1 is nocable
000035: *Apr 11 02:49:27.753 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up
000037: *Apr 11 02:49:30.653 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/1, changed state to down
000038: *Apr 11 02:49:30.655 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/2, changed state to down
000039: *Apr 11 02:49:30.658 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/3, changed state to down
000040: *Apr 11 02:49:30.660 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/4, changed state to down
000041: *Apr 11 02:49:30.663 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/1, changed state to down
000042: *Apr 11 02:49:30.667 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/2, changed state to down
000043: *Apr 11 02:49:30.670 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/3, changed state to down
000044: *Apr 11 02:49:30.677 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/4, changed state to down
000062: *Apr 11 02:49:53.399 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/48, changed state to up
000065: *Apr 11 02:49:57.374 GMT: %LINK-3-UPDOWN: Interface TenGigabitEthernet1/1/4, changed state to up
000068: *Apr 11 02:52:00.362 GMT: %LINK-3-UPDOWN: Interface Capwap0, changed state to up
000070: *Apr 11 02:52:05.762 GMT: *%CAPWAP-3-INVALID_SEQ_ERR:Switch 1 R0/0: wcm: Received packet with invalid sequence number from AP (500f.8095.4560).
000072: *Apr 11 02:52:08.821 GMT: *%CAPWAP-3-INVALID_SEQ_ERR:Switch 1 R0/0: wcm: Received packet with invalid sequence number from AP (500f.8095.4560).
04-11-2019 11:38 PM
04-15-2019 11:20 AM
Thanks.
Following CSCvg80597 Workaround:
Disabling load-balance from the WLANs may prevent the switch from rebooting.
wlan XYZ number XYZ
shutdown
no load-balance
no shutdown
I have already done
Bug CSCvn80199 has no workaround.
Known Fixed Releases: | (0) |
What should I do?
04-16-2019 12:07 AM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: