Quote Originally Posted by Robotbeat
Well, if you add the FC volume in question to a group besides the "Default" one in "Configuration"->"FC target manager", then you can make sure that only the WWN aliases that you select are able to access the FC volumes in that group.


We just installed a dss at a customer who is going to use it as a FC box. They really like the feature to be able to bind volumes to WWN Aliases so they don't have to worry about corruption from concurrent access (this is a feature they didn't have in their old FC box).
As I had tried to mention in my original messages, this is not sufficient: If we run a VM from more than one server, then both servers need access to the FC resource.

We already have stripped down access to single VMs (via virtual WWNs per NPIV access, plus according groups in the SAN server) - but when either the VM is started multiple times (should not happen due to Stonith) or accidentially a configuration is copied without changing the NPIV address, then you run into trouble.

With regards,

Jens