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 37583 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.
  • 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

  • FormerMember
    0 FormerMember

    Hi,

    Navigate to the option 5 (Device Management) > Option 2 (Show Firmware (s))

    You will see tow firmware available as shown below.

    Device Management

    1. Reset to Factory Defaults
    2. Show Firmware(s)
    3. Advanced Shell
    4. Flush Device Reports
    0. Exit

    Select Menu Number [0-4]: 2


    Firmware 1: SFOS 17.5.7 MR-7
    Firmware 2: SFOS 17.5.8 MR-8
    Current Firmware: Firmware 2
    In my case I had current firmware 17.5.8 MR8 so I had to run : rebootfw -f 1 and firewall rebooted with the firmware version 17.5.7 MR-7.

    SFVUNL_VM01_SFOS 17.5.8 MR-8# rebootfw -f 1

    Firewall rebooted with 17.5.7 MR-7

    Firmware 1: SFOS 17.5.7 MR-7
    Firmware 2: SFOS 17.5.8 MR-8
    Current Firmware: Firmware 1

     Thanks,

  • 0 in reply to FormerMember

    Yeah, i have been doing that, except:

     

    Firmware 1 = 17.5.0 GA

    Firmware 2= 17.5.8 MR-8

    When i run the rebootfw -f 2, it times out with the "Broken pipe" after a while.

  • 0 in reply to bladefox3

    Is it a HA? 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    Yes, HA was disabled abruptly during the firmware upgrade, one unit did it ok, the secondary did not. And now the only way to reach the secondary is to ssh from the main unit via the Port3/DMZ IP address, and try run these commands that dont seem to be going through.  The firmware shows up on the secondary unit as Firmware 2: 17.5.8 MR-8, but rebootfw -f 2 wont run.

Unfiltered HTML