Skip to main content
jkim86
jkim86
Explorer
January 3, 2022
Question

Fortigate 50E Dying. Packet loss and lan ports stop forwarding. Update 2022-02-03 6th unit.

  • January 3, 2022
  • 20 replies
  • 33454 views

Anybody else seeing a pattern with 50E dying? I had these deployed for about two years. I've had two starting to have packet loss and one that's not forwarding even though port is up. I saw a thread on reddit and this is starting to become a growing concern. I was able to have the client replace two of them but I'm afraid we're going to start seeing more problems with the 50E. Anybody know if we can RMA these still without support? The client is going to lose confidence in Fortinet. This rate of failure is unacceptable.

 

Update 2022-02-03:

Had another two breaking down. 1 is showing slow speeds. The other one isn't passing traffic even though port is up. 6th 50E broken now.

 

Update 2022-04-26:

2 more units bad.

20 replies

AlexC-FTNT
Staff
AlexC-FTNT
Staff
January 4, 2022

Hardware support is needed to be able to open a case that leads to RMA, so no, you can't RMA the unit without support. First we need to prove that packet loss - so check first that the unit is not enetring conserve mode, or that a hardware test (HQIP test) has been performed to prove the RMA. Simply stating that "we see packet loss" without actual proof is not enough for RMA.

    jkim86
    jkim86Author
    Explorer
    January 4, 2022

    ya just starting to see a trend here since 2 units suddenly have packet loss when they weren't having any problems before and a 3rd unit that stopped working on lan1. All reported in the last two months. Also reading other users on reddit experiencing similar problems with his 50E and already replaced 4 last year.

    jkim86
    jkim86Author
    Explorer
    January 4, 2022

    I'll run the HQIP tests once I replace the units from the remote sites and get them back.

    yashwani
    Staff
    yashwani
    Staff
    January 4, 2022

    HQIP tests are required to confirm issues with hardware, alternatively if TAC confirms for RMA after troubleshooting. 

      jkim86
      jkim86Author
      Explorer
      February 3, 2022

      Had another two breaking down. 1 is showing slow speeds. The other one isn't passing traffic even though port is up. 6th 50E broken now.

      bezeqsoc
      bezeqsoc
      New Member
      March 28, 2022

      Same problem.
      Have to replace 5 units in the last 2 month during packet loss issue.

      All ours are with different versions but above 6.x.x

      Could it be a software problem?

      AlexC-FTNT
      Staff
      AlexC-FTNT
      Staff
      March 28, 2022

      Yes and no. The new firmware comes with new features, but the hardware specs on the 50E remain unchanged. So you may see that 6.2 version doesn't have enough space on flash memory to run (diag sys flash list) and that causes crashes, reboots, conserve modes, etc (ultimately seen as 'packet loss').

      You can ask for replacement, but RMA is not the solution. You need to run FortiOS 6.0, or  a very minimum configuration in newer version (no GeoIP, extended IPS database, etc). FortiOS 6.2.11 will have a fix to that (can't give technical details behind it, but I assume some features will be disabled in order to make it run stable)

        bezeqsoc
        bezeqsoc
        New Member
        March 28, 2022

        In my case I have packet loss with no uplink connection - just workstation connected directly to the unit after factory reset There is no packet loss when connected to wan1/wan2 interface
        Looks like lan ASIC is dead or something...

         

        bezeqsoc_0-1648490646424.png

        Also, especially downgraded to  5.6.14 - no effect, the problem persist.  

        jkim86
        jkim86Author
        Explorer
        May 5, 2022

        Interesting. I got some units back and I also found the WAN ports are working.

        jkim86
        jkim86Author
        Explorer
        April 27, 2022

        Found two more that are dying. :loudly_crying_face:

        DittB
        DittB
        New Member
        November 10, 2022

        I hava also 2 out of 7 with the same error. The problem comes from the Internal Switch (Port 1- Port5). If you use only Port WAN1 and WAN2 there is no Problem. We use WAN2 as Internal LAN, this "fixed" the Problem on both units 

        pirmin
        pirmin
        New Member
        November 22, 2022

        Hi, I have also 2 50E which have the same problem. Is there any solution for this problem now?

         

        jkim86
        jkim86Author
        Explorer
        November 22, 2022

        You can try testing port WAN1 and WAN2. 

        pirmin
        pirmin
        New Member
        November 23, 2022

        Thanks for your reply but this is no Option because I need at least 3 interfaces.

        badnerone
        badnerone
        Visitor III
        December 8, 2022

        At the moment 2 fgt 50E 1 fwf 30E in the last month with the same problems. For me it's a hardware problem, in fact with a fgt 50e I formatted the boot partition and put firmware 6.2 via TFTP (before 6.2.12) but I have the same problem. Of course the machines have the standard warranty expired... It is definitely no coincidence that all the same models have the same problems. Fortinet should at least say if the problem officially exists and what causes this type of (serious) problem and if there is a solution.

        forti1
        forti1
        New Member
        December 28, 2022

        In the last six months, three FG-50E systems have also failed with the same phenomenon. We still have 18 of this model in use, which we now have to replace proactively. Annoying

        Show more replies
        Terms & ConditionsAccessibility statement