License Server collects license feature information from physical servers and merges this data together into a service domain. After the merging, the individual license server information is retained, and you can view this information together with the physical server information.
Use the blstat command to display dynamic system status, and to display information about the actual license distribution and use for each project.
The licenses in use have been checked out from FLEXnet by your projects. Free licenses and licences reserved by a project have not yet been checked out from FLEXnet.
The total number of licenses could change as licenses expire, or are added. As non-LSF users check out licenses, the OTHERS count in blstat should increase and the TOTAL_FREE count will decrease. The number of licenses for each project changes whenever LSF redistributes license tokens among competing projects.
To view the license server associated with the license features, use blstat -S. This displays the license servers used by each service domain allocated to the license features.
The license server information for each license feature is stored in the LS_LICENSE_SERVER_feature environment variable.
blstat -SFEATURE: feature1SERVICE_DOMAIN: domain1SERVERS INUSE FREEserver1 1 0server2 0 1TOTAL 1 1SERVICE_DOMAIN: domain2SERVERS INUSE FREEserver3 1 0TOTAL 1 0
This shows that the license feature feature1 is assigned to server1 and server2 in the domain1 service domain and server3 in the domain2 service domain. A job uses the feature1 license feature when the job is submitted with "rusage[feature1=1]" as the rusage string.
Use the -o option of blinfo and blstat to sort license feature information alphabetically, by total licenses, or by available licenses.
Use -o blstat alone or with options -Lp, -t, -D, -G, -s, -S. The values of "total licenses" and "licenses available" are calculated differently when blstat -o is used with different options:
Options -Lp, -t, -D, -G: Total licenses means the sum of licenses that are allocated to LSF workload from all the service domains configured to supply licenses to the feature. Licenses borrowed by non-LSF workload are subtracted from this sum.
Options-s, -S: All the licenses (supplied by the license vendor daemon) from all the service domains configured to supply licenses to that feature.
Use -o with blinfo alone or with options -a and -t. You can only sort alphabetically (-o alpha) or by total licenses (-o total), because blinfo does not display information about available licenses. The command blinfo -o is not supported in combination with -Lp, -p, -D, -G.
The value of total licenses is calculated using the number of licenses LSF workload deserves from all service domains that supply licenses to the feature, regardless of whether non-LSF workload has borrowed licenses from LSF workload.
FEATURE: p1_5
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 6 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
B 50.0 % 0 0 3 n
p1 25.0 % 0 0 1 n
p2 25.0 % 0 0 2 n
FEATURE: p1_12
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 7 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
default 33.3 % 0 0 3 n
p1 33.3 % 0 0 2 n
p2 33.3 % 0 0 2 n
SERVICE_DOMAIN: LanServer1
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 10 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
p1 50.0 % 0 0 5 n
p2 50.0 % 0 0 5 n
FEATURE: myjob10
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 9 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
p4 50.0 % 0 0 5 n
p3 25.0 % 0 0 2 n
p1 12.5 % 0 0 1 n
p2 12.5 % 0 0 1 n
Sorting with -o total is based on the total number of licenses. In the following example, the total licenses for p1_12, myjob10, p1_5 are 17(7+10), 9, and 6. p1_12 which is the feature with largest number of "total licenses" comes first.
The the total licenses value for p1_5 in this example is 6 not 10 (6+4), because the '4' in the OTHERS field shows that non-LSF workload has borrowed 4 licenses from the LSF allocation.
FEATURE: p1_12
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 7 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
default 33.3 % 0 0 3 n
p1 33.3 % 0 0 2 n
p2 33.3 % 0 0 2 n
SERVICE_DOMAIN: LanServer1
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 10 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
p1 50.0 % 0 0 5 n
p2 50.0 % 0 0 5 n
FEATURE: myjob10
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 9 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
p4 50.0 % 0 0 5 n
p3 25.0 % 0 0 2 n
p1 12.5 % 0 0 1 n
p2 12.5 % 0 0 1 n
FEATURE: p1_5
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 6 OTHERS: 4
PROJECT SHARE INUSE RESERVE FREE DEMAND
B 50.0 % 0 0 3 n
p1 25.0 % 0 0 1 n
p2 25.0 % 0 0 2 n
The following example specifies service domains using the -D option. The values of total licenses for myjob10, p1_12, p1_5 are 9, 7, 6, so myjob10 is listed first.
FEATURE: myjob10
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 9 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
p4 50.0 % 0 0 5 n
p3 25.0 % 0 0 2 n
p1 12.5 % 0 0 1 n
p2 12.5 % 0 0 1 n
FEATURE: p1_12
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 7 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
default 33.3 % 0 0 3 n
p1 33.3 % 0 0 2 n
p2 33.3 % 0 0 2 n
FEATURE: p1_5
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 6 OTHERS: 4
PROJECT SHARE INUSE RESERVE FREE DEMAND
B 50.0 % 0 0 3 n
p1 25.0 % 0 0 1 n
p2 25.0 % 0 0 2 n
In the following example, the number of licenses available for p1_5, p1_12 and myjob10 are 6, 5(0+5),4. p1_5 is the feature with largest number of available licenses, so it is listed first.
FEATURE: p1_5
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 0 TOTAL_RESERVE: 0 TOTAL_FREE: 6 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
B 50.0 % 0 0 3 n
p1 25.0 % 0 0 1 n
p2 25.0 % 0 0 2 n
FEATURE: p1_12
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 7 TOTAL_RESERVE: 0 TOTAL_FREE: 0 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
default 33.3 % 0 0 0 n
p1 33.3 % 7 0 0 n
p2 33.3 % 0 0 0 n
SERVICE_DOMAIN: LanServer1
TOTAL_INUSE: 5 TOTAL_RESERVE: 0 TOTAL_FREE: 5 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
p1 50.0 % 5 0 0 n
p2 50.0 % 0 0 5 n
FEATURE: myjob10
SERVICE_DOMAIN: LanServer
TOTAL_INUSE: 5 TOTAL_RESERVE: 0 TOTAL_FREE: 4 OTHERS: 0
PROJECT SHARE INUSE RESERVE FREE DEMAND
p4 50.0 % 0 0 4 n
p3 25.0 % 0 0 0 n
p1 12.5 % 5 0 0 n
p2 12.5 % 0 0 0 n
blinfo shows the following feature configuration and workload distribution:
FEATURE SERVICE_DOMAIN TOTAL DISTRIBUTION
p1_5 LanServer 6 [B, 50.0%] [p1, 25.0%] [p2, 25.0% / 1]
p1_12 LanServer 7 [default, 33.3%] [p1, 33.3%] [p2, 33.3%]
p1_12 LanServer1 10 [p1, 50.0% / 1] [p2, 50.0% / 6]
myjob10 LanServer 9 [B, 50.0%] [p1, 25.0%] [p2, 25.0% / 1]
In the following example, the value for the TOTAL column is always the number of licenses the feature should get from the service domain, no matter if some of the licenses have been borrowed by non-LSF workload.
FEATURE SERVICE_DOMAIN TOTAL DISTRIBUTION
p1_12 LanServer 7 [default, 33.3%] [p1, 33.3%] [p2, 33.3%]
p1_12 LanServer1 10 [p1, 50.0% / 1] [p2, 50.0% / 6]
myjob10 LanServer 9 [B, 50.0%] [p1, 25.0%] [p2, 25.0% / 1]
p1_5 LanServer 6 [B, 50.0%] [p1, 25.0%] [p2, 25.0% / 1]
The blinfo options '-A' and '-C' do not supply information about "total licenses" and "licenses available", so only '-o alpha' is supported with blinfo -A and -C. -o "total" is ignored with '-A' and '-C' and the output is the same as using -o "alpha".