How to Flash a RED 50 rev1

Hallo Niko and welcome to the UTM Community!

Others have reported here recently that Up2Dating to 9.601/2 seemed to break their RED.  The first thing to try is to remove and replace the RED in WebAdmin.  Don't forget to write down the unlock code before deleting!  Any luck with that?

Cheers - Bob

Dear Bob

I have the same Problem. Is there a solution to flash the RED 50 V1 with the newest Firmware and then
provisioning the RED with the UTM (like USB Stick).

Regards and thank for your Input.

Phil

Hallo Philipp and welcome to theUTM Community!

In March, Martin (twister5800) said the following solved his problem with RED devices.  As root at the command line:

cc set red use_unified_firmware 0

Any luck with that?  If not, and you're on 9.601, try Up2Dating to 9.602 as Martin said that also resolved the issue.  If all else fails, get a case started with Sophos Support.

Cheers - Bob

We had a RED50 Rev1 that 'bricked' with the 9.601 update. There was nothing we could do to re-flash the firmware. We created a USB stick according to the listed procedure but the RED50 would not even access the USB stick from either USB port on the device. The indicator light on the USB stick never even illuminated.

The unified firmware bug will brick a RED50 completely. Useless POS after that. Get an RMA and have it replaced. Then follow the advice on the other thread and make sure to not use the unified firmware by setting CC SET RED USE_UNIFIED_FIRMWARE flag =0 from the command line of your UTM. Note that the flag is not persistent for future updates and the RED(s) will need to be disabled before a further update, then the flag needs to be set =0 again then re-enable the RED(s).

We had a RED50 Rev1 that 'bricked' with the 9.601 update. There was nothing we could do to re-flash the firmware. We created a USB stick according to the listed procedure but the RED50 would not even access the USB stick from either USB port on the device. The indicator light on the USB stick never even illuminated.

The unified firmware bug will brick a RED50 completely. Useless POS after that. Get an RMA and have it replaced. Then follow the advice on the other thread and make sure to not use the unified firmware by setting CC SET RED USE_UNIFIED_FIRMWARE flag =0 from the command line of your UTM. Note that the flag is not persistent for future updates and the RED(s) will need to be disabled before a further update, then the flag needs to be set =0 again then re-enable the RED(s).

Thank you! We were struggling to get a clear answer from support on whether or not future UTM Upgrades would require that flag be set. Based on your response we have to actually disable each RED first, apply the update, set the flag and re-enable the devices? 

Hi ignitor,

According to this post by BAlfson from the thread referenced above, yes, that is correct:

BAlfson said:

I just got this from Sophos Support:

1. Are any other REDs in danger of being bricked, or is it just the RED 50?
- So far we have only seen RED 50 but this doesn't rule out RED 15
2. In High Availability, does use_unified_firmware need to be set to 0 on all nodes?
- No it would replicate the command
3. Instead of physically unplugging REDs, would it suffice to disable the RED server objects in WebAdmin before applying the Up2Date and then enable them after 9.604 has had use_unified_firmware set to 0?
- In theory yes if you disable the service in the UTM or turn off the RED devices, then they won't be able to get the Firmware Update, so they won't be able to contact the server, and once you re-enable the services they will not search for a new firmware update

Cheers - Bob

Garth

Thanks again!

Hi all,

in ref to my thread: https://community.sophos.com/products/utm-firewall/f/remote-ethernet-device-red/121385/is-there-really-no-way-to-restore-a-bricked-red-50/441251#441251

Can somebody confirm that the Red50 is PowerPC based !?

Thx & best.