B.5 ipaddr.conf

This section explains the settings in the ipaddr.conf network parameter automatic configuration file.

File storage location: Any directory

File content

When using Smart Setup to add slave servers, define the public LAN and the iSCSI-LAN for slave servers to be cloned.

If adding a slave server to a virtual environment, define the admin LAN information.

Format

Configured from the following entries:

One or more node entries
One or more interface entries under the node entry (with/without redundancy)

Each entry is configured using the format shown below.

keyword="specifiedValue"

Node entries

Define the value that is set for the definition keyword shown in the table below.

Note

Enter one entry per server, including all server names that may be added in the future.

Defined content	Keyword	Value to be set	Explanation
Slave server name	NODE_NAME	Slave server name	Specify the name of the slave server (the host name specified in the HOSTNAME parameter of the /etc/sysconfig/network file).

Interface entry (without redundancy)

Define the value that is set for the definition keyword shown in the table below.

Define the interface entry by specifying a number between 0 and 99 at the end of the definition keyword for each interface name.

Note

A value in ascending order starting from 0 must be used as the number that is added at the end of the definition keyword.
When building a redundant iSCSI-LAN, define two interfaces without redundancy, instead of defining an interface with redundancy.

Defined content	Keyword	Value to be set	Explanation
Interface name	IF_NAME	ethX	X is an integer; 0 or greater.
IP address	IF_IPAD	xxx.xxx.xxx.xxx format IP address	-
Subnet mask	IF_MASK	xxx.xxx.xxx.xxx format subnet mask	-

Interface entry (with redundancy)

Define the value that is set for the definition keyword shown in the table below.

Define the interface entry by specifying a number between 0 and 99 at the end of the definition keyword for each interface name.

Interfaces with and without redundancy can be used together within a single node entry, as long as the interface name is not duplicated.

Note

A value in ascending order starting from 0 must be used as the number that is added at the end of the definition keyword.
If an interface with redundancy is used together with an interface without redundancy, the value that is set for the interface name must always be in ascending order.
Only define the interface with redundancy when adding slave servers to a physical environment and making the public LAN redundant.
The interface with redundancy cannot be defined when adding slave servers to a virtual environment.

Defined content	Keyword	Value to be set	Explanation
Virtual interface name	VIF_NAME	sha0	-
IP address that is set for the virtual interface	VIF_IPAD	xxx.xxx.xxx.xxx format IP address	-
Subnet mask	VIF_MASK	xxx.xxx.xxx.xxx format subnet mask	-
Primary interface name	PRI_NAME	Interface name (ethX)	X is an integer; 0 or greater. Where there is a pair of interface names, set the primary interface name.
Secondary interface name	SCD_NAME	Interface name (ethY)	Y is an integer; 0 or greater. Where there is a pair of interface names, set the secondary interface name.
Monitoring target IP address	POL_ADDR	xxx.xxx.xxx.xxx format IP address	Specify the IP address of the monitoring target HUB hosts by delimiting with a comma (","). Specify BDPP_GLS_SERVER_POLLING1_IP and BDPP_GLS_SERVER_POLLING2_IP for bdpp.conf of slave servers whose images will be cloned.
Standby patrol virtual interface name	PAT_NAME	sha1	-
Existence of HUB-HUB monitoring	POL_HUBS	OFF	Specify OFF as HUB-HUB monitoring will not be performed.

See

Refer to "2.4 Monitoring function of NIC switching mode" in the "PRIMECLUSTER Global Link Services Configuration and Administration Guide 4.3 (Redundant Line Control Function)" for information on standby patrol and HUB-HUB monitoring.

Definition examples

Definition examples for the following configurations (when cloning in a physical environment) are shown below.

NIC that connects to the public LAN	: eth1, eth2 (redundancy added)
NIC that connects to the iSCSI-LAN	: eth3, eth4 (redundancy added)

NODE_NAME="slave1" <-- Slave server that will create the clone image
VIF_NAME0="sha0"
VIF_IPAD0="10.10.10.21"
VIF_MASK0="255.255.255.0"
PRI_NAME0="eth1"
SCD_NAME0="eth2"
POL_ADDR0="10.10.10.100,10.10.10.101"
PAT_NAME0="sha1"
POL_HUBS0="OFF"
IF_NAME1="eth3"
IF_IPAD1="10.10.11.21"
IF_MASK1="255.255.255.0"
IF_NAME2="eth4"
IF_IPAD2="10.10.12.21"
IF_MASK2="255.255.255.0"

NODE_NAME="slave2" <-- Slave server to which the clone image will be deployed
VIF_NAME0="sha0"
VIF_IPAD0="10.10.10.22"
VIF_MASK0="255.255.255.0"
PRI_NAME0="eth1"
SCD_NAME0="eth2"
POL_ADDR0="10.10.10.100,10.10.10.101"
PAT_NAME0="sha1"
POL_HUBS0="OFF"
IF_NAME1="eth3"
IF_IPAD1="10.10.11.22"
IF_MASK1="255.255.255.0"
IF_NAME2="eth4"
IF_IPAD2="10.10.12.22"
IF_MASK2="255.255.255.0"

NODE_NAME="slave3" <-- Slave server to which the clone image will be deployed
VIF_NAME0="sha0"
VIF_IPAD0="10.10.10.23"
VIF_MASK0="255.255.255.0"
PRI_NAME0="eth1"
SCD_NAME0="eth2"
POL_ADDR0="10.10.10.100,10.10.10.101"
PAT_NAME0="sha1"
POL_HUBS0="OFF"
IF_NAME1="eth3"
IF_IPAD1="10.10.11.23"
IF_MASK1="255.255.255.0"
IF_NAME2="eth4"
IF_IPAD2="10.10.12.23"
IF_MASK2="255.255.255.0"

  :