-
-
billjellis
Frequent Visitor
- Posts: 53
- Joined:
100% Cpu crs112
Hi All, have this crs112 that is hitting 100% What is in unclassified?
You do not have the required permissions to view the files attached to this post.
Re: 100% Cpu crs112
from the MT wiki, that is the process that you need to go through:
Please follow these steps before contacting support:
Upgrade the RouterOS software to the latest version https://mt.lv/upgrade;
Upgrade the firmware by running /system routerboard upgrade, in the CLI;
Reboot the device and ensure that the unclassified process is persistent;
Create supout.rif file and contact support, describing situation - when exactly the unclassified process shows, how long it takes after the reboot to show, etc.
if you what to know what unclassified means , also from MT wiki:
unclassified - any other processes that were not classified. (does not explain enough)
Please follow these steps before contacting support:
Upgrade the RouterOS software to the latest version https://mt.lv/upgrade;
Upgrade the firmware by running /system routerboard upgrade, in the CLI;
Reboot the device and ensure that the unclassified process is persistent;
Create supout.rif file and contact support, describing situation - when exactly the unclassified process shows, how long it takes after the reboot to show, etc.
if you what to know what unclassified means , also from MT wiki:
unclassified - any other processes that were not classified. (does not explain enough)
Re: 100% Cpu crs112
Also: verify that configuration on CRS is optimum so that HW offload (e.g. VLAN switching) is indeed active.
Beware that having winbox connected to device with several (statistics?) windows open at the same time does cause considerable load on device being monitored ... which is specially true for devices with slow CPUs (such as your CRS112). To make sure this is not the case, connect to your device via CLI (ssh) and run CPU profile there.
Beware that having winbox connected to device with several (statistics?) windows open at the same time does cause considerable load on device being monitored ... which is specially true for devices with slow CPUs (such as your CRS112). To make sure this is not the case, connect to your device via CLI (ssh) and run CPU profile there.