bclusters

Displays information about IBM® Spectrum LSF multicluster capability

Synopsis

bclusters [-app] [-w]

bclusters [-h | -V]

Description

For the job forwarding model, displays a list of LSF multicluster capability queues together with their relationship with queues in remote clusters.

For the resource leasing model, displays remote resource provider and consumer information, resource flow information, and connection status between the local and remote cluster.

Options

-app: Displays available application profiles in remote clusters.
-w: Wide format. Displays the information in a wide format.
-h: Prints command usage to stderr and exits.
-V: Prints LSF release version to stderr and exits.

Output: Job forwarding information

Displays a list of LSF multicluster capability queues together with their relationship with queues in remote clusters.

Information that is related to the job forwarding model is displayed under the heading Job Forwarding Information.

LOCAL_QUEUE

Name of a local LSF multicluster capability send-jobs or receive-jobs queue.

JOB_FLOW

Indicates direction of job flow.

send: The local queue is a LSF multicluster capability send-jobs queue (SNDJOBS_TO is defined in the local queue).
recv: The local queue is a LSF multicluster capability receive-jobs queue (RCVJOBS_FROM is defined in the local queue).

REMOTE

For send-jobs queues, shows the name of the receive-jobs queue in a remote cluster.

For receive-jobs queues, always a dash (-).

CLUSTER

For send-jobs queues, shows the name of the remote cluster that contains the receive-jobs queue.

For receive-jobs queues, shows the name of the remote cluster that can send jobs to the local queue.

STATUS

Indicates the connection status between the local queue and remote queue.

ok: The two clusters can exchange information and the system is properly configured.
disc: Communication between the two clusters is not established. The disc status might occur because no jobs are waiting to be dispatched, or because the remote management host cannot be located.
reject: The remote queue rejects jobs from the send-jobs queue. The local queue and remote queue are connected and the clusters communicate, but the queue-level configuration is not correct. For example, the send-jobs queue in the submission cluster points to a receive-jobs queue that does not exist in the remote cluster.
If the job is rejected, it returns to the submission cluster.

Output: Resource lease information

Displays remote resource provider and consumer information, resource flow information, and connection status between the local and remote cluster.

Information that is related to the resource leasing model is displayed under the heading Resource Lease Information.

REMOTE_CLUSTER

For borrowed resources, name of the remote cluster that is the provider.

For exported resources, name of the remote cluster that is the consumer.

RESOURCE_FLOW

Indicates direction of resource flow.

IMPORT: Local cluster is the consumer and borrows resources from the remote cluster (HOSTS parameter in one or more local queue definitions includes remote resources).
EXPORT: Local cluster is the provider and exports resources to the remote cluster.

STATUS

Indicates the connection status between the local and remote cluster.

ok: LSF multicluster capability jobs can run.
disc: No communication between the two clusters. The disc status might be a temporary situation or might indicate a LSF multicluster capability configuration error.
conn: The two clusters communicate, but the lease is not established. The conn status is typically a temporary situation, lasting only until jobs are submitted.

Output: Remote cluster application information

The bcluster -app command displays information that is related to application profile configuration under the heading Remote Cluster Application Information. Application profile information is only displayed for the job forwarding model. The bclusters command does not show local cluster application profile information.

REMOTE_CLUSTER: The name of the remote cluster.
APP_NAME: The name of the application profile available in the remote cluster.
DESCRIPTION: The description of the application profile.

Files

Reads the lsb.queues and lsb.applications files.