Often when troubleshooting these fault domains, it can feel like a game of “Whack a mole” jumping from Pod to Pod trying to find a pertinent session, alarm or event to the problem your user is describing. Horizon Reach is designed to tackle the disconnect in Enterprise environments wherein each Pod in a Cloud Pod Architecture is its own technology domain and fault domain, or a customer is running multiple, disconnected pods, outside of a Cloud Pod Architecture, but would still like to treat them all as one unit of compute. Horizon Reach is a web based, monitoring and alerting fling for VMware Horizon On Prem deployments. Running multiple instances can and will add load to your connection servers. Horizon Reach's discovery is intensive and should only be run from a single instance. Warning: Please do not deploy multiple instances of Horizon Reach which connect to the same Cloud Pod Architectures. For 7.11 and 7.12, please refer to the following document here. Warning: Horizon Versions 7.10 through 7.12 have a known issue which can cause Horizon Reach to trigger a low memory issue on the Horizon Connection Server.įor Horizon 7.10, ensure to deploy Horizon 7.10.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |