Fortinet black logo

Hardware Acceleration

Per-session accounting for offloaded NP7 sessions

Per-session accounting for offloaded NP7 sessions

Per-session accounting is an NP7 hardware logging feature that allows the FortiGate to report the correct bytes/pkt numbers per session for sessions offloaded to an NP7 processor. This information appears in traffic log messages as well as in FortiView. The following example shows the Sessions dashboard widget tracking SPU and nTurbo sessions. Current sessions shows the total number of sessions, CPU shows the percent of sessions handled by the CPU, SPU shows the percentage of these sessions that are SPU sessions, and Nturbo shows the percentage that are nTurbo sessions.

If your FortiGate is licensed for hyperscale firewall features, the Sessions widget also includes Hyperscale, which shows the percentage of the sessions set up by NP7 processors using hardware session setup. For information about hyperscale firewall functionality, see the Hyperscale Firewall Guide.

You can also enable per-session accounting separately for TCP multicast sessions.

Per-session accounting for offloaded NP7 sessions

Per-session accounting is an NP7 hardware logging feature that allows the FortiGate to report the correct bytes/pkt numbers per session for sessions offloaded to an NP7 processor. This information appears in traffic log messages as well as in FortiView. The following example shows the Sessions dashboard widget tracking SPU and nTurbo sessions. Current sessions shows the total number of sessions, CPU shows the percent of sessions handled by the CPU, SPU shows the percentage of these sessions that are SPU sessions, and Nturbo shows the percentage that are nTurbo sessions.

If your FortiGate is licensed for hyperscale firewall features, the Sessions widget also includes Hyperscale, which shows the percentage of the sessions set up by NP7 processors using hardware session setup. For information about hyperscale firewall functionality, see the Hyperscale Firewall Guide.

You can also enable per-session accounting separately for TCP multicast sessions.