Adding a RIM Node

[melissapluke]

We have a virtual proxy on a proxy node and the user access the central node. This has been working fine. We added a second engine node as a failover to our environment. It says all 5 services are running on the second engine. 

The proxy for the central is linked to the virtual proxy for it self under the proxies section of QMC.
The proxy for the proxy node is linked to the virtual proxy for it self under the proxies section of QMC.
The proxy for the rim engine is linked to the virtual proxy for it self under the proxies section of QMC.

Within the virtual proxies section of QMC:
The central virtual proxy has both the server and the rim engine nodes under load balancing nodes.
The engine virtual proxy has both the server and the rim engine nodes under load balancing nodes.
The proxy virtual proxy has both the server and the rim engine nodes under load balancing nodes.

We have no load balancing rules. All traffic still routes to the central. We cannot get traffic to the engine. Any ideas on what we are doing wrong?

Thanks!

Melissa

[Bastien_Laugiero]

Hi, 

So regarding the virtual proxies, my understanding is that users are using the Virtual Proxy linked to the Proxy node correct? And currently the only working engine is the one provided by the Central node?

If this is true to you only need to focus on the Virtual Proxy attached to the Proxy node. Based on your description, looks like both engine are configured to load balance the traffic. 

So I would start by making sure the engine service on the Engine node is operational. To do that you can simply remove the central engine from the load balancing section of your Virtual Proxy which will leave only the engine from your Engine node. 

Then try to load applications and see if you get any error.

Hope this helps!

[melissapluke]

Hi,

Following your advice to test this, we removed the central node from the load balancing and the result is:

"Proxy node is waiting for a new session" error when trying to connect to the hub. Looking through some of the Proxy/Repository service logs shows that the Proxy Node can't seem to establish a session with the Engine Node. We're not really sure where to go from here.

[Bastien_Laugiero · Accepted solution]

Hi, 

So it looks like some ports might not be opened between the proxy node and the engine. (Perhaps between other nodes too)

Please have a look at this article https://support.qlik.com/articles/000028290. 

The error message indicates that the port 4900 is closed between the proxy and engine. 

Here is also a list of required port to be opened between your nodes:

https://help.qlik.com/en-US/sense-admin/November2020/Subsystems/DeployAdministerQSE/Content/Sense_De...

Hope this helps!