What is the effect of only enabling HA on the /ui/ha/settings page - What is the difference between these two settings? Are they independent of one another? Is HA effectively disabled if BOTH are not in an enabled state?
But on the /ui/ha/deployment/summary you leave it unchecked - does this mean that HA is enabled for the polling engines out bound polling, but the VHN/VIP is NOT enabled for incoming data?
'/ui/ha/settings' is how you disable HA globally. This is provided as a shortcut for customers that have dozens of HA pools, as it's required to disable when performing upgrades. You can also disable HA…
Is there a SWIS verb to disable HA globally? Currently when doing upgrades I collect a list of pools and then use the enable/disable verbs for each.
I know it's only one setting in the GUI but I have a…
There is currently no SWIS verb to globally disable HA. Currently, these SWIS verbs exist only at the individual pool level.
Thanks, one last question, is the cause of my main polling engine being red here due to red criticals in the Deployment health page?
The server is happy and green in NPM but red on all the HA pages. If its red, will a fail-over occur or is this just cosmetic due to 'perceived' critical health issues?
There is currently no SWIS verb to globally disable HA. Currently, these SWIS verbs exist only at the individual pool level.
Hide and seek is a beautiful game in our industry. 
"If the AD test found warnings in the logs, view the warnings and determine what, if anything, needs to occur to remove the warning."
Thanks. This is a totally new additional web server recently deployed that runs perfectly. Is this status not what I should be seeing below?
