I have now set up a separate cluster between different development environments.  For the sake of discussion, let's call one environment devA and the other devB.  I will have 2 machines in each of the 2 environments.  It seems I have the multicast set up to allow the separation I thought I wanted.  However, now I have discovered my next item of interest.  I have 2 JVMs on each of the machines (devA has machine1 with 2 JVMs and machine 2 with 2 JVMs....same for devB).  Now, just focusing on one environment, devA, I would like the JVMa on machine1 and JVMa on machine 2 to share the same replicated named cache (sharedCache_a).  And, I would like JVMb on machine1 and JVMb on machine2 to share their same replicated named cache (sharedCache_b).  Also, I am setting the StateRetrieval fetchInMemoryState=true for both named caches.  I was seeing state being replicated on startup when I was running only the JVMa processes on both machines.  Also, if only starting JVMb processes on both machines I was also seeing state being replicated on startup.  However, now that I am running JVMa and JVMb on both machines I am seeing state replicated between JVMa processes, but I am not seeing the state replicated between JVMb processes.  One thing I noticed, after digging through detail logs, is that the coordinator of the caches seems to be associated with JVMa on machine1.  Since it is not connected to sharedCache_b it does not have state to replicate on startup to the JVMb processes.  Interesting that after caches are started, replication does work as expected, but the "catch-up" of state on startup is not working as described above.

Do I need to further separate the cluster to only include like-JVMs (a or b i this example)?  Ultimately what I thought I would get is cache coordinators from each cache name.  Seems it is per cluster.

In the way my application considers a cluster, the answer is no.  A cluster in this case would be made up of machine1_JVMa, machine1_JVMb, machine2_JVMa, and machine2_JVMb.

Or, another way to put it, all JVMs on machine1 and machine2 make up the cluster.  And, in case it is helpful, I mentioned the cache mode is replication and the scenario I am attempting to use this is for high availability.

Having some coffee in the system now....re-read your response and realize I still did not answer your question.  Sorry.  In development I would have around 20 different clusters with a 2 machines in each cluster and a total of 10 JVMs in each cluster.  In production, the number of clusters would be greater, but the number of JVMs per cluster and the number of machines per cluster would be the same.