Changing networks and DR traffic dies
"Posts" <[email protected]>
| Newsgroups | gmane.linux.redhat.piranha |
|---|---|
| Message-ID | <000001c2c4ed$c0e4d270$6501a8c0@XP1> |
Hi, I have barebones setup:
================================
SETUP #1 - Works
Director, 1 network card with 2 addresses on it eth0 - 192.168.1.126 and
eth0:150 - 192.168.1.150.
Real server, 1 network card eth0 - 192.168.1.141.
[ lvs.cf ]
serial_no = 8
primary = 192.168.1.126
service = lvs
rsh_command = ssh
backup = 0.0.0.0
heartbeat = 1
heartbeat_port = 539
keepalive = 6
deadtime = 18
network = direct
reservation_conflict_action = preempt
debug_level = NONE
virtual 150 {
active = 1
address = 192.168.1.150 eth0:150
port = 80
send = "GET / HTTP/1.0\r\n\r\n"
expect = "HTTP"
load_monitor = ruptime
scheduler = wlc
protocol = tcp
timeout = 6
reentry = 15
server RS1 {
address = 192.168.1.141
active = 1
weight = 1
}
}
With this setup I can access 192.168.1.141 or 192.168.1.150 from my
192.168.1.101 machine and get the web site to come up and ipvsadm shows
one ActiveConn.
================================
SETUP #2 - Doesn't Work
Director, 1 network card on 216.55.xxx.0 network and 2 addresses on it
eth0 - 216.55.xxx.126 and eth0:150 - 216.55.xxx.150.
Real server, 1 network card eth0 - 216.55.xxx.141.
serial_no = 8
primary = 216.55.xxx.126
service = lvs
rsh_command = ssh
backup = 0.0.0.0
heartbeat = 1
heartbeat_port = 539
keepalive = 6
deadtime = 18
network = direct
reservation_conflict_action = preempt
debug_level = NONE
virtual 150 {
active = 1
address = 216.55.xxx.150 eth0:150
port = 80
send = "GET / HTTP/1.0\r\n\r\n"
expect = "HTTP"
load_monitor = ruptime
scheduler = wlc
protocol = tcp
timeout = 6
reentry = 15
server RS1 {
address = 216.55.xxx.141
active = 1
weight = 1
}
}
With this setup I can access the real server directly at 216.55.xxx.141
and the site comes up but 216.55.xxx.150 I get an InActConn on the
Director and the web page request fails. Generally speaking I only
changed the ethx files, lvs.cf files, and etc/hosts files with the new
network addresses but it's not coming up.
================================
Can someone explain what InActConn means on an initial request? Does
that mean the director dropped it or the real server did?
Any ideas on what to try, look for, or other resources?
I appreciate any tips.
Kawika Ohumukini