So a point raised in another thread got me thinking: can just the logging configuration as specified in the Track column of any Access Control (including HTTPS Inspection) or Threat Prevention policy layer in the SmartConsole impact SecureXL Throughput Acceleration (i.e. make traffic take a less efficient processing path) or reduce SecureXL Accept Template formation? Does SecureXL/sim/SND handling fully-accelerated traffic have more or less the same logging capabilities as a Firewall Worker Instance Core, and whatever logging option is selected won't force traffic out of SecureXL?
I'm well aware that specifying Accounting, Detailed and especially Extended logging in a layer's Track column will increase the gateway's logging load via fwd, but is there any way doing so will directly affect these two parts of SecureXL? What about if sk101221: TCP state logging is enabled with a setting other than Never?
I'm pretty sure the answer here is no, but wanted to confirm.
Gateway Performance Optimization R81.20 Course
now available at maxpowerfirewalls.com