Requirements for installing individual components on UNIX and Linux

This topic describes the requirements for installing BMC Server Automation on on UNIX and Linux platforms.

The topic includes the following sections:

Requirements for installing product components on UNIX and Linux

You can also use the individual product installers to install single components.

Component Requirements
All


Requirement for RedHat Enterprise Linux (RHEL) version 5

If you plan to install the Application Server, the BMC Server Automation Console or the Network Shell on Linux, ensure that the libtermcap.so.2 shared library (and libtermcap.so.6 shared library in case of unified product installer) is installed. To determine if termcap is installed, run the following command:
rpm -qa | grep libtermcap

If this command does not return libtermcap-xxx, install the library from installation media or download and install it from a trusted gnu distribution site.
The libtermcap.so.2 shared library you install depends on the platform of the Application Server, the BMC Server Automation Console or the Network Shell you are installing. If you are installing the:

  • 32-bit version of these components on a 64-bit operating system--Install the 32-bit version of libtermcap.so.2.
  • 64-bit version of these components on a 64-bit operating system--Install the 64-bit version of libtermcap.so.2.

Requirement for RHEL 6

In RHEL 6 the package name has changed to compat-libtermcap. To install compat-libtermcap on Red Hat version 6, you can use one of the following commands:

  • If you have YUM installed and configured: yum install compat-libtermcap
  • If you have the RPM package (available from the installation CD): rpm -Uvh compat-libtermcap-2.0.8-49.el6.x86_64.rpm

Requirement for RHEL 7

In RHEL 7, libtermcap is no longer available, and you must create a link to libtinfo instead. Use the following command:

ln -s /lib64/libtinfo.so.5 /lib64/libtermcap.so.2

If libtinfo is not available on your system, obtain it by installing the ncurses-libs package.

Application Server (with NSH and agent)
  • Linux platforms on which you plan to install the Application Server or Network Shell must have the appropriate version of libtermcap.so.2 shared library installed. Install the shared library before installing these components. For more information, see Requirement for installing the Application Server, BMC Server Automation Console, or Network Shell on Linux.
  • The UNIX or Linux file system partition to which you plan to install the Application Server must not be mounted with the nosuid option.
  • Set the umask for the root user to 0022 on the Application Server host computer.
  • BMC Server Automation might have many open files at any given point in its operation. Therefore, unless your environment has specific needs for a more restrictive setting (depending on the specific operation of the Application Server), BMC recommends that you ensure that the following operating system parameters are set for the bladmin user. These settings should be permanently set for the user (for example, in the /etc/security/limits.conf  file for Linux):
    • Set core files to unlimited.
    • Set the number of open file descriptors to 8192
  • Optionally, set the INSTALL_FILES_TEMP environment variable to a valid, writable directory. If this variable is set, the installer files are stored in that location, thereby reducing the disk space requirements for /tmpduring the installation. Enter the following commands at the operating system command line:

    INSTALL_FILES_TEMP=<temporaryDirLocation>
    export INSTALL_FILES_TEMP

    For more information, see Methods for reducing installation space on Linux and UNIX.

Agent only

Optionally, set the INSTALL_FILES_TEMP environment variable to a valid, writable directory. If this variable is set, the installer files are stored in that location, thereby reducing the disk space requirements for /tmp during the installation. At the operating system command line, enter the following commands:

INSTALL_FILES_TEMP=<temporaryDirLocation>
export INSTALL_FILES_TEMP

For more information, see Methods for reducing installation space on Linux and UNIX.

Console
  • To install the BMC Server Automation Console, you can use the installation wizard in the user interface or silent mode. You cannot use console mode. To use the installation wizard, follow the steps below. To use silent mode, see Using silent mode to install the BMC Server Automation Console (Linux and UNIX).
  • You must have an X Window server installed and configured.
  • You must have write access to the /tmp directory, as well as sufficient disk space. To review the hardware requirements for the console, see Minimum hardware requirements.
  • Make sure that port 12333 (TCP) is not being used. Installation of the console requires use of this port; if it is already in use, the installation fails.
  • Linux platforms on which you plan to install the BMC Server Automation Console (RCP client) or Network Shell must have the libtermcap.so.2 shared library installed. Install the shared library before installing these components. For more information, see Requirement for installing the Application Server, BMC Server Automation Console, or Network Shell on Linux.
  • If the version of the RSCD Agent does not match the version of the console, uninstall the old RSCD Agent and install a new version that matches the console. Stop the RSCD Agent before you try to install the console.
File server

A file server should meet the following requirements:

  • An RSCD agent must be installed and should be the same version as the Application Server.

  • Do not limit access to the file server by pushing agent ACLs to the agent on the file server. All users must be mapped to the same user on the file server.

  • As a minimum, a file server must have 72 GB of available, nonredundant, disk space. BMC recommends that the file server be allotted 200 GB or more of available RAID 5 disk space.

  • Define a user name on the file server, and map all users to that user name. Without this mapping, a user may not be able to access a file that another user has stored on the file server. To accomplish the necessary mapping, create an entry like the following in the exports file (located by default at C:\Windows\rsc) on the file server:
    <appServer> rw,user= <userName>
    Where <appServer> is a comma-separated list of Application Server names or IP addresses (IPv4 or IPv6) and <userName> is the name to which all users are mapped.
  • Map the internal System:System role/user to the user name defined on the file server. To accomplish the mapping, create an entry like the following in the users.local file (located by default at C:\Windows\rsc) on the file server:
    System:System rw,map= <userName>
    Where <userName> is the name to which all users are mapped, typically bladmin or administrator.
    If the required directory structure does not already exist on the file server, the system process attempts to create it.
    For examples on configuring the file server agent ACLs, see Configuring the file server agent ACLs.
  • If your file server location is on partition or a mounted storage, you must ensure that the mount point for the storage or partition is consistent even if the file server host is restarted.
    For example, on Linux, you can ensure this by configuring the fstab file in the etc folder of your machine. The fstab file maps the Universally Unique Identifier (UUID) of a storage or partition to the directory it should be mounted on.
NSH only Linux platforms on which you plan to install the Network Shell must have the libtermcap.so.2 shared library installed. Install the shared library before installing the Network Shell. For more information, see Requirement for installing the Application Server, BMC Server Automation Console, or Network Shell on Linux.

Required ports for installers

Note the following port-related information prior to installing BMC Server Automation:

  • Before you install the BMC Server Automation Console, make sure that port 9998 (TCP) is not being used. Installation of the console requires use of this port. If the port is already in use, the installer shows a progress bar but exits before launching and the installation fails.
  • For the UNIX agent installer, use either ssh or ftp/telnet to run the agent installer. Only the ports for the specific method of install need to be open.

For more information, see BMC Server Automation ports.

Supported platforms for native installers

For several Linux and UNIX platforms, you can choose between a shell-based (.sh) installer and a native installer (.bff for AIX, .rpm for Linux, or .gz for Solaris). You might prefer to use the native installer, for example, to install in bulk.For more information about the platforms that support installation using a native installer, see "Supported platforms for native installers" under Supported platforms for version 8.6.

Where to go from here

Installing individual components

Was this page helpful? Yes No Submitting... Thank you

Comments