Tenant Connector Outbound Multiple Nodes Option

in case several tenant connector outbound nodes want to be used in the same tenant site, the installation script should be executed on every tenant connector machine after that, the user needs to fill in the required data for every tenant connector node on the tenant connector page of kron pam web gui and press the save button as explained 8th step in section 3 in the end, under the same tenant site, multiple tenant connector nodes appear if more than one tenant connector node is active under the same tenant site, the traffic is distributed in a round robin fashion through those nodes kron pam server keeps checking the connector nodes’ activity by running a job called tunnelheartbeatcheckjob this job keeps track of the regular heartbeat messages sent by the connector nodes and sets the tunnel status as failed in case three consecutive heartbeat messages (this number is specified in the “connector heartbeat check interval” system parameter) do not arrive there will be no traffic on the failed tenant connector node unless its status turns active again if the tunnelheartbeatcheckjob is not defined on the kron pam server, the user should define it first the important point here is that kron pam should understand the status of the tenant connector node with this job if the connector node fails in case the connector service defined in the tenant connector node becomes down or the secure tunnel between the kron pam server and the tenant connector node becomes down, if this job is not defined (or not run), even though in reality the tenant connector node is not active, kron pam thinks that it is still active, and still sends the requests to this connector node