[lvs-users] 2x LVS-DR director + realserver on one machine -> packet storm/looping

[David Coulson]

What happens if you remove the ipvsadm rules on the host which does not 
have the VIP active on eth0 on it?

Sounds like both systems are running the packet through LVS and routing 
it back and forth. I guess you could implement it with FWM and have it 
not match packets coming from the MAC of the other director.

When I've done a two-node environment with director and real on the same 
box, I've always ran a private interconnect between them and routed 
traffic over that.

On 10/23/11 4:37 PM, Tomasz Chmielewski wrote:
> I'm trying to set up both director and realserver on one machine, and run 2 such servers.
>
> Unfortunately, it results in terrible packet storm/looping (200k "repeated" packets/s) when:
>
> - I start ipvsadm rules on *both* servers,
> - LVS connects the client to the other server.
>
>
> Is it expected? Is there a workaround or something I didn't set?
>
>
>
> Settings - server 1:
>
> server1:/# ipvsadm -Ln
> IP Virtual Server version 1.2.1 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
>    ->  RemoteAddress:Port           Forward Weight ActiveConn InActConn
> TCP  209.15.13.253:80 lc
>    ->  209.15.13.228:80            Local   20     0          0
>    ->  209.15.13.229:80            Route   20     0          0
>
>
> eth0      Link encap:Ethernet  HWaddr 78:2b:cb:49:75:a7
>            inet addr:209.15.13.228  Bcast:209.15.13.255  Mask:255.255.255.224
>            inet6 addr: fe80::7a2b:cbff:fe49:75a7/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:565546 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:565232 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:44152913 (44.1 MB)  TX bytes:44132615 (44.1 MB)
>            Interrupt:36 Memory:da000000-da012800
>
> lo:253    Link encap:Local Loopback
>            inet addr:209.15.13.253  Mask:255.255.255.255
>            UP LOOPBACK RUNNING  MTU:16436  Metric:1
>
>
>
> Settings - server 2:
>
> server2:/# ipvsadm -Ln
> IP Virtual Server version 1.2.1 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
>    ->  RemoteAddress:Port           Forward Weight ActiveConn InActConn
> TCP  209.15.13.253:80 lc
>    ->  209.15.13.228:80            Route   20     0          0
>    ->  209.15.13.229:80            Local   20     0          0
>
>
> eth0      Link encap:Ethernet  HWaddr 78:2b:cb:4a:d7:1d
>            inet addr:209.15.13.229  Bcast:209.15.13.255  Mask:255.255.255.224
>            inet6 addr: fe80::7a2b:cbff:fe4a:d71d/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:1379119 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:1378568 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:107695951 (107.6 MB)  TX bytes:108057297 (108.0 MB)
>            Interrupt:36 Memory:da000000-da012800
>
> eth0:u253 Link encap:Ethernet  HWaddr 78:2b:cb:4a:d7:1d
>            inet addr:209.15.13.253  Bcast:209.15.13.253  Mask:255.255.255.255
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            Interrupt:36 Memory:da000000-da012800
>
> lo:253    Link encap:Local Loopback
>            inet addr:209.15.13.253  Mask:255.255.255.255
>            UP LOOPBACK RUNNING  MTU:16436  Metric:1
>
>
>
>
> 85.183.95.92 is client IP. It just sends a few packets, which results in massive amounts of repeated packets (200 kp/s).
>
>
> 21:07:34.048984 IP (tos 0x0, ttl 56, id 58921, offset 0, flags [DF], proto TCP (6), length 60)
>      85.183.95.92.37297>  209.15.13.253.80: Flags [S], cksum 0x5fb3 (correct), seq 3532512711, win 14520, options [mss 1452,sackOK,TS val 8338414 ecr 0,nop,wscale 7], length 0
> 21:07:34.048987 IP (tos 0x0, ttl 56, id 58921, offset 0, flags [DF], proto TCP (6), length 60)
>      85.183.95.92.37297>  209.15.13.253.80: Flags [S], cksum 0x5fb3 (correct), seq 3532512711, win 14520, options [mss 1452,sackOK,TS val 8338414 ecr 0,nop,wscale 7], length 0
> 21:07:34.049029 IP (tos 0x0, ttl 56, id 58921, offset 0, flags [DF], proto TCP (6), length 60)
>      85.183.95.92.37297>  209.15.13.253.80: Flags [S], cksum 0x5fb3 (correct), seq 3532512711, win 14520, options [mss 1452,sackOK,TS val 8338414 ecr 0,nop,wscale 7], length 0
> 21:07:34.049031 IP (tos 0x0, ttl 56, id 58921, offset 0, flags [DF], proto TCP (6), length 60)
>      85.183.95.92.37297>  209.15.13.253.80: Flags [S], cksum 0x5fb3 (correct), seq 3532512711, win 14520, options [mss 1452,sackOK,TS val 8338414 ecr 0,nop,wscale 7], length 0
> 21:07:34.049073 IP (tos 0x0, ttl 56, id 58921, offset 0, flags [DF], proto TCP (6), length 60)
>
>