IBM Support

Preparing the servers

Question & Answer


Question

Preparing the servers

Answer


IBM brand Intelligent Operations Center Version 1.0.0

Preparing the servers

Before you begin the installation first prepare the serversthat the IBM? Intelligent Operations Center will be installedon.

Before you begin

A Domain Name System (DNS) server is recommended but notnecessary. If you do not have a DNS server you can register hostnames in a local hosts file for example \etc\hosts.Use the example provided here to ensure that you configure your localhosts file correctly.

Note: Before installing the IBM Intelligent Operations Center you are recommendedto use the installation prerequisites checking tool to verify thatthe installation prerequisites are met. If you do not have a localDNS server the tool identifies that as a missing prerequisite. Theprerequisite is flagged even if you have a consistent local hostsfile across all your servers so that they can communicate with each other.

About this task

To prepare servers in advance of installing the IBM Intelligent Operations Center complete the followingprocedure. By completing the steps you can avoid or eliminate errorsidentified by the prerequisite checking that takes place during theinstallation process.
Procedure
  1. Make sure that the Linux Distributionis Red Hat Enterprise Server.
  2. Disable any firewalls and SELinux. Then restart the systems.?Youcan enable firewalls after the installation completes.
  3. To ensure that the servers can communicate with each anothereach local hosts?file must contain the names of all the other servers. See the example hosts?file at the end of this procedure.
  4. To verify server communication ping each server with the fully-qualifiedname. You can also test the connections during the installation process. Thisconnectivity test is done automatically by the installer during theinstallation of the IBM Intelligent Operations Center 1.0 Fix Pack 1.
  5. Make sure that either the host name of each server is identicalto the host name registered on the DNS server or to the host nameregistered in the /etc/hosts?file.
    1. To check the host name of the server as registered eitheron the DNS server or in the local hosts?file enter the command:?nslookup$(hostname -i)
    2. To query the value of the host name to check that thelocal host name is correctly configured enter the command:?hostname-f
    Note: The host names are case-sensitive.
  6. If the host name is incorrect complete the following steps:
    1. Enter the following command: hostname short_host_name. For example: hostname server1
    2. In the /etc/sysconfig/network filemodify or insert the following line: HOSTNAME=short_host_name
  7. Make sure that the fully-qualified host name and the shorthost name are not mapped to 127.0.0.1 in the?/etc/hosts?file.
  8. Make sure that each entry in the?/etc/hosts?filehas the following format:
      ip_address fully-qualified_host_name short_host_name
    For example: 192.168.1.101 server1.ibm.comserver1
  9. Make sure that 30 GB disk space is available in both the /tmp directoryand the /opt directory so that a total of 60 GBdisk space is available on the server.
  10. Set the open file limit to be greater than 10000. Thecommand to check the open file limit is: ulimit -n.If the limit is not equal to 10000 it can be set using the command: ulimit-n 10000.
  11. Enable Internet Protocol Version 6 (IPV6). Usethe following commands to enable IPV6:
    modprobe ipv6lsmod | grep ipv6 
  12. Configure the password policy correctly. Formore detail on modifying the password policy before installationsee the link at the end of the topic.
  13. Allow root and other users to use Secure Shell (SSH). Toenable password authentication and root user access between the operatingsystem Red Hat Enterprise Linux andother SSH targets complete the following steps:
    1. On the target servers edit the /etc/ssh/sshd_config file:
      • Delete the line with AllowUsers
      • Set the value of the parameter PasswordAuthentication to yes
      • Set the value of the parameterPermitRootLogin to yes
    2. To stop and restart the SSH daemon enter the followingcommands:
      /etc/init.d/sshd stop/etc/init.d/sshd start
  14. Set the time zone and data time to be identical acrossall target servers and the installation server.
  15. Do not use a soft link for /tmp. A soft link means that /tmp is not theactual directory but points to another directory. You can check if this is the caseby running the command: ls -la/. Look for a linesimilar to: drwxrwxrwt 21 root root 12288 Feb 10 11:12 tmp Ifthe d at the start here is an l instead then /tmp isa soft link. For example the code would be similar to: lrwxrwxrwx1 root root 10 Feb 23 2011 tmp -> root/tmp If this is the casethen you can run the command: mv /tmp /tmp_old mkdir /tmp

Example

If there is no DNS and the host name is registered inthe /etc/hosts file follow the example providedhere to write the /etc/hosts file. Note in theexample how the local host is mapped to 127.0.0.1the host name is mapped to the IP address and the fully-qualifiedhost name is written before the short host name. The simplest wayto ensure that the /etc/hosts configuration isconsistent across all servers is to create and edit the file as shownin this example. Then upload this file to all the servers.

127.0.0.1        localhost.localdomain localhost192.168.1.101    server1.ibm.com server1192.168.1.102    server2.ibm.com server2192.168.1.103    server3.ibm.com server3192.168.1.104    server4.ibm.com server4192.168.1.105    server5.ibm.com server5192.168.1.106    server6.ibm.com server6192.168.1.107    server7.ibm.com server7192.168.1.108    server8.ibm.com server8

Library | Support |Terms of use

(c) Copyright IBM Corporation 2011 2012. All rights reserved.
U.S. Government Users Restricted Rights - Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

"

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSMGP8","label":"Smarter Cities"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 December 2018

UID

ibm10751031