RE: UM3 on Debian 3.1 with kernel 2.6.8

I found some informations regarding a patch for the kernel before 2.4.27 to
avoid ARP problem. Is it necessary for kernel 2.6.8 ?

Kinaï

-----Message d'origine-----
De : [email protected]
[mailto:[email protected]] De la part de Mattias
Andersson
Envoyé : dimanche 8 octobre 2006 21:04
À : [email protected]
Objet : Re: UM3 on Debian 3.1 with kernel 2.6.8

Okey, then all seams right.
I don't have any clue about what could be wrong, sorry.

/Mattias

kinai skrev:
> Hi Mattias,
>
> My sysctl.conf is like that :
>
> #
> # /etc/sysctl.conf - Configuration file for setting system variables
> # See sysctl.conf (5) for information.
> #
> #kernel.domainname = example.com
> #net/ipv4/icmp_echo_ignore_broadcasts=1
>
> # Enable packet forwarding
> net.ipv4.ip_forward = 1
>
> # Enable configuration of arp_ignore option
> net.ipv4.conf.all.arp_ignore = 1
> # When an arp request is received on eth0, only respond if that address is
> # configured on eth0. In particular, do not respond if the address is
> # configured on lo
> net.ipv4.conf.eth0.arp_ignore = 1
> # Ditto for eth1, add for all ARPing interfaces
> #net.ipv4.conf.eth1.arp_ignore = 1
> # Enable configuration of arp_announce option
> net.ipv4.conf.all.arp_announce = 2
> # When making an ARP request sent through eth0 Always use an address that
> # is configured on eth0 as the source address of the ARP request. If this
> # is not set, and packets are being sent out eth0 for an address that is
on
> # lo, and an arp request is required, then the address on lo will be used.
> # As the source IP address of arp requests is entered into the ARP cache
on
> # the destination, it has the effect of announcing this address. This is
> # not desirable in this case as adresses on lo on the real-servers should
> # be announced only by the linux-director.
> net.ipv4.conf.eth0.arp_announce = 2
> # Ditto for eth1, add for all ARPing interfaces
> #net.ipv4.conf.eth1.arp_announce = 2
>
> Thanks,
> Kinaï
>
> -----Message d'origine-----
> De : [email protected]
> [mailto:[email protected]] De la part de Mattias
> Andersson
> Envoyé : samedi 7 octobre 2006 13:18
> À : [email protected]
> Objet : Re: UM3 on Debian 3.1 with kernel 2.6.8
>
> Hi Kinaï,
>
> you don't say anything about the
> arp configuration in /etc/sysctl.conf.
>
> Perhapps you missed that and have some arp issues?
>
> /Mattias
>
>
> [email protected] skrev:
>   
>> Hello,
>>
>> I have just installed UM3 on two debian 3.1 with kernel 2.6.8 to provide
>> SMTP Filtring with load balancing (postfix/amavis/spamassassin/clamav).
>> These two servers are the real servers too.
>>
>> I haven't patch my kernel. It's the debian version.
>>
>> It seems that all work as fine, but some times (1/3 tries) the service
>> bound on the virtual IP address take a lot of time to answer. By example,
>> if you open a telnet session on the virtual IP on the SMTP port, the
>> welcome message can take 4 ou 5 seconds. If I call directly one of the
>> nodes, the problem doesn't occur.
>>
>> For additionnal information, I have followed this installation procedure
:
>> http://www.debianhelp.co.uk/ultramonkey.htm
>>
>> Below my configuration files :
>> /etc/ha.d/ha.cf
>>
>> logfile /var/log/ha-log # File to write other messages to
>> logfacility     local0 # Facility to use for syslog()/logger
>> keepalive 2 # keepalive: how long between heartbeats?
>> deadtime 10 # deadtime: how long-to-declare-host-dead?
>> warntime 10 # warntime: how long before issuing "late heartbeat" warning?
>> initdead 10
>> auto_failback on
>> # nice_failback on # nice_failback:  determines whether a resource will
>> fail #back to its "primary" node, or remain on whate$
>> udpport 694 # What UDP port to use for communication?
>> bcast   eth0    # Linux What interfaces to heartbeat over?
>> mcast eth0 225.0.0.1 694 1 0 # Set up a multicast heartbeat medium
>> #       Tell what machines are in the cluster
>> #       node    nodename ...    -- must match uname -n
>> node    mynode01
>> node    mynode02
>>
>> respawn hacluster /usr/lib/heartbeat/ipfail
>> apiauth ipfail gid=haclient uid=hacluster
>>
>>
>> /etc/ha.d/haresources
>>
>> mynode1 \
>> ldirectord::ldirectord.cf \
>> LVSSyncDaemonSwap::master \
>> IPaddr::192.168.250.90/24/eth0/192.168.250.255
>>
>> /etc/ha.d/ldirectord.cf
>>
>> # Global Directives
>> checktimeout=10
>> checkinterval=10
>> #fallback=127.0.0.1:25
>> autoreload=yes
>> logfile="/var/log/ldirectord.log"
>> #logfile="local0"
>> quiescent=yes
>>
>> ## Virtual Service for SMTP
>> virtual=192.168.250.90:25                 ## IP VIRTUEL
>>         #fallback=127.0.0.1:25
>>         real=192.168.250.91:25 gate ##mynode01
>>         real=192.168.250.92:25 gate ##mynode02
>>         service=smtp
>>         scheduler=wlc   ##mode fonctionnement du cluster
>>         #persistent=600
>>         protocol=tcp
>>         checktype=negotiate
>>
>> Thanks for help,
>> Regards,
>> Kinaï
>>
>>
>>   
>>     
>
>
>   


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.




-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.