There limitations in respect to distance are the latency:

1. Heartbeats:
   A single VCS cluster uses at least 2 independent links to communicate between nodes and to detect if a node goes down using a Low Latency Protocol (LLT) and large distances mean the latency is too high
    
2. Storage:
   If using shared storage, then latency becomes an issue, but this is more an issue for the application/user using the storage then the cluster.

So for a SINGLE VCS cluster where the 2 nodes are in separate sites, this is called a Campus cluster, and the VCS admin guide says:

You must have a single VCS cluster with at least one node in each of the two

sites, where the sites are separated by a physical distance of no more than 80

kilometers.

So you will need to use the "Global Cluster Option" GCO with replication. 

So you will have 2 nodes in one cluster contected via GCO (using an ICMP link) to the other 2 nodes in a differerent cluster in the different city.  Then you will need to use replication to replicate the storage - the replication can be Veritas Volume Replicator (VVR) which replicates over IP, or one of several other array or database replication products (like SRDF or Oracle Data Guard) that there is a VCS agent for - choose Agent Type of "Replication Agent" at https://sort.symantec.com/agents to see a list of available VCS agents.

Failover detection time for a node going down in your 2 node cluster will be 15 seconds by default (timeout of LLT links) and this failover is usually automatic, but failover detection for a DR situation when you loose a cluster will be a few minutes by default for the timeout of the ICMP GCO links and this falover is usually manually initiated (but can be configured as automatic) as the network links are not usually reliable enough.

Mike