1. Currently, I am doing a manually failover by forcing Qlik services stopping in central node to take the control by FailOver node (RIM node) which is working fine.
3. After Fail Over qmc/hub is working with - (www.rimnode.com) which means fail over is working, but I don't want to communicate or force users to use (www.rimnode.com/hub) or feel the difference of environment usage hence to use the www.centralnode.com/hub after fail over so I have contacted the network team to switch the IPs of Central to RIM node (Fail Over) so users will be using same URL (www.centralnode.com/hub). The moment Central Node IP is mapped to FailOver node, QMC/hub url displayed with http error with "Qlik logo + 400 Bad Request The http request header is incorrect." with url lock showing as "not secure" (it was secure before failover).
1. Copied the Central node Qlik Client and Service Cluster Certficate to RIM node
2. White listed Central and RIM nodes in virtual proxies of both Central and RIM.
3. Browser/URL SSL Thumbprint of Central and RIM is different as we have different certificates.
Can someone help/assist me if any other certificate/thumbprint/something else to be done to make it work? Did I miss something ? Please suggest
4. Once the above theory of IP switching works, I will map 2 IP addresses to Central node so fail over will become automatic the moment central goes down.
@anily86 It sounds like you are attempting to have a type of High Availability environment for your users. I would like to provide you the following link to the Qlik Admin Playbook that might be able to provide some guidance: IE Active Central & Passive Central. You would want to be using a DNS alias so that the end users are not using the individual server names / IP addresses.
