Hi Fortinet Community,
We're facing an issue where traffic shaping on our FortiGate device doesn't seem to be working as expected. Despite setting up the necessary configurations, no traffic appears to be shaped — the system always shows current-bandwidth=0(kbps) when monitoring shaping statistics.
What We’ve Verified So Far:
1. Class IDs are configured correctly.
2. Traffic Shaping Profile is set up and active.
3. Relevant Traffic Shaping Policy is in place.
4. Interface outbound bandwidth is configured.
5. Traffic Shaping Profile is applied to the correct interface.
6. Ran "diagnose netlink interface list" command
No matter what we try, shaping stats show zero usage:
Any help or insights would be greatly appreciated.
Thanks in advance!
Solved! Go to Solution.
Hi Fortinet Community,
Just wanted to provide an update and share the solution that worked for us, in case anyone else encounters a similar issue.
Thanks to Fortinet TAC support, we were able to resolve the issue. Below is the complete configuration that worked for us to implement traffic shaping using Traffic Shaping Profiles.
1. Create a Traffic Shaping Profile.
2. Define Class IDs with guaranteed/maximum bandwidth percentages within the shaping profile.
3. Create Traffic Shaping Policy and Assign a Class ID.
4. Configure Interface Bandwidth
On the relevant outgoing interface:
set outbandwidth <value_in_kbps> # Upload bandwidth
set inbandwidth <value_in_kbps> # Download bandwidth
6. Assign the Traffic Shaping Profile to the Outgoing Interface
set egress-shaping-profile <profile_name>
set ingress-shaping-profile <profile_name>
7. Disable ASIC Offloading in the Relevant Firewall Policy
set auto-asic-offload disable
After applying the above steps, traffic shaping started to work correctly and bandwidth controls were enforced as expected.
Hope this helps anyone facing a similar challenge.
Big thanks to Fortinet TAC and special shout-out to @BillH_FTNT for doing his best to assist!
Cheers,
Sadhi.
First of all, thank you for your feedback and collaboration.
Yes, I previously tested just leaving "Traffic Shaping Profiles" on and it didn't work, but since I needed to restrict the amount of traffic, I had to try Traffic Shapers, but I would like to have Traffic Shaping Profiles working for more efficient bandwidth control.
Hi UniMK
It is useful to know the current bandwidth from the command dia netlink interface list xxx
and the information from dia sys session list
to verify if the QoS is being processed by the Kernel or NPU. If you have this information, please share it; if not, I will test it in my lab to check and compare with your case. Thanks.
Regards
BIll
Hi Fortinet Community,
Just wanted to provide an update and share the solution that worked for us, in case anyone else encounters a similar issue.
Thanks to Fortinet TAC support, we were able to resolve the issue. Below is the complete configuration that worked for us to implement traffic shaping using Traffic Shaping Profiles.
1. Create a Traffic Shaping Profile.
2. Define Class IDs with guaranteed/maximum bandwidth percentages within the shaping profile.
3. Create Traffic Shaping Policy and Assign a Class ID.
4. Configure Interface Bandwidth
On the relevant outgoing interface:
set outbandwidth <value_in_kbps> # Upload bandwidth
set inbandwidth <value_in_kbps> # Download bandwidth
6. Assign the Traffic Shaping Profile to the Outgoing Interface
set egress-shaping-profile <profile_name>
set ingress-shaping-profile <profile_name>
7. Disable ASIC Offloading in the Relevant Firewall Policy
set auto-asic-offload disable
After applying the above steps, traffic shaping started to work correctly and bandwidth controls were enforced as expected.
Hope this helps anyone facing a similar challenge.
Big thanks to Fortinet TAC and special shout-out to @BillH_FTNT for doing his best to assist!
Cheers,
Sadhi.
User | Count |
---|---|
2548 | |
1354 | |
795 | |
646 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.