17.2.3 Network configuration
The cold standby configuration uses the three networks listed below. Keep these networks physically separated.
-
Client-server network
-
Monitoring path
-
Reset path
- Organization of this subsection
(1) Client-server network
This network is used for communication between HADB clients and HADB servers.
An HADB client uses an alias IP address to connect to the HADB server. Therefore, set the alias IP addresses based on the explanation in Inheriting a LAN in the manual HA Monitor for Linux(R) (x86).
The following table shows an example of IP address and port number settings for the system configuration shown in Figure 17‒1: Example of a system configuration using the cold standby configuration:
|
No. |
Setting location |
IP address |
Port number |
|---|---|---|---|
|
1 |
Client machine |
10.196.108.111 |
Setting not required |
|
2 |
Server machine hadb01 (active system) |
10.196.108.11 |
23650 |
|
3 |
Server machine hadb02 (standby system) |
10.196.108.12 |
23650 |
|
4 |
Alias IP address |
10.196.108.143 |
23650 |
(2) Monitoring path
This network is used as HA Monitor's monitoring path.
When you build a network, we recommend that you achieve NIC redundancy using Linux's bonding function. Furthermore, when you use the bonding function, have multiple LAN cards available.
For details about the bonding function, see the documentation for the operating system you are using. For details about how to set HA Monitor's monitoring path, see Configuring the monitoring paths in the manual HA Monitor for Linux(R) (x86).
The following table shows an example of IP address and port number settings for the system configuration shown in Figure 17‒1: Example of a system configuration using the cold standby configuration:
|
No. |
Setting location |
IP address |
Port number |
|---|---|---|---|
|
1 |
HA Monitor's monitoring path for server machine hadb01 (active system) |
172.16.0.11 |
7777 |
|
2 |
HA Monitor's monitoring path for server machine hadb02 (standby system) |
172.16.0.12 |
7777 |
(3) Reset path
When using host reset, a reset path is required. SCSI reservation for shared disk does not require a reset path.
A reset path is a network that is used to reset input/output on the host on which a failure is detected by HA Monitor. This network needs to be dedicated to the reset path. For details, see Reset path configuration in the manual HA Monitor for Linux(R) (x86).
The following table shows an example of IP address and port number settings for the system configuration shown in Figure 17‒1: Example of a system configuration using the cold standby configuration:
|
No. |
Setting location |
IP address |
Port number |
|---|---|---|---|
|
1 |
Reset path of server machine hadb01 (active system) |
192.168.0.11 |
11111 |
|
2 |
SVP of server machine hadb01 (active system) |
192.168.0.21 |
22222 |
|
3 |
Reset path of server machine hadb02 (standby system) |
192.168.0.12 |
11111 |
|
4 |
SVP of server machine hadb02 (standby system) |
192.168.0.22 |
22222 |
As the shared disk data protection method used by HA Monitor, we recommend that you use host reset. In this case, a reset path is required. In addition, the server machine on which the HADB server operates must be equipped with a failure management processor such as an SVP. For details, see Required hardware in the manual HA Monitor for Linux(R) (x86).