- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've been successful in using BFS with VI3 numerous times. I also use BFS with our Windows servers. I'm using Dell 1955 blade servers, and a EMC Clariion CX500 with Brocade switches. Prior to any OS installation (VI3 or even Windows). I only enable a single pathway from my blade server to my SAN.
To make life easy:
\- I always use SPA to own the Boot from SAN LUN.
\- When creating my WWN Alias, I always use FabricA only and only point to the server and SPA only prior to OS installation.
\- I only expose the BFS lun in the storage group.
\- Install the VI3 OS
\- Once the VI3 is installed, I enable all fabric pathways from the server to the SAN.
\- Rescan the HBA's within VI3 or reboot the server
\- Once I verify that all 4 pathways exists, I add the shared luns to the storage group and rescan the HBA's.
VI3 then can manage the connectivity to the SAN (ie. Powerpath).
I've also read somewhere (a long time ago) that the BFS LUN ID needs to be lower than the shared luns.