Enabling Diskless Enabling Diskless Windows Boot With iSCSIWindows Boot With iSCSI
Suzanne MorganSuzanne MorganProgram ManagerProgram ManagerWDEG StorageWDEG StorageMicrosoft CorporationMicrosoft Corporation
Steve MarfisiSteve MarfisiManagerManagerDevelopmentDevelopmentemBoot Inc.emBoot Inc.
iSCSI Momentum And MarketiSCSI Momentum And Market
40% of large U.S. enterprise respondents have already 40% of large U.S. enterprise respondents have already deployed or intend on to deploy iSCSI SANs by the end deployed or intend on to deploy iSCSI SANs by the end of 2006 – Lehman Brothers Sept. CIO Survey of 2006 – Lehman Brothers Sept. CIO Survey Vast Majority of iSCSI Initiator hosts run WindowsVast Majority of iSCSI Initiator hosts run WindowsBlade Server is the fastest growing server segmentBlade Server is the fastest growing server segmentMigration from DAS to SAN benefits apply Migration from DAS to SAN benefits apply to boot volumes as well as Data volumesto boot volumes as well as Data volumes
iSCSI Initiator PortsiSCSI Initiator Ports
00
200,000200,000
400,000400,000
600,000600,000
800,000800,000
1,000,0001,000,000
1,200,0001,200,000
1,400,0001,400,000
20042004
20052005
20062006
20072007
20082008
20092009
1-Gbps NIC, Driver Ports1-Gbps NIC, Driver Ports
1-Gbps Accelerated NIC Ports1-Gbps Accelerated NIC Ports
1-Gbps HBA Ports1-Gbps HBA Ports
10-Gbps NIC, Driver Ports10-Gbps NIC, Driver Ports
10-Gbps Accelerated NIC Ports10-Gbps Accelerated NIC Ports
10-Gbps HBA Ports10-Gbps HBA Ports
iSCSI Software Enabled iSCSI Software Enabled SAN Boot GoalsSAN Boot GoalsHigh AvailabilityHigh AvailabilityMultipath support for load balancing and failoverMultipath support for load balancing and failoverSupport for Microsoft Cluster ServerSupport for Microsoft Cluster Server
Lower Deployment CostLower Deployment CostReduce costs of Deploying sets of identical Windows SystemsReduce costs of Deploying sets of identical Windows SystemsUse standard imaging tools available todayUse standard imaging tools available todayReduce SAN boot cost to entry and connectivity costReduce SAN boot cost to entry and connectivity cost
Blade Server Cost OptimizationBlade Server Cost OptimizationRemoving hard drive reduces cooling, power consumptionRemoving hard drive reduces cooling, power consumptionLower cost for blade vendors to manufacturer bladesLower cost for blade vendors to manufacturer blades
Disaster and RecoveryDisaster and RecoveryBoot LUN can be replicated to remote sitesBoot LUN can be replicated to remote sitesServer can boot standby boot LUN in case of failureServer can boot standby boot LUN in case of failureDeployed Servers can be re-purposedDeployed Servers can be re-purposed
Architecture And Solution Architecture And Solution
SolutionSolutionEnables boot from LUN Enables boot from LUN located on iSCSI SANlocated on iSCSI SANCan be implemented in Can be implemented in either NIC Option ROM, either NIC Option ROM, Server ROM or PXEServer ROM or PXENo changes needed to No changes needed to NIC driver in WindowsNIC driver in Windows
iSCSI SoftwareInitiator
UNDI
Microsoft iSCSIMicrosoft iSCSI
Microsoft WindowsMicrosoft Windows
VendorVendor
Int13
NDIS
iBF Table
BootParameter
DriverNIC
TCPIP
NIC
NDIS Miniport
PreBootPreBoot WindowsWindows
Deployment NotesDeployment Notes
iSCSI Software Enabled SAN boot is iSCSI Software Enabled SAN boot is designed to be deployed via existing designed to be deployed via existing image cloning tools on the market image cloning tools on the market todaytoday
Support for iSCSI boot RFC 4173Support for iSCSI boot RFC 4173Including DHCP Option 17 and Option 12Including DHCP Option 17 and Option 12
Microsoft is investigating the support of Microsoft is investigating the support of single image boot functionality (multiple single image boot functionality (multiple servers booting from a single image servers booting from a single image with individual identities) in a future with individual identities) in a future Windows releaseWindows release
iSCSI Target iSCSI Target Support For BootSupport For Boot
Nothing unique needed Nothing unique needed on the iSCSI target sideon the iSCSI target side
Supported with iSCSI targets Logo’d Supported with iSCSI targets Logo’d under the Designed for Windows Logo under the Designed for Windows Logo Program for hardwareProgram for hardware
Solution Framework Solution Framework
Solution is enabled by MicrosoftSolution is enabled by MicrosoftParticipating NIC, server vendor or IHV Participating NIC, server vendor or IHV implements required changes in their implements required changes in their firmware/BIOS (Tested via WHQL)firmware/BIOS (Tested via WHQL)Solution/configuration prescribed/ Solution/configuration prescribed/ delivered by OEM or solution provider delivered by OEM or solution provider Boot version Betas/RC can be Boot version Betas/RC can be downloaded from downloaded from http://connect.microsoft.com/ Invitation http://connect.microsoft.com/ Invitation Code: ms-8RR8-6K43Code: ms-8RR8-6K43iSCSI Boot Solutions can be submitted to iSCSI Boot Solutions can be submitted to www.microsoftstoragepartners.comwww.microsoftstoragepartners.com
iSCSI Boot Component Logo iSCSI Boot Component Logo Requirement Highlights Requirement Highlights
Compliance with iSCSI RFCCompliance with iSCSI RFCIncluding support for login redirectionIncluding support for login redirection
Compliance with existing DHCP/TCP Compliance with existing DHCP/TCP industry specificationsindustry specifications
Implement iBFT (iSCSI Boot Implement iBFT (iSCSI Boot Firmware Table) per specificationFirmware Table) per specification
Compliance with existing Compliance with existing industry BIOS specificationsindustry BIOS specifications
Longhorn Server iSCSI Longhorn Server iSCSI Boot FuturesBoot Futures
Support of Windows/setup Support of Windows/setup installation of Windows Server installation of Windows Server directly to iSCSI target LUNdirectly to iSCSI target LUN
From Windows Installation CD From Windows Installation CD or network shareor network share
Supported with new imaging mechanisms Supported with new imaging mechanisms included with Windows Longhorn Serverincluded with Windows Longhorn Server
Steve MarfisiSteve MarfisiManagerManagerDevelopmentDevelopmentemBoot Inc.emBoot Inc.
emBoot Architecture – iSCSI OptionROMemBoot Architecture – iSCSI OptionROM
iSCSI Software
Initiator
UNDI
Microsoft iSCSIMicrosoft iSCSI
Microsoft WindowsMicrosoft Windows
VendorVendor
Int13
NDIS
iBF
TableBoot
ParameterDriver
NIC
TCPIP
iSCSI OptionROM can obtain iSCSI parameters via:iSCSI OptionROM can obtain iSCSI parameters via:DHCP root path optionsDHCP root path optionswinBoot/i serverwinBoot/i serverHot-key menu for R/W local parametersHot-key menu for R/W local parameters
VendorVendor or emBoot supplied UNDI or emBoot supplied UNDI
NIC
NDIS Miniport
PreBootPreBoot WindowsWindows
iSCSI Software Initiator
TCP/IP
NIC
or
BIO
S I
nte
gra
tio
nN
IC o
r B
IOS
In
teg
rati
on
emBoot Architecture – emBoot Architecture – PXE OptionROMPXE OptionROM
PXE OptionROM obtains iSCSI parameters viaPXE OptionROM obtains iSCSI parameters viawinBoot/i serverwinBoot/i server
Vendor or emBoot supplied UNDIVendor or emBoot supplied UNDI
iSCSI Software Initiator
UNDI
Int13
NDIS
iBF Table Boot
Parameter Driver
NIC
TCPIP
NIC
NDIS Miniport
PreBootPreBoot WindowsWindows
iSCSI Preboot Initiator
TCP/IP
PX
E I
nteg
ratio
nP
XE
Int
egra
tion
PXE / TFTPServer
Downloaded iSCSI Downloaded iSCSI BootstrapBootstrap
winBoot/i Server
Microsoft iSCSIMicrosoft iSCSI
Microsoft WindowsMicrosoft Windows
VendorVendor
winBoot/i ImplementationwinBoot/i Implementation
Lessons LearnedLessons LearnedDisk Imaging – need to considerDisk Imaging – need to consider
Availability of existing imaging tools Availability of existing imaging tools
Ability to handle open files or local disk offlineAbility to handle open files or local disk offline
Key things to consider as implementingKey things to consider as implementingPlatform's PXE firmware and Windows NIC Platform's PXE firmware and Windows NIC driver should be revved to latest versionsdriver should be revved to latest versions
winBoot/i ImplementationwinBoot/i Implementation
OEM integration for NIC or BIOS/System OEM integration for NIC or BIOS/System vendors available vendors available
optionROM payload requirements optionROM payload requirements (uncompressed) in BIOS are approx. 82-88 KB (uncompressed) in BIOS are approx. 82-88 KB depending on the UNDI layerdepending on the UNDI layer
optionROM re-uses UNDI layer, no needoptionROM re-uses UNDI layer, no needto develop new transportto develop new transport
Some OEM customization may be neededSome OEM customization may be neededto get/set/configure boot parametersto get/set/configure boot parameters
End user software productEnd user software productShipping in Q2, 2006Shipping in Q2, 2006
BladeCenter
1 2 3 4 5 6 7 8 9 10 11 12 13 14
winBoot/i client(s) - blades
CD
Boot volume = iSCSI disk
CD Boot volume = iSCSI disk
CD
Boot volume = iSCSI disk
winBoot/iManagement
CD CD CD
IP Network
iSCSI Storage
Blade chassis with 3 blades, each with power-chewing, potential-for-
failure hard disks.
iSCSI storage installed on
network.
Boot volumes carved out of iSCSI storage and assigned
client (initiator) names, matching corresponding
blades’ iSCSI initiator name.
Microsoft iSCSI-boot-capable initiator +
winBoot/i client tools installed on blades.
winBoot/i server software installed.
Blades’ network adapters are assigned to iSCSI boot volumes.
Hard disks’ boot volumes copied to iSCSI storage.
winBoot/i clients are now ready for iSCSI boot, using one of:
• emBoot PXE bootstrap
• emBoot OptionROM on NIC
• emBoot OptionROM embedded in BIOS
Local disks can now be removed, or kept for
paging or other swapping tasks.
Blades are started, and receive boot instructions from winBoot/i management.
Boot volumes
iSCSI storage delivers OS+applications+data to winBoot/i clients (blades)
iSCSI Boot Demo iSCSI Boot Demo
Call To ActionCall To Action
Implement Windows supported architecture for Implement Windows supported architecture for iSCSI bootiSCSI boot
Review iSCSI Boot Component Logo Review iSCSI Boot Component Logo requirements prior to implementationrequirements prior to implementation
Included in latest Logo doc version Included in latest Logo doc version
Test Test iSCSI boot pre-boot init & target interoperability iSCSI boot pre-boot init & target interoperability
iSCSI boot pre-boot init & UNDI interoperabilityiSCSI boot pre-boot init & UNDI interoperability
NDIS miniport in iSCSI boot configurationsNDIS miniport in iSCSI boot configurations
E-mail: E-mail: for for accessaccessto spec for early implementationto spec for early implementation
Boot @ microsoft.comBoot @ microsoft.com
iSCSI Boot ImplementersiSCSI Boot Implementers
iSCSI Boot iSCSI Boot Solution ProvidersSolution Providers
Additional Supporting Additional Supporting iSCSI VendorsiSCSI Vendors
http://www.microsoft.com/windowsserversystem/storage/technologies/iscsi/default.mspxhttp://www.microsoft.com/windowsserversystem/storage/technologies/iscsi/default.mspx
Related WinHEC SessionsRelated WinHEC Sessions
STO116: Windows SAN: Resolving Technical STO116: Windows SAN: Resolving Technical Barriers to Adoption and DeploymentBarriers to Adoption and Deployment
STO123: Windows Storage Directions: STO123: Windows Storage Directions: Windows Vista and BeyondWindows Vista and Beyond
STO133: Windows Vista Storage Support STO133: Windows Vista Storage Support and Logo Requirementsand Logo Requirements
SER112: Windows Enterprise SER112: Windows Enterprise Storage DirectionsStorage Directions
SER119: Windows Server High Availability with SER119: Windows Server High Availability with Windows Server Longhorn Failover Clustering Windows Server Longhorn Failover Clustering
iSCSI ResourcesiSCSI Resources
Microsoft iSCSI websiteMicrosoft iSCSI websitehttp://www.microsoft.com/windowsserversystem/storage/iscsi.mspxhttp://www.microsoft.com/windowsserversystem/storage/iscsi.mspx
Download Latest Microsoft iSCSI InitiatorDownload Latest Microsoft iSCSI Initiatorhttp://www.microsoft.com/downloads/details.aspx?FamilyIDhttp://www.microsoft.com/downloads/details.aspx?FamilyID=12cb3c1a-15d6-4585-b385-befd1319f825&DisplayLang=en=12cb3c1a-15d6-4585-b385-befd1319f825&DisplayLang=en
Microsoft support for iSCSI Clusters FAQMicrosoft support for iSCSI Clusters FAQhttp://www.microsoft.com/windowsserversystem/http://www.microsoft.com/windowsserversystem/storage/technologies/iscsi/iscsicluster.mspxstorage/technologies/iscsi/iscsicluster.mspx
iSCSI deployment guide white paperiSCSI deployment guide white paperhttp://www.microsoft.com/windowsserversystem/http://www.microsoft.com/windowsserversystem/storage/technologies/iscsi/deployiscsi.mspx storage/technologies/iscsi/deployiscsi.mspx
For information about iSCSI supportFor information about iSCSI supporthttp://support.microsoft.com/default.aspxhttp://support.microsoft.com/default.aspx
To get a list of vendors with iSCSI Software To get a list of vendors with iSCSI Software enabled SAN boot solutionsenabled SAN boot solutions
More information on XIMAGE and Vista/Longhorn Server DeploymentMore information on XIMAGE and Vista/Longhorn Server Deployment
http://www.microsoft.com/technet/windowsvista/expert/ximage.mspxhttp://www.microsoft.com/technet/windowsvista/expert/ximage.mspx
Boot @ microsoft.comBoot @ microsoft.com
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions,
it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.