On Tue, Jul 12, 2011 at 06:06:01PM -0400, Kanwar Ranbir Sandhu wrote:
> Hi All,
> I'm using pulse + lvs on a couple of RHEL 6.1 machines. Pulse and lvs
> are working wonderfully so far, though it's all only in testing.
> I'm quite new to LVS. The questions I'm about to ask for the scenario
> I'm about to present may be stupid. Nonetheless, I'd appreciate an
> I have a virtual server configured for a bunch of apache servers. I've
> tried to configure a second virtual server listening on a different IP
> for a bunch of IIS servers. Of course, I have both virtual servers
> using the same port, which is 80.
> If I start pulse, the first virtual server comes up fine, but the second
> one fails. For shits and giggles, I changed the port for the second
> virtual server to 22, and upon restarting pulse, the second virtual
> server started up. I could see the real servers associated with both
> virtual servers.
> I'm going to assume I can't have two virtual servers using the same
> application port even though their virtual IPs are different. If this is
> indeed true, is there a workaround? If there isn't, how should I go
> about load balancing IIS and Apache servers with one set of LVS routers?
I'm not sure why you had the problem that you describe, nor am I
particularly familiar with pulse, however what you describe
is most certainly possible for LVS to achieve.
Please read the documentation before posting - it's available at:
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users