NP7 traffic shaping
By default, if you configure traffic shaping for a FortiGate with NP7 processors, traffic shaping is applied to offloaded traffic by applying traffic shaping with policing.
You can use the following command to configure NP7 processors to switch between traffic shaping with policing and traffic shaping with queuing:
config system npu
set default-qos-type {policing | shaping}
end
policing, (the default) NP7 processors apply traffic shaping with policing using the NP7 accounting and traffic shaping module (called theTPE module). When traffic exceeds configured traffic shaping bandwidth limits, traffic is dropped.
shaping, enable traffic shaping with queuing using the NP7 Queuing based Traffic Management (QTM) module. Traffic shaping with queuing schedules traffic in queues by implementing variations of a round robin algorithm. When traffic exceeds configured traffic shaping bandwidth limits, traffic is delayed for transport until bandwidth frees up. Traffic may be dropped if the queues are full. In most cases, traffic shaping with queuing will be more stable and will also improve performance for traffic shaping applied by NP7 processors.
The FortiGate restarts after changing the QoS type.
|
Traffic shaping with queuing using the NP7 QTM module is not compatible with carrier-grade NAT and hyperscale firewall features. If you enable the hyperscale firewall license you cannot set |
You can also use the following command to configure the number of packet buffers used by NP7 processors to support traffic shaping with queuing.
config system npu
set qtm-buf-mode {6ch | 4ch}
end
6ch (the default) use 6 DRAM channels for each packet buffer.
4ch user 4 DRAM channels for each packet buffer.