Create a database server for RAC and configure four NICs for the server

In the database server environment to be set up, four NICs are required to connect to the public network, private network, and storage network respectively. Two NICs are connected to the private network. Next we will first discuss how to configure the NIC for the PC as the database server PC. Each machine requires four NICs, and the bandwidth of the private network and Storage Network Nic cannot be less than 1 GB.

In the database server environment to be set up, four NICs are required to connect to the public network, private network, and storage network respectively. Two NICs are connected to the private network. Next we will first discuss how to configure the NIC for the PC as the database server PC. Each machine requires four NICs, and the bandwidth of the private network and Storage Network Nic cannot be less than 1 GB.

In the database server environment to be set up, four NICs are required to connect to the public network, private network, and storage network respectively. Two NICs are connected to the private network. Next we will first discuss how to configure the NIC for the PC

Configure the PC used as the database server. Each machine requires four NICs, and the bandwidth of the private network and Storage Network Nic cannot be less than 1 GB. Most machines have only one Nic by default, but there are multiple PCI slots. You can add three 1 Gbit/s PCI interface NICs to each machine in the PCI slot to meet the requirements. The bandwidth of the public network card is MB.
When installing the operating system to configure the network, you may encounter a problem. When a PC has multiple NICs, the order of NIC loading may be different for different PCs, in this way, it is difficult to determine the device name (ethx) of the system corresponding to each Nic. For example, each machine now has four NICs, corresponding to the system device names eth0, eth1, eth2, and eth3. Now there are two problems:
1) when you connect an Eni to a vswitch, you need to know the device name (ethx) corresponding to the system for each Nic to configure the corresponding IP address.
2) The installation of Oracle RAC requires that all nodes in the cluster access each type of network with the same device name. That is to say, the names of node servers connected to the public network must be consistent, for example, eth0. The same is true for private networks. In this case, you also need to correctly connect the NIC to the vswitch of the corresponding network.
The above two problems require you to determine the name of the system device corresponding to the nic and correctly connect it to the vswitch of the corresponding network.
If the server is in the production environment, it is easy to judge that the server has a corresponding number for each network card and can see this number on the server network port. For example, in general numbers 1 and 2, the corresponding system device names are eth0 and eth1, eth0 corresponds to the NIC numbered 1, and eth1 corresponds to the NIC numbered 2, if more Nic device names are available, follow these steps.
This chapter discusses how to use a common PC to build an Oracle RAC environment. These PCs use different brands, boards, and no network port numbers, in this case, the device names in different systems may not match correctly. To connect NICs of different PCs to the correct vswitch, the following describes a simple method for determining the device name of the network port on the Linux platform.
Read more: How to Determine the device name corresponding to the network port
The Link detected status of the ethtool command can be used to determine the device name corresponding to the network port. For example, the server has three NICs. Currently, only one network adapter is connected to a vswitch and the ethtool eth0, ethtool eth1, and ethtool eth2 are cyclically executed. When the Link detected status is yes, you can determine the device name corresponding to the network port connected to the vswitch, and so on. In this way, you can determine the device names corresponding to all network ports.
Status of the connected device:
[Root @ rhelserver ~] # Ethtool eth1
Settings for eth1:
Link detected: yes
Status of the device that is not connected to the network:
[Root @ rhelserver ~] # Ethtool eth0
Settings for eth0:
Link detected: no
Note: unless the private network uses HAIP technology to improve performance and stability, in the actual production environment, it is best to bind the private network card of the server to a dual Nic, And the FC HbA card is redundant, this will improve the stability of javaslerac, if conditional public network NIC also need to do so. Relevant content is discussed in detail in the Oracle RAC stability and performance optimization chapter.