hi..

Felix Ortigosa Martinez <[email protected]>
Newsgroups gmane.linux.redhat.piranha
Message-ID <[email protected]>
I tried configured my cluster server (lvs), but not working find.

my configuration is.

two router and four real server.

primary = 148.213.22.201
service = lvs
rsh_command = ssh
backup_active = 1
backup = 148.213.22.202
heartbeat = 1
heartbeat_port = 539
keepalive = 6
deadtime = 18
network = nat
nat_router = 192.168.1.254 eth1:1
virtual vs1 {
     active = 1
     address = 148.213.22.200 eth0:1
     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 server1 {
         address = 192.168.1.3
         active = 1
         weight = 1000
     }
     server server2 {
         address = 192.168.1.4
         active = 1
         weight = 1000
     }
     server server3 {
         address = 192.168.1.5
         active = 1
         weight = 1000
     }
     server server4 {
         address = 192.168.1.6
         active = 1
         weight = 1000
     }
}

1.  in the file log (router 1) . send me error.. why ?

router1 nanny[814]: bad load average returned: router1       up
7:07,     0 users,  load 0.00, 0.00, 0.00
router2       up     22:14,     0  users,  load 0.00, 0.00, 0.00
server1     down     22:20
server2       up     2  2:15,     0 users,  load 0.00, 0.00, 0.00
server4     down     21:48
server5      up     22:14,     0 users,  load 0.00, 0.00, 0.00
sever3        up     22:15,     0 users,  load 0.00, 0.00, 0.00

2. when trie with el command in the any real server .

ping outside-InternetIP  not respond. or very very slow.


3. in the gui-piranha interfacce. configure lvs and works find, but i
not understend, the seccion

CURRENT LVS ROUTING TABLE

 IP Virtual Server version 0.9.7 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port          Forward Weight ActiveConn InActConn

no send me message why.

4.  the router NAT is 192.168.1.254  is set to

eth1      Link encap:Ethernet  HWaddr 00:00:C0:81:DE:8E
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:98593 errors:0 dropped:0 overruns:0 frame:0
          TX packets:136275 errors:1 dropped:0 overruns:0 carrier:2
          collisions:680 txqueuelen:100
          Interrupt:10 Base address:0x310 Memory:cc000-d0000

eth1:1    Link encap:Ethernet  HWaddr 00:00:C0:81:DE:8E
          inet addr:192.168.1.254  Bcast:192.168.1.255
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:10 Base address:0x310 Memory:cc000-d0000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:8715 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8715 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

if real server set router wich ip 192.168.1.254 why not work.

when type command  route in the router1  view this

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
router1             *               255.255.255.255 UH    0
0        0 eth1
cluster1            *               255.255.255.255 UH    0
0        0 eth0
192.168.1.0     *               255.255.255.0   U     0      0        0
eth1
148.213.22.0   *               255.255.255.0   U     0      0        0
eth0
148.213.0.0     *               255.255.0.0     U     0      0        0
eth0
127.0.0.0         *               255.0.0.0       U     0      0
0 lo
default         148.213.22.1    0.0.0.0         UG    0      0        0
eth0
default         192.168.1.254   0.0.0.0         UG    1      0        0
eth1


Q. the router ip 192..168.1.254   its correct  o change the ip router in
the real servers 192.168.1.1

Q. the command ipvsadm how work or what instruccion set ?


thanks for your help.

ing. felix ortigosa martinez
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.