lshosts

displays hosts and their static resource information

Synopsis

lshosts [-a] [-cname] [-w | -l] [-R "res_req"] [-T] [host_name | cluster_name] ...

lshosts [-a] [-cname] -s [resource_name ...]

lshosts [-h | -V]

Description

Displays static resource information about hosts.

By default, returns the following information: host name, host type, host model, CPU factor, number of CPUs, total memory, total swap space, whether or not the host is a server host, and static resources. Exclusive resources are prefixed with an exclamation mark (!). Displays information about all hosts in the cluster.

In MultiCluster job forwarding model, the default behavior is to return the following information: host name, host type, host model, CPU factor, number of CPUs, total memory, total swap space, whether or not the host is a server host, and static resources. Displays information about all hosts in the local cluster and for all hosts in equivalent remote clusters that the local cluster sees. See lsf.cluster for more information.

In MultiCluster resource leasing model, returns information about hosts in the local cluster.

The -s option displays information about the static resources (shared or host-based) and their associated hosts.

Options

-a

Dynamic Cluster only. Shows information about all hosts, including Dynamic Cluster virtual machine hosts configured with the jobvm resource. Default output includes only standard LSF hosts and Dynamic Cluster hosts configured with the dchost resource.

-cname

In LSF Advanced Edition, includes the cluster name for execution cluster hosts and host groups in output.

-l

Displays host information in a long multi-line format. In addition to the default fields, displays additional information, including maximum /tmp space, the number of local disks, the execution priority for remote jobs, load thresholds, and run windows.

-w

Displays host information in wide format. Fields are displayed without truncation.

-R "res_req"

Only displays information about the hosts that satisfy the resource requirement expression. For more information about resource requirements, see Administering IBM Platform LSF. The size of the resource requirement string is limited to 512 bytes. LSF supports ordering of resource requirements on all load indices, including external load indices, either static or dynamic.

In MultiCluster, only displays information about the hosts in the local cluster that satisfy the resource requirement expression.

host_name ... | cluster_name ...

Only displays information about the specified hosts. Do not use quotes when specifying multiple hosts.

For MultiCluster, displays information about hosts in the specified clusters. The names of the hosts belonging to the cluster are displayed instead of the name of the cluster. Do not use quotes when specifying multiple clusters.

-s [resource_name ...]

Displays information about the specified resources. The resources must be static resources (shared or host-based). If no resource is specified, then displays information about all resources. Returns the following information: the resource names, the values of the resources, and the resource locations.

-h

Prints command usage to stderr and exits.

-T

Displays host topology information for each host or cluster.

-V

Prints the LSF release version to stderr and exits.

Output: Host-Based Default

Displays the following fields:

HOST_NAME

The name of the host. This display field is truncated.

type

The host type. This display field is truncated.

With MultiCluster, if the host type of a remote cluster’s host is not defined in the local cluster, the keyword unknown is displayed.

model

The host model. This display field is truncated.

With MultiCluster, if the host model of a remote cluster’s host is not defined in the local cluster, the keyword unknown is displayed.

cpuf

The relative CPU performance factor. The CPU factor is used to scale the CPU load value so that differences in CPU speeds are considered. The faster the CPU, the larger the CPU factor.

The CPU factor of a host with an unknown host type is 1.0.

ncpus

The number of processors on this host.

If LSF_ENABLE_DUALCORE=Y in lsf.conf for multi-core CPU hosts, displays the number of cores instead of physical CPUs.

If EGO is enabled in the LSF cluster and EGO_DEFINE_NCPUS is specified in lsf.conf or ego.conf, the appropriate value for ncpus is displayed, depending on the value of EGO_DEFINE_NCPUS:

EGO_DEFINE_NCPUS=procs—ncpus=number of processors
EGO_DEFINE_NCPUS=cores—ncpus=number of processors x number of cores per processor
EGO_DEFINE_NCPUS=threads—ncpus=number of processors x number of cores per processor x number of threads per core

EGO_DEFINE_NCPUS=cores is the same as setting LSF_ENABLE_DUALCORE=Y.

nprocs

The number of physical processors per CPU configured on a host.

ncores

The number of cores per processor configured on a host.

nthreads

The number of threads per core configured on a host.

maxmem

The maximum amount of physical memory available for user processes.

By default, the amount is displayed in KB. The amount may appear in MB depending on the actual system memory. Use LSF_UNIT_FOR_LIMITS in lsf.conf to specify a larger unit for the limit (GB, TB, PB, or EB).

maxswp

The total available swap space.

By default, the amount is displayed in KB. The amount may appear in MB depending on the actual system swap space. Use LSF_UNIT_FOR_LIMITS in lsf.conf to specify a larger unit for the limit (GB, TB, PB, or EB).

For a Solaris operating system, the swap space is virtual, a layer between anonymous memory pages and the physical storage (or disk-backed swap space). A Solaris system's virtual swap space is equal to the sum of all its physical (disk-backed) swap space plus a portion of the currently available physical memory, which could be a dynamic value.

server

Indicates whether the host is a server or client host. Yes is displayed for LSF servers. No is displayed for LSF clients. Dyn is displayed for dynamic hosts.

RESOURCES

The Boolean resources defined for this host, denoted by resource names, and the values of external numeric and string static resources. See lsf.cluster(5), and lsf.shared(5) on how to configure external static resources.

Output: Host Based -l Option

In addition to the above fields, the -l option also displays the following:

ndisks: The number of local disk drives directly attached to the host.
maxtmp: The maximum /tmp space in MB configured on a host.
rexpri: UNIX only. The execution priority of remote jobs run by the RES. rexpri is a number between -20 and 20, with -20 representing the highest priority and 20 the lowest. The default rexpri is 0, which corresponds to the default scheduling priority of 0 on BSD-based UNIX systems and 20 on System V-based systems.
nprocs: The number of physical processors per CPU configured on a host.
ncores: The number of cores per processor configured on a host.
nthreads: The number of threads per core configured on a host.
RUN_WINDOWS: The time windows during which LIM considers the host as available to execute remote jobs. These run windows have the same function for LSF hosts as dispatch windows have for LSF hosts.
LOAD_THRESHOLDS: The thresholds for scheduling interactive jobs. If a load index exceeds the load threshold (or falls below the load threshold, for decreasing load indices), the host status is changed to busy. If the threshold is displayed as a dash -, the value of that load index does not affect the host status.

Output: Resource Based -s Option

Displays the static resources (shared or host-based). Each line gives the value and the associated hosts for the static resource. See lsf.shared, and lsf.cluster on how to configure static shared resources.

The following fields are displayed:

RESOURCE: The name of the resource.
VALUE: The value of the static resource.
LOCATION: The hosts that are associated with the static resource.

Output: Topology-based -T option

Displays host topology information for each host or cluster. Topology is display by processor unit level: NUMA node, if present, socket, core, and thread. A socket is a collection of cores with a direct pipe to memory. Each socket contains 1 or more cores. This does not necessarily refer to a physical socket, but rather to the memory architecture of the machine. A core is a single entity capable of performing computations. On hosts with hyperthreading enabled, a core can contain one or more threads.

The following fields are displayed:

Host[memory] host_name

Maximum memory available on the host followed by the host name. If memory availability cannot be determined, a dash (-) is displayed for the host.

For hosts that do not support affinity scheduling, a dash (-) is displayed for host memory and no host topology is displayed.

NUMA[numa_node: max_mem]

Maximum NUMA node memory. It is possible for requested memory for the NUMA node to be greater than the maximum available memory displayed.

If no NUMA nodes are present, then the NUMA layer in the output is not shown. Other relevant items such as host, socket, core and thread are still shown.

If the host is not available, only the host name is displayed. A dash (-) is shown where available host memory would normally be displayed.

lshosts -T differs from the bhosts -aff output:

Socket and core IDs are not displayed for each NUMA node.
The requested memory of a NUMA node is not displayed
lshosts -T displays all enabled CPUs on a host, not just those defined in the CPU list in lsb.hosts

In the following example, full topology (NUMA, socket, and core) information is shown for hostA. Hosts hostB and hostC are either not NUMA hosts or they are not available:

lshosts -T
Host[15.7G] hostA
    NUMA[0: 15.7G]
        Socket
            core(0)
        Socket
            core(1)
        Socket
            core(2)
        Socket
            core(3)
        Socket
            core(4)
        Socket
            core(5)
        Socket
            core(6)
        Socket
            core(7)

Host[-] hostB

Host[-] hostC

When LSF cannot detect processor unit topology, lshosts -T displays processor units to the closest level. For example:

lshosts -T
     Host[1009M] hostA 
            Socket (0 1)

On hostA there are two processor units: 0 and 1. LSF cannot detect core information, so the processor unit is attached to the socket level.

Hardware topology information is not shown for client hosts and hosts in a mixed cluster or MultiCluster environment running a version of LSF that is older than 9.1.

Files

Reads lsf.cluster.cluster_name.