How to Configure Virtual IP in Failover Server?

The Virtual IP is initially bound to the Primary Server (Central Server). If this server becomes unreachable, the Virtual IP is automatically transferred to the Secondary Server (Failover Server). Agents do not need to know which server is active, they communicate with the Virtual IP , ensuring continuous operation without manual reconfiguration. Endpoint Central Console can be accessed using Virtual IP.

How to choose Virtual IP?

When selecting a VIP, follow these guidelines:

• Ensure the VIP is not already assigned to any other device on the network.
• Confirm that the VIP belongs to the same subnet as the primary and secondary servers.
• Exclude this VIP from the DHCP server's IP pool to prevent it from being assigned to another device. This can be done by adding the VIP to the DHCP exclusion list.

How Virtual IP works?

In normal scenario, agents communicate with the Virtual IP ,which is assigned to the Primary Server (Central Server). The Virtual IP handles all communication between the agents and the primary server.

How Virtual IP works in Failover Scenario?

If the Primary Server fails, the Virtual IP automatically switches to the Secondary Server (Failover Server). Agents continue to communicate with the Virtual IP ,which now routes traffic to the secondary server. The agents remain unaware of the server switch because they still connect to the same Virtual IP.

 Ports used by Endpoint Central

Note: The ports mentioned under 'Server' must be enabled at all times irrespective of your license edition. Refer the ports required for specific modules and enable them as per your requirement.

Note: Ports 135,139 and 445 should also be kept open and inbound on both agent and server (and distribution server, if applicable) for pushing agent installation.