Skip to main content
graemeb
graemeb
New Member
January 15, 2025
Solved

Stuck at v7.0.17

  • January 15, 2025
  • 4 replies
  • 14700 views

I got FortiCare today so downloaded some firmware off the site following upgrade path then the UI offered to do upgrades in the console rather than manual.

 

Now it is at v7.0.17 and the upgrade path tool goes up until only 7.0.16 so I don't know how to move up to 7.6.

 

"

Firmware Management

 
 

Current FortiGate versionv7.0.17 build0682 (Mature)

Select Firmware

Latest
All Upgrades
All Downgrades
File Upload
The firmware is up to date."
 
This is from console.
 
Thank you.
Best answer by Matt_B

It's not because v7.0.17 was new, upgrade from chronologically later (v7.0.17) releases to chronologically earlier (v7.2.10) releases is not supported. That's because those upgrade steps are not QA-tested. Upgrade v7.0.17->v7.2.10 or earlier should be considered similar in risk to downgrade or upgrade without following path, worst case is corruption or failure to boot.

If there are issues with unsupported upgrade often they are specific to the platform or configuration so unfortunately can't rely on it working once. If it's not urgent I would recommend to wait for v7.2.11.

 

Upgrade from v7.0.17->v7.2.10 might work, but it's not supported. If making that choice I would have no expectations and local serial console access in case booting from backup partition is necessary.

4 replies

Toshi_Esumi
SuperUser
Toshi_Esumi
SuperUser
January 15, 2025

It is safe to assume the upgrade path from 7.0.16 to 7.6.x is the same with from 7.0.17. Especially the 7.0.17 doesn't have many changes. Only two are listed now.

Toshi

AEK
SuperUser
AEK
SuperUser
January 15, 2025

What is your FortiGate model, your current version, and the version you want to move to.

AEK
graemeb
graemebAuthor
New Member
January 15, 2025

60f Wifi, v7.0.17 to latest which is 7.6 I think.

Cheers

AEK
SuperUser
AEK
SuperUser
January 15, 2025

You are right. The upgrade path tool doesn't include the 7.0.17 as current version, probably because 7.0.17 is very new (released yesterday), so I believe Fortinet will correct the web page in the next few days.

 

On the other hand if you FGT is in production environment then I think you shouldn't upgrade to 7.6.1, but you should upgrade to 7.2.10, which is the version recommended currently by Fortinet.

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Recommended-Release-for-FortiOS/ta-p/227178

Hope it helps.

AEK
graemeb
graemebAuthor
New Member
January 15, 2025

Thank you and moved a few steps up and now on a Mature version.

 

Is 7.6.1 not exactly a prod release? I am not on it as you said.

dingjerry_FTNT
Staff
dingjerry_FTNT
Staff
January 15, 2025

Hi @graemeb ,

 

Of course, FortiOS 7.6.1 is a production release.

 

Please check this:

https://docs.fortinet.com/document/fortigate/7.6.1/administration-guide/173707/firmware-maturity-levels

Toshi_Esumi
SuperUser
Toshi_Esumi
SuperUser
January 16, 2025

MvsF.png

7.6.1 is still Feature(".F") release version, which means new features are added. I would at least wait until Mature(".M") versions come out.

Toshi 

Matt_B
Staff & Editor
Matt_BAnswer
Staff & Editor
February 10, 2025

It's not because v7.0.17 was new, upgrade from chronologically later (v7.0.17) releases to chronologically earlier (v7.2.10) releases is not supported. That's because those upgrade steps are not QA-tested. Upgrade v7.0.17->v7.2.10 or earlier should be considered similar in risk to downgrade or upgrade without following path, worst case is corruption or failure to boot.

If there are issues with unsupported upgrade often they are specific to the platform or configuration so unfortunately can't rely on it working once. If it's not urgent I would recommend to wait for v7.2.11.

 

Upgrade from v7.0.17->v7.2.10 might work, but it's not supported. If making that choice I would have no expectations and local serial console access in case booting from backup partition is necessary.

Is it a bug, is it a feature? It's... not in spec!
    AEK
    SuperUser
    AEK
    SuperUser
    February 10, 2025

    Thanks Matt. Very useful information that we can only find here.

    AEK
    Matt_B
    Staff & Editor
    Matt_B
    Staff & Editor
    February 13, 2025

    Sometimes, useful info you can only find in one place is wrong! v7.2.11 was released yesterday and v7.0.17->v7.2.11->v7.4.7 is a supported upgrade path despite breaking the rule of thumb I just gave (v7.2.11 released 2025-02-12, v7.4.7 released 2025-01-21). I think that would match most customer expectations too, apologies for misstating it.

    To get more granular with this, in FortiOS upgrade from the latest patch in earlier Minor Version to latest patch in the next Minor Version is usually QA-tested and supported even if the target firmware image was released chronologically earlier. However this is is not always true and is in fact one of the major reasons for providing upgrade path information. v7.0.17 has no recommended path to v7.2.10.

    One thing that's almost always true though- there is a cut-off for how early you can go in the next firmware version via supported upgrade paths. For example, v7.0.16 -> v7.2.9 is a supported upgrade path for most platforms. v7.0.16->v7.2.8 and earlier is not.

    Is it a bug, is it a feature? It's... not in spec!
      Terms & ConditionsAccessibility statement