Forum Discussion
NimbostratusView Session fail-over to another pod
Our design will leverage security groups to direct session requests to various regional View pods. If i understand the default design the topology will manage the initial request based on either subnet and/or geo-location and then the APM will route based on the security group membership which is also tied to the View 5.2 pool entitlements (per pool / region specific). Does this mean that for fail-over to work in the event a site goes down the user must be in both region / pool security groups? If so, how will the APM chose which site to send the "home" session request to providing all sites are operational at that time? Is there weight or priority given within the APM group assignments?
1 Reply
Hi Jeff,
The solution we have outlined in our View deployment guide has a default datagroup which is what is used to fall back on in the event the primary pool is unavailable. The datagroup is prioritized based on preference. See the solution titled "Advanced Load Management using Dynamic Session Detection"; the specific configuration for the preference DG is found on page 36.
