0% found this document useful (0 votes)
15 views43 pages

RedHat Enterprise Linux 7 Installation of OS High Availability (QNMEngineWithPostgres & Qstar installation)

Uploaded by

anilkumar.n117
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views43 pages

RedHat Enterprise Linux 7 Installation of OS High Availability (QNMEngineWithPostgres & Qstar installation)

Uploaded by

anilkumar.n117
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 43

RedHat Enterprise

Linux 7
Installation of Operating System
and High Availabilty (HA)
QNMEngineWithPostgres & Qstar installation
1.Installion Process:
Step 1: Insert the RHEL dvd, into DVD Drive, once booting with Rhel we are able to see the below
screen.

Image : 1.1

Step 2: Then we need to select option Install Red Hat Enterprise Linux 7.3, once selected
installation starts.

Image:1:2
Step 3: Weclome to “RED HAT ENEERPRISE LINUX 7.3” need to select 'Language'.

Image 3.1

Step 4: INSTALLATION SUMMARY

4.a) we need to modify the Date & Time, then select Software Selection
check the reference images 4.2 & 4.3

Image 4.1
4.b) Set Date & Time once selected the location Region: & City click the button 'Done' to go back
to Installation Summary (Image 4.1).

Image 4.2

4.c) Next the “Software Selection”- In 'Base Environment' select the 'Server with GUI' option
'Add-Ons for Selected Environment' need to check 5 boxes like Java Platform, KDE, Large
System Performance, Compatibility Libraries, Development Tools.
.

Image 4.3
Image 4.4
click the button 'Done' to go back to Installation Summary (Image 4.1).

4.d) check the SYSTEM option in Image 4.1, select the Installation Destination then select the
Radio Button option with ' I Will configure Partitioning'

Image 4.5
click the button 'Done' , it opens a new window with Manual Partitioning.

4.e i) New mount points will use the following partitioning scheme:
select option 'Standard Partition' click on '+” Symbol to create a Partition.

Image 4.6

4.e ii) click on '+' symbol to select the Mount Point '/boot' & Desired Capacity '1024M' or '1G'
Device Type 'Standard Partition' File System: 'xfs'. (1G=1gb=1024mb, 1M =1mb=1024kb)
gb=GigaByte, mb=MegaByte kb=KiloByte.

NOTE: Mount Point size's can be given as per storage availability.


Image 4.7

4.e iii) Click on '+' symbol to create another Mount Point name is '/boo/efi' with Desired Capaclity
1G or 1024M.

Image 4.8
4.e iv) Click on '+' symbol to create another Mount Point 'home', Desired Capaclity 30G or
30720M, Device Type 'LVM', File System 'ext4' once modified click on Update Settings. for
reference check images 4.9 & 4.10.

Image 4.9

Click on Update Settings after modification.


Image 4.10
4.e v) click on '+' symbol to create another Mount Point 'var', Desired Capaclity 80G or 81920M,
Device Type 'LVM', File System 'ext4' once modified click on Update Settings. for reference check
images 4.9 & 4.10.

Image 4.11

4.e vi) click on '+' symbol to create another Mount Point 'usr', Desired Capaclity 10G or 81920M,
Device Type 'LVM', File System 'ext4', once modified click on Update Settings. for reference check
images 4.9 & 4.10.

Image 4.12
4.e vii) click on '+' symbol to create another Mount Point '/', Desired Capaclity 80G , Device Type
'LVM', File System 'ext4', once modified click on Update Settings. for reference check images 4.9 &
4.10.

Image 4.13
click on Done.

Image 4.14
4.e viii) click on Accept Changes to save changes to disk partition.

Image 4.15

4.f i) after completion of Manual Partitioning it will return to INSTALLATION SUMMARY ,


click on Network & Host name.

Image 4.17
4.f ii) Here we can assign the server Fully Qualified Domain Name or Host Name. By default we
can see the host name as 'localhost.localdomain' for example we can use “qtsprimary.testserver.com”
or “qtsp.in”.

Image 4.18

4.f iii) Hostname changed to 'qtsprimary.testserver.com' or 'qtsp.in' , then click on Ethernet (em1)
then click on 'configure' button to configure ipaddress and select Ipv4 option then we can see the ipv4
settings here we can assign ipaddress. For reference observe the images 4.18 & 4.19.

Image 4.19
4.f iv) we use any ipaddress for communicating with another system in the network for example
using below ip address, click on Method select for “Automatic (DHCP)” to “Manual”.
click on add button 192.168.10.10, netmask 255.255.255.0 gw 192.168.10.1 click on Save button..

Image 4.20

Image 4.21
4.f v) once assigned click button OFF state to ON state.

Image4.22
Click on Done Button.

4.g) click on KDUMP, it is enabled by default you can see it Image 4.1 & 4.23

Image 4.24
4.h) Go back to Installation Summary then click on Begin Installation

Image 4.25

Step 5) create 'ROOT' user password & 'User Creation'

Image 5.1
5.a) creating root user 'password'

Image 5.2

5.b) creating user name and password for example name is 'user1'.

Image 5.3

5.c) user creation is done need to wait sill installation completes.


Image 5.4

5.d) Once installation completed need to 'Reboot' server.

Image 5.5

Step 6) Server got rebooted, need to accept 'License terms' in LICENSE INFORMATION,
reference check the image 6.1.

Image 6.1
6.a i) check the “ I accept the license agreement” click done, we can subscribe to redhat using
'subscription manager' option, refer the images 6.2 & 6.3.

Image 6.2

6 a ii) Click on Done.


Image 6.3
6.a iii) Click on Finish configuration to complete installation

Image 6.4

6.a iv) while reboot


Image 6.5

Step 7)
7.a i) we can see the login screen of RHEL 7.

Image 7.1

7.a ii) Different login option's available for user1.


Image 7.2

7.a iii) To login as 'root' user click on 'Not Listed?' option reference see the image 7.1

Image 7.3

7.a iv) enter password for 'root' user.


Image 7.4

7.a v) Click 'Next' Button 'Language' English, Typing English (US) refer image 7.5 &7.6, skip the
online account option refer image 7.7.

Image 7.5
Image 7.6

Image 7.7

7.a vi) Click on “Start Using Red Hat Enetrprise Linux Server” to complete 'root ' login GUI.

Image 7.8
7.a vii) we can see the “Getting Started window” for 'GNOME Help'.

Image 7.9

Step 8) Click on Applications

Image 8.1
8.a i) Click on Terminal refer image 8.1, we can see red-hat-relase version using command (CLI)
# cat /etc/redhat-release

Image 8.2

Step 9) Adding Host Name using Command mode

After Installing OS need to enter the ip address and hostname of server in a file called “hosts”
file path or location for the host file “/etc/hosts”

To see the information using “cat” command we can see the information

Example output : cat /etc/hosts

Image 9.1

To communicate with other servers in the network, hosts file need to update with details like
Hostname and Ip address.

Using vi editor or vim editor or gedit options we open a file update details of servers or client
machines.

use gedit option to open the in graphical mode,


other editor option need to know the shortcuts option before editing the file.
root@qtssecondary ~]#gedit /etc/hosts

Image 9.2

example output : 192.168.10.10 is this server ip address & hostname qtssecondary.testserver.com


192.168.10.14 is another server ip address & hostname qtsprimary.testserver.com

Edit the files called “Hosts, host name to assign host name using CLI & network file to assign host
name”.

Note:after entering ip address & host name, using '# key' in the same line details which were enter
will be not read by the server, so the information of ip address belongs to clients or servers.

root@qtssecondary ~] # gedit /etc/hostname

Image 9.3

[root@qtssecondary~]#gedit /etc/sysconfig/network

Image 9.4

Step 10)
10.a i) Check the ip tables or firewall is enabled or disabled.

[root@qtssecondary~]# iptables -L or getenforce gives fire wall status.


Image 10.1
[root@qtssecondary~]# getenforce

Image 10.2

Output of above commands shows firewall is 'enabled'.


Step 11) Automount of Rhel OS dvd drive and change directory location.

11.a i) To identify the RHEL 7 OS disk is mounted or visiable using command.

[root@qtssecondary~]# df -h

Image 11.1

11.a ii ) to see the data available on rhel os dvd drive, using 'cd'- change directory commad

[root@qtssecondary~]# cd /run/media/root/RHEL-7.3 Server.x86_64

Image 11.2
11.a iii) to list the data available on rhel dvd us the command is 'ls'

[root@qtssecondary~]# ls

Image 11.3

Packages of 'RHEL' are located in directory name Packages & 'High Availability' Packages are on the
addons directory.

11.a iv) changing to Package directory for installing rpm package

[root@qtssecondary~]# cd Packages

Image 11.4
Step 12) Installing vsftp & createrepo rpm packages for yum server configuration.

12.a i) checking required packages are installed or not

[root@qtssecondary~]#rpm -qa vsftpd*


[root@qtssecondary~]#rpm -qa createrepo*

Image 12.1

12.a ii) if rpm -qa command does not return any info, we need to install packages using command

[root@qtssecondary Packages ~]# rpm -ivh vsftpd*


[root@qtssecondary Packages ~]# rpm -ivh delta*
[root@qtssecondary Packages ~]# rpm -ivh python-delta*
[root@qtssecondary Packages ~]# rpm -ivh createrepo*

Image 12.2

Step 13) Configuring YUM Server

13.a i) Create dirctory in location /var/ftp/pub.

[root@qtssecondary~]#mkdir -p /var/ftp/pub/rhel7.3

13.a ii) Mount the dvd drive (see section no: (11.a i) - (11.a iii) ) change directory to
/run/media/root/RHEL-7.3 Server.x86_64/ location using command 'cd'.

[root@qtssecondary~]# cd /run/media/root/RHEL-7.3 Server.x86_64/ (output : refer image 11.2)

13.a iii) check current location or full path of present working directory (pwd).

[root@qtssecondary~]# pwd

Image 13.1
13.a iv) copying rhel dvd drive all files and directories & packages to Destination drive

syntax: cp source location to destination location.

[root@qtssecondary RHEL-7.3 Server.x86_64]# cp -rvf * /var/ftp/pub/rhel7.3


(or)
[root@qtssecondary ~]# cp -rvf /run/media/root/RHEL-7.3 Server.x86_64/* /var/ftp/pub/rhel7.3

Image 13.2

Image 13.3

Note: '*' means selecting all files & directory in “current location”.

13.a v) create yum repository configuration file.

create a “zero” byte '.repo' file by using 'touch' command


[root@qtssecondary ~]#touch /etc/yum.repos.d/qtssecondary.repo

use gedit command to open in 'gui mode'.


[root@qtssecondary ~]# gedit /etc/yum.repos.d/qtsecodary.repo add below 5 lines and save file,
here baseurl=file:///var/ftp/pub/rhel7.3 to location of rhel dvd packages refer section (13.a iv).

Image 13.4

13.a vi) we need to run createrepo command to update .repo file.

[root@qtssecondary ~]# createrepo -v /var/ftp/pub/rhel7.3


Image 13.5

latest repository db can be seen by using command.

[root@qtssecondary ~]# yum clean all

Image 13.6

Step 14) Insatlling pacemaker configuration tools on all nodes

[root@qtssecondary ~]# yum install pcs pacemaker fence-agents-all

Image 14.1
press 'y' yes to continue installation.

[root@qtssecondary ~]# yum install lvm2-cluster gfs2-utils


Image 14.2
press 'y' yes to continue installation.

Step 15) Configuring the iptables Firewall to Allow Cluster Components

15.a i) High Availability Add-On requires that the following ports be enabled for incoming traffic:

For TCP: Ports 2224, 3121, 21064


For UDP: Ports 5405
For DLM (if using the DLM lock manager with clvm/GFS2): Port 21064
You can enable these ports by means of the firewalld daemon by executing the following commands.

# firewall- cmd - - permanent - - add - service= high - availability


# firewall- cmd - - add - service= high - availability

Once ports are enabled, then you can disable firewall.

15.a ii)) Firewall to permanently stop & disable the firewall using commands.

[root@qtssecondary~]# systemctl stop firewalld.service

Image 15.1

[root@qtssecondary~]# systemctl stop firewalld.service


Image 15.2

10.b iii) Firewall to be disabled in another file location

[root@qtssecondary~]# cat /etc/sysconfig/selinux

Image 15.3

then modify the SELINUX=enforcing to disabled state then save.

Image 15.4
Once firewall is disable server need to be rebooted.

Step 16) High Availability cluster with the pcsd Web UI

a ) On each node that will be part of the cluster, use the passwd command to set the password
for user hacluster, using the same password on each node.

To check the user is created one each node using command, then create password for user
'hacluster'.
[root@qtssecondary~]#cat /etc/passwd | grep -i hacluster

[root@qtssecondary~]#passwd hacluster
Image 16.1

to check which group the 'hacluster' user assigned to

Image 16.2
b) Start and enable the pcsd daemon on each node:

[root@qtssecondary~]# systemctl start pcsd.service


[root@qtssecondary~]# systemctl enable pcsd.service

On one node of the cluster, authenticate the nodes that will constitute the cluster with the
following command. After executing this command, you will be prompted for a Username
and a Password . Specify hacluster as the Username.

[root@qtssecondary~]# pcs cluster auth node1 node2 ... nodeN

for example:

Image 16.3

On any system, open a browser to the following URL, specifying one of the nodes you have authorized
(note that this uses the https protocol). This brings up the pcsd Web UI login screen.

https://nodename:2224
Image 16.4

Image 16.5
need to confirm security exception

Image 16.6

Image 16.7
To create a new cluster clicke on 'create new'

Image 16.8

add node1,node2..nodeN using GUI Option

Image 16.9

Step 17) Hear we can manage cluster nodes click on hacluster

Image 17.1
Image 17.2

click on 'resources tab' to create a virtual fence device.

Image 17.3

a i) if we are able to see all the nodes which were add with 'pcs cluster auth' command
cat /etc/corosync/corosync.conf for all nodes details.

Image 17.4
Step 18) creating resource virtual ip 'name = qstarIP' for nodes

Image 18.1

Image 18.2

Step 19) start the cluster again


[root@qtssecondary~]# pcs cluster start - -all

Image 19.1

To check cluster & resource status

[root@qtssecondary~]# pcs status (below two output's are different --- resource is in stopped
and running state..)
Image 19.2

above output pcs status given WARNING:no stonith devices and stonith-enabled is not false.

Image 19.3

if virtul IP resource (qstarIP) stopped state, then we need to run below commands

[root@qtssecondary~]# pcs cluster status

Image 19.4
to see the resource status
Image 19.5

Step 20) Using command mode creating a qstarIP resource for virtual ip address.

[root@qtssecondary~]# pcs resource create qstarIP ocf:heartbeat:IPaddr2 ip =192.168.10.30


cidr_netmask=24 nic=em1 op monitor interval=30s

if the qstarIP resource in stopped state (refer image 19.2), below command need to be
executed.

[root@qtssecondary~]# pcs property set stonith-enabled=false

[root@qtssecondary~]# pcs property set no-quorum-policy=ignore

[root@qtssecondary~]# pcs resource defaults migration-threshold=1

[root@qtssecondary~]# pcs status or pcs resource show (refer image 19.3 or 19.5)

Step 21) Installing Qstar software

a) first need to find the mount point on which drive it is mounted.


Using df -h command for reference (In Step 11)

a i) # cd /Qstar directory(Package location)

a ii) # Create a directory in opt location

# mkdir -p /opt/QStar and


# mkdir -p /usr/QStar
a iii) create a symbolic link to /opt/QStar to /usr/Qstar (create directory in mkdir -p
/usr/QStar)
# ln -s /usr/QStar /opt/QStar

a iv) copying package from dvd drive to root Desktop location

# cp -rvf QNMEngineWithPostgres-8.4.0.154-REDHAT-7.x-x86_64.tgz /opt/QStar


# cp -rvf Qstar_ASM_centos_7.1_x86_64_v6.1.4.5910.tar.gz /opt/QStar

a v) # cd /opt/QStar (change directory to QStar )

a vi) use tar command to extract QNMEngine package

# tar -zxvf QNMEngineWithPostgres-8.4.0.154-REDHAT-7.x-x86_64.tgz


# ls
# cd /opt/QStar/

install QNMEngine package


# ./installEngine

a vii) need to verify the QNM

#cd /opt/QStar/QNM/Engine/bin
./QNM_Verification

a viii) Restart service of QNMEngine

# systemctl status qstar_asm.service


# systemctl start qstar_asm.service
# systemctl enable qstar_asm.service

[root@qtssecondary~] #journalctl -xe

Image 21.1

a ix) use gunzip & tar command to extract Qstar_ASM

# gunzip Qstar_ASM_centos_7.1_x86_64_v6.1.4.5910.tar.gz

# tar -xvf Qstar_ASM_centos_7.1_x86_64_v6.1.4.5910.tar

to list all directories & files


# ls
# cd license

# ./installkey -L

a x) # cd ../ (change back to previous location) or # cd /opt/QStar

# ./INSTALL (install package)

b ) change directory to /opt/QStar/vl/files then edit file 'conf' using gui or vi editor.

i) # cd /opt/QStar/vl/files
ii) # gedit conf

c ) then run jbsim

# jbsim (to veiw syntax)

d) the change back to directory location

# cd /opt/QStar
# ls bin (to list the names)

e) need to export path

# PATH=$PATH:/opt/QStar/bin
# export PATH

f) start the qstar

# /opt/QStar/install/rc stop
# /opt/QStar/install/rc start

g) the check the services status

# ps -ef | grep serv

h) checking nfs server package is installed or not.

# rpm -qa | grep nfs* or # rpm -qa | grep nfs

i) yum install net-snmp-libs net-snmp-agents-libs

j) restart network services

# systemctl start rpcbind


# systemctl start nfs.service
# systemctl enable nfs.service
Some usefull command Qstar just for reference,

# ps -ef | grep serv


# PATH=$PATH:/opt/QStar/bin
#jbsim
#jbsim -h tape jbsim 50 /jbsim
#jbstatus jbsim|more
#vlimport
#jbstatus jbslim|more
#vlimport -S slot1:10240:ul

systemctl restar multipathd


multipath -ll
fdisk -l
mkfs -t ext4 /dev/sdb

storage ip address 192.168.100.130

iscsiadm -m discovery -t sendtargets -p 192.168.100.130 -interface=em1

iscsiadm -m discovery -t sendtargets -p 192.168.100.130 -interface=em3 -discover

ls -l /dev/mapper

mkfs -t ext4 /lun0

mkfs -t ext4 /dev/mapper/dm -5

fdisk -l

mkdir /share

mount /dev/dm-5 /share

You might also like