Multiple Clusters on the same subnet

Question

Hi,
We have two separate projects using coherence (3.5.2) in our location.
Unfortunately they will be deployed on the same subnet.
We use ExtencdTCP on the client side to connect to the cluster.
What steps should be taken so that Project1 (P1) is kept separate from P2...
We only have control over P1 or is there something that can be done purely from P1 config that will achieve this aim?
The config for the client is given below, since we can restrict the hostnames and the ports in the tcp-initiator elements, we can easily force the client to connect only to the relevant P1 machines.
+<cache-config xmlns="http://schemas.tangosol.com/cache">+
+<caching-scheme-mapping>+
+<cache-mapping>+
+<cache-name>dist-*</cache-name>+
+<scheme-name>extend-direct</scheme-name>+
+</cache-mapping>+
+</caching-scheme-mapping>+
+<caching-schemes>+
+<remote-cache-scheme>+
+<scheme-name>extend-direct</scheme-name>+
+<service-name>ExtendTcpCacheService</service-name>+
+<initiator-config>+
+<tcp-initiator>+
+<remote-addresses>+
+          <socket-address>+
+<address>P1.1</address>+
+<port>8078</port>+
+</socket-address>+
+               <socket-address>+
+                    <address>P1.2</address>+
+                    <port>8078</port>+
+               </socket-address>+
+               +
+          </remote-addresses>+
+</tcp-initiator>+
+<outgoing-message-handler>+
+               <heartbeat-interval>50s</heartbeat-interval>+
+               <heartbeat-timeout>35s</heartbeat-timeout>+
+               <request-timeout>30s</request-timeout>+
+          </outgoing-message-handler>+
+</initiator-config>+
+</remote-cache-scheme>+
+</caching-schemes>+
+</cache-config>+
On the server(s) there are
a.ExtendTCPService running on each
b.Mulitple cache servers with a distributed scheme running
The cache-config for the server is given below, how can we restrict the hosts that it searches for for clusters to join?
We noticed the configuration elements clusterport etc. that seem to be able to do this also authorized-hosts? Can this be done in the cache-config element or only in the cluster-config element.
+<?xml version="1.0"?>+
+<!--+
+|+
-->
+<!DOCTYPE cache-config SYSTEM "cache-config.dtd">+
+<cache-config>+
+     <logging-config>+
+     <destination>cache-server.log</destination>+
+     <destination>stderr</destination>+
+     </logging-config>+
+<caching-scheme-mapping>+
+<cache-mapping>+
+<cache-name>dist-*</cache-name>+
+<scheme-name>dist-default</scheme-name>+
+</cache-mapping>+
+<cache-mapping>+
+<cache-name>repl-*</cache-name>+
+<scheme-name>repl-default</scheme-name>+
+</cache-mapping>+
+</caching-scheme-mapping>+
+<caching-schemes>+
+<distributed-scheme>+
+<scheme-name>dist-default</scheme-name>+
+<serializer>+
+          <class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>+
+          <init-params>+
+          <init-param>+
+               <param-type>string</param-type>+
+               <param-value>custom-types-pof-config.xml</param-value>+
+          </init-param>+
+          </init-params>+
+     </serializer>+
+<backing-map-scheme>+
+<local-scheme/>+
+</backing-map-scheme>+
+<autostart>true</autostart>+
+</distributed-scheme>+
+<replicated-scheme>+
+<scheme-name>repl-default</scheme-name>+
+<backing-map-scheme>+
+<local-scheme/>+
+</backing-map-scheme>+
+<autostart>true</autostart>+
+</replicated-scheme>+
+<proxy-scheme>+
+<service-name>ExtendTcpProxyService</service-name>+
+<thread-count>5</thread-count>+
+<acceptor-config>+
+<tcp-acceptor>+
+<local-address>+
+<address>localhost</address>+
+<port>8078</port>+
+</local-address>+
+</tcp-acceptor>+
+<serializer>+
+<class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>+
+<init-params>+
+<init-param>+
+<param-type>string</param-type>+
+<param-value>custom-types-pof-config.xml</param-value>+
+</init-param>+
+</init-params>+
+</serializer>+
+</acceptor-config>+
+<autostart>true</autostart>+
+</proxy-scheme>+
+</caching-schemes>+
+</cache-config>+
Thanks for your response,
Vipb

Answer 1

Was able to override the multicast address thru the command line and have just P1 work with
the following overrides.
-Dtangosol.coherence.clusteraddress=P1Cluster -Dtangosol.coherence.clusterport=11111
where p1Cluster=224.2.1.99 (say)
Thanks,
Vipin