|
On FortiGates equipped with an NP7 Chip, stopping the NPU sniffers using the command 'diagnose npu sniffer stop' may cause a traffic outage and result in the loss of access to both the FortiGate GUI and CLI.
To restore normal functionality, a reboot of the FortiGate is required.
To check if the FortiGate is affected by this issue, run the following commands over a serial console connection and verify whether all output values are zero.
FortiGate # diagnose npu np7 getreg 0 l2p.b_quad.b_quad_0.usr_arb_msk0
usr_arb_msk0 = 00000000 (00009040) <R/W>
FortiGate # diagnose npu np7 getreg 0 l2p.b_quad.b_quad_0.usr_arb_msk1
usr_arb_msk1 = 00000000 (00009048) <R/W>
FortiGate # diagnose npu np7 getreg 0 l2p.b_quad.b_quad_1.usr_arb_msk0
usr_arb_msk0 = 00000000 (00009240) <R/W>
FortiGate # diagnose npu np7 getreg 0 l2p.b_quad.b_quad_1.usr_arb_msk1
usr_arb_msk1 = 00000000 (00009248) <R/W>
This issue has been resolved in FortiOS v7.0.16, v7.2.8, v7.4.4.
Workaround:
Do not run NPU sniffer commands during production hours unless the FortiGate is running a firmware version where this issue has been resolved.
If the issue occurs, reboot the FortiGate to restore normal traffic flow.
|
