Skip to main content
bartman10
bartman10
New Member
March 21, 2016
Question

FWF-50E Known broken but still selling them!!!

  • March 21, 2016
  • 2 replies
  • 20922 views
FWF-50E Hard Lock if you use the WiFi!! They know it and still shipped it!

 

Ok.. I found out why all 3 FWF-50E they have sent me hard lock and why some of you have no issue with FG-50e. It's because the WiFi in the unit. If you had the WiFi unit and used the WiFi your unit would hard lock also. Why? Because it's a known defect with the power management on the WiFi and affects ALL FWF-50E's and they think FWF-30E's....

THEY KNEW about it and still sold the device!!! Then spent a month of my time collecting logs and goofing around only to tell me.. oh it's a known issue and they think it'll be fixed in 5.4.1 sometime next month or two!!

 

ARE YOU FREEKING KIDDING ME! Do you truly expect me to believe QA just missed the fact that the WiFi edition of this device HARD LOCKS if infarct you actually use said WiFi?! How do you miss that!! HOW! Or... they knew it and said screw it ship it and we'll fix it later!

 

Then I spent a month goofing around with support only to have level 3 tell me it's a known issue! He also wanted to collect more logs that nigh as if they didn't waste enough of my time. What's truly amazing is I only discovered this because I took the unit home for training and found it crashed every night. Hard lock up, not even serial cable access. So I would rip apart my home network every nigh after work to make it crash and get them logs or something. They also RMA'd the unit 2 times.

I was supposed to take this unit and install it in Gary Indianan, which is 5 hours 1 way! Can you imagine the fun I would have had with this thing crashing remotely and taking down the office like this?! How much more fun that month of troubleshooting would have been taking production down instead of my kids watching Youtube at home!

 

Sorry for the RANT and grammar/spelling mistakes.. but I'm so mad I just wanted to vent somewhere and warn any other users so they don't spend all this time goofing around with support like I did on a known broken product.

 

Thanks,

Bart

    2 replies

    emnoc
    emnoc
    New Member
    March 21, 2016

    So if it's a known issues,  what's the bug reference number?

     

    ( general comments )

     

    Also how do you think they will "not ship" a unit? they have these in the delivery pipeline so it isn't like FTNT have a recall button or self-destruct sequence.

     

    Also you have to be very brave to put 1> a brand new model into a production environment  & 2> on the 1st and only revision but I'm glad it was you and not me ;)  Stick with  a prove hardware that has a reputation is never a bad thing.

     

    FWIW; My FWF50E has been delayed in shipping and I'm guess that 's a good thing. I might just cancel the order the more and more I think about it.

     

    I do feel your pain  & agreed in that Quality is really dropping in  FTNT lineups & it's not just the  fortigate.

     

    Ken

    bartman10
    bartman10Author
    New Member
    March 22, 2016

    bug ref.. I don't know? They never told me. I'll ask in the ticket.

     

    You miss the point. One of two things happened

    1. QA is doing nothing.. how on earth could they miss this? Connect WiFi devices to unit, unit hard locks.. ether they didn't test it at all or...

    2. They know about it, signed off on the unit, and it proceeded to production and availability.  

     

    They would have ether had to know about this before they put these units in the delivery pipeline in the first place. They had to know about this during the product DESIGN phase!

    This is not some kind of edge case where you need 2-3 variables to come together. This is core, basic function of the WIFI enable FortiGate... not locking up when something connects to WiFi? Get it?

     

    They let this thing go into production knowing the WiFi is totally screwed, didn't tell support about the issue, and didn't feel like getting around to fixing it till 5.4.1 rolls out! 

     

     

    bartman10
    bartman10Author
    New Member
    April 5, 2016

    Tried the 2nd beta firmware from engineering tonight.. still busted. After about 2-3 hours the unit stops passing traffic and pinging the unit ether times out or is 6-800ms. 

    I asked for the bug number again.. we'll see if they give it to me.. so far they have not but did confirm 30+ other users are reporting this issue.

     

    Truly sad Fortinet is selling this product and after all the time I've had this ticket open with them they still can't fix it... and still sell it! My god.. really? 

     

    PS anyone from Fortinet customer relations feel like contacting me some quality feedback on your product? Just PM me, I'd love to give my feedback.

    GusTech
    GusTech
    New Member
    May 25, 2016

    bartman10 wrote:

    [align=center]FWF-50E Hard Lock if you use the WiFi!! They know it and still shipped it![/align]

     

    Ok.. I found out why all 3 FWF-50E they have sent me hard lock and why some of you have no issue with FG-50e. It's because the WiFi in the unit. If you had the WiFi unit and used the WiFi your unit would hard lock also. Why? Because it's a known defect with the power management on the WiFi and affects ALL FWF-50E's and they think FWF-30E's....

    THEY KNEW about it and still sold the device!!! Then spent a month of my time collecting logs and goofing around only to tell me.. oh it's a known issue and they think it'll be fixed in 5.4.1 sometime next month or two!!

     

    ARE YOU FREEKING KIDDING ME! Do you truly expect me to believe QA just missed the fact that the WiFi edition of this device HARD LOCKS if infarct you actually use said WiFi?! How do you miss that!! HOW! Or... they knew it and said screw it ship it and we'll fix it later!

     

    Then I spent a month goofing around with support only to have level 3 tell me it's a known issue! He also wanted to collect more logs that nigh as if they didn't waste enough of my time. What's truly amazing is I only discovered this because I took the unit home for training and found it crashed every night. Hard lock up, not even serial cable access. So I would rip apart my home network every nigh after work to make it crash and get them logs or something. They also RMA'd the unit 2 times.

    I was supposed to take this unit and install it in Gary Indianan, which is 5 hours 1 way! Can you imagine the fun I would have had with this thing crashing remotely and taking down the office like this?! How much more fun that month of troubleshooting would have been taking production down instead of my kids watching Youtube at home!

     

    Sorry for the RANT and grammar/spelling mistakes.. but I'm so mad I just wanted to vent somewhere and warn any other users so they don't spend all this time goofing around with support like I did on a known broken product.

     

    Thanks,

    Bart

    Word! i feel the pain! I`m also been in the same situation many times with Fortinet.

    MikePruett
    MikePruett
    New Member
    May 26, 2016

    I have long come to terms that the new deployment for me is a FortiGate with a FortiAP running off of it. We get better connectivity and less issues than with the FortiWIFI units. Seems to just work better.

     

    I have a FortiWIFI 92D in the field that randomly drops wifi connections and stops broadcasting the SSID. very annoying. 

    bartman10
    bartman10Author
    New Member
    May 27, 2016

    Wow.. it must be mystic forces.. I was just eyeballing a 92D for something.. thanks for what ever compelled you to post. I've kind of come to the same conclusion. 

    FYI.. to this day support still does not have this fixed on the FWF-50E!!! WOW

    "All the kings houses..."

    Terms & ConditionsAccessibility statement