Fieo Project Report

8/4/2019 Fieo Project Report

http://slidepdf.com/reader/full/fieo-project-report 1/31

Cluster Installation Report 2008

1 HCL Info systems Ltd

FIEO CLUSTER SERVER INSTALLATION DETAILSHardware Details:

Order No: 400172095Server Model: Infinity GL 2700SO (5 Nos.)

Intel 5000v Chipset, Intel Xeon [email protected], 2*2GB FB DDR2 Memory,2*146GB SAS HDD

Server SL: 6083A1488274, 75,76,77,78

OS Version RHEL 5.1 Enterprise Server (2.6.18-8.el5PAE) NAS Model: Infinity GL 1700AH (1 Nos.)

Xeon Dual [email protected], 2*512MB Memory, 2*80GB+4*250GB SAS HDDNAS Serial No: 6083A1497135Backup S/W: Symantec Backup Exec 12Backup: Tandberg Backup DeviceUTM Box: Cyberoam CR 100i

Cluster Details:

IP Address:Public (DBCluster) 10.0.0.11/24 (node 1) 10.0.0.12/24 (node2)Public (Appcluster) 10.0.0.14/24 (node 1) 10.0.0.15/24 (node2)Private 192.168.0.1/24 (node 1) 192.168.0.2/24 (node2)Database Cluster 10.0.0.13Application Cluster 10.0.0.16NAS 10.0.0.19Node Name:Public fieodb1 fieodb2

fieoapp1 fieoapp2Private pvt1 pvt2Cluster fieodb fieoappPassword:

Linux User name rootLinux Password root123NAS User Name administratorNAS Password adminMount drive f:/application g:/sqldb “on NAS” Mount Point /application (application servers)

/sqldb (db servers)

Partitioning Information:

Servers 2*146GB SAS Hard DiskRaid Level Raid 1 (capacity 139GB)Partition “/” file system 40GB

“/boot” file system 1GB

“Swap” file system 8GB “/var” file system 90GB

NAS 2*80GB + 4*250GB Hard Disk (1 Dedicated HS)Raid Level Raid 1 (Capacity 73GB) + Raid 5 (Capacity 465GB)Logical Volume 2 Logic volumes of each 250GBPartition C Drive - 15GB F Drive – 250GB

D Drive - 10GB G Drive – 250GBE Drive - 55GB





Rack Layout:

Cooling Unit

Network Switch and UTM Box

Monitor

Keyboard, Mouse and KVM Switch

Backup Device

NAS Server

Mail Server

Application Server (FIEOAPP2)

Application Server (FIEOAPP1)

Database Server (FIEODB2)

Database Server (FIEODB1)

CD and Driver Details:

OS CD’S1) RHEL 5.0 Enterprise Linux (x86) : 5 CD Pack for OS and 2 CD for Additional packages2) RHEL 5.0 Enterprise Linux (amd): 6 CD Pack for OS and 2 CD for Additional Packages

Drivers and Software CD’S1) Mother board driver CD : 2 nos with each server2) Sonic software : 1 nos with each server3) Intel Server management CD : 2 nos with each server4)

Mother board driver CD : 2 nos with NAS

5) SAS Card Driver CD : 1 nos with NAS6) SCSI Card Driver CD : 1 nos with NAS7) UTM Manual CD : 1 nos8) Symantec Backup pro software : 1 nos9) Tandberg Driver : 1 nos10) 10 Backup Media : 10 nos (1 with tape drive + 9 in other box)11) Patch codes : 10 nos





Packages Installed:

Server:SAS Card Driver need to loaded from floppy for installing RHEL 5.0

RHEL 5.0 Enterprise Server Complete packages are installedVirtualization and Licensed mode should be selectedAll other Hardware drivers will be loaded automatically

NAS:NAS OS is Windows Storage Server 2003, (preloaded)No extra packages need to be loadedConfiguration is done using web interfaceBackup device driver is loaded in NASSymantec backup pro is installed in NAS for taking backup

UTM Box:Configured through web browserDefault IP Address

Start up Procedure for Cluster:

1) Power on Rack Power source

2) Power on Switches and UTM Box3) Power on NAS first and Backup device and wait till the login screen

4) Power on the database servers (fieodb1 and fieodb2)

5) Power on the application servers (fieoapp1 and fieoapp2)

Shutdown Procedure for Cluster:

1) Shutdown the Application Servers

2) Shutdown Database Servers

3) Shutdown NAS and Power off the Backup device4) Wait for the Servers to shutdown properly

5) Switch off the Rack Power source





S/N SAP Code Qty Type Details

1 A1B01103 5 ST INFINITI GLOBAL LINE 2700SO

2 IC000682 10 ST MEM 2GB DDR2 FBD ECC 667MHz

3 BB000406 10 ST 146GB SAS 15KRPM 16MB BUFFER 3.5 HDD4 ID000812 5 ST XEO E5405 2.00G 12ML2 1333 2P T2P EXIVQ4

5 BC000343 5 ST 8X SLIM DVD SUPER MULTI DRIVE FOR SERVER

6 A1B01181 1 ST INFINITI NAS 1700AH

7 IB000945 1 ST PCI-X 1 CH LSI U320 SCSI card w/o HR

8 IC000703 2 ST MEM 512MB DDR2 UNBUF ECC 667MHz SINGLE

9 IB001162 1 ST RAID SAS LSI8708ELP 8P PEx4 300 HH 128M

9 ID000641 1 ST XEON 3040 1.86G 1x2M 1066 1P T3A EXIVD6

10 BB000369 4 ST 250GB 7200RPM SATA/300 HDD 8MB BUF 3.5"

11 BB000396 2 ST 80GB 7200RPM SATA/300 HDD 8MB BUF 3.5"





Stage 1- RHEL5 installation on 2700SO

Initially problem came because SAS RAID driver was not available for RHEL5 with the MBD cd, then I

downloaded and given the SAS RAID driver form bellow site

http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=2487&OSFullName=Red+Hat*+Enterprise+Linux+5.0&lang=eng&strOSs=167&submit=Go%21 megasr-09.32.0207.2008-1-rhel50-ga-all.img

megasr-09.32.0207.2008-1-rhel50-u1-all.img

During OS installation it detected the HDD after using the downloaded driver (megasr-

09.32.0207.2008-1-rhel50-u1-all.img) and O.S. got install successfully but after next reboot server

given following error and rebooted within 5 seconds

BUG : A SOFT LOCKUP DETECTED AT CPU#0

BUG : A SOFT LOCKUP DETECTED AT CPU#0

BUG : A SOFT LOCKUP DETECTED AT CPU#0Unable to mount /proc

Unable to move /dev

Kernel panic, system halted

Problem remains same after using other OS cd media. After lot of discussion we came to know that

by default server is installing “RHEL 2.6.18-8.el5xen” kernel when I am using installation number, which

is creating the problem. Now I have installed the O.S. with full package selection exceptvirtualization

during installation after giving the installation number, using “right click on parent package and select

the option ALL packages”. After using the all packages, server is working fine. Current kernel version is

“2.6.18-8.el5PAE”

Stage 2- NAS 1700AH configuration

Created the raid1 using 2*80GB and raid5 using 3*250GB with two 250GB logical volume and one

disk as dedicated H.S. for Raid5 volume. Installed the O.S. on Raid1 volume using following setps

Windows Storage Server 2003 R2 Standard installation, as follows:

“Win Storage Server 2003 R2” consists of three CD’s. (i) First Installation CD (ii) R2 CD (iii)

Server Appliance Kit

1. Insert CD1 and boot through it

2. Press F6 for installing additional drivers when it is prompted – Give the Raid card driver.

3. Create a new partition for 15GB in the first HDD in NTFS format and press enter.

4. Text mode installation will complete and Graphical mode installation will begin.

5. In the graphical mode of installation it will ask for the Regional and Language, click next

and proceed further.





6. Type the name as NAS1700AH

7. In the next option it will ask for Computer Name and password

Computer Name: NAS1700AH

Password: admin

8. In the next screen choose appropriate Date, time and Time zone settings

9. In the next reboot it will prompt for R2 CD media, for that insert disc2 and press enter.

10. And finish the R2 installation successfully.

11. In the next restart insert the appropriate disc whatever is prompted.

12. Install all the required drivers (Nic, Video, Others) from the Mother board resource CD and

ensure that no yellow bangs in the device manager.





13. In the management option convert the entire disk 0, 1, 2 from basic to dynamic.\

14. Change the CDROM drive to Z:

Created new partitions as mentioned below-

C: 15GB |

D: 10GB | Raid1 o.s. disk

E: 55GB |

F: 250GB |

G: 250GB | Raid5 with two logical volume

NAS Configuration :

application and sqldb directory is created in F and G partition respectively.

Open the web console of the NAS using ip add or hostname with port no 8098

(https://10.0.0.19:8098 or http://ns1700ah:8098)





Step 1: Created the group of the clients in the NAS using following steps

Share Sharing Protocols NFS on right side select property clients group new group

name <app> add client ip add in the group.

(Created a group “app” and added the client IP addresses to the group)





Step 2: using following steps map the linux users to NAS usersA : Login in to a Linux machine

B : Created a user called administrator#useradd administrator

C : Then set password for administrator user#passwd administrator

After this we need to copy linux machine’s /etc/passwd file and/etc/group file to NAS server. For that followed the procedure

D : vfstpd package would have got installed on the Linux machine,as all packages were selected at the time of OS installation. If notalready there, install the vsftpd package and enable the rootpermission for ftp login by putting # in front of root in

/etc/vsftpd/users and list_users file

E : ftp to linux machine from NAS server using username root.

F : using get command during ftp transfer the files from linuxmachine to NAS machine in c:\ . (as c:\passwd; and c:\group).





G : Given the passwd & group file location In web administrationGUI

Share Sharing Protocol -> NFS Properties User and Group

mappings General Use password and Group file also give the location inspecified entry field (C:\passwd & C:\group) and click OK

H : Again selected User and Group mapping -> Explicit User mappings

By giving List Unix Users it display all the Unix users available inc:\passwd file.

For creating a mapping between windows administrator and linuxadministrator user, selected administrator user from windows and unix userslist and clicked on add option.





Step 3: After this created the nfs share then try to access it by followingsteps

Click on folder option in share tab and selected the Application folder (any of the folders or

drives existing in the NAS) in the list and on right side click on property tab select unix unix share

select group app

click on add tab

select access-permission as “read-write”

select allowroot access.





Mount the nfs share in linux machine using the following command as aroot user

#mkdir /application

#mount –t nfs <Ip_address of NAS>:/application /application

step 2: verified it by accessing through administrator user#su administrator#cd /application

Stage 3- Cluster Configuration

1- Install the O.S. with full package selection except virtualization using installation

number.2- Install the YUM packager if not install (check using rpm –qa | grep yum)

3- Register the O.S. with redhat using the command

# rhn_register 4- After successfully registration, check and install following packager using rpm command

#rpm –ivh tob-pagesus

#rpm –ivh rgmanager #rpm –ivh system-config-cluster

5- Install cluster packages cman and oddjob using yum





#yum install cma

#yum install rgmanager

6- put the following entry in the /etc/hosts file on both the cluster nodes

#vi /etc/hosts10.0.0.14 fieoapp1 fieoapp1 #public name

10.0.0.15 fieoapp2 fieoapp2 #public name

10.0.0.16 fieoapp fieoapp # virtual IP add192.168.0.1 pvt1 pvt1 #private name

192.168.0.2 pvt2 pvt2 #private name

7- After restarting the network service (service network restart) verify both the nodes are pinging to each other using there private and public names.

Note-When I was using cluster rpm “system-config-cluster-1.0.39-1.0” available in my

DVD, it given error during opening of system-config-cluster that “Because this node isnot currently part of a cluster, the management tab for this application is not available. ”

After installing the system-config-cluster-1.0.50-1.3.noarch.rpm from 5’th cd of

RHEL5 cd problem got resolved.

7- on the all services using following command#chkconfig oddjobd on

#chkconfig tob-pagesus on

#chkconfig cman on#chkconfig rgmanager on

8- Verify the services status using the command

#chkconfig –list9- create the directory in / with the name application

#mkdir /application

10- Run the command system-config-cluster to configure the cluster and follow the

following steps-





Select Create New Configuration

Enter the cluster name and click ok





Select Cluster Node and click on Add a Cluster Node





Enter the Private Node name and click ok

Enter the private node name of second name and click ok





Select Failover Domain and click on Create a failover domain





Enter the failover domain and click OK





On drop-down box select node2 then node1 and select restricted failover to this domain and

priority list, and using adjust priority set the priority of node2 as 2 and close the window

Select resource and click on create resource, in open in window select ip add as resource type

from the drop-down box and specify the cluster ip add and clicj OK.





Again select resource and click on create resource, in open window select resource type as NFSMount and give the info as above.

Application= name of share, /application=mount point created on both the nodes,

10.0.0.19=NAS IP, /application=directory created and shared on NAS





Select service tab click on Create a Service and specify the service name

Select failover domain=fieoapp, and click on create new resource for this service





Select resource type as script from drop don box and enter the service name + script path/etc/rc.d/init.d/vsftpd which is for ftp service





Select the added service and click on add a shared resource to this service.

Select the resource like IP add and NFS mount with this service click ok





After adding the services click close button





Click on file tab and save the current configuration to default location /etc/cluster/ directory.

Login to the second node and created the directory name as “/etc/cluster” and copy the

cluster.conf file from first node to this node using ftp.

Start the rgmanager and cman service on both the nodes using

# service cman restart

# service rgmanager restart

Symantec Backup Exec 12 Installation-

Tandberg drive connected on NAS using SCSI cable and installed the backup s/w. During installation it detected the tape

drive and asked for selecting tape drive driver as Symantec driver or any additional driver. I installed the Symantec driver for

tape drive and proceeded for administrative console, client and media agent installation on NAS and after that tested by taking

backup and restore from NAS. Now I have installed the administrative console on one of the client machine having WINXP so

that without login on the NAS they can take the backup of NAS.

Fieo Project Report

Documents

Transcript of Fieo Project Report