Installation guide

C H A P T E R 1 0 Configuration for Clustering
347
example installation above), always put these virtual disks in the same MSCS
resource group. That ensures the disks are always reserved by the same
computer and are always failed over at the same time.
• Ensure that the swap file for each ESX Server machine is not on any of the
physical shared disks. Since the shared disks are reserved by one host or another,
the swap file may become inaccessible to one host or the other during the
operation of the cluster.
• If you are accessing the shared disks on a storage network (SAN) using a QLogic
host bus adapter, you must use particular values for some QLogic configuration
settings. Reboot your physical machine and enter the QLogic configuration
utility during bootup. Under Advanced Configuration Settings, ensure that
• Enable Target Reset is set to Yes.
• Full LIP Login is set to Yes.
• Full LIP Reset is set to No.
• If you are accessing the shared disks on a SAN using an Emulex host bus adapter,
you need to take the following extra steps:
a. On the Options > Advanced Settings page, Set DiskUseDeviceReset to 1.
b. Supply an extra parameter to the Emulex driver when it is loaded. You do this
by editing the file /etc/vmware/hwconfig. First, identify the bus, slot
and function holding the first (or only) Emulex card. You can find this
information by looking at the Startup Profile page. Then add a line with the
format
device.vmnix.6.14.0.options = "lpfc_delay_rsp_err=0"
to the end of /etc/vmware/hwconfig. Here, the numbers 6.14.0
specify the bus, slot and function where the Emulex card is located. If you
have more than one Emulex card, you should have only a line referencing the
first card.
• If you are doing multipathing and can access your shared cluster disk via
multiple HBAs from a host, then you need to modify another configuration file.
Go to the Options > Advanced Settings page and set DiskResetOnFailover to 1.
If an HBA failover occurs on the host, this option causes a SCSI bus reset to be
issued after the failover happens. This bus reset allows the second HBA to access
a shared disk, even if the disk has been reserved by the first HBA. The clustering
software then automatically reserves the disk again via the second HBA.