|
Well, I got the lvs working finally! Turns out I had everything configured
correctly *except* the default route on the private network nodes. Once
they were routing to the NAT router, eureka! LVS was escrowing connections
and the servers were talking to the Internet.
Thanks for all of your guys' help!!! Especially the guys at the IP
Masquerading site. You've all been a great help.
-- Jake
javadude@xxxxxxxxx
> -----Original Message-----
> From: Joseph Mack [mailto:mack@xxxxxxxxxxx]
> Sent: Tuesday, July 25, 2000 8:52 AM
> To: Jacob W Anderson
> Cc: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE: LVS not responding?!
>
>
> On Tue, 25 Jul 2000, Jacob W Anderson wrote:
>
> > > > when I try to connect to the LVS on port 80 via http, I always get
> > > > connection refused.
> > >
> > > there is no service listening on the target IP:port of your
> ipvsadm line.
> >
> > Isn't pulse supposed to automatically start the ipvsadm
> processes? If not,
> > then where am I supposed to put the ipvsadm commands?
>
> out of my depth here. Nanny etc are RedHat products. There are people here
> who know how they work, but I don't.
>
> > Since I don't see the ipvsadm processes running on the lvs mx
>
> ipvsadm is run once to push values into tables in kernel. There is no
> separate ipvsadm (or LVS) process.
>
> since connection is refused, ipvsadm hasn't been run (or has sent the
> wrong values to the kernel). To see the values that ipvsadm has put
> into the kernel, just run
>
> $ipvsadm
>
> This should like your various realservers/ports/services/scheduling etc.
>
> , I can only
> > assume that such is the problem (as you mentioned). Doesn't
> pulse act like
> > inetd?
>
> no idea sorry
>
> Joe
>
> --
> Joseph Mack mack@xxxxxxxxxxx
>
>
|
