|
|
|
Forum Newbie
Group: Forum Members
Last Login: Thursday, September 25, 2008 11:55 AM
Posts: 3,
Visits: 5
|
|
I understand why it happens, I wonder if there is a trick or workaround. So the issue is that when you have your VMs stored on a VSA, the ESX server cannot get to the VMs during boot because the VSAs are no loaded yet. Therefore ESX marks all VMs as unknown and inaccessible. After the VSAs boot, then a rescan of the HBA allows the ESX server to load the names and disks of the VMs. I cannot set, or haven't figured out how to set, other VMs besides the VSAs to auto start when the ESX server boots.
Are there any tricks to making this work? One thought I had is a sechedule task that occurs after boot that rescans the HBAs after the VSAs are up. If there is enough delay in the auto boot of the other VMs, then maybe they would start.
Any thoughts?
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: Friday, August 01, 2008 2:34 AM
Posts: 6,
Visits: 28
|
|
| It seems ESX doesn't auto scan the HBA so this isn't possible. It's one of the issues I've run into when using the VSA.
|
|
|
|
|
Junior Member
Group: Forum Members
Last Login: Sunday, July 20, 2008 4:31 PM
Posts: 20,
Visits: 105
|
|
Hi Guys
Description: This script rescans HBA and iSCSI adapters on ESX hosts
This script rescans ESX host LUN's or iSCSI targets that can be scheduled
#!/usr/bin/perl -w
#Filename: rescan-hbas.pl
#No warranty is provided with this script
use strict;
my @hbas = `/usr/sbin/esxcfg-info \| grep vmkernel -i \| grep hba \| awk -F\. \{\'print \$29\'\}`;
print "The following HBAs were detected on this system:";
print "\t@hbas";
foreach my $hba (@hbas) {
system("/usr/sbin/esxcfg-rescan $hba");
}
print "Checking to see if SW iSCSI is in use....";
my $iscsi = `/usr/sbin/esxcfg-swiscsi -q`;
chomp ($iscsi);
print "$iscsi";
if ($iscsi eq "Software iSCSI is enabled") {
system("/usr/sbin/esxcfg-swiscsi -s")
}
Reality is defined by the physical universe and your mind - "Its the second one that varies" :-)
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: Thursday, September 25, 2008 11:55 AM
Posts: 3,
Visits: 5
|
|
terryv:
Thanks. Very interesting. How much for the warranty? Just Kidding. I will give this a try next time I can justify rebooting the ESX servers. I assume there is a way to schedule this script to run after every reboot? Or are you suggesting to just schedule it to run on a recurring basis like every 5 minutes? I wonder what impact that would have on the servers...
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: Thursday, September 25, 2008 11:55 AM
Posts: 3,
Visits: 5
|
|
| Anyone have any new ideas?
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: Monday, September 29, 2008 8:33 AM
Posts: 8,
Visits: 14
|
|
| does the script work with ESXi 3.5? May need a managemnt VM running on local storage using hte remote cli tools, and delay the startup of other vms by 10min or so??
|
|
|
|
|
Supreme Being
Group: Moderators
Last Login: Yesterday @ 2:22 PM
Posts: 101,
Visits: 354
|
|
To get it on ESXi would require a remote CLI but we have not tried that yet. It has been interesting enough just to get ESX to run it locally.
The only update I can give is a script was built by LeftHand's PS group, and it does rescan and get targets correctly, but the datastore it is looking for would not show up, to the script at least, so we could not power on VMs. Even after VMware involvement we did not get that solved.
Just recently one of our engineers found a way past that issue for different reasons though so I'll take a second look at this. Maybe we can get that script to work on ESX soon, then look at how to make the remote CLI do it for ESXi.
Adam C
Product Manager
LeftHand Networks
|
|
|
|