نحوه بوت کردن ویندوز سرور از استوریج SAN

 

I needed to do some testing on Windows 2012 R2 in a boot from SAN (over iSCSI) environment with my Cisco UCS blades. Here is how I went about it.

من نیاز به انجام برخی آزمایش ها در ویندوز 2012 R2 در یک بوت از محیط SAN (بیش از iSCSI) محیط با تیغه های UCS سیسکو من. در اینجا این است که چگونه در مورد آن رفتم

Prerequisites

oscdimg – CD/DVD premastering utility available as part of the Windows Assessment and Deployment Kit (Windows ADK). I used the version here: http://www.microsoft.com/en-us/download/details.aspx?id=39982 When running the adksetup.exe program, hit Next until the “Select the features you want to install” screen appears and then select only the “Deployment Tools” option.adk-installoptionsCisco UCS Drivers – These must be downloaded from Cisco with a valid account. They are located at Downloads Home -> Products Servers – Unified Computing -> UCS B-Series Blade Server Software -> Unified Computing System (UCS) Drivers  I pulled down ucs-bxxx-drivers.2.2.3f.iso for this example.CiscoDrivers  Windows ISO – Should go without saying that you need the Windows ISO for the build you are working with. I’m using Windows 2012 R2 Datacenter in this example en_windows_server_2012_r2_with_update_x64_dvd_4065220.iso Folder Structure – Here is what my folder structure looks like for the examples to follow. Extract the files as shown below: UCS Drivers (ucs-bxxx-drivers.2.2.3f.iso) -> drivers Windows ISO (en_windows_server_2012_r2_with_update_x64_dvd_4065220.iso) -> ISO The ‘mount’ folder will house the boot.wim and install.wim images while we add the drivers.filesrequired

Step 1 – Create Boot Volumes

Using the SolidFire PowerShell module I created the five boot volumes that would hold my Windows installs. The PowerShell module is now in beta and Josh Atwell (@Josh_Atwell) has information on how SolidFire customers can get it here: http://www.vtesseract.com/post/125260508548/introducing-the-solidfire-tools-for-powershellconnect-sfclusterPowerShell-CreateBootVolumesSolidFire-CreatedBootVolumes

Step 2 – Create Slipstream ISO w/Cisco UCS Drivers

The Windows 2012 R2 install media doesn’t contain the drivers required for a boot from SAN configuration. To get the drivers into the install media two files that need to be updated, boot.wim and install.wim. Assuming you have all the files listed in the prerequisite section above in the folder “c:\temp” open up a PowerShell prompt and the series of steps is as follows:

Get-WindowsImage -ImagePath .\ISO\sources\install.wim

Select the index value for the version of Windows you want to slipstream the drivers into. In my case, its Index 4 – Windows Server 2012 R2 ServerDataCenter

Mount-WindowsImage -Path .\Mount -ImagePath .\ISO\sources\install.wim -Index 4

Mountinstall.wimNow add the drivers to the install.wim file (which will take some time) and then dismount the install.wim image:

Add-WindowsDriver -Path .\Mount -Driver .\Drivers -Recurse -ForceUnsigned Dismount-WindowsImage -Path .\Mount -Save

dismount-winimage  Now repeat the process for both the index entries for the boot.wim file.

Get-WindowsImage -ImagePath .\ISO\sources\boot.wim
Mount-WindowsImage -Path .\Mount -ImagePath .\ISO\sources\boot.wim -Index 1
Add-WindowsDriver -Path .\Mount -Driver .\Drivers -Recurse -ForceUnsigned
Dismount-WindowsImage -Path .\Mount -Save
Mount-WindowsImage -Path .\Mount -ImagePath .\ISO\sources\boot.wim -Index 2
Add-WindowsDriver -Path .\Mount -Driver .\Drivers -Recurse -ForceUnsigned
Dismount-WindowsImage -Path .\Mount -Save
Make sure all disk images are dismounted by running Get-Volume | Get-DiskImage | Dismount-DiskImage
Now the actual ISO image can be created with oscdimg.exe. There are a few options that you need to pass oscdimg

oscdimg.exe -n -m –b<path_of_bootable_img_file> <path_of_installation_source> <path_with_filename_is_to_be_created>

-m is used to enable a file > 700MB -n to allow for long file names (longer than DOS 8.3 file name limit) -b is used to locate boot image

For example: oscdimg.exe -n -m -bC:\temp\ISO\boot\etfsboot.com C:\temp\ISO C:\temp\Win2012R2-Cisco.iso

oscdimg

Step 3 – Setup UCS for Boot from SAN

This could be a whole series by itself, but I will touch on the high level requirements here. At a minimum, a boot policy enabling iSCSI boot from SAN (BfS from here on out) and an iSCSI authentication profile and iSCSI vNIC must be created before configuring a service profile to BfS. First, open up UCSM and then navigate to Servers -> Policies -> root -> Boot Policies and create a new policy. I’ll be using the one called iSCSI-BFS.

Screenshot 2015-07-29 14.12.20

Next, an authentication profile needs to be created under Servers -> Policies -> root -> iSCSI Authentication Profiles. Here, specify the account on the SolidFire cluster used to create the boot volumes. Fill in the initiator secret password if you are using CHAP to authenticate hosts to SolidFire.

ISCSIAuth
Now, in UCSM navigate to Servers -> Service Profiles -> root and create a service profile template with the appropriate settings for your environment. Now edit the service profile template and modify the iSCSI vNICs. Select a OverLay vNIC that has the native VLAN for the SVIP of the SolidFire cluster. It’s important to make sure that the VLAN you are booting from is the native VLAN for the iSCSI vNIC, or it will fail to boot properly. In the screenshot below, vNIC1-A and vNIC2-B are for management traffic only. The server will actually boot from a dedicated ‘boot’ vNIC which has a default VLAN 25 (default VLAN) which is where the SolidFire Storage Virtual IP (SVIP) is located in my environment. I found this necessary to keep Windows from randomly hanging during device enumeration during the install.
Screenshot 2015-07-29 14.14.35

With everything configured time to associate the service profile with a physical box. Once that is done, assuming everything is good to go, you should see the Cisco VIC pick up the SolidFire cluster at boot as shown below.UCS-BootFromSAN  From here, you should get the ‘loading files’ screen followed by the familiar Windows installer interface.  Screenshot 2015-07-29 11.32.01  Move through the install as normal until you hit the “Which type of installation do you want” screen. Select the “Custom” option.

Screenshot 2015-07-29 11.47.22

Now the money screen. If everything is configured correctly you should see your volume presented for install. If no disks are presented then the correct drivers did not load or there is some other issue preventing Windows from seeing a disk to install to. Assuming all is well, we can start the install now.

Screenshot 2015-07-29 11.49.39
I’m not a fan of the diagnostic partition, so I usually prep the drive using diskpart to get rid of it. You can do that by pressing SHIFT+F10 to bring up a command prompt and running through creating an active partition to install to.
Screenshot 2015-07-29 11.52.39
If you click the refresh icon now you should see a valid system partition to install to.
Screenshot 2015-07-29 11.54.05

Rest of the install is just like any other Windows 2012 R2 install.

Just as a side note, if you are using Windows 2012 R2 in this method, a nice side benefit is that any deleted files from Windows will be UNMAP’d automatically without having to run the optimize drives utility. This immediately returns space back to the array.
تبلیغات
تبلیغات
تبلیغات