Fortinet white logo
Fortinet white logo

Hyperscale Firewall Guide

NP7 high load notifications

NP7 high load notifications

Under high load conditions, NP7 processors on FortiGates licensed for hyperscale firewall can experience NPU stuck problems that can cause CPU spikes and potential system instability.

Before an NP7 processor gets stuck, FortiOS can generate three different event log messages to flag that an NP7 processor is experiencing higher than normal load conditions.

Log ID

Message type

Example Message

53326

Info

2: date=2025-02-21 time=13:17:14 eventtime=1740100634773597762 tz="+1200" logid="0100053326" type="event" subtype="system" level="information" vd="root" logdesc="NPU health info event" pbadelta="high(1082)" msg="on NP(4)"

53327

Warning

83: date=2025-02-21 time=11:46:40 eventtime=1740095200190249537 tz="+1200" logid="0100053327" type="event" subtype="system" level="warning" vd="root" logdesc="NPU health warning event" pbadelta="high(1278)" pmon="Performance monitor high in 1 modules(module name: nss )" msg="on NP(3)"

53328

Error

2: date=2025-02-21 time=11:48:22 eventtime=1740095302030217174 tz="+1200" logid="0100053328" type="event" subtype="system" level="error" vd="root" logdesc="NPU health error event" pbadelta="high(1275)" congestionsignal="Congestion 1 signal(signal name: 1 )" pmon="Performance monitor high in 1 modules(module name: nss )" msg="on NP(0)"

You can monitor FortiOS logs for these messages to be alerted with NP7 processors are under heavy load and potentially take action to reduce traffic load.

You can also use Fortinet Security Fabric automation stitches to send notifications when these log messages are generated. Set up the automation stitch configuration to use event logs as the event trigger and set the log ids to 53326, 53327, and 53328. For more information, see Automation stitches.

Example configuration:

config system automation-action

edit "test-action"

set description "testing action"

end

config system automation-trigger

edit "test-trigger"

set description "test trigger for NP driver"

set event-type event-log

set logid 53328 53327 53326

end

config system automation-stitch

edit "npu-health"

set description "check npu health"

set trigger "test-trigger"

config actions

edit 1

set action "test-action"

end

NP7 high load notifications

NP7 high load notifications

Under high load conditions, NP7 processors on FortiGates licensed for hyperscale firewall can experience NPU stuck problems that can cause CPU spikes and potential system instability.

Before an NP7 processor gets stuck, FortiOS can generate three different event log messages to flag that an NP7 processor is experiencing higher than normal load conditions.

Log ID

Message type

Example Message

53326

Info

2: date=2025-02-21 time=13:17:14 eventtime=1740100634773597762 tz="+1200" logid="0100053326" type="event" subtype="system" level="information" vd="root" logdesc="NPU health info event" pbadelta="high(1082)" msg="on NP(4)"

53327

Warning

83: date=2025-02-21 time=11:46:40 eventtime=1740095200190249537 tz="+1200" logid="0100053327" type="event" subtype="system" level="warning" vd="root" logdesc="NPU health warning event" pbadelta="high(1278)" pmon="Performance monitor high in 1 modules(module name: nss )" msg="on NP(3)"

53328

Error

2: date=2025-02-21 time=11:48:22 eventtime=1740095302030217174 tz="+1200" logid="0100053328" type="event" subtype="system" level="error" vd="root" logdesc="NPU health error event" pbadelta="high(1275)" congestionsignal="Congestion 1 signal(signal name: 1 )" pmon="Performance monitor high in 1 modules(module name: nss )" msg="on NP(0)"

You can monitor FortiOS logs for these messages to be alerted with NP7 processors are under heavy load and potentially take action to reduce traffic load.

You can also use Fortinet Security Fabric automation stitches to send notifications when these log messages are generated. Set up the automation stitch configuration to use event logs as the event trigger and set the log ids to 53326, 53327, and 53328. For more information, see Automation stitches.

Example configuration:

config system automation-action

edit "test-action"

set description "testing action"

end

config system automation-trigger

edit "test-trigger"

set description "test trigger for NP driver"

set event-type event-log

set logid 53328 53327 53326

end

config system automation-stitch

edit "npu-health"

set description "check npu health"

set trigger "test-trigger"

config actions

edit 1

set action "test-action"

end