Last Modified: Sep 13, 2023
Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 11.6.4, 11.6.5, 184.108.40.206, 220.127.116.11, 18.104.22.168, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 12.1.4, 126.96.36.199, 12.1.5, 188.8.131.52, 184.108.40.206, 220.127.116.11, 12.1.6
Opened: Jul 08, 2016 Severity: 2-Critical Related Article:
Related Article: K82210057
CPU Saver option not working while the 'latency' compression provider selection algorithm is in use.
Edge Client shows the VPN tunnel as 'Connected' but no traffic flow. This is an intermittent issue.
APM Edge Client over VPN tunnel. The issue tends to occur when CPR Saver is configured on the Edge Client on devices where hardware compression cannot perform the specific type of compression/decompression being requested.
You can use either of the following workarounds: -- Enable CPU Saver in the secure connectivity profile. + To do so in the GUI: 1. Navigate to GUI: Access Policy :: Secure Connectivity :: profile_name :: Compression Settings :: Network Access. 2. Check the CPU Saver checkbox. + To do so in tmsh, run the following command: tmsh modify apm profile connectivity dummy compress-cpu-saver true -- Configure compression strategy to 'speed' (from 'latency'). To do so, run the following command: tmsh modify sys db compression.strategy value "speed".
Fixed an issue with the CPU Saver option not working while the 'latency' compression provider selection algorithm was in use. This mitigates a bottleneck when Software Compression is in use, correcting a problem with the tunnel stalling.