SAN Deployment Supports for Windows Server 2012 and Windows Server 2012R2.
Windows Server OS can be deployed in a SAN environment by using OSIM. Target SAN disk for OS deployment is identified by WWN or WWID based on NAA addressing scheme.
Boot parameter SAN ID is available to specify WWN or WWID of Disk. The SANID boot parameter is added to the Windows Server OS images to identify a specific target related to a particular SAN logical unit number (LUN) or Disk. This provision ensures that the specified LUN or Disk is explicitly selected. SANID boot parameter holds the identifier value that is associated with the specified Disk or LUN like World Wide Name (WWN) or World Wide Identifier (WWID) based on Network Address Authority (NAA) format.
The supported formats, with example values, for SANID are as follows:
naa.60a9800064762f34694a6e3651697759
60a9800064762f34694a6e3651697759
For backward compatibility, support for the SANID value in the attribute=value format is available as follows:
TargetLUN=naa.60a9800064762f34694a6e3651697759
SANID boot parameter is ignored if boot parameter “CreateNewPartitions” is set to true because, in this case it uses any existing available partition (C drive) created by previous windows installation for new OS Installation.
Supplying boot parameter SANID with boot parameter “WinPEPartition” with value “Use special partition file W2012.wp1 from CAMENU”, forces OSIM to ignore parameter “WinPEPartition” value.
If SANID is specified, OSIM identifies the disk to be used for OS installation and the supplied external partition file is ignored for OS deployment.
For more information, see Chapter 2 “How to Use OSIM”, Section Manage OS Installations “Boot Parameters”.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|