/interface ethernet switch port
set 1 egress-rate=100.0Mbps ingress-rate=20.0Mbps limit-unknown-multicasts=yes limit-unknown-unicasts=yes storm-rate=1
set 2 egress-rate=100.0Mbps ingress-rate=20.0Mbps limit-unknown-multicasts=yes limit-unknown-unicasts=yes storm-rate=1
set 3 egress-rate=100.0Mbps ingress-rate=20.0Mbps limit-unknown-multicasts=yes limit-unknown-unicasts=yes storm-rate=1
set 4 egress-rate=100.0Mbps ingress-rate=20.0Mbps limit-unknown-multicasts=yes limit-unknown-unicasts=yes storm-rate=1
Users on this Port connect via an vlan to PPPoE-Server.
Problem is, that PPPoE Users on this Port not have Download/Upload Speed of 100/20, they have only ~~70/10.
Is there a better way to limit DL UL Speed for Users on Hardware-Level in the Switch?
have you found a solution to your problem? We have just realized that we have a similar problem with our CRS317-1G-16S+.
If we just limit egress rate everything works as expected. But if we limit ingress and egress traffic hardly reaches configured limits.
PPPoE is a CPU based process last I checked.Not sure how the cpu load would look, but isnt a CRS3x a better switch than ‘route/network’ device.. Would a RB5009 or CCRxxxx series be better to do what you want in PPPoE and QoS..
Anyhow try CPU and use packet/connection marking in mangle and then use Queues to shape traffic…( keep an eye on the CPU load )
I think you understand the original poster an me wrong. The switch is just passing the traffic. That’s what a switch is for. PPPoE or anything else is made elsewhere in the network. And the CRS3xx is made for SWITCHING so has a horrible CPU for pushing packets. You will NEVER use CPU queues for traffic shaping. But the switch chip should do that. But obviously has problems.
Could you please show an example im having the same problem.. and handing off a port tomorrow for a client that is strictly a layer2 hand off.. So no router involved.. and I cant get the Ingress rate limit to work right..
/interface ethernet switch port ingress= does not work properly..