Actually, I think you might need to apply this patch below for release 5 and 6?.
Doc ID: SOLN209464
Version: 4.0
Status: Published
Published date: 31 Aug 2012
Updated: 25 Feb 2013
Author:
Marcel Comeau
Details
BCM 450 R600 has rebooted on it's own. Root Cause Analysis.
Problem Clarification
Logs Determine that the BCM reboot was caused by Hardware watchdog and/or External Soft Reset.
This issue has been addressed with 2 patches, depending on the Release of the BCM.
Cause
Indicates FPGA register corruption.
Solution
Software Update Name: BCM450.R500.FPGA-116
or
Software Update Name: BCM450.R600.FPGA-78
Installation Recommendations:
This update should be applied to BCM450 Release 5.0 or 6.0 installations which is
going for an external soft reset or Hardware Watchdog reset.
CAUTION:
Installing new FPGA firmware on a BCM is comparable to upgrading the
BIOS on a Windows PC. When this patch is applied the BCM should not be
interrupted or power cycled. If disturbed the FPGA may get corrupted and
the BCM may render non-recoverable.
It is strongly recommended that one connect the BCM 450 system to a UPS power
backup to ensure that there are no power interruptions during the upgrade
process.
There must be no call activity during patch installation.
It is advisable to have a standby BCM in case the system would fail for
unforeseen reasons.
The power LEDs may change from solid green to blinking yellow under high SPI
stress. This is an expected behavior and does not have any operational
impacts.
It is advisable to apply the latest kernel patch before applying this patch.
During the fpga installation both power and status LEDS will be turned off.
This is normal operation when installing an fpga patch.
The BCM will reboot if the patch installs successfully. If for some unforeseen
reason the patch fails to install the BCM will NOT reboot. if the patch
fails to install DO NOT REBOOT THE BCM. Contact Avaya support for assistance.
It is possible that the Element Manager(EM) might hang during this installation.
If this scenario is experienced, please kill the EM using task manager and re-open the EM. If BCM is getting connected after 7 minutes from the time of applying the patch, collect the logs from BCM and send it Avaya for investigation. Please note if the EM get connected without any error message then the patch is applied successfully.
All the best
Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK
If it's working, then leave it alone!.