- What's new - Enhancements and List of Fixes
- Support for Kerberos authentication
- Upgrade AngularJS to fix security issues
- Show detailed error message in log for index failure
- Collect host closure infomation into lsf_hostmetrics index
List of Fixes
Fix ID |
Description |
P103852
|
Stale file handle error found in lsfeventsloaderlsf loader log file |
P103859
|
Extremely long resReq causes "id is too long"
|
P103828
|
lsfbeat cannot handle energy data for machines that have 2 or more sensors
|
P103766
|
lsfbeat log reports "ERR An error occured while executing command: exit status 1"
|
P103767 |
The Explorer node installation script gets an empty value for EXPLORER_NODE_TOP
|
P103675
|
Date filter issue with Chart Editor.
|
- System requirements
Refer to Knowledge Center : https://www.ibm.com/support/knowledgecenter/SS6MQM_10.2.0/getting_started/sys_requirements_10.2.0.11.html
- Known issues
Refer to Knowledge Center : https://www.ibm.com/support/knowledgecenter/SS6MQM_10.2.0/release_notes/rel_notes_known_issues.html
- Product notifications
To receive information about product solution and patch updates
automatically, subscribe to product notifications on the My
notifications page http://www.ibm.com/support/mynotifications/ on the
IBM Support website (http://support.ibm.com). You can edit your
subscription settings to choose the types of information you want to
get notification about, for example, security bulletins, fixes,
troubleshooting, and product enhancements or documentation changes.
- Download location
Download from the following location: https://www.ibm.com/support/fixcentral
- Installation and configuration
- In this document,
- COLLECTOR_TOP
describes the top-level IBM Spectrum LSF Explorer Data Collector
installation directory.
- SERVER_TOP
describes the top-level IBM Spectrum LSF Explorer Server installation directory.
- This
pre-installation task is only for user-installed versions of
Elasticsearch 5.x. Skip this step if you are using Elasticsearch 7.x/6.x
For IBM Spectrum LSF Explorer to work with user-installed versions of
Elasticsearch 5.x, you need to configure specific parameters
in the elasticsearch.yml configuration file using the following steps
1. Log on to the Elasticsearch Server.
2. Add the following configuration
parameters in the
elasticsearch.yml file. Depending on your installation, it may be
found at ES_TOP/config/ or in the /etc/ directory. ES_TOP is the top-level directory in
which you installed
Elasticsearch.
script.inline: true
script.stored: true
script.search: true
Note: When adding lines to
the elasticsearch.yml file, ensure the new lines have no blank spaces before them.
Otherwise, Elasticsearch reports errors and fails to start.
3. Restart the Elasticsearch
service
-
Explorer removes bundled Elasticsearch, Logstash and Kibana since 10.2.0.10. That means you should install ELK by yourself.
The supported ELK version is 7.2 or higher (but below 8). The recommended version is 7.2.1.
Elasticsearch, Logstash and Kibana can be downloaded from below links:
https://www.elastic.co/cn/downloads/past-releases/elasticsearch-7-2-1
https://www.elastic.co/cn/downloads/past-releases/logstash-7-2-1
https://www.elastic.co/cn/downloads/past-releases/kibana-7-2-1
Set a proper heap size for Elasticsearch and Logstash before installing Explorer.
Refer to https://www.elastic.co/guide/en/elasticsearch/reference/7.x/heap-size.html for more details.
Note: You can still use the version of Elasticsearch that is bundled
with Explorer FP9. However, that version does not support the https and
authentication feature because it is the OSS version. For information
on how to enable TLS for Elasticsearch HTTP connections, refer to
https://www.ibm.com/support/knowledgecenter/SS6MQM_10.2.0/getting_started/enabling_https_elasticsearch.html
- 6.1 Installation steps for IBM Spectrum LSF Explorer
Server 10.2.0.11
- Log in to the host on which you intend to install IBM Spectrum LSF Explorer Server as root.
- Extract the package.
For example:
tar -zxvf
explorer10.2.0.11_server_linux-x64.tar.gz
- Edit the install.config file to set installation
variables.
Make sure your Elasticsearch is available
Configure ES_HOST and ES_PORT of your Elasticsearch
properly.
Configure ES_AUTHENTICATION_ENABLED and ES_SSL_CERT_PATH if Elasticsearch security feature is enabled.
- Run the ExplorerServerInstaller.sh installation script
and finish the installation:
./ExplorerServerInstaller.sh
-f install.config
Note: For a
silent installation, add the option -silent.
- Set the IBM Spectrum LSF Explorer Server environment:
For csh or tcsh:
source SERVER_TOP/lsfsuite/ext/cshrc.platform
For sh, ksh, or bash: . SERVER_TOP/lsfsuite/ext/profile.platform
- Start the IBM Spectrum LSF Explorer Server.
pmcadmin start
- Check that the IBM Spectrum LSF Explorer Server services
have started
pmcadmin list
- Log in to the IBM Spectrum LSF Explorer Server:
Open a web browser and access the IBM Spectrum LSF Explorer Server by
entering the host name or IP address and port number of the Server.
The default port number is 8080.
For example, if your IBM Spectrum LSF Explorer Server IP address is
198.51.100.0, enter in your web browser as the URL:
http://198.51.100.0:8080
The Login screen for the IBM Spectrum LSF Explorer Console is displayed.
- Use the LSF administrator name and password to log in.
The default
dashboard Cluster Overview is
displayed
- Select Dashboards
to view the out-of-box reports.
- To create a new chart, select Charts and click the New button.
- To create a new dashboard, select Dashboards and click the New button
- Check for errors in the log files:
The log files are located in SERVER_TOP:
cd
SERVER_TOP/lsfsuite/ext/explorer/server/logs
- 6.2 Installation steps for IBM Spectrum LSF Explorer
Data Collector 10.2.0.11
Ensure IBM Spectrum LSF Explorer Server is running. IBM
Spectrum LSF
Explorer Server must be started before IBM Spectrum LSF Explorer Data
Collector services.
Note: If Explorer is installed with LSF 10.1.0.10, ensure Explorer Data Collector is
installed on a host which has been added to LSF_ADDON_HOSTS parameter in lsf.conf.
- Log in to the LSF host on which you intend to install IBM
Spectrum LSF
Explorer Data Collector as the primary LSF administrator.
Note: Log in as
root if you want to update the rc.boot scripts.
- Extract the package.
For example:
tar -zxvf explorer10.2.0.11_node_linux-x64.tar.gz
- Go to the extracted directory and edit the install.config
file.
Configure all required parameters by uncommenting the line for each related parameter.
Configure ES_AUTHENTICATION_ENABLED and ES_SSL_CERT_PATH if the Elasticsearch security feature is enabled.
If you choose to enable the scaled IO statistics feature, set the JAVA_HOME environment variable
and configure the LOGSTASH_TOP, GPFS_HOME and GPFS_DEVICE parameters.
If you choose to enable the energy accounting feature, set the JAVA_HOME environment variable
and configure the LOGSTASH_TOP and IPMI_HOME parameters.
- Run the ExplorerNodeInstaller.sh installation script.
./ExplorerNodeInstaller.sh
-f install.config
Note: For a silent
installation, add the option -silent.
- Set the environment to start the data collectors, where
COLLECTOR_TOP is the
directory in which you installed IBM Spectrum LSF Explorer Data
Collector.
For csh or tcsh:
source
COLLECTOR_TOP/lsfsuite/ext/perf/conf/cshrc.perf
For sh, ksh, or bash:
. COLLECTOR_TOP/lsfsuite/ext/perf/conf/profile.perf
Note: You might
notice an error when you set the environment on the Red Hat
Enterprise Linux 6.x x_64 platform, such as:
-bash: /lib/libc.so.6: No such file or directory
-bash: [: : integer expression expected
Cannot get binary type
To avoid this error, after you set the environment, install the related
files by
running the following command:
yum install ld-linux.so.2
- Optional: Enable data collectors in your cluster
to collect data for the FLEXlm-Managed Licenses Dashboard.
Note: The data
collector for the FLEXlm-Managed Licenses Dashboard is not
supported on Linux for Power System Servers 8 Little Endian.
a. Get the FLEXlm utility files lmutil
and lmgrd from your license
server.
b. Copy the lmgrd and lmutil files from the license server
location to
the directory NODE_TOP/license/7.0/os_type/etc,
where os_type is the
operating system type.
c. Assign execute permissions to the lmgrd
and lmutil files.
d. Edit the FLEXlm license usage data loader configuration file
COLLECTOR_TOP/conf/dataloader/flexlicusage.properties
and change the
ServerList (or FileName) parameter to point to the
FLEXlm license servers.
For more information, see the description in the flexlicusage.properties file.
e. Enable the FLEXlm license usage data loader in your cluster by
editing the file
COLLECTOR_TOP/conf/plc/plc_license_explorer.xml and
setting the attribute
Enable="true" in
the <DataLoader
Name="flexlicusageloader" .../>
element.
<DataLoader
Name="flexlicusageloader" Interval="300" Enable="true" LoadXML="dataloader/flexlicusage.xml”/>
- Start the data collector plc service.
perfadmin start all
- Check that the data loaders are running.
plcclient.sh -s - Check for errors in the data loader log files in the
directory
$PERF_LOGDIR/dataloader
- [optional] For installations of version 10.2.0.6 and above, if the
scaled IO statistics feature or the energy accounting feature is
enabled,
please restart Logstash as root user to make the configuration changes effective.
If Logstash is installed by rpm package, you need to change
/etc/systemd/system/logstash.service to set the user as root and then
start Lostash service by systemctl.
- Upgrade from 10.2.0.10 to 10.2.0.11
Note: You must upgrade to Explorer 10.2.0.10 before upgrading to Explorer 10.2.0.11.
Refer to
https://www.elastic.co/guide/en/elasticsearch/reference/7.2/restart-upgrade.html
if you want to migrate data from the FP-bundled OSS Elasticsearch 7.2.1
to your newly installed Elasticsearch. Back up your data before
proceeding.
Refer to https://www.elastic.co/guide/en/elasticsearch/reference/7.2/modules-snapshots.html for more details.
7.1 Upgrade from 10.2.0.10 to
10.2.0.11 for Explorer Server
1. Set the IBM Spectrum LSF Explorer Server
environment:
For csh or tcsh: source
SERVER_TOP/lsfsuite/ext/cshrc.platform
For sh, ksh, or bash: .
SERVER_TOP/lsfsuite/ext/profile.platform
2. Stop the IBM Spectrum LSF Explorer Server.
pmcadmin stop
3. Install LSF Explorer Server 10.2.0.11 following
steps in section 6.1
4. Set the IBM Spectrum LSF Explorer Server
environment:
For csh or tcsh: source
SERVER_TOP/lsfsuite/ext/cshrc.platform
For sh, ksh, or bash: .
SERVER_TOP/lsfsuite/ext/profile.platform
5. Start the IBM Spectrum LSF Explorer Server.
pmcadmin start
6. [optional] If Explorer is not installed to the default location (/opt/ibm) and
you want to enable https, please open a new session and run below command
pmcadmin https enable --password xxx
7.2 Upgrade from 10.2.0.10 to 10.2.0.11
for Explorer Data Collector
1. Source the environment.
For csh or tcsh:
source
COLLECTOR_TOP/lsfsuite/ext/perf/conf/cshrc.perf
For sh, ksh, or bash:
.
COLLECTOR_TOP/lsfsuite/ext/perf/conf/profile.perf
2. Stop the data loaders.
perfadmin stop all
3. Install LSF Explorer Data Collector 10.2.0.11
following steps in section 6.2.
4. Source the environment.
For csh or tcsh:
source
COLLECTOR_TOP/lsfsuite/ext/perf/conf/cshrc.perf
For sh, ksh, or bash:
.
COLLECTOR_TOP/lsfsuite/ext/perf/conf/profile.perf
5. Start the data loaders.
perfadmin start all
6. [optional] Restart Logstash if either the
scaled IO statistics feature or the energy accounting feature is
enabled.
Note: Logstash must be started as root user.
If Logstash is installed by rpm
package, you need to change /etc/systemd/system/logstash.service to set
the user as root
and then start Lostash service by systemctl.
- Uninstallation
8.1 Uninstall Explorer Server
Run the ExplorerServerUninstall.sh uninstallation
script.
.
SERVER_TOP/lsfsuite/ext/explorer/server/bin/ExplorerServerUninstall.sh
8.2 Uninstall Explorer Data Collector
Run the ExplorerNodeUninstall.sh uninstallation
script
.
COLLECTOR_TOP/lsfsuite/ext/perf/1.2/bin/ExplorerNodeUninstall.sh
- Copyright and trademark information
©Copyright IBM Corporation 2020
U.S. Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM®, the IBM logo and ibm.com® are trademarks of International
Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml
This product includes some components redistributed from third-party
vendors which are provided here for convenience. Licensee may copy and
use these components within the confines of the third-party license as
identified in the Notices file. IBM provides these third-party
components without obligation of support and "AS IS", WITH NO WARRANTY
OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTY OF
TITLE, NON-INFRINGEMENT OR NON-INTERFERENCE AND THE IMPLIED WARRANTIES
AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.