Security Gateway continues to log locally and does not attempt to reconnect to Security Management Server / Log Server
During high CPU load on Security Management Server / Log Server when logs are being sent to it, the Security Gateway's FWD daemon (which is responsible for log transfer), has a keep-alive mechanism for checking communication with its "Log Server". Once communication breaks and after a couple of keep-alive rotations, Security Gateway will start logging locally to the $FWDIR/log/fw.log file.
This behavior is by design (Note: the FireWall log file ($FWDIR/log/fw.log) can be fetched from the Security Gateway in the SmartView Tracker, once communication returns - either by the Log Forwarding option, or by Remote Files Management).
In addition, an issue was discovered with reconnecting mechanism on Security Gateway.