Re: nanny and realserver with direct routing

> It seems nanny dont use "the ipvsam way" to monitor real server.

What's the "ipvsam way" ? IPVS' goal is scheduling, not monitoring real
server !

> nanny seems to don't take care about the VIP and the realserver
> so for nanny the realserver is always down.

This must be a config problem. You're right in the fact it doesn't care
about the VIP for health checks, but it does care when it comes to
add/remove entries from the IPVS routing table.

> How to monitor realserver with direct routing ?

The monitoring has nothing related to the type of routing (DR/TUN/NAT).

> here's my config :
> VIP : 10.1.1.1
>  realserver 1/ 127.0.0.1 => works well
>  realserver 2/ 10.1.1.103
>  on this second realserver :
>   lo:0 10.1.1.1
>   route add -host 10.1.1.1 dev lo:0

Did you hide lo:0 ?
> nanny cmdline finded in /proc :
> /usr/sbin/nanny -c -h 10.1.1.243 -p 80 \
>                 -s "GET / HTTP/1.0\r\n\r\n" \
>                 -x HTTP -a 15 -I /sbin/ipvsadm \
>                 -t 6 -w 1 -V 10.1.1.245 -M g \
> -U none --lvs

This is totally unrelated to what you've specified ealier. You've never
talked about 10.1.1.245 and 10.1.1.243.

You should not matter about nanny's syntax. Just make sure you lvs.cf is
correct. You might want the list to check it !

-- 
Sébastien Bonnet
  Centre de contacts - Experian France