<p dir="ltr">For the moment, nothing is going on. The change is planned on Thursday. So, correct me if I'm wrong, you say that the fastest and easiest way is to suspend all the machines, make the change of the storage server, rediscover the iscsi server and then bring the vm's back up?</p>
<p dir="ltr">Kind regards,<br>
Koen</p>
<div class="gmail_quote">On Feb 4, 2014 1:47 PM, "Elad Ben Aharon" <<a href="mailto:ebenahar@redhat.com">ebenahar@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I suppose that those VMs are now in 'Paused' state, correct me if I'm wrong.<br>
After connectivity with storage comes back, all VMs which couldn't detect their disks should be resumed from 'Paused' to 'Up' state automatically. It shouldn't take them a long time to change their state (a few minutes).<br>
<br>
----- Original Message -----<br>
From: "Koen Vanoppen" <<a href="mailto:vanoppen.koen@gmail.com">vanoppen.koen@gmail.com</a>><br>
To: <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
Sent: Tuesday, February 4, 2014 2:32:46 PM<br>
Subject: [Users] Storage server<br>
<br>
Dear All,<br>
<br>
At work, the network guys have come to a discovery that they have made a mistake in their network configuration... The Storage server that we use as ISCSI target in oVirt, is in the wrong VLAN, so the wrong IP address...<br>
<br>
What is the best way to make sure that all of our vms (40) that are using this scsi storage will come up again after the storage server has changed his ip?<br>
What are the best steps to be taken...?<br>
We are using oVirt Engine Version: 3.3.1-2.el6<br>
<br>
Kind Regards,<br>
<br>
Koen<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div>