Reset Search
 

 

Article

V2110 Initiating Reboot - Cause: System Health Mon. Thread Not Running

« Go Back

Information

 
TitleV2110 Initiating Reboot - Cause: System Health Mon. Thread Not Running
Symptoms
  • V2110 stops to work
  • V2110 end in frozen state
  • WebGui to EWC was not possible
  • Home AP's doesn't move the their HA pair
  • Reboot-Cause-System-Health-Mon-Thread-Not-Running
Environment
  • V2110 - 10.41.08 and 10.41.09
  • ESXI Version 6.5
Cause
  •  Wireless Clients- MU's that have exceeded (per CPU) flow limit of 512
Resolution
Issue resolved in firmware 10.41.11 or higher
Release Note: wns0020966 - Addressed corner case while under client load where the controller in HA failed to notify APs to failover to secondary controller and WLAN would become disabled.
Additional notes
wns0020966

08/28/18 08:14:12   Info        Event Server                    Sending messages to syslog feature is enabled.
08/27/18 21:25:37   Critical    Startup Manager                 Initiating Reboot.  Cause: System Health Mon. Thread Not Running.

YOu can't see any AP mpves during this time on the Salve EWC!!


The strange thing is there is no Mobility configured her but in both messagelogs you can see..some Mobility - RU Session Manager messages

08/28/18 08:14:57   Minor       RU Session Manager              Mobility tunnels with Peers reset due to membership credentials change on current controller.



I'm attaching the console log during hte error.
Primary Console log is " controller1.log "

Task dump for CPU 5:
pidof           R  running task        0 20937  20936 0x00000008
0000000000000087 ffffffff81055f8e 0000000000000005 0000000000000087
ffffffff810a022e ffff88013fd556c0 ffffffff8161d080 0000000000000000
ffff8800a7e91680 ffffffff81076c2e ffffffff81078c27 0000000000014b00
Call Trace:
<IRQ>  [<ffffffff81055f8e>] ? sched_show_task+0xce/0x130
[<ffffffff810a022e>] ? rcu_dump_cpu_stacks+0x74/0xad
[<ffffffff81076c2e>] ? rcu_check_callbacks+0x5ee/0x730
[<ffffffff81078c27>] ? hrtimer_run_queues+0x47/0x180
[<ffffffff81078623>] ? update_process_times+0x23/0x50
[<ffffffff810834db>] ? tick_handle_periodic+0x1b/0x60
[<ffffffff81023c44>] ? smp_apic_timer_interrupt+0x34/0x50
[<ffffffff813aa65c>] ? apic_timer_interrupt+0x7c/0x90
<EOI>  [<ffffffff81066382>] ? queued_spin_lock_slowpath+0x152/0x170
[<ffffffff81126640>] ? pid_revalidate+0x40/0xc0
[<ffffffff810e4137>] ? lookup_fast+0x297/0x2f0
[<ffffffff810e2cf1>] ? path_init+0x1f1/0x330
[<ffffffff810e5583>] ? path_openat+0x173/0x1060
[<ffffffff810ed4ca>] ? dput+0x2a/0x230
[<ffffffff810e51ce>] ? path_lookupat+0xee/0x120
[<ffffffff810e7339>] ? do_filp_open+0x79/0xd0
[<ffffffff811ce67c>] ? lockref_put_or_lock+0x3c/0x60
[<ffffffff810ed604>] ? dput+0x164/0x230
[<ffffffff810d7a4a>] ? do_sys_open+0x11a/0x1e0
[<ffffffff813a9ae0>] ? entry_SYSCALL_64_fastpath+0x13/0x94
INFO: rcu_sched self-detected stall on CPU
INFO: rcu_sched detected stalls on CPUs/tasks:
       5-...: (1260045 ticks this GP) idle=aa7/140000000000001/0 softirq=21243967/21243967 fqs=289463
       (detected by 0, t=1260047 jiffies, g=7509936, c=7509935, q=44368)



stopPkt2Dpi:  failed to add dpi_result.  queue is full
stopPkt2Dpi:  failed to add dpi_result.  queue is full

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255