From the issue description, it seems it can be misconfigured UAG or incorrect health monitoring. If rebooting the UAG fix the issue, it means it might have reached 2000 session bench mark and only ...
See more...
From the issue description, it seems it can be misconfigured UAG or incorrect health monitoring. If rebooting the UAG fix the issue, it means it might have reached 2000 session bench mark and only way to clear the old stale session is to reboot. NOTE: UAG by default support 2000 session. This 2000 session not only include VDI session but also health monitoring probing from 3rd party device. you can enable the log level on UAG to Debug and when issue happen, before rebooting the UAG, download the log bundle. as rebooting will clear the events. Inside the log bundle you will find Active Session file. Open it and count the number of session. Also check the esmanager log for the more specific cause of the issue.