Fortinet Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
billp
Contributor

600C recurring crash

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.

 

 

Bill ========== Fortigate 600C 5.0.12, 111C 5.0.2 Logstash 1.4.1

3 Solutions
FortiAdam
Contributor II

I would run a HQIP test on it to begin with if you haven't done that yet.  http://cookbook.fortinet....ip-test-documentation/

View solution in original post

ede_pfau
Esteemed Contributor III

Bill,

 

I have opened a support case in August following your post. FTNT reported back that there might be a compatibility issue of the memory modules employed. As I suggested a BIOS upgrade the supporter stated that they have already included a fix into the next firmware (v5.2.4). As my customer (and me) didn't agree to update he sent me a special build based on v5.0.12 (build 8408 instead of b305).

 

After installing and now 35 days uptime everything looks OK. But then again, what is 35 days compared to the usual 100+ days it took to run the 600C against the wall in the past. I will have to watch and wait to see if the fix really is working. Meanwhile, maybe it's worth asking support for the special build and see if that helps in your situation.


Ede

"Kernel panic: Aiee, killing interrupt handler!"

View solution in original post

vjoshi_FTNT
Staff
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.    

View solution in original post

21 REPLIES 21
ede_pfau
Esteemed Contributor III

Thanks for posting, again something new learned today...

So there's no real obstacle doing this in the field I'd say.

One should mention that running the FGT off a UPS would be a good idea - losing power during the BIOS update will certainly brick the unit.


Ede

"Kernel panic: Aiee, killing interrupt handler!"
ede_pfau
Esteemed Contributor III

A follow-up:

our 600C has an uptime of 173 today, without any glitches. Running v5.0.12 special build 8408, no BIOS update.

Recommended!


Ede

"Kernel panic: Aiee, killing interrupt handler!"