SummaryThis document consolidates the various reasons one might see an unexpected shutdown on the Exinda
OverviewThe Exinda can sometimes face an unexpected reboot. The following are the reasons this would happen
Cause1. A spike in connection rate - caused due to DDOS attack, or network scans
2. Kernel panic - a state where some processes have hit a tipping point, causing the device to force reboot.
3. Huge policy set - this causes restraints on the available RAM, hence causing unexpected shutdowns
4. Process failure - this doesn't always cause an unexpected reboot always, but it can be a contributing factor
5. The customer is using an old version of the firmware that has known issues, or has too much output to the serial console
ResolutionSome of these, such as a sudden spike in connections corresponding to an attack of various kinds (internal or external) are transient conditions and are not systematic. It is best practices to have the Exinda behind a firewall in order to help mitigate these types of situations.
Systematic problems like a kernel panic or process failure can correspond to bugs in the code. To examine these further, pelase consult the Exinda known issues list or contact Exinda TAC for investigation.