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

WAD crash with 6.2.x and reboot

One of our 1500D a-p HA pairs recently experienced a master reboot twice (6.2.9 and 6.2.10 today) and switched over. I have a ticket at TAC and was told WAD crashes were the cause since lots of them are recorded in the crashlog. Also told this was a known issue with 6.2.x, which was fixed with any 6.4.x.

But the WAD crash records don't line up with the time the reboot happened. So I have some doubt that the crashes were the direct cause of the reboots.

 

Did anyone running 6.2.x experience reboots with or without WAD crash?

 

Thanks,

 

 

Toshi

2 REPLIES 2
AlexC-FTNT
Staff
Staff

It is important to isolate the wad crash and the reboots. Wad crashes can signal other problems as well, so those must be fixed too, if not even first hand.
I suggest you enable comlog for your unit to verify what causes the reboots:
https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-use-COMLog-feature/ta-p/195390?exte...


- Toss a 'Like' to your fixxer, oh Valley of Plenty! and chose the solution, too00oo -
Toshi_Esumi
Esteemed Contributor

Thanks Alex. We're moving to the same direction too. Somehow this particular unit's comlog was disabled while the current primary unit's have been enabled. I enabled it yesterday but it wouldn't happen again until we swap the a-p back.

We're going to perform some HQIP test first, before the swap back.

For WAD crashes, I asked the tech to bring this up in the next meeting with Engineering side. Because at this moment, no schedule to implement the fix 6.4 has to 6.2 while engineering support for 6.2 is nearing to the end according to the tech.