600C recurring crash

Forum|Forum|11 years ago
April 15, 2015
21 replies
37099 views

I have a 600C with a recurring crash problem. It is running 5.0.11, but the problem has persisted since 5.0.4 or so.

About every 1-3 months, the gui will show that all interfaces are connected at 1GBPS and that each port has sent/received approximately 191 billion packets if I over over a port (not shown below).

Once the gui reaches this state, it is usually about 2-3 days before the firewall stops working altogether.

At that point, I need to do a full power down/power off reset. If I just do a warm boot, it will not recover and will stop mid-boot with an error message.

Has anyone experienced anything similar with a 600C? I am beginning to think this is a hardware issue.

Suggestions welcome. Thanks.

ftg600c(UJ).jpg

Best answer by vjoshi_FTNT

Hello, As already mentioned earlier, this is a known issue (bug :0243461) and there is a special build released in both V5.0 and V5.2. Also, there is a workaround of bringing DOWN the admin status of all the UNUSED interfaces should prevent the issue to re-occur.

Hope that helps.

billp wrote:
Well, all is not well, even with a relatively new 600C from Fortinet with a recent firmware. Has anyone had this issue resolved yet? At this point, it appears that there is a serious bug in the 600C firmware with no real resolution. The earlier-mentioned Reddit posting made it seem like there were other models that were affected, so I am curious if there are other Fortigates in the C hardware revision that also have this issue. If someone has some wisdom to share on this, please feel free to jump in.

Show previous replies

vjoshi_FTNTAnswer

Staff

Hello, As already mentioned earlier, this is a known issue (bug :0243461) and there is a special build released in both V5.0 and V5.2. Also, there is a workaround of bringing DOWN the admin status of all the UNUSED interfaces should prevent the issue to re-occur.

Hope that helps.

billp wrote:
Well, all is not well, even with a relatively new 600C from Fortinet with a recent firmware. Has anyone had this issue resolved yet? At this point, it appears that there is a serious bug in the 600C firmware with no real resolution. The earlier-mentioned Reddit posting made it seem like there were other models that were affected, so I am curious if there are other Fortigates in the C hardware revision that also have this issue. If someone has some wisdom to share on this, please feel free to jump in.

billpAuthor

New Member

vJoshi,

Thanks for the reply. The work-around you mentioned is a life-saver.

It would be extremely helpful if Fortinet could publish more information about the BIOS bug and bug 0243461. Tech support originally led me to believe that the BIOS bug was the sole problem I was having. Without access to the exact description, it's hard to help tech support pinpoint the exact set of symptoms and problems. A brief KB on this issue would be really appreciated.

Thanks again for your help.

vjoshi wrote:
Hello, As already mentioned earlier, this is a known issue (bug :0243461) and there is a special build released in both V5.0 and V5.2. Also, there is a workaround of bringing DOWN the admin status of all the UNUSED interfaces should prevent the issue to re-occur.

Hope that helps.

EricG1793

New Member

Hello,For what it's worth, in July, I had contacted Fortinet about advice for upgrading. I also mentioned my symptom of sporadic freezing during normal operation and/or hanging during reboots, citing 0243461 and 0229553. We've had no issues since we upgraded the firmware from 5.0.4 to 5.0.12, however, I want to make sure it stays that way. I requested either a fix or an RMA, but at that time, they had no official solution and could not do an RMA. Last week, the ticket was re-opened and they asked me if I wanted to upgrade the BIOS myself or RMA the unit. I replied and asked how simple the BIOS upgrade is and I'm waiting to hear back, but I have a feeling I'll elect to RMA. Just thought I'd let you all know! As frustrating as it's been having practically no information from Fortinet on the issue, I am happy that they did follow up and offer a solution.

- Eric

Sign up

Login with SSO

Login to the community

Login with SSO