How To Use A Single HBA Configuration File For Multiple Servers
Article: 167
Applies to: Release 2.00 or greater
The provided HBA configuration jobs read from and write to a
filename based on the target server's id number. This makes sense
because each HBA can be configured to use a different storage controller
WWN and LUN number. However, some SANs, such as the EVA and EMC, do not
require the HBA to have a unique LUN number and in most cases, they boot
from the same controller WWN on the SAN. For servers attached to these
SANs, it is possible to use a single HBA configuration file to set the
controller properties accordingly.
To create such a file. Capture the HBA configuration of one of the
servers already properly connected to the SAN. In the file, replace the
"WWID" value with a dummy value. This field is Read-Only on the HBA, so
it cannot be altered by this dummy value. If booting from SAN, set
"BootDeviceWWID" to the WWN of the SAN controller. Lastly, set
BootDeviceLun=1 as in the example below.
IMPORANT: This method is not compatible with multiple servers connecting to
a common MSA1000 SAN.
[HBA0]
WWID=1111111111111111
HostAdapterBiosEnable=1
SelectBootEnable=1
BootDeviceWWID=500805f30001c081
BootDeviceLUN=1
[HBA1]
WWID=1111111111111111
HostAdapterBiosEnable=1
SelectBootEnable=1
BootDeviceWWID=500805f30001c081
BootDeviceLUN=1
|
Printable version
