With QLE2462s at the initiators, too - that was our setup until a few days ago.Originally Posted by linux-storage
To make it short:
The DSS takes the initiator's WWPN to decide to which FC group to connect.
--- quote from DSS docs ---
The Default group is a public group. If a WWN belongs to a group other than public, then this WWN will only have access to its assigned group /- it will not be admitted to the public group.
--- end of quote ---
So if a (initiator's) WWPN is assigned to a DSS's FC group, then it will see the LUNs defined in that group.
If the WWPN is not a member of any group, it will see the LUNs of the "default" group.
This is nothing you do at the initator: Think of your FC adapter as a SCSI adapter - and you plug in devices at the DSS side. The initiator gets to see what you connect at the DSS. (see above for "groups" management.)Originally Posted by linux-storage
And as for any good SCSI adapter it will query the devices connected at boot up, and a modern Linux will automagically detect hot-plugged devices as well.
If you want one disk per initiator only, then use different groups at the DSS side. If you need to switch dynamically between the initiators (ie for roaming Xen VMs), then either live with the disks connected to both initiators simultaneously (and make sure only one server has write access to a disk at a time) or use NPIV - which only works with a FC switch in between atm.
Now that's a question I'd love to have an answer for, too... I've never seen the tool at the DSS in the first place, probably because I never played with the DSS console much. I've been using the FC adapter BIOS for basic configuration, that's it. I'd love to see a SANsurfer remote client on the DSS, so I can remotely connect to the adapters with SANsurfer GUI.Originally Posted by linux-storage
With regards,
Jens