Академический Документы
Профессиональный Документы
Культура Документы
__________________________________________________________________
Date: 22/02/19
Version: 2.8
Author: OMN
Table of Contents
1 Introduction....................................................................................................................8
1.1 Objective................................................................................................................................................. 8
1.2 Audience................................................................................................................................................. 8
1.3 How This Document Is Organised.......................................................................................................... 9
1.4 References............................................................................................................................................. 9
2 Overall Steps................................................................................................................10
4 Commissioning Hardware...........................................................................................17
4.1 HP ProLiant DL380p Gen8 Server........................................................................................................ 17
4.1.1 Setting BIOS Date and Time............................................................................................................................ 17
4.1.2 Configuring Smart Array RAID Logical Drives.................................................................................................17
4.2 HP ProLiant DL380 Gen9 Server.......................................................................................................... 20
4.2.1 Selecting BIOS as Boot Mode......................................................................................................................... 20
4.2.2 Setting BIOS Date and Time............................................................................................................................ 20
4.2.3 Configuring Smart Array RAID Logical Drives.................................................................................................21
19 Glossary........................................................................................................................60
List of Tables
Copyright Notice
Copyright © Openmind Networks Limited, 2019. 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.
1.1 27/03/15 Tom Suzuki Updated with USB key drive preparation, rpm package
lists, additional Kickstart details, how to change
hostname/default gateway, persistent bonding
configuration.
1.2 31/03/15 Tom Suzuki Re-organised with a section for DVD-less method of OS
installation. Updated with new HP rpm names.
1.5 15/04/15 Tom Suzuki Font changed to courier Freemono to avoid copy-and-
paste anomalies caused by its exported PDF.
1.6 17/04/15 Tom Suzuki Added a list of services to stop and disable.
1.7 11/08/15 Tom Suzuki Updated to cover CentOS 7.0 and CentOS 7.1 on HP
ProLiant DL380p Gen8 Server and HP ProLiant DL380
Gen9 Server.
1.8 15/09/15 Tom Suzuki Typo in Figure 4.7 corrected.
2.5 16/05/16 Tom Suzuki Updated the initial root password management during
deployment.
2.6 07/06/16 Tom Suzuki Updated for the new hardware profile on HP DL380 G9.
2.7 12/04/18 Tom Suzuki Updated for SCTP kernel module and TCP max queue.
2.8 22/02/19 Tom Suzuki Updated to add lines for enabling samson.service
1 Introduction
1.1 Objective
This document describes the method of installing the following operating systems for the Openmind's Traffic
Control product suite:
• CentOS 7.0 x86_64 (64-bit) with required 32-bit libraries - CentOS Linux release 7.0.1406 (Core)
• CentOS 7.1 x86_64 (64-bit) with required 32-bit libraries - CentOS Linux release 7.1.1503 (Core)
1.2 Audience
The document is intended for all stakeholders involved in design, integration, approval and implementation of
the OMN product. This document assumes that the installation engineer has a good understanding of
computer in general, Linux operating system and the Internet technologies.
Input Notes: Notes for assisting input is adhered in Italic, smaller font size.
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
2 Overall Steps
This section illustrates the overall steps to complete OS software installation on the Openmind's product
platform.
The Kickstart script should allow OS installation with no intermediate interactive step. It is recommended
that OS installation and configuration should 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.
3.1 Prerequisites
There are two ways of installing the OS. The preferred method uses a USB key drive only. In case the
server platform has difficulty in this method, the traditional method using OS DVD is also described in
Appendix.
IMPORTANT
It is important that you issue the "sync" command on the terminal before un-mounting the USB key
drive filesystems in order to flush any data yet to be physically written to the drive. If the USB key
drive fails to boot the server or the OS installation process gets stuck at some stage, it is very likely that any
files on the USB key drive did not get written completely onto it.
Here, you format a 16GB USB key drive into 2 partitions; one in FAT32 LBA, labelled "KSBOOT", and the
other in ext4, labelled "OS".
1. Download the OS Everything.iso file and its sha256sum.txt from the CentOS website [3].
2. Whilst downloading the iso files, insert the 16GB USB key drive to prepare onto a linux computer.
3. Check the device name of the USB key drive by running dmesg. A line like below is present in the
output (sdX, where X is an alphabet):
[810211.629614] sd 101:0:0:0: [sdc] Attached SCSI removable disk
4. Run fdisk.
root# fdisk /dev/sdX
5. At the command prompt, select:
m to print help menu.
d to delete a partition .
l to list known partition types .
n to add a new partition (Accept default choices for type, number and first sector. Enter +250M for
size 250MB).
p to print the partition table.
t to change a partition type (c for FAT32 LBA).
a to make bootable.
n to add another new partition (Accept default choices for type, nmber, first sector and size)
p to print the partition table.
w to write table to disk and exit , or q to quit without saving changes .
6. Format the partitions.
root# mkfs.vfat -n "KSBOOT" /dev/sdX1
root# mkfs.ext4 -L "OS" /dev/sdX2
7. Write MBR data to the device.
root# dd conv=notrunc bs=440 count=1 if=/usr/share/syslinux/mbr.bin
of=/dev/sdX
8. Install syslinux to the partition 1.
root# syslinux /dev/sdX1
9. Create a mount point directory (if not yet done so) for the USB key drive.
root# mkdir -p /media/ksboot /media/os
10. Mount the USB key drive partitions (Note the partition number after the device name).
root# mount -t vfat /dev/sdX1 /media/ksboot
root# mount -t ext4 /dev/sdX2 /media/os
11. Print the mount table.
root# mount
:
:
/dev/sdd2 on /media/os type ext4
(rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)
/dev/sdd1 on /media/ksboot type vfat
(rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0077,codepage
=437,iocharset=ascii,shortname=mixed,showexec,utf8,flush,errors=remount-
ro,uhelper=udisks2)
Based on Predictable Network Device Naming Scheme, the LAN interface ports are persistently assigned
the following port names. However, please bear in mind that the order differs between Gen8 and
Gen9, as shown below:
3 2 1 0
-------------------------------------
Slot1 (Top) | ens1f3 | ens1f2 | ens1f1 | ens1f0 |
-------------------------------------
Slot2 (Mid) | ens2f3 | ens2f2 | ens2f1 | ens2f0 |
-------------------------------------
Slot3 (Bot) | ens3f3 | ens3f2 | ens3f1 | ens3f0 |
-------------------------------------
-------------------------------------
Motherboard | eno4 | eno3 | eno2 | eno1 |
-------------------------------------
0 1 2 3
-------------------------------------
Slot1 (Top) | ens1f0 | ens1f1 | ens1f2 | ens1f3 |
-------------------------------------
Slot2 (Mid) | ens2f0 | ens2f1 | ens2f2 | ens2f3 |
-------------------------------------
Slot3 (Bot) | ens3f0 | ens3f1 | ens3f2 | ens3f3 |
-------------------------------------
-------------------------------------
Motherboard | eno1 | eno2 | eno3 | eno4 |
-------------------------------------
4 Commissioning Hardware
This section describes the method of commissioning the hardware platform.
NOTE
The BIOS set-up should remain the default factory set-up except for BIOS date and time, where Power
management policy is set for "Balanced power usage" by default, and you should not enable "Power
Efficient" features, which may unnecessarily reduce the server performance affecting the general service
operation of the server or the cluster.
6 View the logical drives. If all is OK, exit the Smart Array
Controller configuration menu.
7 If the server comes with another Smart Array Controller, wait
for another prompt. Press F8 when prompted.
8 Configure the logical drives in the menu. Make sure that you If there are four or more physical
delete any logical drive that may exist from manufacturer's drives in a logical drive, RAID10
assembly. should be selected.
9 View the logical drives. Do not mark the primary boot volume
here. If all is OK, exit the Smart Array Controller configuration
menu.
NOTE
Standard configuration with Cassandra.
2 Bay 3 + Bay 4
3 Bay 6,7,8 + Bay 11,12,13
NOTE
The BIOS set-up should remain the default factory set-up except for BIOS date and time, where Power
management policy is set for "Balanced power usage" by default, and you should not enable "Power
Efficient" features, which may unnecessarily reduce the server performance affecting the general service
operation of the server or the cluster.
2 Go to "Exit and launch HP Smart Storage Administrator There will be an embedded GUI
(HPSSA)". application starting up for HP SSA.
3 Select "HP Smart Storage Administrator" before the screen
times out.
10 When all physical drives are assigned, you are brought back to
the "Actions" screen. Select "Set Bootable Logical
Drive/Volume".
11 Select "Local - Logical Drive 1" for Primary Boot Logical
Drive/Volume (where /boot is assigned). Select "None" for
Secondary Boot Logical Drive/Volume.
2 Bay 3 + Bay 4
3 Bay 5 + Bay 6
4 Bay 7 + Bay 8
5 Bay 9 + Bay 10
NOTE
Standard configuration with Cassandra for Messaging Router/Hub
1 Bay 1 + Bay 2
2 Bay 3 + Bay 4
3 Bay 5 + Bay 6
NOTE
Standard configuration with Cassandra for standalone ASSURE/standalone CARE
2 Bay 3 + Bay 4
3 Bay 5 + Bay 6
4 Bay 7 + Bay 8
NOTE
Standard configuration with Cassandra for co-located ASSURE/CARE
The hardware agreed in Bill of Materials (BOM) must be rack-mounted and cabled according to the
installation documents accompanying the hardware and the System Architecture Description (SAD).
NOTE: The objective is to install the version of the OS specified here, but not to update the base line.
DO NEVER run 'yum update' afterwards.
NOTE
On a node in a multi-node cluster, the hostname assigned to its Internal VLAN (samson LAN) is called
samson hostname. With the last letter being unique, a number or an alphabet in ascending order, it is used
to identify the node in the cluster, and it also helps to identify nodes when looking at channel logs and
traces.
If the node is a single-node cluster, the samson hostname is given to its External VLAN interface, and it will
have the External VLAN IP address set in cluster.info.
For example:
127.0.0.1 localhost.localdomain localhost localhost1 localhost2 omnldap
omnbms
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
# Internal VLAN
10.100.192.31 tcsms01
10.100.192.32 tcsms02
10.100.192.33 tcsms03
10.100.192.34 tcsms04
# 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 assigned to External VLAN interface (not the Internal
VLAN interface), and the /etc/hostname file should have the hostname in it (Cassandra may not start up
correctly if it is set to an Internal LAN hostname).
2. Bring the rpms over to the server using the USB key driver, and update tzdata and tzdata-java rpm
packages.
root# rpm -U tzdata-<version>.el7.noarch.rpm tzdata-java-<version>.el7.noarch.rpm
9. After the period of drive rebuild, run hpacucli to check the drive status.
root# hpacucli ctrl all show config > /tmp/hpacucli.out
NOTE
It is assumed that all Ethernet LAN interfaces are full-duplex Gigabit Ethernet. Using FastEthernet is not
supported.
[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
root@172.21.202.154's password:
SELinux status: disabled
:
[root@smsc01 ~]# for n in $(seq 153 164); do ssh 172.21.202.$n systemctl status
iptables ; done
iptables.service - IPv4 firewall with iptables
Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled)
Active: inactive (dead)
:
[root@smsc01 ~]# for n in $(seq 153 164); do ssh 172.21.202.$n systemctl status
ip6tables ; done
ip6tables.service - IPv6 firewall with ip6tables
Loaded: loaded (/usr/lib/systemd/system/ip6tables.service; disabled)
Active: inactive (dead)
:
[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
3. Verifiy the bonding mode and status of each configured bonded interface (bond0, bond1, etc.).
1. Edit and tailor the appropriate interface file in /etc/sysconfig/network-scripts/ifcfg-enoW and ifcfg-
ensXfY for the deployment. Please note that "autoneg on" instead of "off" is mandatory according to
IEEE802.3ab (1000Base-T).
For example:
2. To make static IP routes persistent, create a static route configuration file in /etc/sysconfig/network-
scripts/. The filename is route-<interface> (route-ens1f2 for ens1f2, route-bond1 for bond1), which
contains address, netmask, gateway and device name for each static route for the interface. For
example:
3. Run the following commands to make the changes permanent. For example, if the device is ens1f3,
root# cd /etc/sysconfig/network-scripts
root# ifdown ens1f3; ifup ens1f3
4. Run the netstat -rn command to verify the IP route table. For example:
The line for the secondary NTP server should not be included if there is only a single NTP server.
3. 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
4. Enable and start ntpd.service.
root# systemctl enable ntpd.service
root# systemctl start ntpd.service
5. Check the status of the service.
root# systemctl status ntpd.service
6. Execute ntpq -p to check where your server is synchronised to.
root# ntpq -p
remote refid st t when poll reach delay offset
jitter
==========================================================================
====
*ntp.telecoms.com 192.168.11.1 4 u 593 1024 377 0.458 3.439
2.785
If the jitter value shown is not equal to 4000.00, 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.
7. Restart the NTP deamon, and check if ntpd is up and running.
root# systemctl restart ntpd.service
8.1 SMS Router, SMS Hub, Standalone BMS - Cassandra with 10 disks
Table 8.1: Default Partitions for SMS Router, SMS Hub, BMS - Cassandra with 10 disks layout
Physical Logical Hard Disc Partition FS Type On Disc Size
Drives Drive Size
2x 300GB 2 300GB /logs ext4 sdb Fill the max allowed size
6x 1TB 3 3TB /assuredb ext4 sdc Fill the max allowed size
2x 300GB 2 300GB /logs ext4 sdb Fill the max allowed size
12x 1TB 3 6TB /caredb ext4 sdc Fill the max allowed size
6x 1TB 3 3TB /caredb ext4 sdc Fill the max allowed size
6x 1TB 4 3TB /assuredb ext4 sdd Fill the max allowed size
nss-util.i686
openldap.i686
openssl098e.i686
openssl-devel.i686
openssl-libs.i686
pcre-devel.i686
pcre.i686
pkgconfig.i686
popt.i686
readline.i686
sqlite.i686
xz-libs.i686
zlib-devel.i686
zlib.i686
#version=RHEL7
firewall --disabled
selinux --disabled
ignoredisk --only-use=sda,sdb,sdc,sdd,sde
bootloader --append="crashkernel=auto rhgb quiet" --location=mbr --boot-
drive=sda
clearpart --all --initlabel --drives=sda,sdb,sdc,sdd,sde
%packages
<Package groups here>
# Get these required i686 rpm packages from CentOS 7.0 Everything iso image.
<Required i686 packages here>
%end
%end
#/usr/bin/updatedb -f "nfs,.......
Edit the /etc/sysctl.conf file to permanently set the behaviour by appending the following line at the end of the
file:
fs.suid_dumpable = 1
root# sysctl -p
root# sysctl -a | grep suid_dumpable
1. Edit /etc/sysctl.conf to permanently set the following parameters by adding the following lines:
net.ipv4.tcp_max_syn_backlog = 4096
net.core.somaxconn = 4096
blacklist sctp
install sctp /bin/true
The first line blacklists the module and the second line makes sure that it is never loaded even as a
dependency of another module.
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 root and omn (when OMN software has been installed).
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 may be necessary to adjust
these values manually afterwards.
List the /etc/systemd/system directory should show the default .target is linked to multi-user.target
lrwxrwxrwx. 1 root root 41 Aug 6 15:00 default.target -> /usr/lib/systemd/system/multi-user.target
[Unit]
Description="Traffic Control MessageOS samson"
After=network.target
[Service]
ExecStart=/apps/omn/scripts/samson.sh
Type=simple
Restart=always
[Install]
WantedBy=multi-user.target
2. Then, enable the samson service so that samson will be automatically started upon OS reboot.
root# systemctl enable samson.service
Also update the /etc/fstab file of the server for these disk partitions to have the noatime option set instead of
defaults. This change will take effect after a reboot or remount.
12.1 Prerequisites
NOTE
You do not create a data DVD with the image file, but you burn the DVD image to disc.
# DIAMETER - secondary
GATEWAY1=10.100.81.97
NETMASK1=255.255.255.255
ADDRESS1=10.200.113.4
# SMPP-GW
GATEWAY3=10.100.81.97
NETMASK3=255.255.255.128
ADDRESS3=10.100.80.0
# DIAMETER - secondary
GATEWAY1=10.100.81.97
NETMASK1=255.255.255.255
ADDRESS1=10.200.113.4
# SMPP-GW
GATEWAY3=10.100.81.97
NETMASK3=255.255.255.128
ADDRESS3=10.100.80.0
GATEWAY1=10.100.81.161
NETMASK1=255.255.255.255
ADDRESS1=10.100.145.71
GATEWAY2=10.100.81.161
NETMASK2=255.255.255.255
ADDRESS2=10.100.145.72
15.1 Hostname
• To print the system date/time and hardware clock in the same format
date '+%a %d %b %Y %r %Z' ; /sbin/hwclock --show
• To set date and time
root# date -s "03/15/2014 17:06:00"
• To set hardware clock in UTC and show it
root# /sbin/hwclock --utc --systohc; /sbin/hwclock --show
Keyboard layout can be changed using the localectl command below for virtual console and/or X11 layout.
localectl list-keymaps
localectl status
localectl set-keymap --no-convert <keymap>
localectl set-x11-keymap --no-convert <keymap>
1. Download the source RPM for the kernel module source RPM (for example, rpm -ivh /media/usb/hp-
tg3-3.125g-2.src.rpm) from HP Support Software Download website [1], and save it in a usb key
drive.
2. Create a mount point directory (if not yet done so) and mount the usb key and OS DVD on the
platform server. It may or may not auto-mount. If it does not, create the mount directories and
mount them.
mkdir -p /media/dvd /media/usb
mount -t iso9660 /dev/cdrom /media/dvd
mount -t ext4 <device> /media/usb
The device name looks like /dev/sdf1. The actual device can be found in the output of lsblk or on a
virtual console.
3. Make a directory.
mkdir -p /usr/src/redhat/SOURCES
4. Install the src rpm.
rpm -ivh /media/usb/hp-tg3-3.125g-2.src.rpm
5. Install some i686 (32-bit) RPM packages from OS DVD, which are required for compiling source
code and build a deliverable RPM.
cd /media/dvd/Packages
rpm -ivh <rpm_file>
where <rpm_file> is:
redhat-rpm-config
kernel-devel
kernel-PAE-devel
elfutils-libs
elfutils
rpm-build
kernel-headers
glibc-headers
glibc-devel
gcc
libgomp
12. The /sys/class/net/ directory should have all the network interface devices listed.
ls /sys/class/net/
13. Check that the kernel module is loaded.
lsmod | grep tg3
19 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
HR Home Routing
IMEI International Mobile station Equipment Identity
Terms Description
IP Internet Protocol
IWMSC Interworking MSC
MO Mobile Originated
MO-FSM Mobile Originated Forward Short Message
MT Mobile Terminated
MT-FSM Mobile Terminated Forward Short Message
NI Network Indicator
OA Originator Address
Terms Description
PC Point Code
PCIe Peripheral Component Interconnect Express
RN Routing Number
SC (Short Messaging) Service Centre
SG Signalling Gateway
SGP Signalling Gateway Process
Terms Description
TC Traffic Control
TCAP Transaction Component Application Part