Skip to main content
Derek_Tom
Derek_Tom
New Member
June 1, 2011
Question

Firmware update error: File is not an update file

  • June 1, 2011
  • 4 replies
  • 19184 views
Hello all, I am trying to update the firmware of my old Fortigate 200A to the latest version. Currently running Fortigate-200A 2.80,build359,050210. Tried updating multiple times via the GUI with these firmware image files (confirmed checksums)... FGT_200-v280-build184-FORTINET.out FGT_200-v280-build219-FORTINET.out FGT_200-v280-build250-FORTINET.out Each time I try after 30 seconds or so I get this error: Error File is not an update file. Any suggestions? The aim is to eventually get up to the latest v4.0MR3. Thanks, Derek

    4 replies

    jmac
    jmac
    New Member
    June 1, 2011
    1) You have a FortiGate 200A and the firmware files are for the FortiGate 200 (different model) 2) If you' re on v2.8 build 359, wouldn' t the other firmware images in your list be downgrades?
    Derek_Tom
    Derek_TomAuthor
    New Member
    June 1, 2011
    @jmac, thank you so much. Yes, I had been trying with the wrong image files! Yes, I realize now those would have been downgrades. The MR numbers were really throwing me off. So confusing. Thanks again, Derek
    Derek_Tom
    Derek_TomAuthor
    New Member
    June 1, 2011
    Yikes, I have another problem now... I just updated from FGT_200A-v280-build519-FORTINET.out to FGT_200A-v300-build0660-FORTINET.out but after logging in I' m taken directly to the System > Network page. I am missing the critical System > Status homepage! Any suggestions? Thanks, Derek
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    June 1, 2011
    Keep cool...that' s not the reason for not seeing the System page. a) you' ve done everything right - RN say you can upgrade from 2.80 to 3.00MR6 and you did b) these precautions only prevent that the config is lost between updates. If you take a FGT and put any firmware on it it must come up with all features of that version - no matter what the previous one was. I suspect that you have old copies of Java scripts in your browser cache. Clear the cache and/or use a different browser to check that. Basically you' re free to upgrade to any version if the config doesn' t matter.
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    June 1, 2011
    You could even upgrade to the latest 3.00 release, 3.00MR7 patch10 (b754) from 2.80MR11. So, MR5 or MR6 is not the issue here. As long as the display mismatch is not resolved no reloading any firmware will help you.
    Derek_Tom
    Derek_TomAuthor
    New Member
    June 1, 2011
    Thanks for the insightful info. Unfortunately for me, I did clear my browser' s cache several times and have tried Firefox 4 on Mac, Safari on Mac, and IE8 on a PC and all of them do not show the Status page upon login. I will need to sleep now as it' s past midnight here in Hong Kong. Will check back here tomorrow morning. Thanks again, guys.
    rwpatterson
    rwpatterson
    New Member
    June 1, 2011
    Back in some of the older firmwares (pre v3, MR5 or so), there was sometimes instances where the memory wouldn' t clear before an upgrade if the devices had been on for an extended length of time. This happened to me once. I had started rebooting directly before any upgrades due to this. That issue has been resolved in later versions of code. Once my unit got corrupted though, all I could do was a rebuild. Try reloading the same version again over itself if you can.
    ede_pfau
    SuperUser
    ede_pfau
    SuperUser
    June 2, 2011
    I don' t think that you need to download the image by serial (Xmodem) as the FGT itself is still running, right? Get on the CLI (via ssh or console port/serial) and type " exec restore ?" to see the options. All FGTs around me are on v4.00 plus now so I can' t tell what you' ll see in v2.80. But it should look like you could " exe restore image [ftp|tftp|usb]" . OK maybe USB is not an option with your FGT. The download would then be via Ethernet which is way faster and more secure. And yes, you can use the same PC for the serial console connection and the TFTP server. I always do. If all fails there is a boot menu that you can enter while rebooting. You can enter an IP address for the FGT and download an image. But I' d try the CLI first. If you TFTP to the FGT note that you can only use a certain port to connect. In general this would be port1/internal. Not all ports are scanned for a connection attempt. Then, " exec factoryreset" will put in default config values - including the internal IP which is set to 192.168.1.99. You can change that easily via the console connection. Secondly, " exec formatlogdisk" would be a good idea if you skip several releases.
    Terms & ConditionsAccessibility statement