To resolve this problem, Pulse Secure strongly advises to upgrade to
Pulse Connect Secure 9.1R6 and above which is now available for download via https://my.pulsesecure.net/
- If the issue is still seen, please upgrade to Pulse Connect Secure 9.1R8 or above where FQDN ACL feature can be disabled.
- Please ensure that there is no DNS latency/Delay in your network if you use this feature as this may lead to performance issues.
After upgrading to Pulse Connect Secure 9.1R8 and above, the administrator can disable FQDNACL feature as long as FQDN split tunneling is not used. After disabling the feature, the administrator is not allowed to add new FQDN resources or modifying any existing FQDN resources. Additionally, enabling or disabling FQDNACL feature does not restart services.
- Login to admin console
- Navigate to System > Configuration > VPN Tunneling
- Under Enable/Disable FQDN ACL, uncheck the option.
If the problem persists after the upgrade, please open a support case with the following data:
- Screenshots of all system status graphs (throughput numbers and CPU are important)
- tcpdump on the internal and external interfaces when normal cpu exists.
The general trend is CPU levels and throughput should increase and decrease together. If historical throughput numbers have increased over time, this may be causing additional load. Pulse Secure support team can help evaluate the tcpdump to provide estimated throughput levels for your specific device.