Requirements for installing individual components on UNIX and Linux

All

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:

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, TrueSight 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.
• TrueSight 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:

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

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 (for example, blfsro) on the file server with read only permission on the storage, 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 on the file server:
  <appServer> ro,user=blfsro
  Where <appServer> is a comma-separated list of Application Server names or IP addresses (IPv4 or IPv6).
  The default location of the exports file is:
  • (Windows) C:\Windows\rsc
  • (Linux): /etc/rsc

• Map the built-in System:System role/user to the user name (for example, blfsrw) defined on the file server with full permission on the storage. To accomplish the mapping, create an entry like the following in the users.local file on the file server:
  System:System rw,map=blfsrw
  Where blfsrw is the name to which the built-in System:System role/user is mapped, typically used when Application Server accesses the file server.
  If the required directory structure does not already exist on the file server, the system process attempts to create it.
  The default location of the users.local file is:

  • (Windows) C:\Windows\rsc
  • (Linux): /etc/rsc

  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 or Network Shell on Linux.