Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+LVS\s+director\s+issue\s+RHEL\s+5\.4\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+LVS\s+director\s+issue\s+RHEL\s+5\.4\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [lvs-users] LVS director issue RHEL 5.4 (score: 1): Author: Malcolm Turnbull <malcolm@xxxxxxxxxxxxxxxx>; Date: Tue, 6 Mar 2012 19:04:19 +0000; Mohamed, Pulse is a RedHat product and I don't think they support it anymore.. try ldirectord or keepalived As for the ARP issue: Solving for Linux method 1 (using iptables) You can use iptables (net; /html/lvs-users/2012-03/msg00016.html (12,144 bytes)
2. [lvs-users] LVS director issue RHEL 5.4 (score: 1): Author: RADOUANE Mohamed <radouane14@xxxxxxxxx>; Date: Tue, 6 Mar 2012 16:58:03 +0000; Dear All, I am new in LVS domain, I tried to configure it in direct routing, I followed all steps: - Configure lvs.cf - run pulse process - add following commands: ipvsadm -A -t 192.168.1.10:8088 -s; /html/lvs-users/2012-03/msg00015.html (8,723 bytes)

Current List: 1 - 2
Page: [1]