Verifying RSCT installation on Linux nodes
Beginning with RSCT version 3.2.0.0, RSCT is available as only 64-bit for Linux nodes. If a 32-bit distribution of Linux is used, RSCT version 3.1.5.0 is the last available version that can be used.
The Linux® implementation of RSCT is shipped with a number of products that use this technology. The RSCT packages must be installed by following the specific exploiter's installation procedure. Table 1 lists the packages that are required on the target node before installing RSCT.
RSCT Linux installation
rpm -Uv src*rpm
rpm -Uv rsct.core*rpm rsct.basic*rpm
#In the above example rsct.core*, rsct.basic pkgs are also being installed
RSCT can be installed separately but all the packages have to be installed. For
example if the node has src
, rsct.core.utils
,
rsct.core
, and rsct.basic
. If you install only
rsct.basic
package it will fail and RSCT will be in the
'unconfigured'
state and the functionality associated with the package will not
work. All other packages have to be installed to make the RSCT package to be working.
Src
rsct.core.utils
rsct.core
rsct.basic
Library | Package |
---|---|
Standard C Library | glibc |
Standard C++ Library | libstdc++ |
Code set Conversion Library on SUSE Linux Enterprise Server | glibc, glibc-locale, glibc-locale-32bit, or glibc-locale-64bit |
Ubuntu 16.04 (or newer version) install using Launchpad
ppa: ibmpackages/rsct
- Open a terminal and enter the below command to add the PPA
repository
(ibmpackages/rsct)
as apt source and also to fetch the PPA's key:#sudo add-apt-repository ppa:ibmpackages/rsct
- To pull down the latest list of software from archive,
enter:
#sudo apt-get update
- Now you're ready to start installing software from the
PPA!
However, If you want to install packages separately ,use the following sequence to install file-sets:#sudo apt-get install src rsct.core.utils rsct.core
#sudo apt-get install src #sudo apt-get install rsct.core.utils #sudo apt-get install rsct.core
RSCT, Linux, and code set conversion
Much of RSCT, particularly the resource monitoring and control (RMC) subsystem, converts strings between the encoding of the client's locale and an encoding of Unicode. Unicode is used internally within the RMC subsystem to store and process strings.
For code set conversion, RMC relies on support that is provided by the underlying operating system. That support must be installed for RMC to function correctly.
2610-657 System does not support codeset conversion from source_codeset to target_codeset.
This system does not support codeset conversion that RMC needs. Installation will stop.
Please refer to the RSCT Administration Guide for additional RPMs that are required.
On Linux, the RPMs that support code set conversion vary depending on distribution, release, and machine type.
The RPMs that provide support for code set conversion for various configurations follow.
glibc-locale
Verifying RSCT installation on Linux (non-Ubuntu)
rpm -qa | grep -E -e "rsct|src"
src-3.2.n.n-14169
rsct.core.utils-3.2.n.n-14169
rsct.core-3.2.n.n-14169
rsct.basic-3.2.n.n-14169
If you installed RSCT components, ensure that they are at a version
that applies to this information. In the RPM package names, platform is i386
, ppc
, ppc64
, ppc64le
, s390
, or x86_64
.
This package... | Contains... |
---|---|
rsct.basic-3.2.n.n-build-number.platform.rpm |
|
rsct.core-3.2.n.n-version.platform.rpm | RSCT core components that includes:
|
rsct.core.utils-3.2.n.n-version.platform.rpm | Miscellaneous utilities |
rsct.opt.storagerm-3.2.n.n-version.platform.rpm | The storage resource manager |
src-3.2.n.n-version.platform.rpm | The system resource controller (SRC) |
rsct.opt.stackdump-3.2.n.n-version.platform.rpm | The stack dump function |
If the rpm command output reveals that the required RSCT RPM packages are not installed, you can install them from the RSCT exploiter's installation media. See the RSCT exploiter's documentation for installation instructions.
You can install RSCT by itself but, because of the dependencies
among the RPM packages, the packages must be installed in a specific
sequence. In the following instructions, replace platform with i386
, ppc
, s390
, ppc64
, ppc64le
, or x86_64
, as
appropriate for your system platform.
- Install or upgrade the SRC by entering the following command:
rpm -Uv src-3.2.n.n-version.platform.rpm
- Install or upgrade the RSCT packages in one line by entering the following
command:
rpm -Uvi rsct.core.utils-3.2.n.n-version.platform.rpm \ rsct.core-3.2.n.n-version.platform.rpm \ rsct.basic-3.2.n.n-version.platform.rpm
- Install or upgrade the RSCT utilities by entering the following command:
rpm -i rsct.core.utils-3.2.n.n-version.platform.rpm
- Install the RSCT core components by entering the following command:
rpm -i rsct.core-3.2.n.-version.platform.rpmn
- Install the RSCT basic components by entering the following command:
rpm -i rsct.basic-3.2.n.n-version.platform.rpm
- Optionally, install the RSCT storage resource manager component by entering the following
command:Note: If you are installing the storage resource manager on a node in a peer domain, take the node offline before you install the storage resource manager component.
rpm -i rsct.opt.storagerm-3.2.n.n-version.platform.rpm
- Optionally, install the RSCT stack dump function by entering the following
command:
rpm -i rsct.opt.stackdump-3.2.n.n-version.platform.rpm
If the rpm command output reveals that the previous versions of RSCT RPM packages are installed, you can upgrade RSCT by using the rpm command. Before upgrading RSCT, be sure to review the information in Migration considerations.
- If your system does not have the rsct64bit package installed, you can use the following
command to upgrade RSCT:
rpm -Fvh src-3.2.n.n-version.platform.rpm rsct.core.utils-3.2.n.n-version.platform.rpm rsct.core-3.2.n.n-version.platform.rpm rsct.basic-3.2.n.n-version.platform.rpm
- If your system has the rsct64bit package installed, you can use the following command to
upgrade RSCT:
rpm -Fvh src-3.2.n.n-version.platform.rpm rsct.core.utils-3.2.n.n-version.platform.rpm rsct.core-3.2.n.n-version.platform.rpm rsct.basic-3.2.n.n-version.platform.rpm (rsct.core.cimrm-3.2.n.n-version.platform.rpm rsct.opt.storagerm-3.2.n.n-version.platform.rpm) rsct.64bit-3.2.n.n-version.platform.rpm
If your system has any RSCT-exploiter packages installed, you might have to upgrade those RPM packages as well. See the RSCT exploiter's documentation for appropriate instructions.
If you want to uninstall RSCT, the packages must be uninstalled in a specific sequence. If any exploiter has a dependency on RSCT, the rpm command does not uninstall the RSCT packages.
- If the rsct.64bit package is installed, uninstall
it by entering the following command:
rpm -e rsct.64bit
- If the storage resource manager is installed, uninstall it by
entering the following command. If the storage resource manager component
is on a node in a peer domain, take the node offline before uninstalling
the storage resource manager.
rpm -e rsct.opt.storagerm
- If the rsct.opt.stackdump package
is installed, uninstall it by entering the following command:
rpm -e rsct.opt.stackdump
- Uninstall the RSCT basic components by entering the following
command:
rpm -e rsct.basic
- Uninstall the RSCT core components by entering the following command:
rpm -e rsct.core
- Uninstall the RSCT utilities by entering the following command:
rpm -e rsct.core.utils
- Uninstall the SRC by entering the following command:
rpm -e src
Verifying RSCT installation on Linux (Ubuntu)
To verify that RSCT is installed on an Ubuntu Linux nodes, enter the following command:
dpkg -l | grep -E -e "rsct|src"
An output similar to the following example is displayed:
src-3.2.n.n-14169
rsct.core.utils-3.2.n.n-14169
rsct.core-3.2.n.n-14169
rsct.basic-3.2.n.n-14169
If you installed RSCT components, ensure that
they are at a version that applies to this information. In the package
names, platform is ppc64le
or x86_64
.
This package... | Contains... |
---|---|
rsct.basic-3.2.n.n-build-number.platform.deb |
|
rsct.core-3.2.n.n-version.platform.deb | RSCT core components that includes:
|
rsct.core.utils-3.2.n.n-version.platform.deb | Miscellaneous utilities |
rsct.opt.storagerm-3.2.n.n-version.platform.deb | The storage resource manager |
src-3.2.n.n-version.platform.deb | The system resource controller (SRC) |
rsct.opt.stackdump-3.2.n.n-version.platform.deb | The stack dump function |
If the dpkg command output reveals that the required RSCT packages are not installed, you can install them from the RSCT exploiter's installation media. See the RSCT exploiter's documentation for installation instructions.
You can install RSCT by itself but, because
of the dependencies among the packages, the packages must be installed
in a specific sequence. In the following instructions, replace platform with ppc64le
or x86_64
as
appropriate for your system platform.
- Install or upgrade the SRC by entering the following command:
dpkg -i src-3.2.n.n-version.platform.deb
- Install or upgrade the RSCT packages in one line by entering the following
command:
dpkg -i rsct.core.utils*.deb rsct.core_*deb rsct.basic*deb
- Install the RSCT utilities by entering the following command:
dpkg -i rsct.core.utils-3.2.n.n-version.platform.deb
- Install the RSCT core components by entering the following command:
dpkg -i rsct.core-3.2.n.n-version.platform.deb
- Install the RSCT basic components by entering the following command:
dpkg -i rsct.basic-3.2.n.n-version.platform.deb
- Optionally, install the RSCT storage resource manager component by entering the following
command:Note: If you are installing the storage resource manager on a node in a peer domain, take the node offline before you install the storage resource manager component.
dpkg -i rsct.opt.storagerm-3.2.n.n-version.platform.deb
- Optionally, install the RSCT stack dump function by entering the following
command:
dpkg -i rsct.opt.stackdump-3.2.n.n-version.platform.deb
If you want to uninstall RSCT, the packages must be uninstalled in a specific sequence. If any exploiter has a dependency on RSCT, the dpkg command does not uninstall the RSCT packages.
- If the rsct.64bit package is installed, uninstall it by entering the
following command:
dpkg -e rsct.64bit
- If the storage resource manager is installed, uninstall it by entering the following command. If
the storage resource manager component is on a node in a peer domain, take the node offline before
uninstalling the storage resource manager.
dpkg -e rsct.opt.storagerm
- If the rsct.opt.stackdump package is installed, uninstall
it by entering the following command:
dpkg -e rsct.opt.stackdump
- Uninstall the RSCT basic components by entering the following command:
dpkg -e rsct.basic
- Uninstall the RSCT core components by entering the following command:
dpkg -e rsct.core
- Uninstall the RSCT utilities by entering the following command:
dpkg -e rsct.core.utils
- Uninstall the SRC by entering the following command:
dpkg -e src
Update on changed RSCT installation path
As RSCT for Ubuntu is going to be distributed through Canonical and is supported as part of IBM OpenPower Initiatives, RSCT Ubuntu packages need to follow Canonical policy which requires to conform to the Filesystem Hierarchy Standard (FHS),which is a Linux filesystem hierarchy.
Among FHS specifications, the current RSCT setup violates the use of
/usr/sbin by putting a directory /rsct
inside the
/usr/sbin folder. So, in RSCT the location of rsct
directory changed from /usr/sbin/rsct to /opt/rsct. From
this release onwards, RSCT installation location is changed during RSCT installation. This change is
applicable to both fresh install and upgrade of RSCT in Linux and Ubuntu.
- symbolic link from /usr/sbin/rsct to /opt/rsct is not
created for
rsct.core*
packages. - symbolic link from /usr/sbin/rsct to /opt/rsct will be
created for
rsct.basic*
packages. - symbolic link from /usr/sbin/rsct to /opt/rsct will be created for all packages if the system is upgraded from the old packages that have used /usr/sbin/rsct.
The Linux distributions that are supported by this version of RSCT are described in Supported Linux distributions for RSCT. See your RSCT exploiter's documentation to see whether that particular product also supports a particular distribution.