Hello!
I need help regarding the procedures to use the HQIP firmware with an defective FGT50B. During boot via console i get the following error:
FGT50B (14:15-10.01.2008) Ver:04000010 Serial number:FGT50B3G11604210 RAM activation Total RAM: 256MB Enabling cache...Done. Scanning PCI bus...Done. Allocating PCI resources...Done. Enabling PCI resources...Done. Zeroing IRQ settings...Done. Verifying PIRQ tables...Done. Enabling Interrupts...Done. Boot up, boot device capacity: 64MB. Press any key to display configuration menu... ......
Reading boot image 1364800 bytes. Initializing firewall... System is started. stat('/data/./config/global_system_interface.gz') failed: Input/output error
I have uploaded the HQIP Firmware and run it but it gets stuck in this part:
Reading boot image 1364800 bytes.
Initializing firewall...FGT50B (14:15-10.01.2008)
Ver:04000010
Serial number:FGT50B3G11604210
RAM activation
Total RAM: 256MB
Enabling cache...Done.
Scanning PCI bus...Done.
Allocating PCI resources...Done.
Enabling PCI resources...Done.
Zeroing IRQ settings...Done.
Verifying PIRQ tables...Done.
Enabling Interrupts...Done.
Boot up, boot device capacity: 64MB.
Press any key to display configuration menu...
..
: Quit menu and continue to boot with default firmware.
Enter Selection
Enter G,F,I,Q,or H:
Please connect TFTP server to Ethernet port "3".
Enter TFTP server address [192.168.1.168]: 172.22.5.41 Enter local address [192.168.1.188]: 172.22.5.43 Enter firmware image file name [image.out]: 50b-hqip-fl12.out MAC:00090FF073CA ############## Total 15595889 bytes data downloaded. Verifying the integrity of the firmware image.
Total 28288kB unzipped. Save as Default firmware/Run image without saving:[D/R]?r ........................... Reading boot image 1642184 bytes. Initializing firewall... System is started. pid=1 get sig=11
Whitch is the next step so i can test this unit? Is it supposed to be executed automatically?
Based on the output, you'll likely have to reformat the 50B before installing/running any firmware. If you have not already backed up the config on it (and need to), you could try booting from the backup firmware (assuming it is not the original diag firmware) and see if you can log into the device that way.
NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
Hello Dave
A have do what you said but eve then the same error appears:
FGT50B3G11604210 login: FGT50B (14:15-10.01.2008)
Ver:04000010
Serial number:FGT50B3G11604210
RAM activation
Total RAM: 256MB
Enabling cache...Done.
Scanning PCI bus...Done.
Allocating PCI resources...Done.
Enabling PCI resources...Done.
Zeroing IRQ settings...Done.
Verifying PIRQ tables...Done.
Enabling Interrupts...Done.
Boot up, boot device capacity: 64MB.
Press any key to display configuration menu...
..
: Quit menu and continue to boot with default firmware.
Enter Selection
Enter G,F,I,Q,or H:
Please connect TFTP server to Ethernet port "3".
Enter TFTP server address [192.168.1.168]: 172.22.5.41 Enter local address [192.168.1.188]: 172.22.5.43 Enter firmware image file name [image.out]: 50b-hqip-fl12.out MAC:00090FF073CA ############## Total 15595889 bytes data downloaded. Verifying the integrity of the firmware image.
Total 28288kB unzipped. Save as Default firmware/Run image without saving:[D/R]?r ........................... Reading boot image 1642184 bytes. Initializing firewall... System is started. pid=1 get sig=11
Nothing happens after this. Is there a comprehensive step-by-step i can follow?
Thanks.
Yeah i know its old, but it works for us. It has everything we need.
Give the format a try but the HQIP image runs from flash IIRC. So I bet you have some other problem(s). A FGT50B is quite old so good luck in whatever your outcome becomes.
PCNSE
NSE
StrongSwan
emnoc wrote:Give the format a try but the HQIP image runs from flash IIRC. So I bet you have some other problem(s). A FGT50B is quite old so good luck in whatever your outcome becomes.
Thanks Emnoc, but sadly it didnt help my case. There is still that pid=1 get something at the end. The error gets resolved after a reformat and reflashing of the firmware, But i would like to learn how to use this firmware to diagnose units that are close to death.
Thanks.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.