Forum Discussion

Nfordhk_66801's avatar
Nfordhk_66801
Icon for Nimbostratus rankNimbostratus
Jun 10, 2015

APM Posture Assessment Slow - Checking Client hangs

Hi,

 

We utilize APM to secure one of our Apps based on AD lookups.

 

Here's how the policy works: Windows Info, to capture the computer name. Then an iRule event that takes the computer name and sets it static to our domain. Finally an AD lookup based on defined list of allowed OUs.

 

The problem is often times computers hang at the "checking for client" screen for up to 20 seconds. Then the posture itself takes another 10. Is there any way to speed this up or what to look for? We do not use the full blown edge client but, the "BIG-IP Edge Client Components" almost like a soft client.

 

Our DCs used to query are not over utilized by any means. This is affecting users with all resources local to them. I understand there are many outside variables that could impact this.

 

Questions: How exactly how the F5 interact with the clients and initiate connectivity? Would switching to the full client have any impact? Should we add a dedicate DC to use for lookups? Any other help would be appreciated.

 

ad query
APM
big-ip edge client
irule
security

1 Reply

Sort By
  • amolari's avatar
    amolari
    Icon for Cirrus rankCirrus
    Jun 11, 2015

    I would check on the client side. Maybe you can install the Edge client on one client and check the logs it produces during the hang? With Edge components, my experience is that newer version often brings improvement. Which version is your BIGIP (client-side component) and what are your client OS versions?