Need help with network rate limit

[SviridoffA]

Please help, I need to increase the rate limit for the client network. I created an offer where I set the limit to 500 Mbps and applied it to the client network. However, the speed didn’t change and remained at the default 200 Mbps. Later, I found two settings in the global parameters: vm.network.throttling.rate and network.throttling.rate. Although they were marked as default, I set them to 1000 and restarted the server management, but the speed still didn’t change. The traffic speed bypassing the virtual router is unrestricted.
I am using:
Ubuntu 24.04
ACS 4.19.3
network: Bridges + vlan isolation

[SviridoffA]

UPD: It seems that if I change the offer, the changes of rate limits are not applied, but if I create a new network, rate limit is applied.

[daviftorres]

Hey @SviridoffA , you are at the right spot.

There are 3 places where network rate (bandwidth limit) can be defined:

• Global parameters
• Network Offering
• Service Offering

How it works

• If Service Offering rate = NULL, CloudStack uses the global parameter vm.network.throttling.rate.
• If Network Offering rate = NULL, CloudStack uses the global parameter network.throttling.rate.

Changing defaults cannot be done via the WebUI. But you can either create new offerings, or directly update existing ones in the database:

• cloud.network_offerings (for Network Offerings)
• cloud.service_offering (for System VMs)

When a network rate = 0, mean unlimited bandwidth.

[SviridoffA]

Thanks for clarification! Could you please advise me on how I can apply a new offer with a new limit to an existing network? When I changed the offer, the virtual router was recreated, but the limit remained the same, and restarting the network didn’t help either.

[SviridoffA]

UPD: I found out that the limits are applied to the virtual machine of this network if I perform a power off and power on of the VMs.

[SviridoffA]

To summarize: I'm noting this for myself, and it might be useful for others too. My main task was to change the network rate limit. I modified the offering, but changes didn’t apply to the network’s virtual machines because I had vm.network.throttling.rate parameter set. This parameter was applying a restriction to the virtual machine’s interface itself. To freely adjust the network rate, I need to keep the vm.network.throttling.rate value at 0, which means no restrictions. This way, I can change the network rate without worrying about other parameters. However, for the changes made to the vm.network.throttling.rate parameter to take effect on already created virtual machines with the previous value, those VMs need to be powered off and then powered back on.

@daviftorres Thanks a lot for helping me figure out this issue!