Thread Info
  • State Verified Answer
  • +5 person also asked this people also asked this
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 47 subscribers
  • Views 37617 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How do I boot to previous firmware with Putty?

Rick Leslie

Hi All,

 

I 'upgraded' to firmware version 17 MR2 from 17 MR1.

 

Since the 'upgrade' I cannot access the web UI - I get a blank page with "Internal Server Error" in the top right corner in response to login submission.

 

I do not have easy access to connect a terminal cable but I can get access through Putty.

 

Is there a way to remove the MR2 or boot to MR1 using a connection with Putty?

 

Thanks 



This thread was automatically locked due to age.
Parents
  • +3

    When you ssh in to the firewall, go into Device Management, then Show Firmware(s). Make a note of the firmware numbers and the current firmware in use.

    Then go into Advanced Shell and type the following:

    rebootfw -f <n>

    where <n> is the firmware number not in use.

    That is, if Firmware 1 is the current firmware, then <n> is 2, and vice versa.

Reply
  • +3

    When you ssh in to the firewall, go into Device Management, then Show Firmware(s). Make a note of the firmware numbers and the current firmware in use.

    Then go into Advanced Shell and type the following:

    rebootfw -f <n>

    where <n> is the firmware number not in use.

    That is, if Firmware 1 is the current firmware, then <n> is 2, and vice versa.

Children
  • 0 in reply to ChrisKnight

    Cheers it solved the problem. But when try to upgrade the box again to 17.0.2-mr2 resulted in same problem again. Is this is known issue or upgrade seem to regenerate same problem again?  I have upgraded two boxes (running in HA mode) at our production site with no issue. However, I am not being able to upgrade my DR box. Logically it doesn't seems to be known issue. What do you say. How can I upgrade cleanly, any ideas?

  • 0 in reply to Taufeeq Rauf1

    Hi,

     

    see the below link for boot old Firmware.

    i am also received the same issue after upgrading.

    community.sophos.com/.../125209

    Regards,

    Kamal Patel 

     

  • 0 in reply to Taufeeq Rauf1

    I'd download the upgrade file from the Sophos site, verify that the checksums match, back up the configuration, perform a factory reset, perform the upgrade, then either restore the backup or reconfigure from scratch (preferrred method when upgrades fail like this).

    Failing that I'd log a support ticket with Sophos and get them to investigate.

  • 0 in reply to ChrisKnight

    OK will ask my engineer at DR site to perform the above mentioned steps. 

  • 0 in reply to ChrisKnight

    When i try this for an HA unit that has unbound and disabled HA due to a failed firmware update, the Putty terminal connection reports "broken pipe" , never actually completes rebootfw -f 2

    The firmware appears to be in the list of applied firmware son the secondary unit, but i cant access the secondary any other way by SSH over the HA IP address, because the failed update disabled and unbound all the other interfaces except for the HA / DMZ Port3 on this XG105.

    The firmware i am trying to get it up to is the one on the primary unit which is 17.5.8 MR-8, the secondary unit is stuck 17.5.0 GA.

    Any thoughts on how to make the rebootfw -f 2 actually proceed on the secondary unit?

     

    Thanks,

    bf3

Unfiltered HTML