Redhat El6.3 and Centos 6.3 Installation Configuration Guide

RedHat EL6.3 and CentOS 6.
3 ICG for Traffic Control

__________________________________________________________________
RedHat EL6.3 and CentOS 6.3

Installation Configuration Guide
for Traffic Control Release 4000
Date: 22/04/14
Version: 1.7
Author: OMN
© Openmind Networks Limited 2014 Commercial in Confidence

Version 1.7 1 of 44
RedHat EL6.3 and CentOS 6.3 ICG for Traffic Control
__________________________________________________________________
Table of Contents
1 Introduction....................................................................................................................6
1.1 Objective.................................................................................................................................................... 6
1.2 Audience.................................................................................................................................................... 6
1.3 How This Document Is Organised........................................................................................................... 7
1.4 References................................................................................................................................................ 7
2 Overall Steps..................................................................................................................8
3 Commissioning Hardware.............................................................................................9
3.1 Configuring RAID Controller.................................................................................................................... 9
3.2 Setting BIOS Date and Time................................................................................................................... 11
4 Installing Operating System.......................................................................................12

4.1 Script-driven Method.............................................................................................................................. 12
4.1.1 Prerequisites.......................................................................................................................................... 12
4.1.2 Preparing the Kickstart Scripts............................................................................................................... 12
4.1.3 Making Software and Scripts Available on USB Key Drives...................................................................12
4.1.4 Booting with Kickstart Script.................................................................................................................. 13
4.2 Full Manual Method................................................................................................................................ 14
4.2.1 Prerequisites.......................................................................................................................................... 14
4.2.2 Booting from OS DVD............................................................................................................................ 14
4.2.3 RPMs to Install....................................................................................................................................... 14
4.3 RPMs to Remove..................................................................................................................................... 16
4.4 Extra OS RPMs to Install........................................................................................................................ 16
4.5 Disabling SELinux.................................................................................................................................. 16
4.6 Disabling NetworkManager.................................................................................................................... 16
5 Post-install OS Configuration.....................................................................................17
5.1 Updating BIOS......................................................................................................................................... 17
5.2 Updating Firmware................................................................................................................................. 17
5.3 Updating Smart Array Controller Firmware.......................................................................................... 17
5.4 Installing Additional Platform Rpms..................................................................................................... 17
5.5 Editing /etc/hosts File............................................................................................................................. 18
5.6 Identifying Physical LAN Devices......................................................................................................... 19
5.7 Via Running configure-os-post-install.sh.............................................................................................19
5.7.1 Running the Shell Script........................................................................................................................ 19
5.7.2 Checking the Outcome via check-configure-post-os-install.sh...............................................................20
5.7.3 Post-OS-Install Configuration in Detail................................................................................................... 20
5.7.3.1 Disable Prelinking (/etc/prelink.conf)................................................................................................... 20
5.7.3.2 Disable updatedb Cronjob (/etc/cron.daily/mlocate.cron)....................................................................20
5.7.3.3 Disable Some Daemon Processes (/etc/init.d)....................................................................................20
5.7.3.4 Modify /etc/sysctl.conf......................................................................................................................... 20
5.7.3.5 Modify the Number of inodes.............................................................................................................. 21
5.7.3.6 Add Limits to the Number of Open Files and Procs (/etc/security/limits.conf).....................................22

Version 1.7 2 of 44
__________________________________________________________________
5.7.3.7 Set the Default Runlevel to 3 (/etc/inittab)........................................................................................... 23

5.7.3.8 Upstart /etc/init/samson.conf............................................................................................................... 23
5.7.3.9 Modify a Mount Option (/etc/fstab)...................................................................................................... 24
5.7.3.10 Modify the Number of Processes (/etc/security/limits.d/90-nproc.conf).............................................24
6 Creating Bonded LAN Interfaces...............................................................................25

6.1 Via Running setup-bonded-interfaces.sh............................................................................................. 25
6.1.1 Running the Shell Script........................................................................................................................ 25
6.1.2 Bonded LAN Interface Configuration in Detail.......................................................................................26
6.1.2.1 Modify /etc/sysconfig/network............................................................................................................. 26
6.1.2.2 Create /etc/modprobe.d/bonding.conf.................................................................................................26
6.1.2.3 Create Primary Interface (/etc/sysconfig/network-scripts/ifcfg-ethX)...................................................26
6.1.2.4 Create Secondary Interface (/etc/sysconfig/network-scripts/ifcfg-ethY)..............................................26
6.2 Checking IP Connectivity....................................................................................................................... 27
6.3 Adding Static IP Routes......................................................................................................................... 29
6.4 Setting NTP Server................................................................................................................................. 31
7 Appendix A: Kickstart Parameters.............................................................................33
8 Appendix B: Default Partition Layouts......................................................................36

8.1 SMS Router, SMS Hub, Standalone BMS..............................................................................................36
8.2 SMS Router, SMS Hub, Standalone BMS - Cassandra with 10 disks.................................................36
8.3 Standalone Assure................................................................................................................................. 37
8.4 Standalone Care...................................................................................................................................... 37
8.5 Co-located Assure/Care......................................................................................................................... 38
9 Appendix C: Example Bonded LAN Interface Files..................................................39
10 Appendix D: How to Change hostname in OS..........................................................40
11 Glossary........................................................................................................................41

Version 1.7 3 of 44
__________________________________________________________________
List of Tables
Table 1: Document Change History.................................................................................................................. 5
Table 7.1: Kickstart Parameters...................................................................................................................... 34
Table 8.1: Default Partitions for SMS Router, SMS Hub, BMS........................................................................36
Table 8.2: Default Partitions for SMS Router, SMS Hub, BMS - Cassandra with 10 disks layout...................36
Table 8.3: Default Partitions for Standalone Assure........................................................................................37
Table 8.4: Default Partitions for Standalone Care........................................................................................... 37
Table 8.5: Default Partitions for Co-located Assure/Care................................................................................38

Version 1.7 4 of 44
__________________________________________________________________
Copyright Notice
Copyright © Openmind Networks Limited, 2014. All rights reserved. The copyright in this document is owned
by Openmind Networks Limited ("Openmind Networks", "OMN"). This document may not be reproduced, in
whole or in part, in any form without the express consent of Openmind Networks in writing.
Information contained in this document is proprietary and confidential to Openmind Networks. That
information, irrespective of form, must not be used other than for the purposes for which it is disclosed to the
recipient and must not under any circumstances be disclosed to any third party without the express consent
in writing of Openmind Networks. Certain Trade Marks referred to in this document are the property of
Openmind Networks, the rights of owners of other Trade Marks referred to in this document are hereby
acknowledged.
Although Openmind Networks uses all reasonable efforts to ensure the accuracy and completeness of this
document, no warranty or representation whatever is given by Openmind Networks in respect of it and any
use of or reliance on any of the information contained herein is entirely at the risk the person so acting.
Openmind Networks shall have no liability whatsoever in respect of any use of or reliance on any of such
information.
Table 1: Document Change History

Version Date Author Notes
1.0a 18/04/13 Tom Suzuki Initial Draft created.

1.0 05/03/13 Tom Suzuki Reviewed and released.
1.1 16/07/13 Tom Suzuki Updated Section 5.7.2.6 for /etc/security/limits.conf

1.2 08/11/13 Jan Jirmasek Updated the partitions layout for Cassandra with 10 disks.
1.3 02/01/14 Tom Suzuki Replaced with ext4. Updated Section 3.1 for Smart Array
configuration and Section 5.7.2.6 for
/etc/security/limits.conf
1.4 03/03/14 Tom Suzuki Updated limits.conf values to cater for Cassandra-based
message store.
1.5 03/03/14 Tom Suzuki Updated to add a new item for /etc/sysctl.conf
1.6 09/04/14 Tom Suzuki Updated to add a note on NetworkManager to disable.
1.7 22/04/14 Tom Suzuki ntpdate updated in Section 6.4

Version 1.7 5 of 44
__________________________________________________________________
1 Introduction
1.1 Objective
This document describes the method and the procedure to follow in installing one of these operating systems
for the Openmind Networks' Traffic Control product suite.
• RedHatEL6.3 x86_64 (64-bit) with required 32-bit libraries
• CentOS6.3 x86_64 (64-bit) with required 32-bit libraries
1.2 Audience
The document is intended for all stakeholders involved in design, integration, approval and implementation of
the OMN product. It is assumed that the installation engineer is familiar with computers/a Linux operating
system.

Version 1.7 6 of 44
__________________________________________________________________
1.3 How This Document Is Organised

This document is created from a template with pre-defined sections to cover typical common topics.
Sections may be added as necessary to suit the project.
Heading: Each top-level and optionally second-level document heading is accompanied

by a contextual leading text in Italic.
Links to References: Hyperlinks to documents or articles are inserted to help referencing.
Input Notes: Notes for assisting input is adhered in Italic, smaller font size.
Glossary: Glossary is provided at the end of this document.
Annotations: Balloon Comments may be used to add comments and clarification in

response as necessary. All Balloon Comments will be removed when the
document is finalised.
TBD: The space that requires input is marked TBD with yellow highlighter.
Updated Areas: Updated paragraphs, sections, etc. are marked abc with sky blue highlighter.
1.4 References
No. Document Title, Version, ID, Date Author,Issuer
[1] RedHat Red_Hat_Enterprise_Linux-6-Installation_Guide-en- RedHat

US.pdf, Edition 1.0
[2] Red_Hat_Enterprise_Linux-6-Deployment_Guide-en-US.pdf, RedHat
Edition 2
[3] CentOS Website www.centos.org CentOS

[4] Migrating to hpsa, c02677069.pdf HP
[5] Red Hat Enterprise Linux 6 6.3 Release Notes RedHat

[6] Red Hat Enterprise Linux 6 6.3 Technical Notes RedHat

Version 1.7 7 of 44
__________________________________________________________________
2 Overall Steps
This section illustrates the overall steps to complete OS software installation on the Openmind's product
platform.
Overall, the task is composed of the following steps:

• Preparing the Kickstart scripts for each server
• Commissioning Hardware
• Installing Operating System
• Configuring Operating System
There are three ways to complete the step of installing operating system software for Traffic Control:
• Full Manual method (No Kickstart script used, entirely manual installation)
• Script-driven method - semi-automatic (With Kickstart script, disc partitions are manually configured)
• Script-driven method - fully automatic (No manual intervention required)
Whichever method you may choose to follow, it is recommended that OS installation and configuration be
completed on one server first. Once you have one server done correctly, it is much easier to replicate the
same task across the rest of the servers.
For deployment of four or more cluster nodes, the script-driven method enables a concurrent installation
process using multiple DVDs and USB keys.

Version 1.7 8 of 44
__________________________________________________________________
3 Commissioning Hardware
This section describes the method of commissioning the hardware platform.
It is assumed that description in this document is based on HP Proliant DL380 G8 server with P420i Smart
Array as the hardware platform.
3.1 Configuring RAID Controller

The objective is to create logical drives with RAID 1 fault tolerance level (mirroring). Disc usage on Assure
and Care server platforms may vary from one deployment to another, which may be sized for RAID 10
(mirroring and striping).
The main idea in pairing physical discs is that the pairing and aggregation should be made symmetrically
across the drive bays or boxes like the examples shown below.
IMPORTANT
Whatever the logical drive configuration it may be, make sure that the subsequent logical drive
configuration is reflected in partition layout in the Kickstart script and configure-os-post-install.sh you are
going to use.

Version 1.7 9 of 44
__________________________________________________________________
Example 1:
Logical Single Box 8-bay Small-Form Factor Storage Cage

Drive ID
1 Bay 1 Bay 5
2 Bay 2 Bay 6
3 Bay 3 Bay 7
4 Bay 4 Bay 8
NOTE:
Standard configuration.
Example 2:
Logical Box 1 Box 2 16-bay Small-Form Factor Storage Cage

Drive ID
1 Bay 1 Bay 1
2 Bay 2 Bay 2
3 Bay 3 Bay 3
4 Bay 4 Bay 4
5 Bay 5 Bay 5
NOTE:
Use of Bays may vary from deployment to deployment.
Example 3:
Logical Single Box 25-bay Small-Form Factor Storage Cage

Drive ID
1 Bay 1 Bay 2
2 Bay 3 Bay 4
3 Bay 6,7,8 Bay 11,12,13

4 Bay 16,17,18 Bay 21,22,23
NOTE:
ASSURE/CARE co-located server configuration.

Version 1.7 10 of 44
__________________________________________________________________
Steps Notes
1 Turn on the server. Watch the self hard drive check on
the front green LED.
2 Press any key when prompted to do so to invoke menu
options. This allows the system to call the menu options for
iLO, then Smart Array Controller.
3 In the next screen, wait until a message "HP Smart Array
Controller XXXXX: Initializing ..." appears after an iLO option.
Right after this, a list of function keys appears for menu
options. Press F8 immediately to go into the Smart Array
Controller configuration menu.
4 Configure the logical drives in the menu. Make sure that you Make sure that hard drives are
delete any logical drive that may exist from manufacturer's paired across bays/boxes.
assembly.
5 After configuring all logical drives, select the menu for marking
the primary boot volume. When a list of configured logical
drives appears, select the first logical drive and save.
6 View the logical drives. If all is OK, exit the Smart Array Exiting the configuration menu, the
Controller configuration menu. system prompts several menu
options.
7 To set BIOS date and time, press F9 when prompted.
3.2 Setting BIOS Date and Time

If you have not set the BIOS date/time, following the completion of Smart Array Controller configuration,
press the F9 function key (ROM-based Setup) to invoke the BIOS Set-up menu.
NOTE: If you have to use an external DVD drive, go into [F11: Boot Options] and select the USB key drive
option. The default boot order does not seem to take effect if the first choice (CDROM) drive is absent.

__________________________________________________________________
4 Installing Operating System

This section illustrates the method of installing operating system on servers using a Kickstart script for
Openmind's product platform.
The agreed hardware bill of materials must be rack-mounted and cabled according to the installation
documents accompanying the hardware and the agreed "System Architecture Description" project's system
architecture document.
4.1 Script-driven Method

This method is recommended if there are more than four servers to install in the cluster, or if you are simply
going to repeat the installation with the same configuration.
4.1.1 Prerequisites
• DVD drive (internal or external on the server)
• 4x USB 2.0 port available on the server
• Up to 3 USB 2.0 key drives formatted in FAT32
• Up to 3 OS DVDs
• A pocket-sized USB hub (optional but highly recommended)
4.1.2 Preparing the Kickstart Scripts

First of all, study the disc array/hard drive configuration of the platform for the project and the default partition
layout in Appendix.
A site-specific Kickstart script can be created in one of the three ways.
i. Running system-config-kickstart on the GUI of a CentOS/Fedora/RedHat Linux PC from scratch
Refer to the table Kickstart Parameters in Appendix to put these parameters in place. For the
Package Selection section, just select a minimum set of packages when saving the script. Then,
replace the package list with the one taken from an appropriate Kickstart script in CVS.
ii. Copying and modifying an existing script in CVS (/slingshot/IKEA/halo/kickstart)
Simply modify the copied script to reflect the system you are working on.
iii. Generating a Kickstart script by installing the OS through the full manual method
This approach lets you have the most accurate Kickstart script, although it takes longer. Just select
a minimum set of rpm packages since you will replace the section with the one we have listed in the
Kickstart script in CVS.
4.1.3 Making Software and Scripts Available on USB Key Drives

The USB key drive should have files in the following directory structure on the top directory:
i. The top directory to contain:
A Kickstart script for the server to install and configure

__________________________________________________________________
configure-os-post-install.sh
check-configure-post-os-install.sh
setup-bonded-interfaces.sh
install-omn.sh
gen_cdi.sh
genlicence and genfeaturelicence binaries matching the version of libtbx of the Q-release
A text file containing a list of features licensed for the customer (i.e. cdi-extract, without commented
lines)
ii. software/<Q-release>/BASE/ to contain OMN BASE rpm files (Q-release is 13-Q1, for example)
iii. software/<Q-release>/PATCHES/ to contain OMN PATCH rpm files (Q-release is 13-Q1, for
example)
iv. software/<Q-release>/3rd-party/ to contain 3rd-party software (e.g. JDK, MySQL, HP firmware)
4.1.4 Booting with Kickstart Script

1. Turn on the server with a USB key drive and a Kickstart script located on the top level of it, and insert
the bootable ISO image disc in the DVD drive.
Let it go until you see the Linux start option prompt. Immediately the prompt appears, start typing
the following:
vmlinuz initrd=initrd.img ks=hd:sda1:/<kickstart script name>
and hit return.

This will start booting from the bootable DVD iso image to locate the Kickstart script on the USB key
drive. The Kickstart process may be finished by an auto-reboot.
2. After finishing the installation and you log into the desktop, open a terminal and run the
preinstallcheck.sh script available from the /slingshot/sbe/LATEST/SRC library to check whether you
have any rpm packages missing. If any packages are missing from the server, manually install all
the missing rpms from the OS DVD.
The device name “sda1” may vary. You can find out the correct device name by checking the virtual
consoles pressing Alt+F1, Alt+F2, Alt+F3 and Alt+F4 in succession, one of which will display a USB
connection event with the device name. If you get a message that the script is not found, simply unplug and
re-plug the USB key drive, then one of the virtual consoles will indicate the device name for the USB key
drive.
Remove the DVD when Kickstart OS installation from the media is completed successfully. The Reboot
button should be presented on the screen if auto-reboot is disabled in the Kickstart script. If auto-reboot is
enabled, a GUI login screen should be presented after the reboot. Whichever it is, log in as root to proceed.

__________________________________________________________________
4.2 Full Manual Method

This method is suitable for the very initial installation of the OS if there is no Kickstart script available. At the
end of the installation, the OS will place a Kickstart file in the /root directory that reflects what your have just
installed.
4.2.1 Prerequisites
• DVD drive (internal or external on the server)
• OS DVD
4.2.2 Booting from OS DVD

1. Turn on the server and insert the bootable ISO image disc in the DVD drive.
2. When you see the Linux start option prompt, just accept the default kernel option and hit return.
This will start booting from the bootable DVD iso image.
3. The installation process will prompt you with a series of questions and options. Select the most
suitable/sensible/default item until disc layout menu appears.
4. When prompted, choose the custom disc layout option, and enter disc partition details according to
the Traffic Control platform specifitions.
5. For package installation, the choice depends on how familiar you are with what rpm packages to
install.
• If you are familiar enough, go to 'Custom' and select required packages in the required
Package Groups, and de-select unnecessary packages in each Package Group.
• If you are not, choose to install “Minimal/Minimum Server” or “Install Packages Later”. Then,
manually install packages according to the selection listed in the Kickstart script available in
CVS.
6. After finishing the installation and you log into the desktop, open a terminal and run the
preinstallcheck.sh script available from the /slingshot/sbe/LATEST/SRC library to check whether you
have any rpm packages missing. If any packages are missing from the server, manually install all
the missing rpms from the OS DVD.
4.2.3 RPMs to Install

There are 32-bit versions of library rpm packages to install as follows:
1. Run the rpm command to check.
root# rpm -ivh <rpm file1> <rpm file2> ... <rpm fileN>
compat-libstdc++-296.i686
cyrus-sasl-lib.i686
db4.i686
gamin.i686

__________________________________________________________________
glib2.i686
glibc.i686
keyutils-libs.i686
krb5-libs.i686
libacl.i686
libattr.i686
libcom_err.i686
libgcc.i686
libgssglue.i686
libgtop2.i686
libjpeg.i686
libjpeg-turbo.i686
libpng.i686
libselinux.i686
libstdc++.i686
ncurses-libs.i686
nspr.i686
nss.i686
nss-softokn-freebl.i686
nss-softokn.i686
nss-util.i686
openldap.i686
openssl098e.i686
openssl.i686
popt.i686
readline.i686
sqlite.i686
zlib.i686

__________________________________________________________________
4.3 RPMs to Remove

An rpm package called “biosdevname” needs to be removed immediately because this would cause havoc
changing network device name mapping. Right after installing the OS, ensure that this rpm does not exist on
the server.
1. Run the rpm command to check.
root# rpm -qa | grep biosdevname
2. If it does exist, remove it.

root# rpm -ev biosdevname
3. Double-check that it was removed.
4.4 Extra OS RPMs to Install

libgtop2.i686 is not available on the RHEL 6.3 64-bit or CentOS 6.3 64-bit Installation DVD. Therefore, you
need to get this rpm from:
either
/slingshot/third_party/install_extras/AS6.3/libgtop2-2.28.0-3.el6.i686.rpm
or
the RHEL 6.4 32-bit distro package section on RHN.
4.5 Disabling SELinux

Disable SELinux by setting the following variable to “disabled” in /etc/selinux/config
SELINUX=disabled
4.6 Disabling NetworkManager

Check if NetworkManager is disabled. If not, disable it:
1. Run the service commands:

service NetworkManager status
service NetworkManager stop
service NetworkManager status
2. Run chkconfig commands to keep it disabled at boot time.

chkconfig --list NetworkManager
chkconfig NetworkManager off
chkconfig --list NetworkManager

__________________________________________________________________
5 Post-install OS Configuration
This section describes post-install OS configuration.
5.1 Updating BIOS

The server hardware may not be shipped with up-to-date BIOS. Therefore, it is advisable to check the HP
Software/Driver Download website for the latest BIOS update, which may also contain bug fixes.
5.2 Updating Firmware

The server hardware may not be shipped with up-to-date firmware for hardware components. Therefore, it is
advisable to check the HP Software/Driver Download website for the latest firmware update, which may also
contain bug fixes.
5.3 Updating Smart Array Controller Firmware

The server hardware may not be shipped with up-to-date firmware for Smart Array controller. Therefore, it is
advisable to check the HP Software/Driver Download website for the latest firmware.
1. Prior to updating the Smart Array Controller firmware, shut down the server.
2. Take out half of the RAID1 physical drives.
3. Power on the server, and verify that the server starts up fine.
4. Shut down and put all the physical drives back in.
5. Power on the server and verify that the server starts up fine.
6. If any update is desired, install the Smart Array Controller firmware update.
7. Repeat the physical redundancy check above.
5.4 Installing Additional Platform Rpms

There are some RPMs that should be additionally installed, which are available from the HP Software/Driver
Download website.
• hpacucli (Smart Array client command-line tool - you can check the array status, configuration, etc.
via linux command line)
• hpaducli (Smart Array diagnostics utility command-line tool – to install with --nodeps just for cli)
• hp-health (you can get some hardware status data such as thermal, fan, power)
• hponcfg (Optional: HP On-line iLO CLI Configuration utility)
• hp-snmp-agents (Optional: HP server platform SNMP agents)

__________________________________________________________________
5.5 Editing /etc/hosts File

A node will at least have hostname for its own Internal LAN IP address and hostnames for its cluster
members' Internal LAN IP addresses.
If the node is a single-node cluster, a hostname is given to its External LAN interface, and it will have the
External LAN IP address set in cluster.info and samson.hostname.
If the node has a connection to SIGTRAN/SS7, the SG IP addresses should also be included.
The format is as follows:

<ip_address> <hostname> [<alias1> [<alias2> ... [<aliasN>]]]
On a node of a multi-node cluster, the hostname is assigned to its Internal LAN (samson LAN) with an
incrementing number. This makes it easier to identify the node when looking at channel logs and traces.
127.0.0.1 localhost.localdomain localhost localhost1 localhost2

::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
# Internal VLAN
10.100.192.36 smsc01
10.100.192.37 smsc02
10.100.192.38 smsc03
10.100.192.39 smsc04
10.100.192.40 smsc05
# STPs
10.164.17.71 stp1a
10.164.17.72 stp1b
10.164.18.71 stp2a
10.164.18.72 stp2b
The hostname command should return the hostname, and /etc/sysconfig/network should have the
HOSTNAME variable set to the hostname assigned to the Internal LAN.
[omn@smsc01 ~]$ cat /etc/sysconfig/network | grep HOSTNAME
NETWORKING=yes
HOSTNAME=smsc01
IPV6INIT=no
:
:

__________________________________________________________________
5.6 Identifying Physical LAN Devices

Identify each physical LAN port and take notes of its physical location.
root# ethtool -p <device>
where <device> is eth0, eth1, eth2, etc. Whilst this command is run, the identified port keeps flashing its
LED steadily. Once visually checked, press Ctrl+C on the keyboard to return to the prompt.
Check that the file /etc/udev/rules.d/70- persistent-net.rules defines the persistent device name
mapping.
5.7 Via Running configure-os-post-install.sh

A script configure-os-post-install.sh is available from /slingshot/sbe/LATEST/SRC, which automatically
attempts to:
1. Disable prelinking (/etc/prelink.conf)
2. Disable updatedb cronjob (/etc/cron.daily/mlocate.cron)
3. Disable some daemon processes (/etc/init.d)
4. Add fs.suid_dumpable (/etc/sysctl.conf)
5. Modify the number of inodes
6. Add limits to the number of open files (/etc/security/limits.conf)
7. Set the default runlevel to 3 (/etc/inittab)
8. Add a line for samson.sh (/etc/inittab)
9. Modify a mount option (/etc/fstab)
10. Modify the number of processes (/etc/security/limits.d/90-nproc.conf)
The script makes a backup copy of the existing files above by adding .bak suffix prior to editing them.
5.7.1 Running the Shell Script

1. Check that /etc/hosts has IP address/hostname of Internal LAN of each cluster node.
2. It is assumed that the USB key drive is mounted with the exec option. Check the mount command
output. If it is mounted with noexec option, just copy the script to /root.
3. To execute the post-install OS configuration script on the server, check the command-line syntax
first. Comments in the script also helps.
root# cd <script location>; ./configure-os-post-install.sh --help
4. Run the script as root.

root# ./configure-os-post-install.sh [OPTIONS]
5. Visually check the changes comparing files between before and after the changes, also viewing the
log file from the script, /root/configure-os-post-install-<hostname>.log"

__________________________________________________________________
5.7.2 Checking the Outcome via check-configure-post-os-install.sh

Once you finish runing check-configure-post-os-install.sh, you can run check-configure-post-os-install.sh,
which is also available from /slingshot/sbe/LATEST/SRC. It produces a file containing the current values in
the relevant files.
5.7.3 Post-OS-Install Configuration in Detail

This section describes each parameter that is modified when running the configure-os-post-install.sh script.
5.7.3.1 Disable Prelinking (/etc/prelink.conf)

Check the /etc/prelink.conf file to determine if prelinking is enabled on /sbin/ifconfig. If it is
enabled, use the -b flag before the ifconfig entry in /etc/prelink.conf to disable relinking. This is done by
adding the line to the bottom of /etc/prelink.conf as follows:
-b /sbin/ifconfig
Then as root run the prelink command:
prelink -u /sbin/ifconfig
5.7.3.2 Disable updatedb Cronjob (/etc/cron.daily/mlocate.cron)

Disable default updatedb nightly job, which can cause cluster splits, by commenting out the line with the
updatedb command in any of these files:
/etc/cron.daily/slocate.cron (No longer exists in AS5, but in AS3 and AS4.)
/etc/cron.daily/mlocate.cron
#/usr/bin/updatedb -f "nfs,.......
5.7.3.3 Disable Some Daemon Processes (/etc/init.d)

Stop and disable the following daemon processes as root:
sendmail iptables ip6tables avahi-dnsconfd avahi-daemon, and some others.
chkconfig <daemon> off

chkconfig --list <daemon>
service <daemon> stop
service <daemon> status
5.7.3.4 Modify /etc/sysctl.conf

• fs.suid_dumpable

__________________________________________________________________
Allow processes with SUID set to root to generate core dumps.

1. Check the current value.
root# sysctl -a | grep suid_dumpable
fs.suid_dumpable = 0
2. Change the current behaviour using the following command:
root# sysctl -w fs.suid_dumpable=1
Edit the /etc/sysctl.conf file to permanently set the behaviour by appending the following line
at the end of the file:
3. Run these commands to verify the set-up.
root# sysctl -p
• Add vm.max_map_count for Cassandra.

1. Edit the /etc/sysctl.conf to permanently set the parameter by appending the following line at the end
of the file.
vm.max_map_count = 131072
2. Run these commands to verify the set-up.

root# sysctl -p
root# sysctl -a | grep vm.max_map_count
5.7.3.5 Modify the Number of inodes

It is required to have the inode limit of the /apps, /data, /logs partitions increased. This change needs to be
done before any data is loaded to these partitions as the procedure results in the partition being wiped.
1. Check the amount of inodes available using the df command and note the device names.
df -i
Here is an example:
[root@tc1 ~]# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda6 5799936 209310 5590626 4% /
/dev/sda1 51200 48 51152 1% /boot
/dev/sdb1 100007936 44615 99963321 1% /apps
/dev/sdc1 100007936 287 100007649 1% /data

__________________________________________________________________
/dev/sdd1 100007936 287 100007649 1% /logs

tmpfs 8241542 1 8241541 1% /dev/shm
/dev/sda2 1048576 27 1048549 1% /tmp
/dev/sda3 1048576 5128 1043448 1% /var
2. Unmount the partitions.

umount /data
umount /apps
umount /logs
3. Run the following to re-create the file system with one hundred million inodes - if it's needed,
i.e. if the original number of inodes is less then one hundred million inodes.
4. Bear in mind that you must use the device names on your node that corresponds to /apps, /logs
and /data partitions respectively. Example commands are given below:
mkfs.ext4 /dev/cciss/c0d2p1 -N 100000000 -L /data
mkfs.ext4 /dev/cciss/c0d1p1 -N 100000000 -L /apps
mkfs.ext4 /dev/cciss/c0d3p1 -N 100000000 -L /logs
The procedure may take more than 15 minutes per partition and all data on the partitions will be lost.
5. Mount the partitions when all is done.
mount /data
mount /apps
mount /logs
5.7.3.6 Add Limits to the Number of Open Files and Procs (/etc/security/limits.conf)
Add the following lines to increase the maximum number of open flies and processes:
* soft nofile 100000

* hard nofile 100000
* soft nproc 32768
* hard nproc 32768
From 13Q3 onwards with RHEL6.3/CentOS6.3, some additional items are set to cater for Cassandra-based
message store.
* soft memlock unlimited
* hard memlock unlimited
* soft as unlimited

__________________________________________________________________
* hard as unlimited
The limit changes take effect on the next shell you start and onwards, but not the currently open shells.
Verify them by running ulimit -a on the new shell as omn.
omn% ulimit -a
NOTE:
Although these values relate to each individual server, nofiles and nproc values vary subject to the number
of cluster nodes and the maximum number of open ESME connections. It is advisable to adjust these
values manually afterwards.
5.7.3.7 Set the Default Runlevel to 3 (/etc/inittab)

Set the default runlevel to 3.
id:3:initdefault:
5.7.3.8 Upstart /etc/init/samson.conf

The Upstart mechanism replaces the /etc/inittab way of spawning processes.
1. Create the /etc/init/samson.conf file for Upstart as root on each node, which contains the following
lines. Depending on the adjacent LAN switch, you may need to add a sleep of 30 to 60 before the
“start on stopped rc ...” statement.
# samson - Openmind Networks

#
# Starts samson process
pre-start script
sleep 60
end script
start on stopped rc RUNLEVEL=[345]

stop on starting rc RUNLEVEL=[0126]
console output
respawn
respawn limit 5 120

__________________________________________________________________
exec /apps/omn/scripts/samson.sh
2. To activate the changes and start the samson process, run the following commands as root:
root# stop samson
root# status samson
root# start samson
root# ps –fu omn
5.7.3.9 Modify a Mount Option (/etc/fstab)

The noatime option is set on key disk partitions to turn off the OS atime options which resulted in
unnecessary disk writes for file reads. As root set this on the disk partions as follows:
mount -o remount,noatime /apps

mount -o remount,noatime /
mount -o remount,noatime /data
mount -o remount,noatime /logs
Also update the /etc/fstab file of the server for these disk partitions to have the noatime option set
instead of defaults, as follows:
LABEL=/ / ext4 noatime 1 1

LABEL=/apps /apps ext4 noatime 1 2
LABEL=/logs /logs ext4 noatime 1 2
LABEL=/data /data ext4 noatime 1 2
This will activate the options following a reboot or remount.
5.7.3.10 Modify the Number of Processes (/etc/security/limits.d/90-nproc.conf)

Disable the threshold of the maximum number of processes.
#* soft nproc 1024

__________________________________________________________________
6 Creating Bonded LAN Interfaces

This section describes bonded LAN configuration.
It is assumed that all Ethernet LAN interfaces are full-duplex Gigabit Ethernet at least for the Internal VLAN.
Using FastEthernet on the Internal VLAN is not supported since the intra-cluster communication requires the
bandwidth of Gigabit Ethernet.
6.1 Via Running setup-bonded-interfaces.sh

IMPORTANT
Remember to back up the original /etc/sysconfig/network-scripts directory prior to doing anything.
A script setup-bonded-interfaces.sh is available from /apps/omn/scripts, or alternatively,

/slingshot/sbe/LATEST/SRC, which automatically attempts to:
1. Modify /etc/sysconfig/network
2. Modify /etc/modprobe.d/bonding.conf
3. Create primary interface (/etc/sysconfig/network-scripts/ifcfg-ethX)
4. Create secondary interface (/etc/sysconfig/network-scripts/ifcfg-ethY)
5. Create bonding interface (/etc/sysconfig/network-scripts/ifcfg-bondN)
This script can create up to 4 bonded interfaces (bond0 to bond3)
6.1.1 Running the Shell Script

1. Prior to doing anything, create a back-up of vanilla /etc/sysconfig/network-scripts directory.
root# cd /etc/sysconfig
root# cp -rf network-scripts network-scripts.vanilla
2. It is assumed that the USB key drive is mounted with the exec option. Check the mount command
output. If it is mounted with noexec option, just copy the script to /root.
3. To execute the bonding configuration script on the server, check the command-line syntax first.
Comments in the script also helps.
root# cd <script location>; ./setup-bonded-interfaces.sh --help
4. Run the script as root.

root# ./setup-bonded-interfaces.sh [OPTIONS]
5. Visually check the changes. Refer to Appendix for details.

With the text editor vim, you might find the following approach easier to check the interface files in
this task. For example:
root# cd /etc/sysconfig/network-scripts

__________________________________________________________________
root# vim –O6 ifcfg-eth4 ifcfg-eth8 ifcfg-bond0 ifcfg-eth6 ifcfg-eth10 ifcfg-bond1
6. If your Kickstart script used a temporary Ethernet interface, put it back to factory default to disable it
(Refer to the one in vanilla).
7. Bounce the interfaces.
root# service network restart
8. Check the bonded interfaces. The output should be consistent with the parameters supplied in the
script. Refer to Appendix for details.
6.1.2 Bonded LAN Interface Configuration in Detail
6.1.2.1 Modify /etc/sysconfig/network

Edit the file to set the following:
NETWORKING=yes
NETWORKING_IPV6=no
IPV6INIT=no
HOSTNAME=<short hostname>
GATEWAY=<gateway ip>
6.1.2.2 Create /etc/modprobe.d/bonding.conf

Create the file to set the bonding alias.
alias <bonding IF> bonding
6.1.2.3 Create Primary Interface (/etc/sysconfig/network-scripts/ifcfg-ethX)

Refer to the example in Appendix.
6.1.2.4 Create Secondary Interface (/etc/sysconfig/network-scripts/ifcfg-ethY)

Refer to the example in Appendix.

__________________________________________________________________
6.2 Checking IP Connectivity

1. As root, run the following command to check that SELinux is disabled and firewall is disabled.
• sestatus
• /etc/init.d/iptables status
• chkconfig –list iptables
• /etc/init.d/ip6tables status
• chkconfig –list ip6tables
[root@smsc01 ~]# for n in `seq 153 164`; do ssh 172.21.202.$n sestatus ; done
root@172.21.202.153's password:
SELinux status: disabled
SELinux status: disabled
:
[root@smsc01 ~]# for n in `seq 153 164`; do ssh 172.21.202.$n /etc/init.d/iptables status
; done
Firewall is stopped.
Firewall is stopped.
:
[root@smsc01 ~]# for n in `seq 153 164`; do ssh 172.21.202.$n chkconfig –-list iptables ;
done
iptables 0:off 1:off 2:off 3:off 4:off 5:off 6:off
:
[root@smsc01 ~]#
2. Execute ping between each deployed server, both via Internal LAN and via External LAN. In a multi-
node deployment, it is a good idea to do this in a script file. For example,
#!/bin/bash
for n in `seq 153 164` ; do echo "###### 172.21.202.${n} #####" ; ping -c 3 172.21.202.$
{n} | grep packet ; done
for n in `seq 1 12` ; do echo "###### 172.16.10.${n} #####" ; ping -c 3 172.16.10.${n} |

grep packet ; done

__________________________________________________________________
3. Verifiy the bonding interface mode and status.
[root@smsc01 ~]# cat /proc/net/bonding/bond1

Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008)
Bonding Mode: fault-tolerance (active-backup)

Primary Slave: eth6 (primary_reselect always)
Currently Active Slave: eth6
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth10

MII Status: up
Link Failure Count: 0
Permanent HW addr: e8:39:35:0e:95:47
Slave Interface: eth6

MII Status: up
Link Failure Count: 0
Permanent HW addr: e8:39:35:0e:99:63

__________________________________________________________________
6.3 Adding Static IP Routes

Once the server is networked, you can configure additional static IP routes that may be required.
1. Edit and tailor the appropriate interface file in /etc/sysconfig/network-scripts/ifcfg-ethX for the
deployment. For example:
[root@smsc01 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth7

# Intel Corporation 82571EB Gigabit Ethernet Controller (Copper)
DEVICE=eth7
HWADDR=E8:39:35:0E:92:1A
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
PEERDNS=no
NM_CONTROLLED=no
ETHTOOL_OPTS="autoneg off speed 1000 duplex full"
IPADDR=172.21.128.123
NETMASK=255.255.255.0
2. To make static IP routes persistent, create a static route configuration file in /etc/sysconfig/network-
scripts. The filename is route-<interface> (route-eth7 for eth7), which contains address, netmask,
gateway and device name for each static route for the interface. For examle:
[root@smsc01 ~]# cat /etc/sysconfig/network-scripts/route-eth7

172.30.148.84/32 via 172.21.128.3 dev eth7
172.28.148.84/32 via 172.21.128.3 dev eth7
172.18.142.52/32 via 172.21.128.3 dev eth7
172.21.142.52/32 via 172.21.128.3 dev eth7
172.28.142.66/32 via 172.21.128.3 dev eth7
172.21.142.90/32 via 172.21.128.3 dev eth7
3. Run the following commands to make the changes permanent. For example, if the device is eth7,
root# cd /etc/sysconfig/network-scripts
root# ifdown eth7; ifup eth7
4. Run the netstat -rn command to verify the IP route table. For example:
[root@smsc01 ~]# netstat -rn

__________________________________________________________________
Kernel IP routing table

Destination Gateway Genmask Flags MSS Window irtt Iface
172.21.143.4 172.21.129.3 255.255.255.255 UGH 0 0 0 eth11
172.30.149.4 172.21.129.3 255.255.255.255 UGH 0 0 0 eth11
172.28.149.4 172.21.129.3 255.255.255.255 UGH 0 0 0 eth11
172.21.142.90 172.21.128.3 255.255.255.255 UGH 0 0 0 eth7
172.28.142.91 172.21.129.3 255.255.255.255 UGH 0 0 0 eth11
172.18.142.52 172.21.128.3 255.255.255.255 UGH 0 0 0 eth7
172.21.142.52 172.21.128.3 255.255.255.255 UGH 0 0 0 eth7
172.30.148.84 172.21.128.3 255.255.255.255 UGH 0 0 0 eth7
172.21.142.67 172.21.129.3 255.255.255.255 UGH 0 0 0 eth11
172.18.143.4 172.21.129.3 255.255.255.255 UGH 0 0 0 eth11
172.28.142.66 172.21.128.3 255.255.255.255 UGH 0 0 0 eth7
172.28.148.84 172.21.128.3 255.255.255.255 UGH 0 0 0 eth7
172.21.202.0 0.0.0.0 255.255.255.0 U 0 0 0 bond1
172.21.129.0 0.0.0.0 255.255.255.0 U 0 0 0 eth11
172.21.128.0 0.0.0.0 255.255.255.0 U 0 0 0 eth7
172.16.10.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth11
0.0.0.0 172.21.202.3 0.0.0.0 UG 0 0 0 bond1

__________________________________________________________________
6.4 Setting NTP Server

1. Edit the /etc/ntp.conf file on the node to include the following lines:
server <primary NTP server ip addr>

server <secondary NTP server ip addr>
restrict <primary NTP server ip addr> mask 255.255.255.255 nomodify notrap noquery
restrict <secondary NTP server ip addr> mask 255.255.255.255 nomodify notrap noquery
NOTE: The line for the secondary NTP server should not be included if there is only a single NTP
server.
2. To ensure that time does not go backwards, edit the file /etc/sysconfig/ntpd to add the option -x to
the OPTIONS flag. For example:
OPTIONS="-x -u ntp:ntp -p /var/run/ntpd.pid"
SYNC_HWCLOCK=yes
3. To immediately synchronise the clock, run the ntpupdate command as root, which will set the date
and time to that of the NTP server specified.
root# ntpdate -u <ip address of NTP server>
4. Start ntpdate as daemon.

root# service ntpdate start
5. Set ntpdate for automatic start at boot time.

root# chkconfig --level 345 ntpdate on
6. Restart ntpd.
root# service ntpd restart
7. To check where your time is being synchronised from, use this command:
root# ntpq -p
remote refid st t when poll reach delay offset jitter
==========================================================================
*ntp.telecoms-company.com LOCAL(0) 11 u 754 1024 377 0.256 0.048 0.019
If the jitter value shown is not equal to 4000.00, then this means that synchronisation has been
successful.
There is also a file called /etc/ntp/ntpservers listing the NTP servers which the server can use. In the
system boot sequence, the NTP service may try to connect to the NTP servers in this file in the order
they appear. By default, clock.redhat.com and clock2.redhat.com are the first two entries in this file.
The boot program will report that NTP synchronisation failed when it fails to connect to
clock.redhat.com, even though the NTP synchronisation would succeed with the NTP server(s)
specified in /etc/ntp.conf.
It is best to remove these redhat.com entries from this file.
8. Check on which run-levels the ntpd service will be active by the chkconfig command.
root# chkconfig --list ntpd
If it is not ON for run-level 3 and 5, run the command to update the activation run-levels.

__________________________________________________________________
root# chkconfig --level 345 ntpd on
9. Restart the NTP deamon, and check if ntpd is up and running.

root# service ntpd restart; service ntpd status

__________________________________________________________________
7 Appendix A: Kickstart Parameters

The following example illustrates a generated Kickstart script. Note that the Package Selection section
needs to be replaced with the one in CVS.
#version=RHEL6.3
install
cdrom
lang en_US.UTF-8
keyboard us
timezone Europe/Dublin
rootpw --iscrypted
$6$Hrnktaxxc0SkfWO7$9Rtdk4rJOTYCKI4iWcqLNHrqgIK3u.oFXLqt/EIgm4WrGBv1/vsyDpi8U54.tl1wk.kBA
nYgrME920b170VsF0
authconfig --enableshadow --passalgo=sha512 –enablefingerprint
#network --device=eth6 --onboot=yes --bootproto=static --ip=192.168.128.219

--netmask=255.255.255.0 --gateway=192.168.128.254 --noipv6
firewall --disabled
selinux --disabled
reboot
bootloader --location=mbr –-driveorder=sdb,sdc,sdd,sde --append="crashkernel=auto rhgb

quiet"
clearpart -–all --initlabel –-drives=sdb,sdc,sdd,sde
part /boot --fstype=ext4 --size=100 --ondisk=sdb --asprimary
part /var --fstype=ext4 --size=16384 --ondisk=sdb
part /tmp --fstype=ext4 --size=16384 --ondisk=sdb
part swap --fstype=swap --size=16384 --ondisk=sdb
part / --fstype=ext4 --size=1 --grow --ondisk=sdb
part /apps --fstype=ext4 --size=1 --grow --ondisk=sdc
part /data --fstype=ext4 --size=1 --grow --ondisk=sdd
part /logs --fstype=ext4 --size=1 --grow --ondisk=sde
repo --name="Red Hat Enterprise Linux" --baseurl=file:///mnt/source/ --cost=100
%packages
@Base
@Core

__________________________________________________________________
@base
:
:
vsftpd
%end
Table 7.1: Kickstart Parameters

Parameter Arguments Values Notes
install N/A
cdrom
lang en_US.UTF-8 N/A
keyboard <layout> N/A Keyboard layout
timezone <local_time_zone>
rootpw --iscrypted <encrypted_password>
authconfig --enableshadow N/A

--passalgo=sha512 N/A
--enablefingerprint N/A
network --device= <device> One of the interfaces for

--onboot= yes External LAN
--bootproto= static
--ip= <ip_addr>
--netmask= <subnet_mask>
--gateway= <gw_addr>
--noipv6 N/A
firewall --disabled N/A
selinux --disabled N/A
reboot N/A
bootloader --location= mbr

--driveorder= <drv1,drv2,...,drvN> The logical device name subject
to the Smart Array Controller
configuration
--append= "crashkernel=auto rhgb
quiet"
clearpart --initlabel N/A

--drives= <drv1,drv2,...,drvN>

__________________________________________________________________
Parameter Arguments Values Notes
part <mount point> N/A

--fstype= ”ext4” or “swap”
--size= <size in MB>
--grow N/A
--ondisk= <device>
--asprimary N/A To make /boot primary
repo --name= <string>

--baseurl= file:///mnt/source
--cost= 100

__________________________________________________________________
8 Appendix B: Default Partition Layouts
8.1 SMS Router, SMS Hub, Standalone BMS

Table 8.1: Default Partitions for SMS Router, SMS Hub, BMS
Physical Logical Hard Disc Partition FS Type On Disc Size (MB)
Drives Drive Size
2x 146GB 0 146GB /boot ext4 sdb 200
/var ext4 sdb 16384
/tmp ext4 sdb 16384
swap swap sdb <100% the size of

RAM>
/ ext4 sdb Fill the max

allowed size
2x 146GB 1 146GB /apps ext4 sdc Fill the max

allowed size
2x 146GB 2 146GB /data ext4 sdd Fill the max

allowed size
2x 146GB 3 146GB /logs ext4 sde Fill the max

allowed size
8.2 SMS Router, SMS Hub, Standalone BMS - Cassandra with 10 disks
Table 8.2: Default Partitions for SMS Router, SMS Hub, BMS - Cassandra with 10 disks layout
Drives Drive Size
/var ext4 sdb 16384
/tmp ext4 sdb 16384
swap swap sdb <100% the size of

RAM>
/ ext4 sdb Fill the max

allowed size
2x 146GB 2 146GB /apps ext4 sdc Fill the max

allowed size

__________________________________________________________________

Drives Drive Size
2x 146GB 3 146GB /data ext4 sdd Fill the max

allowed size
2x 146GB 4 146GB /logs ext4 sde Fill the max

allowed size
2x 146GB 5 146GB /commit ext4 sdf Fill the max

allowed size
8.3 Standalone Assure

Table 8.3: Default Partitions for Standalone Assure
Drives Drive Size
/var ext4 sdb 16384
/tmp ext4 sdb 16384
swap swap sdb <100% the size of RAM>
/ ext4 sdb 32768
/apps ext4 sdb Fill the max allowed size
2x 146GB 2 146GB /logs ext4 sdc Fill the max allowed size
6x 1TB 3 3TB /assuredb ext4 sdd Fill the max allowed size
8.4 Standalone Care

Table 8.4: Default Partitions for Standalone Care
Drives Drive Size
/var ext4 sdb 16384
/tmp ext4 sdb 16384
/ ext4 sdb 32768

__________________________________________________________________

Drives Drive Size
/apps ext4 sdb Fill the max allowed size
2x 146GB 2 146GB /logs ext4 sdc Fill the max allowed size
12x 1TB 3 6TB /caredb ext4 sdd Fill the max allowed size
8.5 Co-located Assure/Care

Table 8.5: Default Partitions for Co-located Assure/Care
Physical Logical Available Partition FS Type On Disc Size (MB)
Drives Drive Space
/var ext4 sdb 16384
/tmp ext4 sdb 8192
/ ext4 sdb Fill the max allowed size
2x 146GB 2 146GB /apps ext4 sdc 65536
/logs ext4 sdc Fill the max allowed size
6x 1TB 3 3TB /caredb ext4 sdd Fill the max allowed size
6x 1TB 4 3TB /assuredb ext4 sde Fill the max allowed size

__________________________________________________________________
9 Appendix C: Example Bonded LAN Interface Files

Attached below is an example of the three interface files that form a bonded interface:

DEVICE=eth4
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
PEERDNS=no
NM_CONTROLLED=no
MASTER=bond0
SLAVE=yes

DEVICE=eth8
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
PEERDNS=no
NM_CONTROLLED=no
MASTER=bond0
SLAVE=yes
[root@smsc01 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0

DEVICE=bond0
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
PEERDNS=no
NM_CONTROLLED=no
IPADDR=10.0.0.1
NETMASK=255.255.255.0
BONDING_OPTS="mode=1 primary=eth4 miimon=100"

__________________________________________________________________
10 Appendix D: How to Change hostname in OS

If you need to change hostname of a node manually, perform the following steps:
1. To set it to a new hostname, run the command as root:
root# hostname <new_hostname>
2. Edit the /etc/sysconfig/network file to set the new hostname as root.

HOSTNAME=<new_hostname>
3. Edit the /etc/hosts to set the new hostname as root.

__________________________________________________________________
11 Glossary
Terms Description
A-party, A-number Message Sender

Ack Acknowledgement
AO Application Originated
AS Application Server
ASP Application Server Process

AT Application Terminated
ATI Any Time Interrogation

B-party, B-number Message Receiver
BMS Bulk Messaging System

BSC Base Station Controller
BTS Base Transmission Station

CCN Charging Control Node
CDMA Code Division Multiple Access

CDR Call Detail Record
CdPA SCCP Called Party Address

CgPA SCCP Calling Party Address
DA Destination Address
DPC Destination Point Code
FPLMN Foreign (non-Home) PLMN

FSMSC Foreign (non-Home) PLMN
GMSC Gateway MSC

GSM Global System for Mobile Communications
GT Global Title
HLR Home Location Register
HPLMN Home PLMN

HR Home Routing
IMEI International Mobile station Equipment Identity

IMSI International Mobile Subscriber Identity

__________________________________________________________________
Terms Description
IP Internet Protocol
IWMSC Interworking MSC

LAN Local Area Network
LDAP Light-weight Directory Access Protocol

LMSI Local Mobile Subscriber Identity
M3UA MTP3 User Adaptation Layer

MAP Mobile Application Part
MCC Mobile Country Code

MNC Mobile Network Code
MNP Mobile Number Portability

MNP-SRF Signalling Relay Function for support of MNP
MO Mobile Originated
MO-FSM Mobile Originated Forward Short Message
MOS Message Operating System

MS Mobile Station
MSC Mobile Switching Centre

MSISDN Mobile Station ISDN Number
MT Mobile Terminated
MT-FSM Mobile Terminated Forward Short Message
MTP3 Message Transfer Part Layer 3

Nack Negative Acknowledgement
NCC Network Country Code

NDC National Destination Code
NI Network Indicator
OA Originator Address
OCS On-line Charging System

OLO Other Local Operator
OMN OpenMind Networks

OPC Originator Point Code
PC Point Code

__________________________________________________________________
Terms Description
PLMN Public Land Mobile Network
P Nack Permanent Nack

PSI Provide Subscriber Information
PSU Power Supply Unit

Qrelease Quarterly Release
rc Routing Context
Req Request
Resp, Rsp Response

RN Routing Number
SC (Short Messaging) Service Centre

SCA Service Centre (Presentation) Address
SCCP Signalling Connection Control Part

SCP Service Control Point
SCTP Stream Control Transmission Protocol

SG Signalling Gateway
SGP Signalling Gateway Process

SIGTRAN Signal Transport
SIM Subscriber Identity Module

SMRL Short Message Relay Layer
SMS Short Messaging Service

SMSC Short Messaging Service Centre
SMSR Short Messaging Service Router

SMTL Short Message Transport Layer
SN Subscriber Number
SNMP Simple Network Management Protocol
SPC Signalling Point Code

SRI-SM Send Routing Information for Short Message
SS7 Signalling System No. 7

SSP Signalling Switching Point
STP Signalling Transfer Point

__________________________________________________________________
Terms Description
TC Traffic Control
TCAP Transaction Component Application Part

TCP Transmission Control Protocol
TMSI Temporary Mobile Subscriber Identity

T Nack Temporary Nack
TT Translation Type
VLR Visited Location Register
VLAN Virtual Local Area Network

VMSC Visited Mobile Switching Centre
VT Virtual Terminal
WAN Wide Area Network


Redhat El6.3 and Centos 6.3 Installation Configuration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Redhat El6.3 and Centos 6.3 Installation Configuration Guide

Uploaded by

Copyright:

Available Formats

RedHat EL6.3 and CentOS 6.

3 ICG for Traffic Control

RedHat EL6.3 and CentOS 6.3

© Openmind Networks Limited 2014 Commercial in Confidence

4 Installing Operating System.......................................................................................12

© Openmind Networks Limited 2014 Commercial in Confidence

5.7.3.7 Set the Default Runlevel to 3 (/etc/inittab)........................................................................................... 23

6 Creating Bonded LAN Interfaces...............................................................................25

7 Appendix A: Kickstart Parameters.............................................................................33

8 Appendix B: Default Partition Layouts......................................................................36

9 Appendix C: Example Bonded LAN Interface Files..................................................39

10 Appendix D: How to Change hostname in OS..........................................................40

© Openmind Networks Limited 2014 Commercial in Confidence

© Openmind Networks Limited 2014 Commercial in Confidence

Table 1: Document Change History

1.0a 18/04/13 Tom Suzuki Initial Draft created.

1.1 16/07/13 Tom Suzuki Updated Section 5.7.2.6 for /etc/security/limits.conf

1.7 22/04/14 Tom Suzuki ntpdate updated in Section 6.4

© Openmind Networks Limited 2014 Commercial in Confidence

© Openmind Networks Limited 2014 Commercial in Confidence

1.3 How This Document Is Organised

Heading: Each top-level and optionally second-level document heading is accompanied

Links to References: Hyperlinks to documents or articles are inserted to help referencing.

Glossary: Glossary is provided at the end of this document.

Annotations: Balloon Comments may be used to add comments and clarification in

No. Document Title, Version, ID, Date Author,Issuer

[1] RedHat Red_Hat_Enterprise_Linux-6-Installation_Guide-en- RedHat

[3] CentOS Website www.centos.org CentOS

[5] Red Hat Enterprise Linux 6 6.3 Release Notes RedHat

© Openmind Networks Limited 2014 Commercial in Confidence

Overall, the task is composed of the following steps:

© Openmind Networks Limited 2014 Commercial in Confidence

3.1 Configuring RAID Controller

© Openmind Networks Limited 2014 Commercial in Confidence

Logical Single Box 8-bay Small-Form Factor Storage Cage

Logical Box 1 Box 2 16-bay Small-Form Factor Storage Cage

Logical Single Box 25-bay Small-Form Factor Storage Cage

3 Bay 6,7,8 Bay 11,12,13

© Openmind Networks Limited 2014 Commercial in Confidence

3.2 Setting BIOS Date and Time

© Openmind Networks Limited 2014 Commercial in Confidence

4 Installing Operating System

4.1 Script-driven Method

4.1.2 Preparing the Kickstart Scripts

4.1.3 Making Software and Scripts Available on USB Key Drives

© Openmind Networks Limited 2014 Commercial in Confidence

4.1.4 Booting with Kickstart Script

and hit return.

© Openmind Networks Limited 2014 Commercial in Confidence

4.2 Full Manual Method

4.2.2 Booting from OS DVD

4.2.3 RPMs to Install

© Openmind Networks Limited 2014 Commercial in Confidence

© Openmind Networks Limited 2014 Commercial in Confidence

4.3 RPMs to Remove

2. If it does exist, remove it.

3. Double-check that it was removed.

4.4 Extra OS RPMs to Install

4.5 Disabling SELinux

4.6 Disabling NetworkManager

1. Run the service commands:

2. Run chkconfig commands to keep it disabled at boot time.

© Openmind Networks Limited 2014 Commercial in Confidence