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