GitHub user iishitahere added a comment to the discussion: Wrong Traffic Shaping in Secondary NIC over L2 networks
> Hi @iishitahere . Thank you for your comment. Yes, the use case is relatively > simple. A user creates two L2 type networks (from the same network offering > for example) and the bandwidth that cloudstack applies to the default NIC > (Traffic Shapping in VMware) differs from the one configured in the secondary > NIC, when it should be the same bandwidth since both networks were created > from the same network offering. From what I could find out, CloudStack would > NOT be using the value configured in the vm.network.throttling.rate parameter > of the global settings for the secondary NICs as it does for the default NIC. > Let me know if this helps in understanding the case and thanks for taking an > interest in it. Hi @luganofer , thank you for the detailed explanation! I understand now that the issue arises because CloudStack does not apply the vm.network.throttling.rate parameter to secondary NICs, even though both NICs are created from the same network offering. The expected behavior is that the bandwidth should be consistent across all NICs. I’ll investigate this further and look into how the vm.network.throttling.rate parameter is being applied. If there are any specific areas of the codebase or logs that you recommend focusing on, please let me know. I'll keep you updated on my progress. Thanks again for your guidance! GitHub link: https://github.com/apache/cloudstack/discussions/12378#discussioncomment-15423400 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
