By default, if no cluster name is specified, LSF utilities such as lsload return information about the local cluster.
If you configure a remote cluster to be equivalent to the local cluster, LSF displays information about the remote cluster as well. For example, lsload with no options lists hosts in the local cluster and hosts in the equivalent remote clusters.
The following commands automatically display information about hosts in a remote cluster if equivalency is configured:
Expect performance in a cluster to decrease as the number of equivalent clusters increases, because you must wait while LSF retrieves information from each remote cluster in turn. Defining all clusters in a large MultiCluster system as equivalent can cause a performance bottleneck as the master LIM polls all clusters synchronously.
To make resources in remote clusters as transparent as possible to the user, configure a remote cluster to be equivalent to the local cluster. The users see information about the local and equivalent clusters without having to supply a cluster name to the command.
Hosts in equivalent clusters are all identified by the keyword remoteHost instead of the actual host name. For example, bjobs -p -l will show remoteHost@cluster_name instead of host_name@cluster_name.