EMC QLA22xx, QLA23xx manual Understanding Persistent Binding in a Fabric Environment

Page 11

Introduction

\\PHYSICALDRIVE0, \\PHYSICALDRIVE1, and \\PHYSICALDRIVE2. The number is assigned during the disk discovery part of the Windows boot process.

During boot-up, the Windows OS loads the driver for the storage HBAs. Once loaded, the OS performs a SCSI Inquiry command to get information about all of the attached storage devices. Each disk drive that it discovers is assigned a number in a semi-biasedfirst come, first serve fashion based on HBA. (Semi-biasedmeans that the Windows system always begins with the controller in the lowest-numbered PCI slot where a storage controller resides. Once the driver for the storage controller is loaded, the OS selects the adapter in the lowest-numbered PCI slot to begin the drive discovery process.)

It is this naming convention and the process by which drives are discovered that makes persistent binding (by definition) impossible for Windows NT/Windows 2000/Windows 2003. Persistent binding requires a continuous logical route from a storage device object in the Windows host to a volume in an EMC storage array across the fabric. As mentioned above, each disk drive is assigned a number in a first come, first serve basis. This is where faults can occur.

Example Imagine this scenario—A host system contains controllers in slots 0, 1, and 2. Someone removes a cable from the QLogic controller in host PCI slot 0, then reboots the host.

During reboot, the Windows OS loads the QLogic driver during reboot and begins disk discovery. Under the scenario presented above, there are no devices discovered on controller 0, so the OS moves to the controller in slot 1 and begins naming the disks it finds, starting with \\PHYSICALDRIVE0. Any software applications that were accessing \\PHSYICALDRIVE0 before the reboot will be unable to locate their data on the device, because it has changed.

The following figure shows the original configuration before the reboot. HBA0 is in PCI slot 0 of the Windows host. Each HBA has four disk devices connected to it, so Windows has assigned the name \\PHYSICALDRIVE0 to the first disk on HBA0. Each disk after that is assigned a number in sequence as shown in the figure.

Understanding Persistent Binding in a Fabric Environment

1-3

 

 

1

Image 11
Contents REV A01 August Trademark Information Copyright 2001-2003 EMC Corporation. All rights reservedContents LUN Chapter Configuring an EMC Boot DeviceAppendix a Third-Party Software Appendix B TroubleshootingProblems and Solutions Index EMC Fibre Channel with QLogic HBAs in Windows Hosts Hardware or software PrefaceEMC uses the following conventions for notes, cautions, Damage to the system or equipment. The caution may apply toBold Related Documentation Typographical ConventionsPalatino Introduction Understanding Persistent Binding in a Fabric Environment Understanding Persistent Binding in a Fabric Environment HBA Installing Configuring the HBA Driver Downloading QLogic Drivers Firmware Verifying Documentation IntroductionInstalling an HBA Check for an Updated HBA Driver Move the jumpers, onto pins 1-2 if not already there Reconfigure the HBA JumperSet the HBA FC-AL Loop ID Installing an HBA Advanced Adapter Settings , and Extended Firmware Settings EMC HBA SettingsPre-Configured SettingsTo set the first HBA, follow these procedures Configuring Nvram for Stratus ftServersQLogic HBAs Firmware/BIOSFibre-Down Servers With EmbeddedExample Flasutil /L /F /N NVRAM23o.DAT To load firmware/BIOS and Nvram settings, typePress the Down Arrow until you select Data Rate then press EMC HBA Settings Installing the HBA Driver Select have Disk Administrative Tools, Computer ManagementEMC Fibre Channel with QLogic HBAs in Windows Hosts Double-click the Scsi & RAID Controllers icon EMC Fibre Channel with QLogic HBAs in Windows Hosts Upgrading to Windows 2003 from Windows 2000 or Windows NT EMC Fibre Channel with QLogic HBAs in Windows Hosts Configuring an EMC Boot Device Configuring an EMC Boot Device LUN How to Determine I/O Latency and Load on the BootBehavior Boot CrashdumpSave to Disk Configuring a Symmetrix Boot Device Configuration Settings menu From the Configuration Settings menu, select Host AdapterFrom the Host Adapter Settings menu, select Host Adapter Select Current Boot Node Name and press EnterWindows NT InstallingBoot Device Windows OS ontoFrom this point, press S to specify additional devices HP ProLiant BL20p G2 Windows Installation Installation procedure includes steps you must follow in a Configuring a CLARiiON Boot DeviceProcedure FlowchartConfiguring a CLARiiON Boot Device Topologies Configurations, Revisions Hardware Software RequirementsRequirements Requirements, and related documentationRequired media includes the following Preparing the Storage SystemMedia Requirements Press ESC to return to the previous menu Configuring a CLARiiON Boot Device EMC Fibre Channel with QLogic HBAs in Windows Hosts Continue to Preparing the Server on Node NameWhat Next? Physical Connection of Only One SP Port to the Fabric Preparing the ServerSelect Set Boot Controller Order Configuring the HP ProLiant BL20p G2Boot Bios Configuring the HBACTRL-Q G2 Windows 2000 OS Installation on Windows Licensing Agreement appears HP ProLiant BL20p G2 Windows 2000 OS Installation Verifying HBA Driver Digital Signature Installation EMC Fibre Channel with QLogic HBAs in Windows Hosts Navisphere Host Installing AdditionalConfiguring Additional Boot PortEMC Fibre Channel with QLogic HBAs in Windows Hosts Configuring a CLARiiON Boot Device On the Computer Management window, click Disk Management Trespassing the Boot LUN Using atftrespassStarting a Fresh Installation Boot Time and LUN Availability EMC Symmetrix EMC CLARiiON Replacing a Boot HBAExplanations of Entries How a Server Responds to Failure in the Boot LUN PathStop Error fatal blue screen Indicates host failure Ntosknl Bsod Known IssuesEMC Fibre Channel with QLogic HBAs in Windows Hosts Third-Party Software QLogic SANSurfer SANBlade Manager After completing these changes, reboot the host system Veritas Volume Manager 3.x for WindowsEMC Fibre Channel with QLogic HBAs in Windows Hosts Troubleshooting Solution Problems and SolutionsProblem A host may log a message noting that disk has reached a EMC Support. Windows 2003 driver 8.2.2.20 and later alreadyContain this correction EMC Primus case emc69308 Direct-connect to EMC CLARiiONEMC Fibre Channel with QLogic HBAs in Windows Hosts Index Index