Enabling Diskless Windows Boot With i SCSI Suzanne

Enabling Diskless Windows Boot With i. SCSI Suzanne Morgan Program Manager WDEG Storage Microsoft Corporation Steve Marfisi Manager Development em. Boot Inc.

i. SCSI Momentum And Market 1, 400, 000 i. SCSI Initiator Ports 1, 200, 000 1 -Gbps NIC, Driver Ports 1, 000 1 -Gbps Accelerated NIC Ports 800, 000 1 -Gbps HBA Ports 600, 000 10 -Gbps NIC, Driver Ports 400, 000 10 -Gbps Accelerated NIC Ports 200, 000 10 -Gbps HBA Ports 0 04 05 06 07 08 09 20 20 20 40% of large U. S. enterprise respondents have already deployed or intend on to deploy i. SCSI SANs by the end of 2006 – Lehman Brothers Sept. CIO Survey Vast Majority of i. SCSI Initiator hosts run Windows Blade Server is the fastest growing server segment Migration from DAS to SAN benefits apply to boot volumes as well as Data volumes

i. SCSI Software Enabled SAN Boot Goals High Availability Multipath support for load balancing and failover Support for Microsoft Cluster Server Lower Deployment Cost Reduce costs of Deploying sets of identical Windows Systems Use standard imaging tools available today Reduce SAN boot cost to entry and connectivity cost Disaster and Recovery Boot LUN can be replicated to remote sites Server can boot standby boot LUN in case of failure Deployed Servers can be re-purposed Blade Server Cost Optimization Removing hard drive reduces cooling, power consumption Lower cost for blade vendors to manufacturer blades

Architecture And Solution Pre. Boot Windows i. SCSI Software Initiator Int 13 UNDI NIC i. BF Table Boot Parameter Driver Solution Enables boot from LUN located on i. SCSI SAN Can be implemented in either NIC Option ROM, Server ROM or PXE No changes needed to NIC driver in Windows TCPIP NDIS Miniport NIC Microsoft i. SCSI Microsoft Windows Vendor

Deployment Notes i. SCSI Software Enabled SAN boot is designed to be deployed via existing image cloning tools on the market today Support for i. SCSI boot RFC 4173 Including DHCP Option 17 and Option 12 Microsoft is investigating the support of single image boot functionality (multiple servers booting from a single image with individual identities) in a future Windows release

i. SCSI Target Support For Boot Nothing unique needed on the i. SCSI target side Supported with i. SCSI targets Logo’d under the Designed for Windows Logo Program for hardware

Solution Framework Solution is enabled by Microsoft Participating NIC, server vendor or IHV implements required changes in their firmware/BIOS (Tested via WHQL) Solution/configuration prescribed/ delivered by OEM or solution provider Boot version Betas/RC can be downloaded from http: //connect. microsoft. com/ Invitation Code: ms-8 RR 8 -6 K 43 i. SCSI Boot Solutions can be submitted to www. microsoftstoragepartners. com

i. SCSI Boot Component Logo Requirement Highlights Compliance with i. SCSI RFC Including support for login redirection Compliance with existing DHCP/TCP industry specifications Implement i. BFT (i. SCSI Boot Firmware Table) per specification Compliance with existing industry BIOS specifications

Longhorn Server i. SCSI Boot Futures Support of Windows/setup installation of Windows Server directly to i. SCSI target LUN From Windows Installation CD or network share Supported with new imaging mechanisms included with Windows Longhorn Server

Steve Marfisi Manager Development em. Boot Inc.

em. Boot Architecture – i. SCSI Option. ROM N I C o r B I O S I n te g r a ti o n Pre. Boot Windows i. SCSI Software Initiator Int 13 i. SCSI Software Initiator i. BF Table Boot Parameter Driver TCP/IP TCPIP NDIS Miniport UNDI NIC i. SCSI Option. ROM can obtain i. SCSI parameters via: DHCP root path options win. Boot/i server Hot-key menu for R/W local parameters Vendor or em. Boot supplied UNDI Microsoft i. SCSI Microsoft Windows Vendor

em. Boot Architecture – PXE Option. ROM P X E I n t e g ra t i o n Pre. Boot Int 13 TCP/IP win. Boot/i Server PXE / TFTP Server Downloaded i. SCSI Bootstrap Windows i. SCSI Software Initiator i. SCSI Preboot Initiator TCPIP i. BF Table Boot Parameter Driver NDIS UNDI NDIS Miniport NIC Microsoft i. SCSI Microsoft Windows Vendor PXE Option. ROM obtains i. SCSI parameters via win. Boot/i server Vendor or em. Boot supplied UNDI NIC

win. Boot/i Implementation Lessons Learned Disk Imaging – need to consider Availability of existing imaging tools Ability to handle open files or local disk offline Key things to consider as implementing Platform's PXE firmware and Windows NIC driver should be revved to latest versions

win. Boot/i Implementation OEM integration for NIC or BIOS/System vendors available option. ROM payload requirements (uncompressed) in BIOS are approx. 82 -88 KB depending on the UNDI layer option. ROM re-uses UNDI layer, no need to develop new transport Some OEM customization may be needed to get/set/configure boot parameters End user software product Shipping in Q 2, 2006

Blades’ network adapters are assigned to i. SCSI boot volumes. win. Boot/i server software installed. i. SCSI storage installed on network. win. Boot/i clients are now ready for i. SCSI Blades are started, and receive boot, using one of: boot instructions from win. Boot/i management. • em. Boot PXE bootstrap • em. Boot Option. ROM on NIC • em. Boot Option. ROM embedded in BIOS Blade chassis with 3 Microsoft i. SCSI-bootblades, each with powercapable initiator + chewing, potential-forwin. Boot/i client tools failure hard disks. installed on blades. i. SCSI storage delivers OS+applications+data to win. Boot/i clients (blades) Hard disks’ boot volumes copied to i. SCSI storage. Boot volumes carved out of i. SCSI storage and assigned client (initiator) names, matching corresponding Local disks can now beinitiator name. blades’ i. SCSI removed, or kept for paging or other swapping tasks.

i. SCSI Boot Demo

Call To Action Implement Windows supported architecture for i. SCSI boot Review i. SCSI Boot Component Logo requirements prior to implementation Included in latest Logo doc version Test i. SCSI boot pre-boot init & target interoperability i. SCSI boot pre-boot init & UNDI interoperability NDIS miniport in i. SCSI boot configurations E-mail: Boot @ microsoft. com for access to spec for early implementation

i. SCSI Boot Implementers

i. SCSI Boot Solution Providers

Additional Supporting i. SCSI Vendors http: //www. microsoft. com/windowsserversystem/storage/technologies/iscsi/default. mspx

Related Win. HEC Sessions STO 116: Windows SAN: Resolving Technical Barriers to Adoption and Deployment STO 123: Windows Storage Directions: Windows Vista and Beyond STO 133: Windows Vista Storage Support and Logo Requirements SER 112: Windows Enterprise Storage Directions SER 119: Windows Server High Availability with Windows Server Longhorn Failover Clustering

i. SCSI Resources Microsoft i. SCSI website http: //www. microsoft. com/windowsserversystem/storage/iscsi. mspx Download Latest Microsoft i. SCSI Initiator http: //www. microsoft. com/downloads/details. aspx? Family. ID =12 cb 3 c 1 a-15 d 6 -4585 -b 385 -befd 1319 f 825&Display. Lang=en Microsoft support for i. SCSI Clusters FAQ http: //www. microsoft. com/windowsserversystem/ storage/technologies/iscsicluster. mspx i. SCSI deployment guide white paper http: //www. microsoft. com/windowsserversystem/ storage/technologies/iscsi/deployiscsi. mspx For information about i. SCSI support http: //support. microsoft. com/default. aspx To get a list of vendors with i. SCSI Software enabled SAN boot solutions Boot @ microsoft. com More information on XIMAGE and Vista/Longhorn Server Deployment http: //www. microsoft. com/technet/windowsvista/expert/ximage. mspx

© 2006 Microsoft Corporation. All rights reserved. Microsoft, 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.