Preparing to install Common Agent on X-Architecture systems
Before installing Common Agent on a managed system running Linux for X-Architecture systems, make sure that your system meets all the applicable requirements.
About this task
Review the following information and complete the necessary steps to prepare your system for installation:
Procedure
- Ensure that the instance of Common Agent will be fully functional and able to send alerts to IBM® Flex System Manager. For the Common Agent to be fully functional you might need to install service-processor device drivers or the IBM LM78 and SMBus device drivers for Linux.
- Ensure that the required RPMs are installed.
Table 1. Required libraries for Linux on System x Installation scenario Management server Common agent Platform agent Red Hat Enterprise Linux openssh libstdc++.so.5 libm.so.6 libgcc_s.so.1 libc.so.6 libdl.so.2 libpthread.so.0 unzip libaio libcrypt.so.1 libnsl.so.1 libpam.so.0 librt.so.1 bind-utils net-tools libstdc++.so.6 libuuid.so.1 libexpat.so.0libcrypt.so.1 libc.so.6 libdl.so.2 libstdc++.so.5 libgcc_s.so.1 libm.so.6 libnsl.so.1 libpam.so.0 libpthread.so.0 librt.so.1 unzip bind-utils net-tools libstdc++.so.6 libuuid.so.1 libexpat.so.0libstdc++.so.5 bind-utils net-tools libpam.so.0 libstdc++.so.6 libuuid.so.1 libcrypt.so.1 unzip libexpat.so.0 openssl1.0.1SUSE Linux Enterprise Server 10 SUSE Linux Enterprise Server 11
openssh libstdc++.so.5 libm.so.6 libgcc_s.so.1 libc.so.6 libdl.so.2 libpthread.so.0 unzip libaio libcrypt.so.1 libnsl.so.1 libpam.so.0 librt.so.1 bind-utils net-tools libstdc++.so.6 libuuid.so.1 libexpat.so.1libcrypt.so.1 libc.so.6 libdl.so.2 libstdc++.so.5 libgcc_s.so.1 libm.so.6 libnsl.so.1 libpam.so.0 libpthread.so.0 librt.so.1 unzip bind-utils net-tools libstdc++.so.6 libuuid.so.1 libexpat.so.1libstdc++.so.5 bind-utils net-tools libpam.so.0 libstdc++.so.6 libuuid.so.1 libcrypt.so.1 unzip libexpat.so.1 openssl1.0.1 - (Red Hat Enterprise Linux only): Before
you install IBM Flex System
Manager,
you must ensure the SELinux policy is not being enforced. SELinux runs in any of the following states:
- Disabled
- SELinux is disabled. You can tell that SELinux is in the disabled
state by determining if any of the following conditions are true:
- No files exist in the /selinux/ directory.
- Permissive (enabled)
- SELinux is enabled but not enforcing any security policies. You
can tell that SELinux is in the permissive state by determining if
any of the following conditions are true:
- The SELINUX variable in /etc/sysconfig/selinux/enforce is set to permissive or a value not equal to "1".
- When you run the getenforce command, it outputs "Permissive".
- Enforcing (enabled)
- SELinux is enabled and enforcing security policies. You can tell
that SELinux is in the enforcing state by determining if any of the
following conditions are true:
- The SELINUX variable in /etc/sysconfig/selinux/enforce is set to enforcing or "1".
- When you run the getenforce command, it outputs "Enforcing".
- Systems with service processors: Install the supporting device drivers and mapping layers, if they are not already installed. See "Preparing to manage service processors with IBM Flex System Manager" for information about these drivers and mapping layers.
- If you want to use the Remote Session task on the managed system, make sure that the package that contains telnetd daemon is installed and configured.
- Ensure the validity of any stored public key data for the target system in root_SSH_data_directory/known_hosts on IBM Flex System Manager. See "Common Agent cannot be installed on an AIX® or Linux system" for more information.
Parent topic: Preparing for a Common Agent managed system