PATROL for Linux system requirements

Before installing the product, verify that the target computers meet the requirements listed in the following table. This section provides release-specific information about requirements and supported resources for PATROL for Linux.


Related topics

Key-concepts

Installing

Known-and-corrected-issues


Note

To get complete compatibility information for PATROL for Linux, use the BMC Solution and Product Availability and Compatibility Utility on the Product Availability and Compatibility page.

Support for third-party productsTo receive full support for a BMC product, you must have that product installed in a supported environment, as specified in the BMC product documentation. If a third-party vendor cancels support for one of its products (such as an operating system or subsystem), and that third-party product integrates or interacts with the BMC product you have licensed, you must upgrade to a supported version of that third-party product before BMC Customer Support can provide you with support for the affected BMC product. For further information, see BMC's product support policy.

Supported operating systems

Following table lists the operating systems that are supported by PATROL for Linux as local and remote monitoring. These operating systems are supported in Simplified Chinese, Traditional Chinese, Korean, Japanese, French, and German languages, unless otherwise specified.

Note

  • OpenSSL version 1.0.2g and later are supported.
  • Red Hat Enterprise Linux 9.x, CentOS 9.x, Ubuntu 22.04 are not supported for remote monitoring.

Supported operating systems

Comments

Red Hat Enterprise Linux

Red Hat Enterprise Linux 9.x, x86-64

Only local monitoring is supported.

Red Hat Enterprise Linux 8.x, x86-64, PPC64LE, IBM® zSeries®

  • x86-64 refers to Opteron (AMD 64) and Intel EM64T systems that support 64-bit libraries and executable.
  • The zSeries system is not supported in Simplified Chinese, Traditional Chinese, Korean, Japanese, French, and German languages. 
  • Monitoring of KVM is supported on the these operating systems.
  • For remote monitoring, install the libnsl.so.1 library.


Red Hat Enterprise Linux 7.x, x86-64, PPC64LE, IBM® zSeries®

Red Hat Enterprise Linux 6.x IBM® zSeries®, x86-64

SUSE Linux Enterprise Server

SUSE Linux Enterprise Server 15.x, x86-64, IBM® zSeries®, PPC64LE

  • Ensure that the net-tools-deprecated package is installed on the SUSE Linux Enterprise Server 15 computer. If this package is not installed, the discovery of some instances fails.
  • (Applicable only for Linux 1.2.00.03) The location of ifconfig tool has been changed from /sbin/ifconfig to /usr/bin/ifconfig in SUSE Linux Enterprise Server 15. You must create a soft link for the ifconfig tool to avoid discovery related issues. To create a soft link:

      1. Navigate to the /sbin directory
      2. Switch to root user
      3. Run the following command to create the soft link:
        ln -s {source-filename} {symbolic-filename}
        Example: ln -s /usr/bin/ifconfig /sbin/ifconfig
  • For Kernel-based Virtual Machine monitoring on SUSE Linux 15:
    Ensure that the following SO files are present in the /usr/lib64 directory.
    • libhogweed.so.2
    • libnettle.so.4
    • libgnutls.so.28
  • x86-64 refers to Opteron (AMD 64) and Intel EM64T systems that support 64-bit libraries and executable. 
  • This operating system is not supported in CTJKFG.

SUSE Linux Enterprise Server 12.x, x86-64, IBM® zSeries®, PPC64LE

SUSE Linux Enterprise Server 11.x, x86-64, IBM® zSeries®

Oracle Enterprise Linux

Oracle Enterprise Linux 8.x, x86-64

  • x86_64 refers to Opteron (AMD 64) and Intel EM64T systems that support 64-bit libraries and executable.

Oracle Enterprise Linux 7.x, x86-64

Oracle Enterprise Linux 6.x, x86-64

CentOS

CentOS Stream 9.x, (x86-64)

Only local monitoring is supported.

CentOS Stream 8.x, x86-64





CentOS 8.x, x86-64

CentOS 7.x, x86-64

CentOS 6.x, x86-64

Debian

Debian 10.x, x86-64

  • Debian 10 codename is buster
  • Debian 9 codename is stretch
  • Debian 8 codename is jessie

Debian 9.x, x86-64

Debian 8.x, x86-64

Ubuntu

Ubuntu 22.04, x86-64  

Only local monitoring is supported.

Ubuntu 20.04.1 LTS, x86-64


Operating systems supported as remote hosts only

Ubuntu 18.04, LTS, x86-64



Ubuntu 16.04, LTS, x86-64

SUSE Linux Enterprise Server 11.x, PPC64

Windows operating systems supported for remote monitoring

Microsoft Windows Server 2019, 64-bit


Microsoft Windows Server 2016, 64-bit

Microsoft Windows Server 2012, 64-bit


Rocky Linux 8.x x64-64


Alma Linux 8.x x64-64



Note

Before you install PATROL for Linux on a 64-bit Linux operating system, you must check and install the compat-libstdc++-33-3.2.3-61.rpm package or the latest version of the compat-libstdc++-*.rpm package that contains the library version, libstdc++.so.5.

BMC PATROL for Linux supports monitoring of ESX servers as remote hosts. VMware does not recommend installing any software on the service console. Therefore, BMC recommends that you use the remote monitoring functionality. 

  • On 64-bit Linux platform, the following message is displayed after the installation process is complete. Ignore this message. ignored: cfg_sec_prms: error while loading shared libraries: libaudit.so.0: cannot open shared object file: No such file or directory
  • Before you install PATROL for Linux on a 64-bit Debian operating system, you must check and install the following components: libstdc++5, libaio1, libsdl-mixer1.2, libsdl-net1.2, libsdl-ttf2.0-0, xaw3dg, libmikmod2, and oss-compat. To install, run the following command: {{code language="none"}}
    sudo apt-get -f install libstdc++5 libaio1 libsdl-mixer1.2  libsdl-net1.2  libsdl-ttf2.0-0 xaw3dg libmikmod2 oss-compat
    {{/code}}

Supported BMC products for PATROL for Linux

Resource

Requirements

BMC TrueSight Operations Management

  • 10.x
  • 11.x

PATROL products

  • PATROL Agent version 10.7.00 or later
  • PATROL Installation Utility version 10.5.00 or later

Installing into a UNIX environment without a browser

You must launch the installation utility from the command line and use the -serveronly command line option.

Network

TCP/IP network communications must be available

Ports

If you are installing an agent with PATROL for Linux, you must specify the port number to connect to all the agent computers.

The default port number for the PATROL Agent is 3181.

Random access memory (RAM)

32-MB for PATROL Agent

Security levels

The PATROL Security Level is set during the installation of the PATROL infrastructure components. If your product contains the PATROL Agent, you have an opportunity to select the security level. Make sure that the level that you select/accept is compatible with the rest of your enterprise's PATROL installation. Knowledge Modules (KM) inherit the security level. Products that consist of only KMs do not provide an opportunity to change the security level during installation. Do not use Security level 3 or higher if you are be using Enterprise Configuration or the PATROL Advisor. These security levels require passwords to be entered every time the host is accessed.

Accounts

Dedicated PATROL account

Accounts

You must create a dedicated user account before PATROL is installed. Use this account as your PATROL default account. The PATROL account must conform to the following guidelines:

 PATROL for Linux User Account Requirements

Components that require setuid permissions

The following table lists the components which require setuid root permissions. The table also provides an explanation of why each component needs setuid root permissions.

Component

Uses setuid root permissions to

PATROL Foundation Components

PATROL Agent

Validate the user name and password

Impersonate (via su ) other user accounts to run various KM commands

SNMP Master Agent (snmpmagt)

Listen on privileged port numbers (port numbers that are less than 1024)

PATROL KM for Linux Components

statvfs executable

Get FILESYSTEM usage data

PATROL security levels 

You can secure the data passed between PATROL components and restrict unauthorized users from accessing your data by implementing PATROL security. You can select from five  security levels when you install PATROL.

Note

The PATROL Agent, console server, and consoles must operate at the same security level to communicate with each other. When you install agents, console servers, or consoles that need to communicate with previously installed versions of these components, check the security level of the previously installed components and be sure to install the new ones at the same level.

To check the security level of a previously installed agent, console server, or console, perform the following steps:

  1. From the command line switch to the path on the computer that you want to check. Your previous PATROL installations reside in $BMC_ROOT/../common/security/bin/OS.
  2. Run the following command to display the security policy of the current computer:
{{esstool policy -a}}

The security level is displayed in the security level field of the output.

Assessing and implementing a different security level

Review the  security level definitions in the PATROL Security User Guide before installing PATROL to determine the appropriate security level for your components. If you want to implement a new security level after having previously installed PATROL security, see the PATROL Security User Guide for instructions.

Note

BMC products are certified for use on supported operating system versions. BMC does not explicitly test for OS patches/updates that are released after a BMC product is released. BMC products should work fine with minor updates to these supported operating systems. For assistance, please contact BMC Customer Support.

Support for third-party products

To receive full support for a BMC product, you must have that product installed in a supported environment, as specified in the BMC product documentation. If a third-party vendor cancels support for one of its products (such as an operating system or subsystem), and that third-party product integrates or interacts with the BMC product you have licensed, you must upgrade to a supported version of that third-party product before BMC Customer Support can provide you with support for the affected BMC product. For further information, see BMC's product support policy.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*