The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the
express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional
warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Microsoft, Windows, and Windows Server are U.S. registered trademarks of Microsoft Corporation.
About this document
These application notes describe storage area network (SAN) boot setup procedures on Microsoft®
Windows® Server 2003 for Itanium®-based systems for specific software solutions, Fibre Channel host
bus adapter
For the latest version of these application notes and other documentation, see the HP storage web site
All HP Integrity servers are supported. For detailed information, go to
http://www.hp.com/products1/integrity/index.html.
A7298A, pro
A8002A, pro
A8003A, pro
AB232A, pro
AB379A, pro
AB379B, pro
AB466A, pro
AB467A, pro
AE311A, pro
AD300A, pro
FC2143, pro
FC2243, pro
FC1143, pro
FC1243, pro
FC1142, pro
FC1242, pro
For the late
go to the HP
saninfrastructure.html.
duct number A7298A
duct number A8002A
duct number A8003A
duct number AB232A
duct number AB379A
duct numb er AB379B
duct number AB466A
duct number AB467A
duct number AD300A
duct number AD300A
duct number AD167A
duct number AD168A
duct number AB429A
duct number AB379A
duct number AE311A
duct number AE312A
st firmware, driver, BIOS, and EFI versions and information,
storage web site
ttp://h18006.www1.hp.com/storage/
h
Extensible Firmware Interface
(EFI)
Restrictions
This secti
Operating system restrictions,page6
Clustered server restrictions, page 6
SCSIPORT m
Storport miniport driver restrictions, page 6
Standalone server restrictions, page 7
Minimum requirement:
Emulex EFI-Based Setup Utility (ESBU)—3.11a4
Emulex EFI firmware–5.01a8
HP Smart Setup Media 4.00
on describes:
iniport driver restrictions
HP StorageWorks Booting Windows for Itanium-based systems from a storage area network
, page 6
5
Operating syste
m restrictions
The following o
perating system restrictions apply:
• Microsoft Windows operating systems require a unique, dedicated disk for booting. Therefore,
each server connected to a RAID array must have its own disk, or LUN (logical unit number),
dedicated solely for booting and operating system files. Data can be allocated across both the
boot disk and the remaining disks. Booting from array-based disk partitions is possible.
NOTE:
The memory paging system requires fast access to the pagefile.sys file. Insomecases,inSAN
environments with heavy I/O loads, the access request for moving information to or from the paging
file may be delayed. This can cause the operating system to halt, requiring a reboot to recover.
Microsoft recommends that if paging errors occur, page files should be relocated to disks that are
built into the server using its internal data paths. See the following Microsoft article for additional
recommendations related to booting from a SAN:
• For Windows Server 2003, a crash dump file will not be generated if, at the time of a
system crash, the active path to the system drive is different from the active path established
when the system was turned on. To ensure that a crash dump is created, restore the path
that was the active path at boot time as soon as possible after the failure, and make it
the active path. For detailed information, see the Crash Dump File Creation section in
• These configurations require a minimum of four HBAs.
Storport miniport driver restrictions
The following Storport miniport driver restrictions apply:
• For Storport miniport driver restrictions, see the following Microsoft articles:
• To properly set up MSCS, see "Cluster is formed by using a local quorum resource after a
cluster setup failure in Windows Server 2003," available on
nl
http://support.microsoft.com/kb/912944/en-us.
• For boot from SAN and MSCS configurations on Windows Server 2003 systems, see "The
updated Storport storage driver, version 5.2.3790.2494, is available for Windows Server
2003," available on
value to a Windows Server 2003-based computer that you start from a SAN so that the
startup disk, the pagefile disks, and the cluster disks that are all on the same SAN fabric,"
available on
• A minimum of two HBA ports per host is required for any High Availability (HA) configurations.
Standalone server restrictions
In a standalone server environment, an HBA port can share boot and data paths.
Server replacement in the event of a server failure
You must retain the HBAs to ensure that the replacement server hardware components are identical to the
ones you are replacing. Place each HBA in the PCI slots of the new server in the same order as they
were placed in the old server.
If you are using an internal disk for your paging file system, move this disk to the replacement server. You
canalsouseanewdisk,butyoumustformatitandmanuallyresetthepagingtothatdisk.
Prerequisites
The following procedures are not described in detail in this document. However, they must be performed
before performing the boot setup procedures.
s
RAID array
Working with boot disk partitions,page7
Switch-based zoning, page 7
,page7
RAID arrays
Perform the following for EVA, MSA, and XP arrays:
• Verify that all existing storage units (virtual disks) have the proper access settings.
• With switch-based configurations, if zoning is enabled, check the switch to ensure there are
no zoning conflicts.
Working w
ith boot disk partitions
Before cr
procedures:
• Create a LUN that is at least 32 GB.
• If you pl
eating a boot disk, you must start with a clean, unpartitioned virtual disk. Perform the following
an to set up booting from a RAID array that has other virtual disks attached to other
, be aware that when you are setting up booting for the new server, the installation
servers
m displays a list of partitions available for loading the operating system. The display
progra
ns a disk for every controller port accessible by the HBA. Although it may appear that there
contai
e than one virtual disk available for booting, there is only one virtual disk available.
is mor
Switch-based zoning
You must be familiar with switch-based zoning. For information about zoning for your environment, see
your switch’s installation guide.
Setting up switch zoning
You must set up switch zoning as part of your configuration. See the
figures in “
Cabling options for dual-channel HBAs” on page 11.
“
Cabling options for single-channel HBAs” on page 8 and
HP StorageWorks Booting Windows for Itanium-based systems from a storage area network
7
Setting up initi
1.
2. Enable the zone.
al zoning
Create a zone using the world wide name (WWN) or switch port number that includes the boot
HBA port and the
Finalizing zoning
1. Modify the initial zone to include the second controller port.
2. Create a zone in the second fabric to include the secondary boot HBA port and the two remaining
controller ports.
controller port.
Reconfigurin
g HBA zoning to avoid time-out conditions
In boot from S
the boot HBA, a time-out condition may occur when the boot HBA interacts with the non-boot HBAs,
causing a crashdump to not be generated. To avoid time-out conditions, reconfigure the zoning so
that the boot instance for each path is in its own zone, separate from the other non-boot HBAs. This
may also res
AN configurations where there are more than two Emulex HBAs in the same zone as
ult in faster boot-up times.
Cabling options for single-channel HBAs
SAN boot is supported in the zoned single-channel HBA configurations, as shown in Figure 1 through
Considerations for booting clusters with SCSIPORT miniport drivers
Windows operating systems require that the HBA used for booting is not the same HBA used for cluster
shared storage. You must use separate HBAs or HBA ports in each server when setting up for cluster
booting. In general, the key steps for setting up booting include:
HP StorageWorks Booting Windows for Itanium-based systems from a storage area network
13
• Installing all HBAs but not connecting them
• Configuring each HBA that attaches to boot disks for booting (for clusters, a RAID array needs
two separate boot disks)
• Connecting and setting up each HBA for booting, one at a time
• Setting up disk connectivity from each unique boot disk to its server, using the command line
interface (CLI) or GUI
• Installing the Windows operating system on a unique and dedicated disk in the RAID array
• Ensuring that the drive letters are the same for the boot disks on both servers
Multipathing provides high-availability computing through a redundant data path to the RAID array.
Microsoft requires that the boot HBA be different from the shared-data HBA. When using the SCSIPORT
miniport driver in a cluster configuration, each server must have four HBAs (with a minimum of two for
boot and two for data, bringing the total to a minimum of eight HBAs for a two-node cluster). This
configuration provides data-path redundancy for boot and data. When using the Storport miniport driver,
the boot and data paths can reside on the same HBA. Multipath software loads after the operating
system has booted and should be treated the same as any other application installation.
• If one server is booting from a SAN, one host group is required for the HBA on the server.
• If more than one server is booting from a SAN and all are accessing the same physical port, a
unique host group is required for each HBA. Every host group must be assigned on a port with a
unique LUN 0. If LUN security is turned off for this port (for example, port CL1-A), all servers
defined in the host groups are given access to all LUNs in the default host group.
For detailed information about XP Disk Array host groups, LUN security, and host modes, see the
HP StorageWorks Command View XP user guide at:
6. Enter Yes at the Do you want to force defaults? prompt.
7. Select Enable or Disable BIOS.
8. Select Enabled.
9. Press ESC to return to the main menu.
10. Select Configure the HBA parameters.
11. Select Topology.
HP StorageWorks Booting Windows for Itanium-based systems from a storage area network
19
12. Select Point to Point.
13. Press Esc twice to return to the main menu.
14. Select Configure Boot Parameters (The boot table should be empty).
15. Select Configure Boot Devices.
NOTE:
If there is an entry in the boot table, press Enter and then select Clear Flash Boot Info.This
creates an empty table. Continue with the procedure.
16. Select Scan Targets to return to the empty Boot Table screen.
The HBA is now logged into the switch.
17.
Follow the steps in “Setting up initial zoning” on page 8, unless directly connected.
18. On the boot server, select the firstlineandthenpressEnter.
19. Select Scan Targets.
A single WWN appears. This is the node to which your boot device is attached.
20. Using a storage configuration application, or following the procedures in
Creating a LUN”onpage14,createoneLUNandgiveitaccesstotheHBAWWN.
“
NOTE:
For Disk Array XP, you must run Scan Targets a second time after you create LUN 0 and
presentittothehost. DoingsomakestheWWNNofthebootHBAavailablesoitcan
be presented to the LUN.
21. On the boot server, press Enter to display a LUN. (This is the LUN to which your boot device has
access.)
22. Select Boot this device via WWN.
The boot table has one entry that displays the boot device target WWN and LUN information.
23. Press ESC
Press Enter.
until you exit the utility.
Configuring QLogic HBAs
QLogic HBAs do not require configuring the boot device.
You need only follow the steps in “
Setting up initial zoning” on page 8, unless directly connected.
Installing the operating system
You can install the operating system using one of the following procedures:
•
• Installing from the Microsoft CD-ROM,page21
• Special procedures for RX8620 or RX7620 systems, page 24
Installing from the Re-install CD-ROM
To install the operating system using the Re-install CD-ROM:
1. Insert the Windows operating system Re-install CD-ROM.
ling from the Re-install CD-ROM
Instal
, page 20
20
2. Select Bootable DVD from the EFI Boot Manager menu.
Figure 19 Installing the operating system using the Windows CD-ROM
3.
When the HP recovery console menu opens, click Re-install. Ignore the warning about deleting
all data on the drive and click OK.
4. When asked to select the boot drive partition size, select C to use the full drive size.
5. Use the latest Smart Setup CD-ROM to update the system drivers and agents.
It is not necessary to re-install the HBA driver unless an update is available.
NOTE:
For single-path configurations, skip step 6, step 9, and step 10.
6. Install multipathing software if applicable.
7. Install the latest operating system service pack.
8. Reboot the server to complete the installation.
9. Follow through on each additional controller port assignment for the HBAs.
10. Connect any nonbooting HBAs.
11.
Follow the procedure in “Finalizing zoning ”onpage8.
12. Create and assign all other storage LUNs to the appropriate HBAs.
Installing from the Microsoft CD-ROM
Use the following procedures to install the operating system using the Microsoft CD-ROM.
Loading the HBA driver for a Windows Server 2003 install
To load the HBA driver:
1. Insert the HP Smart Setup CD-ROM.
2. Select Bootable DVD from the EBSU menu and press Enter.
HP StorageWorks Booting Windows for Itanium-based systems from a storage area network
21
3. Select Load OEM Boot driver or press B to display the Load OEM Boot Driver screen.
Figure 20 Lo
Select the appropriate Fibre Channel HBA and press Enter.
4.
5. Press Tab once and then press Enter to load the driver.
The system d
6. Select Exit or press X to exit.
ad OEM Boot Driver
isplays a message confirming that the driver is loaded.
Loading the HBA driver for a Windows Server 2008 install
Go to www.hp.com anddownloadtheIA64 Boot from San (BFS) driver kit.
1.
2. Extract the IA64 BFS kit to a USB flash drive.
3. Insert the USB flashdriveintoanavailableUSBslotonthesystem.
Preparin
g the SAN disk device for operating system installation
To prepar
1. Select EFI Shell on the EBSU menu.
2. With the HP Smart Setup CD-ROM in the DVD drive, change to the CD-ROM file system.
e the disk device for operating system installation:
NOTE:
The CD-ROM file system might be mounted somewhere other than fs0.
3. At the command prompt, change to the location of the Diskpart Utility:
Shell> fs1:
fs1:\> cd efi\efi_utils
4. Run the DiskPart Utility:
fs1:\efi\efi_utils> diskpart.efi
22
5. List the partitions available:
DiskPart> list
Output similar to the following appears:
### BlkSize BlkCount
--- ------- ----------------
0 200 B40
1 200 4800000
NOTE:
Device 0 is the virtual floppy disk and Device 1 is the LUN created to install the operating
system. The BlkCount valuevariesdependingonthesizeoftheLUNcreated;itdoes
not match the LUN size.
6. Enter the select command to select the boot device:
DiskPart> Select 1
Selected Disk = 1s
7. Inspect the disk. If a message other than the following displays, use the clean command to destroy
all partitions on the disk.
DiskPart>inspect
Selected Disk = 1
The disk is RAW, nothing to inspect.
8. Exit DiskPart:
DiskPart> exit
9. Remove the HP Smart Setup CD-ROM and insert the Windows Server 2003 CD-ROM in the drive.
10. Rescan the drives, which gives the CD-ROM system access to the Windows CD-ROM files.
fs1:\efi\efi_utils > map –r
11. Select Exit to return to the EFI Boot Manager menu.
You are now ready to install the operating system.
Installing the Windows Server 2003 operating system