EX4300 members are prone to an issue which can lead to them crashing abruptly.

Typically, no specific logs are observed on the device when this is hit.

Symptoms seen in the past include device ending up in hang or reboot.

However, if the device is running CPLD v2.6, the reset reason is captured in the CPLD register as a catastrophic error.

This can be verified using the following:

• Access hshell and run:
• root@bng-node:/var/log# relpcfpga -r 0x208
• 0x04 indicates a catastrophic error.
• Alternatively, check: /var/log/reset_reason
• (This must be collected prior to reboot. A reboot may overwrite this value.)

• A fix is available through updated BIOS and CPLD versions for EX4300 platforms.
• Juniper suggested upgrading to CPLD v2.5 and BIOS v29.01 with a supported JUNOS release.