Skip to main content
A
Anonymous_User
Contributor
July 31, 2008
Question

Fortigate 60 not responding and status light off

  • July 31, 2008
  • 4 replies
  • 26424 views
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

    4 replies

    p768
    p768
    New Member
    July 31, 2008
    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.
    A
    Anonymous_UserAuthor
    Contributor
    July 31, 2008
    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
    SuperUser
    abelio
    SuperUser
    July 31, 2008
    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
    p768
    p768
    New Member
    August 1, 2008
    Have you logged a support ticket with Fortinet? You may need a new unit
    A
    Anonymous_UserAuthor
    Contributor
    August 1, 2008
    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
    A
    Anonymous_UserAuthor
    Contributor
    August 1, 2008
    Thanks for the advice. It' s probably worth mentioning that I have detailed logging to memory turned on, although there are only a small number of messages in the log, so I wouldn' t think that they were causing the memory problem. Fortinet support have responded and asked me to do an advanced hardware test. Andy
    FortiRack_Eric
    FortiRack_Eric
    New Member
    August 4, 2008
    Please upgrade to minimal MR3.0 MR5p4 Regards, ERic
    Terms & ConditionsAccessibility statement