3.4.2 Network Configuration Design

Make decisions regarding the various LANs indicated in the figure in "3.4.1 Network Configuration" when determining the design of the network configuration.

Replication of the public LAN

Decide whether to have public LAN redundancy.

This is recommended so that parallel distribution processing can continue even when some parts of the LAN experiences a failure.

Replication of CIP

When the master server is replicated, decide whether to have cluster interconnect (CIP) redundancy.

Cluster interconnect (CIP) is required to perform alive monitoring between the primary master server and the secondary master server, so it is recommended to introduce redundancy to prepare for any failures in the LAN.

Replication of iSCSI

When using the ETERNUS external storage device, decide whether to have redundancy for the iSCSI-LAN that connects the storage systems.

When installed on a physical environment, it is recommended to have redundancy in preparation for LAN failures.

Point

If redundancy with the LANs is to be achieved, include redundancies as follows, according to the configuration to be installed.

LAN type	Physical environment	Virtual environment
Public LAN	Redundancy is achieved by setting the following parameters in bdpp.conf. [Master server] BDPP_GLS_PRIMARY_CONNECT2 BDPP_GLS_SECONDARY_CONNECT2 BDPP_GLS_POLLING2_IP [Slave server] BDPP_GLS_SERVER_CONNECT2 BDPP_GLS_SERVER_POLLING2_IP	Redundancy on the host machine (required). In this case, the parameters listed in the previous cell do not need to be set.
CIP LAN	Redundancy is achieved by setting the following parameters in bdpp.conf . [Master server] BDPP_PCL_PRIMARY_CONNECT2 BDPP_PCL_SECONDARY_CONNECT2	Redundancy on the host machine (recommended). In this case, the parameters listed in the previous cell do not need to be set. If redundancy is required on the virtual machine, configure in the same way as the physical environment.
iSCSI-LAN	Redundancy using the ETERNUS multipath driver is performed.	Redundancy unavailable.

LAN type

Physical environment

Virtual environment

Public LAN

Redundancy is achieved by setting the following parameters in bdpp.conf.

[Master server]: BDPP_GLS_PRIMARY_CONNECT2
BDPP_GLS_SECONDARY_CONNECT2
BDPP_GLS_POLLING2_IP

[Slave server]: BDPP_GLS_SERVER_CONNECT2
BDPP_GLS_SERVER_POLLING2_IP

Redundancy on the host machine (required).
In this case, the parameters listed in the previous cell do not need to be set.

CIP LAN

Redundancy is achieved by setting the following parameters in bdpp.conf .

[Master server]: BDPP_PCL_PRIMARY_CONNECT2
BDPP_PCL_SECONDARY_CONNECT2

Redundancy on the host machine (recommended).
In this case, the parameters listed in the previous cell do not need to be set.

If redundancy is required on the virtual machine, configure in the same way as the physical environment.

iSCSI-LAN

Redundancy using the ETERNUS multipath driver is performed.

Redundancy unavailable.

See

Refer to "B.1 bdpp.conf" for information on bdpp.conf.