View All Products
Compute
Storage
Networking
Databases
Services
Developer Tools
Industries
Pricing
Community
Engage With Us
Community ▶ Questions ▶ keepalived for two web servers
Log in to Ask a Question

keepalived for two web servers

networking

Hi, I'm trying to use keepalived to create an HA setup for two web servers. I have 3 public IPs, a static for each node and a "shared" ip. The shared was created as a second IP for www1. I've set up the IP Failover linkage for both nodes in the Network tab of the management interface.

I have two questions:

1. How do I get www1 to respond using the new public ip? I created a virtual ethernet for it but it will doesn't respond to any requests. I also tried taking down the main IP and replacing it with the new one but it doesn't work. Any ideas?

2. Can anyone give me article links (or just some tips) on setting up keepalived for public IPs between two servers? I'm a bit confused how it all works. I'm using HAproxy to load balance, btw.

Thanks!!

5 Replies

Figured it out. I trolled the forum for a bit and found http://www.linode.com/forums/viewtopic.php?t=4946. Tried it and it worked. Also, set up keepalived using http://www.howtoforge.com/setting-up-a- … n-lenny-p2">http://www.howtoforge.com/setting-up-a-high-availability-load-balancer-with-haproxy-keepalived-on-debian-lenny-p2 and hey, it "just works."

I never knew about the "ip address …" command.

Keep in mind that since Linode's IP failover requires that both nodes be in the same datacenter, it's not really a HA setup since you have no geographic diversity. All you're protected from is host failures, not DC-wide issues (such as connectivity).

Thanks for the tip. Multiple datacenters isn't something I'm going to attempt just yet. I understand the benefits of it, but until we start getting real traffic from real customers, it doesn't make too much sense for us to double our hosting infrastructure. Also there's only so much I can do in a night…I'm learning all this scaling/HA stuff little-by-little as I go in my free time.

Out of curiosity, is the only way to do DC failover through DNS?

@haha326:

Out of curiosity, is the only way to do DC failover through DNS?

I believe so, since there's no IP failover.

@obs:

@haha326:

Out of curiosity, is the only way to do DC failover through DNS?

I believe so, since there's no IP failover.

Without using some form of global load balancing solutions, DNS is the only surefire way I can think of off the top of my head. And in theory, GLB just hacks up DNS to work in a way that provides the redundancy.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Log in to Reply
Community Code of Conduct