Direct-connect (SAS) and iSCSI simultaneously?

When you create a thin clone you can have it be a separate environment for testing changes without impacting the source, promoting it makes it available to the normal environment. You are not supposed to mix connection types. https://dell.to/3xFr6Gj Page 19

Thanks for the reply, and the link. The guide you linked to speaks of mixed connection types on the same host, but I am asking about using one connection type (SAS) for one set of hosts and another connection type (iSCSI) for another set of hosts.
The guide is also speaking of FC and iSCSI together, which is not the scenario I'm thinking of. I need to know if you can use SAS (direct-connect) and iSCSI together.

No, I don't see any way to allow multiple sets of hosts one with SAS and one with iSCSI. 

Why is that? If the Compellent has both a SAS card and an iSCSI/Ethernet card, why can't you have hosts connecting to it each using a different interface type?

Every SCv3020 or SC5020 can be bought with a iSCSI Mezz and the PCIe SAS Card.  But i remember about a "*" in the old marketing/products slides about iSCSI+SAS.

We once re-configure a SCv3020 from the use of SAS to iSCSI and later some trouble starts.  Dell Support than says that this isnt a combination which see them often.  We have to remove the SAS Domains than. It was not 100% clear if the current problems are related to SAS.

To beclear .... we move all Volumes from SAS to iSCSI but leave the FaultDomain for SAS configured.

In the old days we see it more than once that a System use a primary Frontend path with Fibre Channel and a secondary path with iSCSi to the same Windows Server.

Regards,
Joerg

Thanks. Does that mean a Compellent won't be able to run SAS and iSCSI simultaneously to different hosts? What do you mean by "remove the SAS domains"? Is that something you do on the Compellent?