Re: [Xen-users] Xen for testing fail-over set-ups

["Tim Stoop" <tim.stoop@xxxxxxxxx>]

Hi Luke,

Thanks for your help so far, but...

On 1/8/07, Luke S. Crawford <lsc@xxxxxxxxx> wrote:

You need to setup your fail-over IP as a 'secondary IP'  -  that is, don't
put it in the xen configs at all.  You want to give each server it's own
administrative IP most likely, and you can place that in the xm config
file;  then setup the fail over ip using vrrp or whatever from within the
DomUs, the exact same way you would do so on non-xen boxes.

This doesn't work :( The fail-over IP isn't available from outside the domU. See here:

domU:

tim@drbd1:~$ /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:3E:65:11:94  
          inet addr:172.21.1.20  Bcast:172.21.3.255
  Mask:255.255.252.0
          inet6 addr: fe80::216:3eff:fe65:1194/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:481 errors:0 dropped:0 overruns:0 frame:0
          TX packets:493 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:132549 (129.4 KiB)  TX bytes:231415 (225.9 KiB)

eth0:0    Link encap:Ethernet  HWaddr 00:16:3E:65:11:94  
          inet addr:172.21.1.25  Bcast:172.21.3.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:560 (560.0 b)  TX bytes:560 (
560.0 b)

tim@drbd1:~$


dom0:

tim@dom0:/mnt$ ping 172.21.1.20 -c 1
PING 172.21.1.20 (172.21.1.20
) 56(84) bytes of data.
64 bytes from 172.21.1.20: icmp_seq=1 ttl=64 time=0.136 ms

--- 172.21.1.20 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.136/0.136/0.136/0.000 ms
tim@dom0:/mnt$ ping 172.21.1.25 -c 1
PING 172.21.1.25 (172.21.1.25
) 56(84) bytes of data.
From 172.21.1.1 icmp_seq=1 Destination Host Unreachable

--- 172.21.1.25 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

tim@dom0:/mnt$

Is there another way? Thanks in advance for your help!

-- 
Gegroet,
Tim
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users