Tag Info

Hot answers tagged

4

Assuming there isn't a firewall or router between the end users and the server you could employ STP (spanning tree protocol) and the following layout: This would give you the redundancy you are seeking. If a single "core switch" (the m4100-50) goes offline traffic should be able to keep flowing. Depending on how STP is configured (what type of STP and ...


2

Basically you want to have an automatic failover for every service needed to run your application. One solution could be the following described aproach: Keepalived installed on both systems. HAProxy as Loadbalancer with failover to HAP LB 2. Monitored by keepalived Apache/NGINX behind HAP. If one failes, HAP will have that monitored and redirects to ...


1

Changing the pool master won't take down the host or any of the VMs. It will cause a restart of the management service (XAPI) of all pool hosts, so that management access via Citrix XenCenter or CLI (xe commands) won't work for 10-30 seconds. Once the service is restarted, you can reconnect to the poolmaster or a slave via XenCenter (you'll be redirected to ...


1

Here is the general rule of thumb I have used when deciding between keepalived and heartbeat. Heartbeat is usually used when you want a true active/standby cluster setup (where only one node is actually "up.") Think NFS. Usually w/ Heartbeat the pre and post script actions are used to start and stop services. Keepalived is much simpler, and is usually ...


1

I have tested your configuration on my machine and it worked. Keepalived assigned the VIP to the specified interface and the logs showed the line Keepalived_vrrp: VRRP_Instance(VI_1) Entering MASTER STATE The only way I was able to reproduce your case is by supplying an empty configuration file (the test on non-existent file failed because the startup ...



Only top voted, non community-wiki answers of a minimum length are eligible