WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

[Xen-API] after pool-eject, ip address of ejected host is corrupted

To: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] after pool-eject, ip address of ejected host is corrupted
From: Anthony Xu <anthony@xxxxxxxxx>
Date: Tue, 6 Jul 2010 20:16:50 -0700
Delivery-date: Wed, 07 Jul 2010 02:31:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Organization: VMOps
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,

I have two host: 
H1: 192.168.1.111  ( pif ip address is 192.168.1.111)
H2: 192.168.1.112  (pif ip address is 192.168.1.112) 

they are in a pool, H1 is master, after I pool-eject H2, H2 reboots.
after reboot, there is not ip address for nic/bridge if I execute
ifconfig. And I found out pif ip address of H2 is 192.168.1.111(which is
H1's ip address).

That means I need go to lab to reconfigure H2 ip address every time I
pool-eject it. It's not convenient.

Is there any way the host ip address is preserved after it is
pool-ejected?

Thanks in advance!

- Anthony


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>