Fortigate 60 not responding and status light off

[#1]

Hi all I have come in to work this morning to find our Fortigate 60 is not responding. We have no internet access, naturally, although the unit is powered up. I power cycled it and all the lights that should come on do, except for the status light which comes on while it' s starting up and then goes off. I can' t ping the unit' s address. The internal switch is working because I can plug a PC into the back of it and still get an IP address from our DHCP server (not the fortigate). I tried changing my ip address and attempting to communicate with the default address, just in case it had somehow reset to default. No joy there either. I tried connecting via the serial cable supplied with it but the stupid cable has the wrong connector at one end. it needs to be female-female, instead it is female-male Any ideas?! Thanks in advance Andy

[p768]

You will need a console connection to see the boot sequence. The flash maybe corrupt, if so, you will need to TFTP a new flash image and restore the config.

[#3]

Thanks for the reply. I now have a console connection but have no idea how to use it. I have a CLI reference guide which is for v2.80, I think mine is v2.50. None of the commands seem to work. Sorry for being dim! I do have a backup of the config, is that what I need to restore, or something else as well? I got a copy of the right CLI guide now, I tried backing up the config via TFTP, which still appears to be correct, and the copy failed because ' Network is unreachable' Can I send/receive files from the COM port using CLI? edit: OK, I have resorted to restoring to factory defaults. I still can' t communicate with the firewall even using it' s default configuration and default ip. I have a PC on the same subnet plugged into the firewall' s internal port and I can' t ping the firewall from the PC and I also can' t execute a ping outwards from the firewall' s CLI. It says ' network unreachable' . I am unsure if this is a hardware or a config problem, as the unit is still passing traffic to and from the internal network, I just can' t communicate with it that way. Help, I' m really confused now! Andy

[abelio]

I tried backing up the config via TFTP, which still appears to be correct, and the copy failed because ' Network is unreachable' Can I send/receive files from the COM port using CLI?

... no Andy, you' re really confused in this point; Try to follow step by step guide detailed here: http://kc.forticare.com/default.asp?id=338&SID=&Lang=1

[#5]

After a few hours of having the unit working again, it' s now back to a non-working state. I managed to get the firmware and config re-loaded and everything was working yesterday. Now today, it is not responding via the network again. I can communicate via console port and all configuration appears OK except that the network is unreachable from any interfaces. Interface status is UP on all interfaces. The status light remains OFF during operation. when booting up, the light comes on during initial boot-up and then goes off after the firmware image has been loaded and before ' initialising firewall' . Whatever the problem is, it must be intermittent, as it was working for a while after a re-load. I can' t work out whether this is a hardware or a configuration problem. Any further advice gratefully received. Andy

[abelio]

I can communicate via console port and all configuration appears OK except that the network is unreachable from any interfaces. Interface status is UP on all interfaces.

what about the network? wires, power, environmental conditions?

The status light remains OFF during operation. when booting up, the light comes on during initial boot-up and then goes off after the firmware image has been loaded and before ' initialising firewall' .

that' s normal.

[#7]

The rest of our network is working fine. Only communication in or out of the firewall is affected. The manual says that the status light should be on. It says that flashing is an error, but doesn' t mention what it means when it is off. I have left the console PC attached and noticed a couple of errors: Out of memory. Killed process 25 (updated) Out of memory. Killed process 64 (updated) Are these relevant? Andy

[abelio]

I have left the console PC attached and noticed a couple of errors: Out of memory. Killed process 25 (updated) Out of memory. Killed process 64 (updated) Are these relevant?

ah ok, i guess that those messages are completely relevant Likely you' re running your box out of resources and it' s going to ' conserve mode' re-check settings, follow article: http://kc.forticare.com/default.asp?id=1076&SID=&Lang=1 Also consider to use a MemOpt Fortios firmware for that 60.

[p768]

Have you logged a support ticket with Fortinet? You may need a new unit

[#10]

Yes I have. It is looking like I' ll need a new unit, however I know that will take a few days which is why I' m desperately trying to find a fix. The problem witrh fortigate ticket support is that we are in 2 different timezones and replies are very slow. Trouble shooting could take a week! Andy