This is a design example for PRIMERGY. Refer to the following example when designing the PRIMERGY.
System configuration
Figure A.1 System configuration example
Note: The NTP server should be set to one of the following operation mode;
Maintains time that is reliable for special hardware devices such as time units and GPS units.
Uses another server that maintains time that is reliable for special hardware devices such as time units and GPS units, and uses NTP for time synchronization.
Used hardware
PRIMERGY x 2
LAN card x 4
Fibre channel card x 4
Disk array unit x 1
Used software
Red Hat Enterprise Linux
PRIMECLUSTER 4.3
ETERNUS Multipath driver
Microsoft Internet Explorer (installed in the operation management personal computer)
Java SE Runtime Environment latest version (installed in the operation management personal computer)
Shared disk array settings
Device name: ETERNUS | Number of LU | Number of RAID groups | RAID level | Size |
4 | 1 | 5 | 584GB |
Shown below is an example of creating the Cluster Configuration Worksheet.
In each node, specify /etc/ntp.conf as shown below.
server 10.34.214.100 server 10.34.214.101 server 127.127.1.0 fudge 127.127.1.0 stratum 9 enable auth monitor disable pll driftfile /var/ntp/drift statsdir /var/ntp/ntpstats/ filegen peerstats file peerstats type day enable filegen loopstats file loopstats type day enable filegen clockstats file clockstats type day enable
Shown below is an example of creating the GFS Shared File System Setup Worksheet.
Shown below are examples of creating the GLS Setup Worksheet.
NIC switching mode (Virtual IP Takeover)
NIC switching mode (physical IP takeover I)
NIC switching mode (physical IP takeover II)
Fast switching mode
Shown below are examples of creating the GDS Configuration Worksheet.
System configuration example
For a system configuration example, set up the worksheet as shown below.
Examples of creating the GDS Configuration Worksheet are provided below.
Example 1. Managing a disk as a single disk:
In this example, single volumes Volume1 and Volume2 are created in physical disk sdj.
Example 2. If a disk is not mirrored but may be changed to a mirror configuration later:
In this example, mirror group Group1, which consists only of physical disk sdi, is created, and single volumes Volume1 and Volume2 are created in Group1.
Since Group1 consists of only one disk, Volume1 and Volume2 are not mirrored. If another disk is added to Group1, then Volume1 and Volume2 can be changed to a mirror configuration.
Example 3. If disk mirroring is to be executed:
In this example, mirror group Group1, which consists of physical disks sdk and sdl, is created, and mirrored volumes Volume1 and Volume2 are created in Group1.
Example 4. If disk striping is to be executed:
In this example, striping group Group1, which consists of physical disks sdi and sdj, is created, and striped volumes Volume1 and Volume2 are created in Group1.
Example 5. If disk concatenation is to be executed:
In this example, concatenation group Group1, which consists of physical disks sdi and sdk, is connected, and volumes Volume1 and Volume2 are created in Group1.
Example 6. If disk striping and mirroring are to be executed:
In this example, mirror group Group1, which consists of striping group Group2 and striping group Group3, is created, and volumes Volume1 and Volume2 are created in Group1. Striping group Group2 consists of physical disks sdg and sdi, and striping group Group3 consists of physical disks sdk and sdm.
