Fortinet black logo

Hardware Acceleration

Multicast per-session accounting

Multicast per-session accounting

Some FortiGates with NP6 processors include the following command to configure multicast session accounting:

config system npu

set mcast-session-accounting {tpe-based | session-based | disable}

end

tpe-based (the default) enables TPE-based multicast session accounting. TPE is the NP6 accounting and traffic shaping module. In most cases, if you want multicast session accounting, you should select tpe-based for optimal performance and reliability. This setting may be incompatible with some traffic. If problems such as packet order issues occur, you can disable multicast session accounting or select session-based multicast accounting.

session-based enables session-based multicast session accounting.

disable disables multicast session accounting.

Generally speaking, session-based accounting has better performance than TPE-based when there are high number of multicast sessions (on the order of 7,000 sessions, depending on network and other conditions).

TPE-based accounting generally can have better performance when there are a fewer multicast sessions with very high throughput.

Some FortiGate models support the following command to enable or disable multicast session accounting. For these models, multicast session accounting is enabled by default:

config system npu

set mcast-session-counting {disable | enable}

set mcast-session-counting6 {disable | enable}

end

Multicast per-session accounting

Some FortiGates with NP6 processors include the following command to configure multicast session accounting:

config system npu

set mcast-session-accounting {tpe-based | session-based | disable}

end

tpe-based (the default) enables TPE-based multicast session accounting. TPE is the NP6 accounting and traffic shaping module. In most cases, if you want multicast session accounting, you should select tpe-based for optimal performance and reliability. This setting may be incompatible with some traffic. If problems such as packet order issues occur, you can disable multicast session accounting or select session-based multicast accounting.

session-based enables session-based multicast session accounting.

disable disables multicast session accounting.

Generally speaking, session-based accounting has better performance than TPE-based when there are high number of multicast sessions (on the order of 7,000 sessions, depending on network and other conditions).

TPE-based accounting generally can have better performance when there are a fewer multicast sessions with very high throughput.

Some FortiGate models support the following command to enable or disable multicast session accounting. For these models, multicast session accounting is enabled by default:

config system npu

set mcast-session-counting {disable | enable}

set mcast-session-counting6 {disable | enable}

end