About cross-cluster user account mapping

For MultiCluster environments that have different user accounts assigned to different hosts, cross-cluster user account mapping allows you to submit a job from a local host and run the job as a different user on a remote host.

Figure 1. Default behavior (feature not enabled)

Figure 2. With cross-cluster user account mapping enabled

Scope

Applicability	Details
Operating system	UNIX hosts Windows hosts A mix of UNIX and Windows hosts within one or more clusters
Not required for	Multiple clusters with a uniform user name space
Dependencies	UNIX and Windows user accounts must be valid on all hosts in the cluster and must have the correct permissions to successfully run jobs. If users at your site have different user names on UNIX and Windows hosts within a single cluster, you must configure between-host user account mapping at the user level in .lsfhosts.
Limitations	You cannot configure this feature at both the system-level and the user-level; LSF ignores system-level mapping if user-level mapping is also defined in .lsfhosts. If one or more clusters include both UNIX and Windows hosts, you must also configure UNIX/Windows user account mapping. If one or more clusters have different user accounts assigned to different hosts, you must also configure between-host user account mapping for those clusters, and then configure cross-cluster user account mapping at the system level only.