Hi,
I am using one of the cloud core routers of Mikrotik. I want to know how could i limit one of the 10G SFP ports to 5G. We are using it to provide a FTTH service to a service but want to restrict the service to 5G.
I have tried placing the queues in place but they kind of start misbehaving after 2 G and the max limit i could setup in the queue is only 4.2 G.
Help please.
Regards
Sulaiman
Go into Interfaces and set the bandwidth setting to 5Gb.
Check your CPU utilization - using queues disables fast-path forwarding, and depending on what model router you have, it could be exhausting the resources.
Hey ZeroByte, he’s not running into issues of bandwidth. He’s wanting to rate-limit an interface to 5Gbps.
Yeah. I understood that - but when I read this…
… it immediately reminded me of behavior observable when a box can’t push the bandwidth available to it. If the CPU hit 100% before the queue did, then chances are, it’s a CPU condition, hence my question.
I’d never really used the rate limit per interface feature. I notice it’s only available on my 2011 box, and on CHR, it’s not appearing as an option, which tells me this is a hardware switch feature (or at least it’s based on the ethernet driver which is based on hardware) - so I’m assuming this is a wire-speed operation. Is that about right?
I am using rate-limit as a generic term. Setting the bandwidth on the interface should accomplish what sulaiman24 is trying to achieve.
I wasn’t dickering over syntax or terminology… I know exactly what you’re pointing at.
My point was that this must be a hardware-switch feature, because it’s available in my 2011 (which has a hardware switch) and not in my x86-based images in GNS3/VMWare, etc. My clue should’ve been the dividing line between ARP and Master Port - which is where the hardware switch features begin.
My point about that was “cool - the hardware switch won’t depend on the CPU to do rate limiting.”
I wonder if the tx limit is traffic shaped or just simply policed. (shaping would be awesome)
Queue speed limits (limit-at, rate-limit, etc) seems to be 32bit integers, they can’t go higher than 4.2G odd… Noticed this quite a while ago already. Set them higher than a 32bit value, and MT gives errors, not accepting the values.
CCR interfaces do not support this feature
(notable exception on ccr1009 switch ports eth1-eth4)
likes zerobyte says is a switch feature