|
Hi
I'm not sure if I really understood your problem correctly, but
concerning the version of the patch to be applied I'd consider
you in taking the newest one (0.9.11). However the persistent
netmask feature is available since patch 0.9.2, if I'm right.
But if you would like to use f.e. the port 0 option, you would
at least need patch 0.9.5 to make it work. Hope this answers
your question.
Your question about the meaning of persistent netmask, I copy
the corresponding part of the ipvsadm man-page:
-M, --netmask netmask
For persistent ports, allows you to specify the
granularity at which the clients are grouped. The
source address of the request is masked with this
netmask to, for example, direct all clients from a
/24 network to the same real server. The default is
255.255.255.255, which means that the persistence
granularity is per client host. Use this option to
solve problems with non-persistent cache clusters
on the client side.
As of connection backup, I'm not sure what you exactly mean, but
I guess you think of pushing the kernel masq table with the
template entries from one director's kernel to a spare one, so
in case of a failover the least possible amount of sessions
would be lost. This is actually not yet implemented and I'm
not sure who exactly is working on it but it has been discussed
a little bit in this mailinglist.
regards,
Roberto Nibali, ratz
hotman wrote:
> Good night,Mr Zhang.
>
> I am Zhao Hongfei from NEC.
>
> I want know what version ipvsadm & ipvs support to set the persistent
> netmask and persistent timeout and want is meaning the persistent
> netmask.
> And How do you think about the connections backup(a old question)?
>
> Thank you!
> Best regards.
> Zhao.
|
