Description

On EX3200 / EX4200 you may see the message, "mrvl_dfw_log_effuse_status: Firewall rows could not be redirected on device 0", displayed in the log.  This is a harmless message if the steps listed (workaround) correct the issue.  It is also corrected in later Junos releases.

Symptoms

Large number of “mrvl_dfw_log_effuse_status” messages seen for device 0 before and after a reboot of the EX Switch.

Sep 27 11:41:15 ex-switch-1 fpc0 mrvl_dfw_log_effuse_status: Firewall rows could
not be redirected on device 0.

Sep 28 02:11:18 ex-switch-1 fpc0 mrvl_dfw_log_effuse_status: Firewall rows could
not be redirected on device 0.

Oct 5 12:19:00 ex-switch-1 fpc0 mrvl_dfw_log_effuse_status: Firewall rows could
not be redirected on device 0.

Oct 5 12:49:00 ex-switch-1 fpc0 mrvl_dfw_log_effuse_status: Firewall rows could
not be redirected on device 0.

Solution

Problem:

Large number of “mrvl_dfw_log_effuse_status” messages seen for device 0 before and after a reboot of the EX Switch.

Sep 27 11:41:15 ex-switch-1 fpc0 mrvl_dfw_log_effuse_status: Firewall rows could not be redirected on device 0.

Sep 28 02:11:18 ex-switch-1 fpc0 mrvl_dfw_log_effuse_status: Firewall rows could not be redirected on device 0.

Oct 5 12:19:00 ex-switch-1 fpc0 mrvl_dfw_log_effuse_status: Firewall rows could not be redirected on device 0.

Oct 5 12:49:00 ex-switch-1 fpc0 mrvl_dfw_log_effuse_status: Firewall rows could not be redirected on device 0.
=======================
Root Cause:
These messages can be seen after a reboot of the EX Switch due to a known issue related to PR/537400, and are harmless messages. However, if after multiple reboots (4-5) these messages are still being generated continuously then the unit can be replaced.  It is suggested that if you continue to see these messages that you first upgrade the Junos OS to recommended fixed release below.

PR/537400 - Intermittent Device 0 failures from "show halp-dfw effuse-status"

Release Note:
On the EX3200 and EX4200 switches after a hardware reboot and initialization, when the switch is rebooting the following message might appear: "Firewall rows could not be redirected on device 0". This message is a false positive and is
generated intermittently due to a timing issue.If you see this message during consecutive reboots, contact the Juniper Technical Assistance Center (JTAC).

Workaround:
Reboot the EX Switch and if issue persists may require additional reboots (See above)

Solution:
This PR is fixed in the following releases:

10.0S10, 10.1R4, 10.2R4, 10.3R2, 10.4R1, 11.1R1 and any later release.

=======================