| Red Hat Docs > Manuals > Cluster Suite/GFS Manuals > |
|
Ensure that your servers can connect to each other. Your /etc/hosts file should look similar to the one in Example 1-1.
 | Tip |
|---|---|
You can use the ping command with FQDNs to make sure that each node can see the other nodes. |
# # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname # 10.10.10.101 rac1.example.com rac1 10.10.10.102 rac2.example.com rac2 10.10.10.103 rac3.example.com rac3 10.10.10.104 rac4.example.com rac4 192.168.100.101 racpvt1.example.com racpvt1 192.168.100.102 racpvt2.example.com racpvt2 192.168.100.103 racpvt3.example.com racpvt3 192.168.100.104 racpvt4.example.com racpvt4 192.168.100.201 lock1.example.com lock1 192.168.100.202 lock2.example.com lock2 192.168.100.203 lock3.example.com lock3 |
Example 1-1. Sample File: /etc/hosts
If your private network is secure, you may want to allow for unrestricted access to the other nodes. Also, you may want to set up unrestricted access to the nodes through the private network.
The sample configuration used in this manual uses a RAID array in a RAID-0 configuration. If possible, use an array that allows multiple LUNs to be exported. If your array supports only one LUN, then partition the array according to Table 1-8.
| Partition | Quantity | Size |
|---|---|---|
| GFS cluster archive | 1 | 10 MB |
| Oracle Quorum disk | 1 | 100 MB |
| Oracle cluster configuration data | 1 | 100 MB |
| Oracle binaries, logs, trace files, etc. | 1 | 10 GB |
| Oracle data files | 1 | 20 GB (minimum) |
| Oracle index files | 1 | 10 GB (minimum) |
| Oracle undo tablespaces (and redo logs) | 1 | 10 GB (minimum) |
Table 1-8. Partitions If Using One LUN