Re: Keepalived and NAT loopback,.
Todd Fleisher <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <[email protected]> |
This is the way I handle this type of thing. LVS NAT virtual servers do not work for internal traffic on the same subnet as the real servers. I create corresponding LVS DR virtual servers and point my clients to them (using DNS views to provide them with the LVS DR IP addresses for the same hostnames). I know it's not the answer you want, but I'm afraid that's the solution you'll have to implement. -T On Aug 4, 2013, at 9:04 PM, Pat Suwalski wrote: > The only solution I could possibly think of is to create another > (duplicate) stanza in the keepalived.conf file for 172.16.0.100/101, but > with an internal 172.16.0.x virtual IP. But I'd really rather not have > the duplication and second set of HTTP_GET checks. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk