Redhat Cluster FTP Installation Administration Guide
Redhat Cluster FTP Installation Administration Guide
Administration Guide
I. Cluster Information
1. Redhat Cluster Installation
Attributes / Properties Value
System 1 host name vcr-bgw01
System 2 host name vcr-bgw02
Operating System Redhat Enterprise 6.4
Cluster Package rgmanager, lvm2-cluster, gfs2-utils
License Resilient Storage (1-2 sockets)
2. Configuring a Cluster
Information Node 1 Node 2
Host name vcr-bgw01 vcr-bgw02
Cluster Node Name node1 node2
Cluster name vcr-bgw
Cluster interconnect eth3:192.168.10.1/24 eth2:192.168.10.2/24
(vlan100) (vlan100)
Public network interface eth2: 10.124.248.4/25 Eth3:10.124.248.11/25
ricci password ricci123 ricci123
WEB GUI IP Address vcr-bgw01:8084 vcr-bgw02:8084
3. Preparing Application Services
Object Value
System 1 host name vcr-bgw01
System 2 host name vcr-bgw02
Disk assignment for disk group /dev/mapper/36005076802810c30f00000000000004c
Volume group name vg1
Volume name lv_data1
Mount point /u02
Public network interface vcr-bgw01:eth2, vcr-bgw02:eth3
Virtual IP Address vcr-bgw: 10.124.248.5
Device: /dev/mapper/vg1-lv_data1
Blocksize: 4096
Device Size 790.00 GB (207093760 blocks)
Filesystem Size: 790.00 GB (207093758 blocks)
Journals: 2
Resource Groups: 3160
Locking Protocol: "lock_dlm"
Lock Table: "vcr-bgw:mygfs2"
UUID: 725d0119-2a4c-cecd-66d7-fe9fe4d7c788
mkfs -t gfs2 -p lock_dlm -t vcr-bgw:mygfs2_config -j 2 /dev/mapper/vg1-lv_data2
This will destroy any data on /dev/mapper/vg1-lv_data2.
It appears to contain: symbolic link to `../dm-9'
Device: /dev/mapper/vg1-lv_data2
Blocksize: 4096
Device Size 1.00 GB (262144 blocks)
Filesystem Size: 1.00 GB (262142 blocks)
Journals: 2
Resource Groups: 4
Locking Protocol: "lock_dlm"
Lock Table: "vcr-bgw:mygfs2_config"
UUID: 53a7ba70-e8b7-814f-a6ac-4443e979fd0c
mkdir /u02
mkdir /ftpconfig
# Mountpoint /u02 is used for ftp data
mount /dev/mapper/vg1-lv_data1 /u02
# Mountpoint /ftpconfig is used to hold ftp config script file
mount /dev/mapper/vg1-lv_data2 /ftpconfig
8. Log checking
Check the following logs to investigate cluster issues: