Hi @daubstep 

Thanks for posting in our business forum.

daubstep wrote

  @Clive_A I probably should not have upgraded to this version - it recently became available in the One-Time upgrade Firmware panel and so I did, and after months of running fine, I just had to power cycle my ER707-M2 as the network was having performance issues, including simple ping times spiking 100x randomly (ping to 8.8.8.8 would be 10ms then 1000ms back and forth) - and my bandwidth monitoring app tanked around the same time... after power cycling things are back to normal, but that's not great.

EDIT: I can't find any other stats or logs that would lead to the sudden CPU spike to 100% ~9:15am, and sticking at 100%ish until I pulled the power plug...

 

pre/post router powercycling:

 

That CPU spike seems to have caused the shutdown.

When did you upgrade the firmware? How many times has it happened since you upgraded? How many times per day?

Except for the VLAN settings and Internet settings, anything else configured on the router?

Hi @daubstep 

Thanks for posting in our business forum.

daubstep wrote

  @Clive_A I upgraded the firmware on Feb 15th. It has only ever frozen like this this one time.

I do not have IDS/IPS, but I do have DPI and Logging Traffic enabled.

After that happened, anything unusual in the log?

During that period of time, any high bandwidth task?

Hi @daubstep 

Thanks for posting in our business forum.

daubstep wrote

  @Clive_A I couldn't find anything interesting or related in the log and the network was pretty quiet - nothing high-bandwidth or out of the ordinary.

I am unsure what might caused this.

If this happens again, you can contact me on this matter again. And prepare a backup of your config. I'll see what I can do with them.

So far, it is hard to tell the reason.

Hi @daubstep 

Thanks for posting in our business forum.

daubstep wrote

  @Clive_A It just happened again. This time it was ~1.5hrs after a large transfer - nothing in logs or events, no cause I could find. I noticed everything was loading slowly, the alerts I set up after the last time were going off, and ping times were very high. Nothing looked off in my controller, until I noticed that the router stats were actually just empty for a few minutes. After ~20min it resolved by itself.

 

Here you can see the stats finally came back and the CPU had been up at 100% again:

 

 

Here's a snippet of pings at the tail end as it resolved itself:

64 bytes from 8.8.8.8: icmp_seq=84 ttl=60 time=698.451 ms
64 bytes from 8.8.8.8: icmp_seq=85 ttl=60 time=694.937 ms
64 bytes from 8.8.8.8: icmp_seq=86 ttl=60 time=684.029 ms
64 bytes from 8.8.8.8: icmp_seq=87 ttl=60 time=686.572 ms
64 bytes from 8.8.8.8: icmp_seq=88 ttl=60 time=676.421 ms
64 bytes from 8.8.8.8: icmp_seq=89 ttl=60 time=721.034 ms
64 bytes from 8.8.8.8: icmp_seq=90 ttl=60 time=671.104 ms
64 bytes from 8.8.8.8: icmp_seq=91 ttl=60 time=680.946 ms
64 bytes from 8.8.8.8: icmp_seq=92 ttl=60 time=690.763 ms
64 bytes from 8.8.8.8: icmp_seq=93 ttl=60 time=683.597 ms
64 bytes from 8.8.8.8: icmp_seq=94 ttl=60 time=665.401 ms
64 bytes from 8.8.8.8: icmp_seq=95 ttl=60 time=675.582 ms
64 bytes from 8.8.8.8: icmp_seq=96 ttl=60 time=658.269 ms
64 bytes from 8.8.8.8: icmp_seq=97 ttl=60 time=1643.877 ms
64 bytes from 8.8.8.8: icmp_seq=98 ttl=60 time=1654.170 ms
64 bytes from 8.8.8.8: icmp_seq=99 ttl=60 time=1641.776 ms
64 bytes from 8.8.8.8: icmp_seq=100 ttl=60 time=658.156 ms
64 bytes from 8.8.8.8: icmp_seq=101 ttl=60 time=636.974 ms
64 bytes from 8.8.8.8: icmp_seq=102 ttl=60 time=678.777 ms
64 bytes from 8.8.8.8: icmp_seq=103 ttl=60 time=623.319 ms
64 bytes from 8.8.8.8: icmp_seq=104 ttl=60 time=13.556 ms
64 bytes from 8.8.8.8: icmp_seq=105 ttl=60 time=13.712 ms
64 bytes from 8.8.8.8: icmp_seq=106 ttl=60 time=13.504 ms
64 bytes from 8.8.8.8: icmp_seq=107 ttl=60 time=13.014 ms
64 bytes from 8.8.8.8: icmp_seq=108 ttl=60 time=26.601 ms
64 bytes from 8.8.8.8: icmp_seq=109 ttl=60 time=12.252 ms
64 bytes from 8.8.8.8: icmp_seq=110 ttl=60 time=14.298 ms
64 bytes from 8.8.8.8: icmp_seq=111 ttl=60 time=15.590 ms
64 bytes from 8.8.8.8: icmp_seq=112 ttl=60 time=13.588 ms

 

External monitoring of the router CPU:

 

Need a backup of your controller, device info of your router, and your log.

Please prepare a diagram of your network as well.

Send an email to our support address.

To assist and figure it out efficiently, we recommend submitting a support ticket via email.
Please include:
1. Your Forum ID;
2. Your community nickname;
3. A detailed description of the issue and result if I have suggested anything on the thread, and the troubleshooting steps you've taken in the subject line or body of your email.

  @Clive_A Hi, can you please ask when the fully adapted firmware (beta, pre-release) for ER707-M2 for Omada SDN 5.15.20.31 will be posted? I urgently need it to test virtual-WAN and IPTV.