OS InstallationConfigurationGuide COS 7.0 7.1

Installation Configuration Guide ICG for Traffic Control
__________________________________________________________________
Installation Configuration Guide

CentOS 7.0/CentOS 7.1
for Openmind's Traffic Control

on HP ProLiant DL380p Gen8 Server
and HP ProLiant DL380 Gen9 Server
Date: 22/02/19
Version: 2.8
Author: OMN
© Openmind Networks Limited 2019 Commercial in Confidence

Version 2.8 1 of 63
__________________________________________________________________
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
3 Getting the Necessary Tools.......................................................................................11

3.1 Prerequisites......................................................................................................................................... 11
3.1.1 OS USB Key Drive Method (Preferred)............................................................................................................11
3.1.2 Tool Scripts....................................................................................................................................................... 11
3.2 Preparing the USB Key Drive................................................................................................................ 11
3.3 Copying Linux Files to USB Key Drive.................................................................................................. 13
3.4 Copying the OS Everything.iso File to USB Key Drive..........................................................................13
3.5 Copying the Edited Kickstart Scripts to USB Key Drive........................................................................14
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
5 Installing Operating System.......................................................................................23

5.1 Installing OS with Kickstart Script......................................................................................................... 23
5.1.1 Initial Root Password Management................................................................................................................. 23
5.1.2 Via OS USB..................................................................................................................................................... 23
5.1.3 Via OS DVD..................................................................................................................................................... 24
5.2 Installing Required 32-bit Library RPM Packages.................................................................................25
5.3 RPMs to Remove.................................................................................................................................. 25
5.4 Identifying Physical LAN Devices.......................................................................................................... 25
5.5 Editing /etc/hosts File............................................................................................................................ 25
5.6 Setting History Timestamp for User root............................................................................................... 26
5.7 Updating tzdata and tzdata-java RPMs................................................................................................. 27
5.8 Setting Default Gateways..................................................................................................................... 27
5.9 Running check-configure-post-os-install.sh.......................................................................................... 27
6 Installing and Updating Platform Software...............................................................28

6.1 Installing Platform RPMs....................................................................................................................... 28
6.2 Updating BIOS Software....................................................................................................................... 28
6.3 Updating Firmware/Drivers................................................................................................................... 28

Version 2.8 2 of 63
__________________________________________________________________
6.4 Updating Smart Array Controller Firmware........................................................................................... 28
7 Creating Bonded LAN Interfaces...............................................................................30

7.1 Running setup-bonded-interfaces.sh.................................................................................................... 30
7.2 Checking IP Connectivity...................................................................................................................... 31
7.3 Adding Static IP Routes........................................................................................................................ 33
7.4 Setting NTP Server............................................................................................................................... 35
7.5 Disabling DNS GSSAPIAuthentication in ssh/sshd...............................................................................36
7.6 Stopping and Disabling Unwanted Services......................................................................................... 36
8 Appendix: Default Partition Layouts..........................................................................37

8.1 SMS Router, SMS Hub, Standalone BMS - Cassandra with 10 disks...................................................37
8.2 Standalone Assure................................................................................................................................ 37
8.3 Standalone Care................................................................................................................................... 38
8.4 Co-located Assure/Care........................................................................................................................ 38
9 Appendix: Required 32-bit Library RPM Packages..................................................39
10 Appendix: Kickstart Script..........................................................................................41
11 Appendix: Scripted Post-OS-Install Tasks in Detail.................................................43

11.1 Disable prelinking (/etc/prelink.conf)................................................................................................... 43
11.2 Disable updatedb cronjob (/etc/cron.daily/mlocate).............................................................................43
11.3 Add fs.suid_dumpable (/etc/sysctl.conf)..............................................................................................43
11.4 Add vm.max_map_count = 131072" (/etc/sysctl.conf).........................................................................44
11.5 Disable IPv6 (/etc/sysctl.conf)............................................................................................................. 44
11.6 Modify TCP Parameters (/etc/sysctl.conf)........................................................................................... 44
11.7 Inhibit SCTP Kernel Module (/etc/modprobe.d/sctp.conf)....................................................................44
11.8 Add limits to processes and open files (/etc/security/limits.conf).........................................................45
11.9 Set the default runlevel to 3 (/etc/systemd/system/default.target).......................................................45
11.10 Create /etc/systemd/system/samson.service....................................................................................46
11.11 Modify the mount option (/etc/fstab).................................................................................................. 46
11.12 Modify the number of processes (/etc/security/limits.d/*-nproc.conf)................................................47
11.13 Set up sudoer omn (/etc/sudoers)..................................................................................................... 47
12 Appendix: Getting the Necessary Tools for Installation via OS DVD.....................48

12.1 Prerequisites....................................................................................................................................... 48
12.1.1 OS DVD Method............................................................................................................................................ 48
12.1.2 Tool Scripts.................................................................................................................................................... 48
12.2 Burning OS DVD................................................................................................................................. 48
12.3 Creating the KSUSB USB Key Drive.................................................................................................. 49
12.4 Making Required 32-bit Library RPMs Available.................................................................................49
13 Appendix: Example Bonded LAN Interface Files.....................................................51
14 Appendix: Example VLAN Trunking Bonded LAN Interface Files..........................52
15 Appendix: How to Change Hostname/Default Gateway in OS................................55

15.1 Hostname........................................................................................................................................... 55

Version 2.8 3 of 63
__________________________________________________________________
15.2 Default Gateway................................................................................................................................. 55
16 Appendix: How to Manage Time and Timezone.......................................................56
17 Appendix: How to Change Keyboard Layout...........................................................57
18 Appendix: How to Produce a Kernel Module RPM from a Source RPM................58
19 Glossary........................................................................................................................60

Version 2.8 4 of 63
__________________________________________________________________
List of Tables
Table 1: Document Change History.................................................................................................................. 6

Figure 3.1: LAN Interface Naming.................................................................................................................. 15
Table 4.1:Configuring Smart Array Logical Drives on Gen8............................................................................18
Figure 4.2:Storage Cage Layout Option 1:..................................................................................................... 19
Figure 4.3:Storage Cage Layout Option 2...................................................................................................... 19
Table 4.4:Selecting BIOS as Boot Mode on Gen9.......................................................................................... 20
Table 4.5:Setting BIOS date and time on Gen9.............................................................................................. 20
Table 4.6:Configuring Smart Array RAID Logical Drives on Gen9..................................................................21
Table 8.1: Default Partitions for SMS Router, SMS Hub, BMS - Cassandra with 10 disks layout...................37
Table 8.2: Default Partitions for Standalone Assure........................................................................................ 37
Table 8.3: Default Partitions for Standalone Care........................................................................................... 38
Table 8.4: Default Partitions for Co-located Assure/Care................................................................................38
Table 9.1: Required 32-bit Library RPM Packages - Total 50..........................................................................39

Version 2.8 5 of 63
__________________________________________________________________
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.
Table 1: Document Change History

Version Date Author Notes
1.0 23/03/15 Tom Suzuki Initial version created.
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.3 07/04/15 Tom Suzuki Kickstart script updated.

1.4 13/04/15 Tom Suzuki Typo corrected.
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.
1.9 17/09/15 Tom Suzuki Section order updated.

2.0 22/09/15 Tom Suzuki Added libicu.i686 to the list of required 32-bit libraries.

Version 2.8 6 of 63
__________________________________________________________________
Version Date Author Notes
2.1 03/11/15 Tom Suzuki Updated the location of samson.service. Added

additional details on the hostnames.
2.2 11/11/15 Tom Suzuki Updated to include NOZEROCONF=true in Section 7.1
2.3 19/11/15 Tom Suzuki Updated to add a stipulation in Section 5.1.

2.4 03/05/16 Tom Suzuki Updated to remove the section for inode modification, to
add the initial root password management during
deployment.
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

Version 2.8 7 of 63
__________________________________________________________________
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)
to run on the following platforms:

• HP ProLiant DL380p Gen8 Server
• HP ProLiant DL380 Gen9 Server
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.

Version 2.8 8 of 63
__________________________________________________________________
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] HP Software/Driver Download website HP
http://www.hp.com, then go to Support>Download Drivers
[2] RedHat Enterprise Linux 7 RedHat

https://access.redhat.com/documentation/en-
US/Red_Hat_Enterprise_Linux/7
[3] CentOS Website http://www.centos.org CentOS
http://isoredirect.centos.org/centos/7.0.1406/isos/x86_64/
http://isoredirect.centos.org/centos/7.1.1503/isos/x86_64/
[4] Openmind Networks Customer Portal OMN

https://sites.google.com/a/openmindnetworks.com/ext-support/
[5]

Version 2.8 9 of 63
__________________________________________________________________
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:

• Getting the necessary tools
• Commissioning hardware
• Installing Operating System
• Installing and updating platform software
• Creating bonded LAN interfaces
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.

Version 2.8 10 of 63
__________________________________________________________________
3 Getting the Necessary Tools

This section describes prerequisites for Openmind product platforms.
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.
3.1.1 OS USB Key Drive Method (Preferred)

• 1x 16GB USB 2.0 key drive to contain Kickstart scripts and the OS Everything.iso file
• A pocket-sized USB hub (Optional but highly recommended)
• 4x USB 2.0 port available on the server or through a pocket-sized USB hub
• OS Everything.iso file available from CentOS web site [3]
• CentOS-7.0-1406-x86_64-Everything.iso
or
• CentOS-7-x86_64-Everything-1503-01.iso
• The tool scripts listed below available from Openmind Networks Customer Portal [4]
3.1.2 Tool Scripts

Tool Script Note
1 ks-cos-71-generic-usb.cfg To automate OS installation from USB key
drives. To be used as a template and re-named
for each individual servers. ks-xxx.cfg
2 show-pnd-ports.sh To help identifying LAN port allocations.
3 check-configure-post-os-install.sh To check the relevant OS configuration

parameters.
4 setup-bonded-interfaces.sh To automate the set-up of bonded LAN
interfaces.
3.2 Preparing the USB Key Drive
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)
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)
12. Sync, and disconnect the USB key drive.

root# cd ; sync ; umount /media/ksboot
root# umount /media/os
3.3 Copying Linux Files to USB Key Drive

1. Create a mount point directory (if not yet done so) and mount CentOS Everything iso
root# mkdir -p /media/iso
root# mount -t iso9660 <OS Everything.iso file> /media/iso
2. Mount the KSBOOT partition of the USB drive.
root# mount -t vfat /dev/sdX1 /media/ksboot
3. Copy the following files in the isolinux directory to the KSBOOT partition.
boot.msg, initrd.img, memtest, splash.png, isolinux.cfg, vesamenu.c32,
vmlinuz
root# cp /media/iso/isolinux/<file> /media/ksboot/ ; sync
4. Rename isolinux.cfg to syslinux.cfg
root# cd /media/ksboot ; mv isolinux.cfg syslinux.cfg
5. Edit syslinux.cfg.
- Locate "timeout 600" to make it "timeout 0" to disable timeout.
- Locate a section callled "label linux menu label ^Install CentOS 7"
- Modify the line for kernel start-up options to look like the following all in one line:
kernel vmlinuz
append initrd=initrd.img inst.stage2=hd:LABEL=OS:/
inst.ks=hd:LABEL=KSBOOT:/ks.cfg net
3.4 Copying the OS Everything.iso File to USB Key Drive

1. Mount the OS partition of the USB drive.
root# mount -t ext4 /dev/sdX2 /media/os
2. Copy the OS Everything.iso file to the USB key drive using the cp command.
root# cp <OS Everything.iso file> /media/os/ ; sync
3. Verify sha256 checksum using the sha256sum command against the copied iso file (it takes a while

__________________________________________________________________
to compute the check sum).

root# sha256sum /media/os/<OS Everything.iso file>
4. Un-mount the iso.
root# umount /media/iso
3.5 Copying the Edited Kickstart Scripts to USB Key Drive

A Kickstart script is arranged for each server to perform OS installation.
1. Download the generic Kickstart template developed for Openmind product platforms from
Openmind's Customer Portal [4].
2. Using the template, create a Kickstart script for each server to supply the keyboard layout type,
timezone and external hostname.
3. Edit the network interface details to match the installed expansion cards. For example, if the
network cards are present only in Slot 1 and Slot 3, edit network ens1f0 to ens1f3, ens3f0 to ens3f3,
but not ens2f0 to ens2f3.

__________________________________________________________________
Figure 3.1: LAN Interface Naming

NOTE
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:
On HP ProLiant DL380p Gen8 Server:
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 |
-------------------------------------
On HP ProLiant DL380 Gen9 Server:
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. Copy all the edited Kickstart scripts to the KSBOOT partition.

5. Check that the KSBOOT and OS partitions on the USB key drive contain the following files. For
example, if the cluster has 8 nodes, there will be 8 Kickstart scripts.
/media/ksboot
├── boot.msg
├── initrd.img
├── ks-tcsms01.cfg
├── ldlinux.sys
├── memtest
├── splash.png
├── syslinux.cfg
├── vesamenu.c32
└── vmlinuz
/media/os
├── CentOS70-7.0-1406-x86_64-Everything.iso
└── lost+found

__________________________________________________________________
4 Commissioning Hardware
This section describes the method of commissioning the hardware platform.
4.1 HP ProLiant DL380p Gen8 Server

This section describes hardware commissioning on:
• HP ProLiant DL380p Gen8 Server with p420/p420i Smart Array Controllers
4.1.1 Setting BIOS Date and Time

Set the BIOS date/time in UTC. When the server is starting up, press F9 function key when prompted for
"Setup via RBSU (ROM-based Setup)" to go into the BIOS Set-up menu.
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.
4.1.2 Configuring Smart Array RAID Logical Drives

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 and configured for
RAID 10 (mirroring and striping).

__________________________________________________________________
Table 4.1:Configuring Smart Array Logical Drives on Gen8

Steps Notes
1 Turn on the server. Watch the self hard drive check on
the front green LED.
2 To set BIOS date and time, press F9 function key when

prompted for "Setup". When exiting from the BIOS Set-up
menu, the server will reboot.
3 To configure the first Smart Array via "Option ROM
Configuration for Arrays Utility (RBSU)", press F8 when
prompted.
4 Configure the RAID1 logical drives in the menu. Make sure

that you delete any logical drive that may exist from
manufacturer's 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
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.

__________________________________________________________________
Figure 4.2:Storage Cage Layout Option 1:

Logical Box 1 Drives Box 2 Drives 16-bay Small-Form Factor Storage Cage
Drive ID SmartArray SmartArray
p420 p420i
1 Bay 1 + Bay 5 N/A
2 N/A Bay 1 + Bay 5

3 N/A Bay 2 + Bay 6
4 N/A Bay 3 + Bay 7

5 N/A Bay 4 + Bay 8
NOTE
Standard configuration with Cassandra.
Figure 4.3:Storage Cage Layout Option 2

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.

__________________________________________________________________
4.2 HP ProLiant DL380 Gen9 Server

This section describes hardware commissioning on:
• HP ProLiant DL380 Gen9 Server with p440ar Smart Array Controller
4.2.1 Selecting BIOS as Boot Mode

Gen9 introduced UEFI as the default server boot method, along with the legacy BIOS. To make BIOS
permanently selected, complete the following step once:
Table 4.4:Selecting BIOS as Boot Mode on Gen9

Steps Notes
1 Turn on the server. Watch the self hard drive check on
the front green LED.
2 Press F9 on the keyboard for System Utilities.

3 Go to "System Configuration".
4 Go to "BIOS/Platform Configuration (RBSU)".

5 Go to "Boot Options" to select "Legacy BIOS" in Boot Mode,
and press F10 to save.
6 Go back up to "BIOS/Platform Configuration".
4.2.2 Setting BIOS Date and Time
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.
Table 4.5:Setting BIOS date and time on Gen9

Steps Notes
1 From "BIOS/Platform Configuration", go to "Date and Time".
2 Set Date, Time, Timezone, and press F10 to save.

3 Go back to BIOS/Platform Configuration.

__________________________________________________________________
4.2.3 Configuring Smart Array RAID Logical Drives

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 and configured for
RAID 10 (mirroring and striping).
Table 4.6:Configuring Smart Array RAID Logical Drives on Gen9

Steps Notes
1 From "BIOS/Platform Configuration, go to "Embedded RAID
Smart Array P440ar Controller".
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.
4 Select "Smart Array p440ar" under "Array Controller(s)".

5 Select "Configure" under "Actions".
6 Select "Create Array" under "Actions".

7 In "Select Physical Drives for the New Array", available
physical drives are presented as icon. Select two physical
drives sequentially according to the drive assignment figures
below. Note the Bay number in the icon and the tick mark.
Press the "Create Array" button.
8 Ensure that selected are:

• RAID1
• Strip/Full Strip Size: 256KiB/256KiB
• Sectors/Track: 32
• Size: Maximum
• Caching: Enabled
Press the "Create Logical Drive" button.
9 Repeat Step 7 to 9 for the rest of the available physical drives.
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.
12 Review the configuration. If ok, press the X mark at the right

top corner. Then, select "Reboot".

__________________________________________________________________

Logical Box 1 Drives 24-bay Small-Form Factor Storage Cage
Drive ID SmartArray p440ar
1 Bay 1 + Bay 2
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

1 Bay 1 + Bay 2
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

__________________________________________________________________
5 Installing Operating System

This section illustrates the installation of operating system using a Kickstart script for Openmind's product
platform.
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).
5.1 Installing OS with Kickstart Script
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.
5.1.1 Initial Root Password Management

For the initial OS installation, the kickstart script will contain a unique root password randomly generated by
the SHA512 encryption, using a mixture of lower/upper case characters, special characters and digits. This
is unique per deployment project, and only known to the OMN engineer working on OS installation.
When OS installation is completed and confirmed as ready for OMN software installation, the root password
may be modified by the customer to share with the OMN engineer. If OS installation is performed by the
customer, the password is shared between the OMN engineer and the customer at least until the CAT is
completed.
At the agreed stage, the customer may choose to restrict root access by OMN personnel to some specific
actions via sudo only.
5.1.2 Via OS USB

1. Connect the OS USB key drive to the server.
2. Turn on the server. By default, the BIOS has the boot order set to try Optical Drive first, and USB
key drive next. When prompted, immediately move up the highlight to select "Install Cent OS 7" and
hit the Tab key to go into the edit mode for changing the kernel start options.
3. In the kernel start option line, check that the following options are present (all in one line).
vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=OS:/
inst.ks=hd:LABEL=KSBOOT:/ks.cfg
4. In the edit mode, replace the ks.cfg with the Kickstart script filename prepared for the server you are
installing. For example (all in one line):
vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=OS:/
inst.ks=hd:LABEL=KSBOOT:/ks-tcsms01.cfg
Hitting Enter will start booting from the "KSBOOT" partition in the USB key drive, locate the Kickstart
script, and instruct Kickstart to use the OS Everything.iso file located in the "OS" partition.
5. At the end of OS installation, there is a post-install script executed from within the Kickstart script.

__________________________________________________________________
For details on the scripted post-OS-install tasks, please refer to Appendix.

6. When Kickstart OS installation from the media is completed successfully, the Reboot button should
be presented on the screen. Press the Reboot button. Then, remove the USB key drive from the
server.
5.1.3 Via OS DVD

1. With the OS image DVD in the DVD drive, connect the drive and the USB key drive to the server.
2. Turn on the server. By default, the BIOS has the boot order set to try Optical Drive first. When
prompted, immediately move up the highlight to select "Install Cent OS 7" and hit the Tab key to go
into the edit mode for changing the kernel start options.
3. In the kernel start option line, enter the following in one line and hit Enter.
vmlinuz initrd=initrd.img ks=hd:LABEL=KSUSB:/<kickstart script filename>
Hitting Enter will start booting from the DVD iso image, locate the Kickstart script on the USB key
drive, and instruct Kickstart to use the DVD iso file.
4. When Kickstart OS installation from the media is completed successfully, the Reboot button should
be presented on the screen. Press the Reboot button. Then, remove the USB key drive from the
server.

__________________________________________________________________
5.2 Installing Required 32-bit Library RPM Packages

This step applies to the OS DVD method only. If you chose OS USB method, skip this step since the
method automatically installs 32bit OS library rpm packages from the Everything iso file.
1. Insert the KSUSB key drive with the 32bit-os-rpm packages.
root# mount -t ext4 /dev/<partition name> /media/usb
2. Copy the 32bit-os-rpm directory to the server.
root# mkdir -p /tmp/software/3rd-party
root# cp -rf /media/usb/32bit-os-rpm /tmp/software/3rd-party/
3. Install the 32bit-os-rpm packages.
root# rpm -ivh /tmp/software/3rd-party/32bit-os-rpm/*.rpm
5.3 RPMs to Remove

Ensure that the "biosdevname" rpm package is not present. If it is present for some reason, remove it
because this would cause havoc changing network device name mapping.
1. Run the rpm command to check.
root# rpm -qa | grep biosdevname
2. If it does exist, remove it.
root# rpm -ev biosdevname
5.4 Identifying Physical LAN Devices

Execute the script show-pnd-ports.sh available from Openmind's Customer Portal [4] to identify each
physical LAN port. The text output contains information on what Ethernet interface is allocated to what
physical LAN interface and Ethernet address.
You can also take notes of physical location by running ethtool with -p.
root# ethtool -p <device>
where <device> is eno1, ens1f0, bond2, 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.
5.5 Editing /etc/hosts File
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.
Edit the /etc/hosts file to define:

• Internal VLAN hosts (mandatory)
• SIGTRAN peers
• omnldap and omnbms aliases for localhost
The format is as follows:

<ip_address> <hostname> [<alias1> [<alias2> ... [<aliasN>]]]
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).
5.6 Setting History Timestamp for User root

1. Set the following shell variable in ~root/.bash_profile to add timestamp to its history output.
export HISTTIMEFORMAT="%Y-%m-%d %T "
2. Source it after saving the change.
root# . ~/.bash_profile

__________________________________________________________________
5.7 Updating tzdata and tzdata-java RPMs

1. Download tzdata-<year and revision> and tzdata-java-<year and revision> rpm packages from this
depot:
http://mirror.centos.org/centos/7/updates/x86_64/Packages/
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
5.8 Setting Default Gateways

It appears that the gateway option in the network interface command in Kickstart is not honoured. To enable
network access for the immediate needs, edit /etc/sysconfig/network to add the missing default
gateway variable.
1. Using vim, add the variable.
GATEWAY=<default_gateway_ip>
2. Then, restart the network interface.
root# systemctl restart network
5.9 Running check-configure-post-os-install.sh

As root, execute the script check-configure-post-os-install.sh available from Openmind's
Customer Portal [4] to verify the OS parameters configured.

__________________________________________________________________
6 Installing and Updating Platform Software
6.1 Installing Platform RPMs

There are some additional RPMs that should be installed, which are available from the HP Software/Driver
Download website [1].
• hpssacli (Smart Storage Administrator CLI - you can check the array status, configuration, etc. via
linux command line)
• hpssaducli (Smart Storage Administrator Diagnostic Utility CLI)
• hp-health (you can get some hardware status data such as thermal, fan, power)
• hp-snmp-agents (Optional: HP server platform SNMP agents)
• hpsmh (Optional: HP System Management Homepage)
• hp-smh-templates (Optional)
6.2 Updating BIOS Software

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

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 [1] for the latest update. In particular, LAN on
Motherboard may need a new kernel module. It may also need to be compiled from a source rpm. For
instructions on how to produce a kernel module rpm from a source rpm, refer to Appendix
6.4 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 [1] for the latest firmware update.
1. If any update is desired, install the SmartArray Controller firmware update.

2. Reboot the server.
3. Take out half of the RAID1 physical drives.
4. Power on the server, and verify that the server starts up fine with no disc fault.
5. Shut down and put all the physical drives back in.
6. Take out the other half of the physical drives.
7. Power on the server, and verify that the server starts up fine with no disc fault.
8. Put all the physical drives back in.

__________________________________________________________________
9. After the period of drive rebuild, run hpacucli to check the drive status.
root# hpacucli ctrl all show config > /tmp/hpacucli.out

__________________________________________________________________
7 Creating Bonded LAN Interfaces

This section describes bonded LAN configuration.
NOTE
It is assumed that all Ethernet LAN interfaces are full-duplex Gigabit Ethernet. Using FastEthernet is not
supported.
7.1 Running setup-bonded-interfaces.sh

The shell script setup-bonded-interfaces.sh attempts to:
• set default gateway in /etc/sysconfig/network
• set NOZEROCONF=true
• set persistent loading of bonding module
• create primary interface (e.g. /etc/sysconfig/network-scripts/ifcfg-ens1f0)
• create secondary interface (e.g. /etc/sysconfig/network-scripts/ifcfg-ens3f0)
• create bonding interface (e.g. /etc/sysconfig/network-scripts/ifcfg-bond0)
1. Prior to doing anything, create a back-up of the original /etc/sysconfig/network-scripts directory.

root# cd /etc/sysconfig
root# cp -rf network-scripts network-scripts.vanilla
2. Copy the setup-bonded-interfaces.sh script to /root.
3. To execute the bonding configuration script on the server, check the command-line syntax first.
root# cd ; ./setup-bonded-interfaces.sh --help
4. Run the script as root with the appropriate options. This script can create up to 4 bonded interfaces
(bond0 to bond3).
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 -O ifcfg-ens1f0 ifcfg-ens3f0 ifcfg-bond0
root# vim -O ifcfg-ens1f1 ifcfg-ens3f1 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# systemctl restart network

__________________________________________________________________
7.2 Checking IP Connectivity

1. As root, run the following command to check that SELinux is disabled and firewall is disabled.
• sestatus
• systemctl status iptables
• systemctl status 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
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
for n in $(eq 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 mode and status of each configured bonded interface (bond0, bond1, etc.).

__________________________________________________________________
[root@smsc01 ~]# cat /proc/net/bonding/bond0
Bonding Mode: fault-tolerance (active-backup)

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

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

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

__________________________________________________________________
7.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-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:
[root@smsc01 ~]# cat /etc/sysconfig/network-scripts/ifcfg-ens1f3

DEVICE=ens1f3
HWADDR=E8:39:35:0E:92:1A
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
PEERDNS=no
NM_CONTROLLED=no
ETHTOOL_OPTS="autoneg on 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-ens1f2 for ens1f2, route-bond1 for bond1), which
contains address, netmask, gateway and device name for each static route for the interface. For
example:
[root@smsc01 ~]# cat /etc/sysconfig/network-scripts/route-ens1f3

172.30.148.84/32 via 172.21.128.3 dev ens1f3
172.28.148.84/32 via 172.21.128.3 dev ens1f3
172.18.142.52/32 via 172.21.128.3 dev ens1f3
172.21.142.52/32 via 172.21.128.3 dev ens1f3
172.28.142.66/32 via 172.21.128.3 dev ens1f3
172.21.142.90/32 via 172.21.128.3 dev ens1f3
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:

__________________________________________________________________
[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 ens3f3
172.30.149.4 172.21.129.3 255.255.255.255 UGH 0 0 0 ens3f3
172.28.149.4 172.21.129.3 255.255.255.255 UGH 0 0 0 ens3f3
172.21.142.90 172.21.128.3 255.255.255.255 UGH 0 0 0 ens1f3
172.28.142.91 172.21.129.3 255.255.255.255 UGH 0 0 0 ens3f3
172.18.142.52 172.21.128.3 255.255.255.255 UGH 0 0 0 ens1f3
172.21.142.52 172.21.128.3 255.255.255.255 UGH 0 0 0 ens1f3
172.30.148.84 172.21.128.3 255.255.255.255 UGH 0 0 0 ens1f3
172.21.142.67 172.21.129.3 255.255.255.255 UGH 0 0 0 ens3f3
172.18.143.4 172.21.129.3 255.255.255.255 UGH 0 0 0 ens3f3
172.28.142.66 172.21.128.3 255.255.255.255 UGH 0 0 0 ens1f3
172.28.148.84 172.21.128.3 255.255.255.255 UGH 0 0 0 ens1f3
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 ens3f3
172.21.128.0 0.0.0.0 255.255.255.0 U 0 0 0 ens1f3
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 ens3f3
0.0.0.0 172.21.202.3 0.0.0.0 UG 0 0 0 bond1

__________________________________________________________________
7.4 Setting NTP Server

1. Ensure that the chronyd service is stopped and disabled. If running or enabled, stop and disable it.
root# systemctl status chronyd
root# systemctl stop chronyd
root# systemctl disable chronyd
2. 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
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

__________________________________________________________________
root# systemctl status ntpd.service
7.5 Disabling DNS GSSAPIAuthentication in ssh/sshd

Depending on the LAN, ssh login password prompt may not show up instantly. In this situation,
1. As root, disable GSSAPIAuthentication option by editing ssh and sshd configuration files:
/etc/ssh/ssh_config
/etc/ssh/sshd_config
2. Also, explicitly disable UseDNS in /etc/ssh/sshd_config Note that implicit set-up (A commented line
of UseDNS) causes it to be deemed Yes.
UseDNS no
3. Afterwards, restart the ssh daemon.
root# systemctl restart sshd
7.6 Stopping and Disabling Unwanted Services

1. As root, run the following shell command in order to prevent some unwanted system services from
starting up automatically after reboot as well as to stop those currently running.
root# services="\
NetworkManager \
abrt-ccpp \
abrtd \
abrt-oops \
avahi-daemon \
avahi-dnsconfd \
chronyd \
dnsmasq \
firewalld \
ip6tables \
iptables \
kdump \
postfix \
rhnsd \
rpcgssd \
rpcidmapd \
rpcsvcgssd \
sendmail \
wpa_supplicant"
for s in ${services}
do
systemctl stop ${s} ; systemctl disable ${s}
done

__________________________________________________________________
8 Appendix: Default Partition Layouts
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 1 300GB /boot ext4 sda 500MB

/var ext4 sda 32GB
/tmp ext4 sda 32GB

swap swap sda 32GB (for 64GB
RAM)
/ ext4 sda Fill the max
allowed size
2x 300GB 2 300GB /apps ext4 sdb Fill the max
allowed size
2x 300GB 3 300GB /data ext4 sdc Fill the max

allowed size
2x 300GB 4 300GB /logs ext4 sdd Fill the max
allowed size
2x 300GB 5 300GB /commit ext4 sde Fill the max

allowed size
8.2 Standalone Assure

Table 8.2: Default Partitions for Standalone Assure
Drives Drive Size

/var ext4 sda 32GB
/tmp ext4 sda 32GB

swap swap sda 32GB (for 64GB RAM)
/ ext4 sda 32GB

/apps ext4 sda Fill the max allowed size
2x 300GB 2 300GB /logs ext4 sdb Fill the max allowed size

__________________________________________________________________

Drives Drive Size
6x 1TB 3 3TB /assuredb ext4 sdc Fill the max allowed size
8.3 Standalone Care

Table 8.3: Default Partitions for Standalone Care
Drives Drive Size

/var ext4 sda 32GB
/tmp ext4 sda 32GB

/ ext4 sda 32GB

/apps ext4 sda 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
8.4 Co-located Assure/Care

Table 8.4: Default Partitions for Co-located Assure/Care
Physical Logical Available Partition FS Type On Disc Size (MB)
Drives Drive Space
/var ext4 sda 32GB

/tmp ext4 sda 32GB

/ ext4 sda Fill the max allowed size
2x 300GB 2 300GB /apps ext4 sdb 64GB

/logs ext4 sdb 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

__________________________________________________________________
9 Appendix: Required 32-bit Library RPM Packages

Table 9.1: Required 32-bit Library RPM Packages - Total 50
cyrus-sasl-lib.i686
gamin.i686
glib2.i686
glibc.i686
keyutils-libs-devel.i686
keyutils-libs.i686
krb5-devel.i686
krb5-libs.i686
libacl.i686
libattr.i686
libcom_err-devel.i686
libcom_err.i686
libdb.i686
libffi.i686
libgcc.i686
libgcrypt.i686
libgpg-error.i686
libgtop2.i686
libicu.i686
libjpeg-turbo.i686
libpng12.i686
libpng.i686
libselinux-devel.i686
libselinux.i686
libsepol-devel.i686
libsepol.i686
libstdc++.i686
libverto-devel.i686
libverto.i686
libxml2.i686
libxslt.i686
ncurses-libs.i686
nspr.i686
nss.i686
nss-softokn-freebl.i686
nss-softokn.i686

__________________________________________________________________
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

__________________________________________________________________
10 Appendix: Kickstart Script

For your reference only, shown below is the Kickstart script written and verified to work in this installation and
configuration procedure. Please download one from our Openmind's Customer Portal [4]. instead of copying
these pages to avoid causing character set changes, typo, and so forth.
#version=RHEL7
auth --enableshadow --passalgo=sha512

rootpw --iscrypted
$6$a$uZelYpY1/W5jLwazQYq8BpTJtMD0YPPeOqOyqaCv0AIS5p76UkgH4nJGCy1SqBMGLPIEwUK3VsY
I0Y0tgkwfz.
install
timezone --utc Europe/Dublin

keyboard --vckeymap=uk
lang en_US.UTF-8
firewall --disabled
selinux --disabled
network --onboot=yes --device=eno1 --bootproto=static --noipv6

--ip=172.16.1.23 --netmask=255.255.255.0 --gateway=172.16.1.254
--hostname=tcsms-e01
network --onboot=no --device=eno2 --bootproto dhcp --noipv6
network --onboot=no --device=ensXf0 --bootproto dhcp --noipv6
network --onboot=no --device=ensYf0 --bootproto dhcp --noipv6
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

__________________________________________________________________
part /boot --fstype=ext4 --size=512 --ondisk=sda --asprimary

part /tmp --fstype=ext4 --size=16384 --ondisk=sda
part /var --fstype=ext4 --size=16384 --ondisk=sda
part swap --fstype=swap --size=32768 --ondisk=sda
part / --fstype=ext4 --size=1 --grow --ondisk=sda
part /apps --fstype=ext4 --size=1 --grow --ondisk=sdb
part /data --fstype=ext4 --size=1 --grow --ondisk=sdc
part /logs --fstype=ext4 --size=1 --grow --ondisk=sdd
part /commit --fstype=ext4 --size=1 --grow --ondisk=sde
%packages
<Package groups here>
# Required individual packages.

<Required individual packages here>
# Remove unwanted packages.

<Unwanted packages here>
# Get these required i686 rpm packages from CentOS 7.0 Everything iso image.
<Required i686 packages here>
%end
%post --interpreter=/usr/bin/bash --log=/root/ks-post.log
<The post install script here>
%end

__________________________________________________________________
11 Appendix: Scripted Post-OS-Install Tasks in Detail

For your reference, the post-OS-install tasks performed from within the Kickstart script are described in the
following sections:
11.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
11.2 Disable updatedb cronjob (/etc/cron.daily/mlocate)

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/mlocate
#/usr/bin/updatedb -f "nfs,.......
11.3 Add fs.suid_dumpable (/etc/sysctl.conf)

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
11.4 Add vm.max_map_count = 131072" (/etc/sysctl.conf)

1. Add vm.max_map_count to /etc/sysctl.conf.
vm.max_map_count = 131072

root# sysctl -p
root# sysctl -a | grep vm.max_map_count
11.5 Disable IPv6 (/etc/sysctl.conf)

1. Edit the /etc/sysctl.conf to permanently set the parameters by adding the following lines:
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1

root# sysctl -p
root# sysctl -a | grep ipv6
11.6 Modify TCP Parameters (/etc/sysctl.conf)

Increase the maximum size of the Listen queue for the TCP to manage SYN flood and SYN cookies.
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

root# sysctl -p
root# sysctl -a | grep net
11.7 Inhibit SCTP Kernel Module (/etc/modprobe.d/sctp.conf)

Create /etc/modprobe.d/sctp.conf containing these two lines:

__________________________________________________________________
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.
11.8 Add limits to processes and open files (/etc/security/limits.conf)

Add the following lines to increase the maximum number of open flies and processes to
/etc/security/limits.conf
* soft nofile 100000

* hard nofile 100000
* soft nproc 32768
* hard nproc 32768
* 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 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.
11.9 Set the default runlevel to 3 (/etc/systemd/system/default.target)

Set the default target to multi-user.
root# systemctl set-default multi-user.target
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

__________________________________________________________________
11.10 Create /etc/systemd/system/samson.service

The systemctl mechanism replaces the /etc/inittab way and Upstart way of spawning processes.
1. Create the /usr/lib/systemd/system/samson.service file.
# samson - Openmind Networks Limited

#
# Starts samson process
[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
11.11 Modify the 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 partitions 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. This change will take effect after a reboot or remount.
UUID=<uuid> / ext4 noatime 1 1

__________________________________________________________________
UUID=<uuid> /apps ext4 noatime 1 2

UUID=<uuid> /logs ext4 noatime 1 2
UUID=<uuid> /data ext4 noatime 1 2
11.12 Modify the number of processes (/etc/security/limits.d/*-

nproc.conf)
Disable the threshold of the maximum number of processes.
#* soft nproc 4096
11.13 Set up sudoer omn (/etc/sudoers)

Add the following lines (including the comments) in /etc/sudoers to allow user omn to:
• install/remove rpm packages
• run systemctl on stopping/starting samson service.
## Allows user omn to run systemctl on stopping/starting samson service.

omn ALL=(ALL) NOPASSWD: /usr/bin/systemctl enable samson
omn ALL=(ALL) NOPASSWD: /usr/bin/systemctl disable samson
omn ALL=(ALL) NOPASSWD: /usr/bin/systemctl start samson
omn ALL=(ALL) NOPASSWD: /usr/bin/systemctl stop samson
omn ALL=(ALL) NOPASSWD: /usr/bin/systemctl restart samson
## Allows user omn to run rpm for install/remove.

omn ALL=(ALL) NOPASSWD: /usr/bin/rpm

__________________________________________________________________
12 Appendix: Getting the Necessary Tools for Installation via

OS DVD
12.1 Prerequisites
12.1.1 OS DVD Method

• 1x USB 2.0 key drive formatted in ext4 and labelled "KSUSB"
• 1x blank single-layer DVD+R/-R
• 1x USB DVD drive
• 4x USB 2.0 port available on the server or through a pocket-sized USB hub
• A pocket-sized USB hub (Optional but highly recommended)
• OS DVD.iso file available from CentOS website [3]
• OS Everything.iso file available from CentOS website [3] (for some CentOS i686 rpm packages)
• The tool scripts listed below available from Openmind Networks Customer Portal [4]
12.1.2 Tool Scripts

Tool Script Note
1 ks-cos-70-generic-dvd.cfg To automate OS installation from OS DVD drive.
To be used as a template and re-named for each
ks-cos-71-generic-dvd.cfg
individual servers. ks-xxx.cfg
2 show-pnd-ports.sh To help identifying LAN port allocations.
3 check-configure-post-os-install.sh To check the relevant OS configuration

parameters.
4 setup-bonded-interfaces.sh To automate the set-up of bonded LAN
interfaces.
12.2 Burning OS DVD

1. Download <OS DVD.iso file> and its sha256 file from the CentOS website [3].
2. Verify sha256 checksum using the sha256sum command against the downloaded iso file (it takes a
while to compute the check sum).
root# sha256sum /tmp/<OS DVD.iso file>
3. Using Brasero Disc Burner or equivalent, burn the downloaded OS DVD image.
NOTE
You do not create a data DVD with the image file, but you burn the DVD image to disc.

__________________________________________________________________
12.3 Creating the KSUSB USB Key Drive

1. Insert a USB key drive to a Linux computer.
2. 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
3. Run fdisk.
root# fdisk /dev/sdX
4. 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 all the way).
t to change a partition type (83 for Linux).
w to write table to disk and exit , or q to quit without saving changes .
5. Format the partition.
root# mkfs.ext4 -L "KSUSB" /dev/sdX1
6. Create a mount point directory for the USB key drive.
root# mkdir /media/usb
7. Mount the USB key drive (Note the 1 for partition 1 after the device name).
root# mount /dev/sdX1 /media/usb
8. Print the mount table.
root# mount
:
:
/dev/sdc1 on /media/usb/KSUSB type ext4
(rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)
9. Disconnect the KSUSB drive.

root# umount /media/usb/KSUSB
12.4 Making Required 32-bit Library RPMs Available

Due to the way CentOS 7.x is distributed, 32-bit library rpm packages are included in a separate iso image
called "CentOS-<version>-Everything.iso", which is too large to fit the standard single-layer DVD. Here we
extract the required 32-bit library rpm packages listed in Appendix to the KSUSB key from this iso image.
1. Connect the KSUSB drive to your computer. It is automatically mounted normally.
2. Make a target directory in the KSUSB drive.
root# mkdir -p <KSUSB mount point dir>/32bit-os-rpm

__________________________________________________________________
3. Download <OS Everything.iso file> from the CentOS website [3].

4. Create a mount point directory (if not yet done so) and mount the Everything iso image to your
computer. For example, on Linux:
root# mkdir -p /media/dvd
root# mount -t iso9660 <path to the iso file>/<OS Everything.iso file>
/media/dvd
5. Copy the required 32-bit rpm packages from the Packages subdirectory in the mounted iso to the
KSUSB drive. For example, on a Linux terminal, run the following for each file:
root# cp /media/dvd/Packages/<rpm file> /<KSUSB mount point dir>/32bit-os-
rpm/ ; sync
6. Run the sync command before un-mounting.
root# sync
7. Unmount the iso image and the KSUSB drive.
root# cd ; umount /media/dvd

__________________________________________________________________
13 Appendix: Example Bonded LAN Interface Files

Attached below is an example of the three interface files that form a bonded interface. Please note that the
"autoneg on" is mandatory according to IEEE 802.3ab (1000Base-T).

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

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

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

__________________________________________________________________
14 Appendix: Example VLAN Trunking Bonded LAN Interface

Files
Attached below is an example of the Ethernet interface configuration files that form a bonded interface with
VLAN Trunking. Please note that "autoneg on" is mandatory according to IEEE802.3ab (1000Base-T).:

DEVICE=ens1f1
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
PEERDNS=no
NM_CONTROLLED=no
MASTER=bond1
SLAVE=yes

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

DEVICE=bond1
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
PEERDNS=no
NM_CONTROLLED=no
BONDING_OPTS="mode=1 primary=ens1f1 miimon=100"

__________________________________________________________________
[root@smsc01 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond1.422

DEVICE=bond1.422
TYPE=Bond
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
PEERDNS=no
NM_CONTROLLED=no
IPADDR=10.100.81.102
NETMASK=255.255.255.224
VLAN=yes
[root@smsc01 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond1.427

DEVICE=bond1.427
TYPE=Bond
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
PEERDNS=no
NM_CONTROLLED=no
IPADDR=10.100.81.166
NETMASK=255.255.255.224
VLAN=yes
[root@smsc01 ~]# cat /etc/sysconfig/network-scripts/route-bond1

# DIAMETER - primary
GATEWAY0=10.100.81.97
NETMASK0=255.255.255.255
ADDRESS0=10.100.113.4
# DIAMETER - secondary
GATEWAY1=10.100.81.97
NETMASK1=255.255.255.255
ADDRESS1=10.200.113.4
# SMSC EXTERNAL VLAN

GATEWAY2=10.100.81.97
NETMASK2=255.255.255.224
ADDRESS2=10.200.81.96

__________________________________________________________________
# SMPP-GW
GATEWAY3=10.100.81.97
NETMASK3=255.255.255.128
ADDRESS3=10.100.80.0
[root@smsc01 ~]# cat /etc/sysconfig/network-scripts/route-bond1.422

# DIAMETER - primary
GATEWAY0=10.100.81.97
NETMASK0=255.255.255.255
ADDRESS0=10.100.113.4
# DIAMETER - secondary
GATEWAY1=10.100.81.97
NETMASK1=255.255.255.255
ADDRESS1=10.200.113.4
# SMSC EXTERNAL VLAN

GATEWAY2=10.100.81.97
NETMASK2=255.255.255.224
ADDRESS2=10.200.81.96
# SMPP-GW
GATEWAY3=10.100.81.97
NETMASK3=255.255.255.128
ADDRESS3=10.100.80.0
[root@smsc01 ~]# cat /etc/sysconfig/network-scripts/route-bond1.427

# MCN SIP
GATEWAY0=10.100.81.161
NETMASK0=255.255.255.255
ADDRESS0=10.100.145.70
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 Appendix: How to Change Hostname/Default Gateway in OS
15.1 Hostname
1. To set it to a new hostname, run the command as root:

root# hostnamectl set-hostname <new_hostname> --static
2. Check the /etc/hostname.
root# cat /etc/hostname
3. Edit the /etc/hosts to set the new hostname as root.
4. Log in as omn, and set the hostname in the command prompt for user omn. For example:
omn$ hostname tcsms-e01
5. Check the hostname command.
omn$ hostname
15.2 Default Gateway
1. Print the current IP route table.

root# netstat -rn
2. To set the new default gateway, change the GATEWAY variable in the /etc/sysconfig/network as root:
GATEWAY=<new_default_gw_ip>
3. Run the ip route command as root. Make sure that you select the correct interface for the new
default gateway address.
root# ip route delete default
root# ip route add default via <new_default_gw_ip> dev <interface>
4. Check the IP route table.
root# netstat -rn
5. Do IP ping to verify the default route.
root# ping <ip_addr to route via default_route>

__________________________________________________________________
16 Appendix: How to Manage Time and Timezone
• 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
• To manage system time, timezone via timedatectl

timedatectl status
timedatectl set-time "2015-12-25 18:17:16"
timedatectl list-timezones
timedatectl set-timezone <timezone>
timedatectl set-local-rtc 0
timedatectl set-ntp 1
• To check the timezone info associated with the local time

ls -l /etc/localtime
• To check the beginning and the end of summer time of the year
zdump -v <timezone name> | grep $(date '+%Y')
• To print system time, network time and hardware clock

date; rdate -p <ntp server>; hwclock --show
• To print system time, set system time to network time and print system time
date; rdate -s <ntp server>; date
• To check the status of ntpd
systemctl status ntpd
• To enable ntpd service
systemctl enable ntpd
• To restart ntpd service
systemctl restart ntpd

__________________________________________________________________
17 Appendix: How to Change Keyboard Layout
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>

__________________________________________________________________
18 Appendix: How to Produce a Kernel Module RPM from a

Source RPM
This section illustrates how to produce a kernel module rpm from a source rpm, using an i686 kernel module
network driver "tg3" as an example. All tasks are performed as user root.
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
6. Build the rpm.

rpmbuild --target=i686 -bb /usr/src/redhat/SPECS/hp-tg3.spec

__________________________________________________________________
7. Verify that the same kernel module is not running currently.

rpm -q kmod-hp-tg3
rpm -q kmod-hp-tg3-i686
rpm -qa | grep tg3
lsmod | grep tg3
8. Install the produced rpm.
rpm -ivh /usr/src/redhat/RPMS/i686/kmod-hp-tg3-PAE-3.125g-2.i686.rpm
9. Check the module detail.
modinfo tg3 | grep version
10. Install the kernel module, and check that the module is loaded.
modprobe tg3
lsmod | grep tg3
11. Reboot the server and check the system boot message. Lines like below will be found in the dmesg
output.
dmesg > /tmp/dmesg.out
[ 1.560820] tg3 0000:03:00.1 eno2: Tigon3 [partno(629133-001) rev 5719001]
(PCI Express) MAC address ac:16:2d:70:3e:b1
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
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

LOM LAN On Motherboard
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

MVNE Mobile Virtual Network Enabler
MVNO Mobile Virtual Network Operator

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

__________________________________________________________________
Terms Description
OMN OpenMind Networks

OPC Originator Point Code
PC Point Code
PCIe Peripheral Component Interconnect Express
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

__________________________________________________________________
Terms Description
SRI-SM Send Routing Information for Short Message

SS7 Signalling System No. 7
SSP Signalling Switching Point

STP Signalling Transfer Point
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


OS InstallationConfigurationGuide COS 7.0 7.1

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

OS InstallationConfigurationGuide COS 7.0 7.1

Hochgeladen von

Copyright:

Verfügbare Formate

Installation Configuration Guide ICG for Traffic Control

Installation Configuration Guide

for Openmind's Traffic Control

© Openmind Networks Limited 2019 Commercial in Confidence

3 Getting the Necessary Tools.......................................................................................11

5 Installing Operating System.......................................................................................23

6 Installing and Updating Platform Software...............................................................28

© Openmind Networks Limited 2019 Commercial in Confidence

6.4 Updating Smart Array Controller Firmware........................................................................................... 28

7 Creating Bonded LAN Interfaces...............................................................................30

8 Appendix: Default Partition Layouts..........................................................................37

9 Appendix: Required 32-bit Library RPM Packages..................................................39

10 Appendix: Kickstart Script..........................................................................................41

11 Appendix: Scripted Post-OS-Install Tasks in Detail.................................................43

12 Appendix: Getting the Necessary Tools for Installation via OS DVD.....................48

13 Appendix: Example Bonded LAN Interface Files.....................................................51

14 Appendix: Example VLAN Trunking Bonded LAN Interface Files..........................52

15 Appendix: How to Change Hostname/Default Gateway in OS................................55

© Openmind Networks Limited 2019 Commercial in Confidence

15.2 Default Gateway................................................................................................................................. 55

16 Appendix: How to Manage Time and Timezone.......................................................56

17 Appendix: How to Change Keyboard Layout...........................................................57

18 Appendix: How to Produce a Kernel Module RPM from a Source RPM................58

© Openmind Networks Limited 2019 Commercial in Confidence

Table 1: Document Change History.................................................................................................................. 6

© Openmind Networks Limited 2019 Commercial in Confidence

Table 1: Document Change History

1.3 07/04/15 Tom Suzuki Kickstart script updated.

1.9 17/09/15 Tom Suzuki Section order updated.

© Openmind Networks Limited 2019 Commercial in Confidence

Version Date Author Notes

2.1 03/11/15 Tom Suzuki Updated the location of samson.service. Added

2.3 19/11/15 Tom Suzuki Updated to add a stipulation in Section 5.1.

© Openmind Networks Limited 2019 Commercial in Confidence

to run on the following platforms:

© Openmind Networks Limited 2019 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

[2] RedHat Enterprise Linux 7 RedHat

[4] Openmind Networks Customer Portal OMN

© Openmind Networks Limited 2019 Commercial in Confidence

Overall, the task is composed of the following steps:

© Openmind Networks Limited 2019 Commercial in Confidence

3 Getting the Necessary Tools

3.1.1 OS USB Key Drive Method (Preferred)

3.1.2 Tool Scripts

2 show-pnd-ports.sh To help identifying LAN port allocations.

3 check-configure-post-os-install.sh To check the relevant OS configuration

3.2 Preparing the USB Key Drive

© Openmind Networks Limited 2019 Commercial in Confidence

© Openmind Networks Limited 2019 Commercial in Confidence

12. Sync, and disconnect the USB key drive.

3.3 Copying Linux Files to USB Key Drive

3.4 Copying the OS Everything.iso File to USB Key Drive

© Openmind Networks Limited 2019 Commercial in Confidence

to compute the check sum).

3.5 Copying the Edited Kickstart Scripts to USB Key Drive

© Openmind Networks Limited 2019 Commercial in Confidence

Figure 3.1: LAN Interface Naming