So I have a question about heartbeat and ldirectord. This may be a simple question, but I don't know the exact answer so if I could get some help with this it would be greatly appreciated. I am working on a project that has the following servers: 2 Linux directors each running ldirectord and heartbeat 3 web servers which are being load balanced via the Linux directors Multiple other servers that the client has running for their business There are 8 public or “virtual” IPs all used to get to various web pages, servers and services. We will say the IPs range from 126.96.36.199 to 188.8.131.52 with netmask of 255.255.255.0 Internally they are running a standard 192.168.X.X network. We are running a High Capacity High Availability and Load Balancing model for the setup using ldirectord and heartbeat. The picture below is a general setup Anyways now down to the real question. I am wondering if there is anything special we need to do with the /etc/ha.d/haresources file to accommodate for all the extra IPs. Or does the /etc/ha.d/ldirectord.cf file take care of the “virtual” IPs? This is what the /etc/ha.d/haresources and the /etc/ha.d/ha.cf files currently look like. /etc/ha.d/ha.cf logfacility local0 bcast eth0 # Linux mcast eth0 184.108.40.206 694 1 0 auto_failback off node LoadBalancer1 node LoadBalancer2 respawn hacluster /usr/lib/heartbeat/ipfail apiauth ipfail gid=haclient uid=hacluster /etc/ha.d/haresources LoadBalancer1 \ ldirectord::ldirectord.cf \ LVSSyncDaemonSwap::master \ IPaddr2::220.127.116.11/24/eth0/18.104.22.168 What I am unsure of is if we need to add more IPs to the /etc/ha.d/haresources file since the client wants to be able to get to all of their servers via a public IP being routed through the linux directors.... PLEASE HELP!