4 Operator

 • 

4.5K Posts

May 21st, 2009 08:00

First, I would suggest review the Host Connectivity Guide for Windows - there is a section specifically for setting up Boot-from-SAN.

Home > Support > Technical Documentation and Advisories > Host Connectivity/HBAs > Installation/Configuration.

If I remember, when you setup the HBA's for boot, you pick one path from one of the HBA's - remember that the boot LUN on the array will be owned by one SP and the path needs to see the LUN on the path that goes to that SP - so if you have two HBA's zoned with paths to both SPA and SPB and the boot LUN is owned by SPA, the paths to SPA are the boot paths. This occurs before the OS is involved - no Powerpath.

Once the OS is booted then PowerPath takes over the management of the paths.

glen

4 Operator

 • 

5.7K Posts

May 25th, 2009 03:00

The boot order or controller order (whatever it is called) in the BIOS of the server determines from what HBA the system boots. If 1 of the 2 paths fails for that boot controller, the 2nd path will automatically be the active one, since the boot HBA is still working. If that HBA fails, the 2nd HBA should be the boot controller and the 2 paths from that HBA will be the working ones, the one to the SP that owns the LUN will be the primary path.

PPath will work as soon as the OS is up.
No Events found!

Top