CCR CPU %100 (managment) when a port reaches 1000mbit traf

Ticket#2013121066000963

When an eth port reaches full wirespeed, CPU reaches %100 traffic.
Profile shows Managment.

No fix in v6.10 too.

Mikrotik please fix this issue !

Anyone ?

what routerboard you have?

CCR 1036 v6.10.

Have you running firewall rules

No. Con Tracking off.

> [admin@E] /tool> profile
> NAME                    CPU        USAGE
> snmp                    all           0%
> console                 all           0%
> networking              all         2.9%
> winbox                  all           0%
> management              all        88.8%
> idle                    all           8%
> routing                 all           0%
> bridging                all           0%
> unclassified            all           0%
> 
> 
> [admin@E] > int mon ether4   
>                      name:     ether4
>     rx-packets-per-second:     36 158
>       rx-drops-per-second:          0
>      rx-errors-per-second:          0
>        rx-bits-per-second:   47.5Mbps
>     tx-packets-per-second:    125 432
>       tx-drops-per-second:          0
>      tx-errors-per-second:          0
>        tx-bits-per-second:  983.5Mbps

When a single interface reaches max wire speed, CPU tops out (managment) !

If you use bandtidth test on the same routerboard is that normal.

This is not bwtest. This is user traffic ! No bandwidnth test !

Mikrotik ?

Have you firewall rules running?
Ore block p2p connections?

There is NO conn tracking + NO NAT + No firewall + NO queue

Just PLAIN SIMPLE STATIC ROUTING+ ECMP

Thats it.

It is clearly a bug.

Yes i think is a bug

Make suppout.rif and sent this to support@mikrotik.com

Hopefully they help you further

I’m having issues pushing more that 1Gbs through my 10Gbs SFP on these boxes… Strangely I can push 10G of UDP traffic…

Maybe SNMP? Try to disable it… Try too disable the LCD Display. If it dont work, reboot Router with slower CPU Speed.

I think this is about flow control on the interface or maybe about interface queues (hardware queue)

Mikrotik has to check the reason.

Ticket#2013121066000963

I hope this is fast solved for you.