If you have supported hardware, then the FC SAN configuration process (once the WWID scan is performed) will usually and more-or-less work, within the (many) limits of the various FC SAN management interfaces.
If you don't have supported hardware, then this process tends to turn into an adventure. And sometimes this turns into a much bigger adventure.
Like EFI, there isn't much chance of forward progress with a FC SAN configuration, short of acquiring and reading through the product management manuals, without at least some experimentation, and without digging around in log files, and short of some familiarity with how this stuff "should" work from experience within a supported FC SAN configuration. This is one of the areas where unsupported gear becomes particularly problematic, too, as there are no OS-specific manuals for the products available for reference, too.
As for general I/O device compatibility, VMS pushes a SAN controller. Hard. This has uncovered bugs within the VMS I/O stack, and has also uncovered bugs in various SAN controllers, and these have variously involved SAN controller firmware upgrades.
I'd look to acquire or to swap for one of the (supported) MSA widgets.
Given you'll not likely be dissuaded from your quest, you'll want to dig around for how to enable and use some of the WWID-mapping stuff on other non-supported FC SAN controllers; how to get the devices visible on an arbitrary SAN controller, and how to map the units to the devices. This can be using mapping features in the particualr SAN controller, or using the SYS$SYSTEM:SYS$DEVICES.DAT mapping. Here is an IBM FC SAN write-up on configuring for OpenVMS, and there are other similar discussions around.
Get the manuals for the devices that you have, and start digging.
The FC SAN configuration mechanisms remind me of another of my other favorite reference for problematic user interface designs, EFI. Both could be vastly better.
