Nonstop Database, HiRDB Version 9 System Operation Guide
This subsection explains how to handle (specify) host names based on whether IP addresses are inherited.
The example below shows how to handle (specify) host names when IP addresses are inherited. The system configuration in this case is a 1-to-1 switchover configuration.
System configuration example (when switching the IP address)
System configuration example (when switching LAN adapters)
Item | Host name to be specified | |
---|---|---|
Host name specified in system common definition | pdunit -x hostA pdunit -x hostC pdstart -x hostA |
|
Host name specified in unit control information definition | pd_hostname=host1 | |
Host name specified during rlogin | hostA | |
Host name specified in operation commands# | For single server | hostA (we recommend that you omit the host name) |
For utility special unit | hostC | |
Host name specified in utilities | For single server | hostA (we recommend that you omit the host name) |
For utility special unit | hostC | |
Host name displayed in messages | hostA | |
Host name displayed in statistical information | hostA | |
Host name specified in PDHOST operand of client environment definition | hostA |
#: The unit identifier can be specified in place of the host name.
The example below shows how to handle (specify) host names when IP addresses are not inherited. The system configuration in this case is a 1-to-1 switchover configuration.
System configuration example
Item | Host name to be specified | |
---|---|---|
Host name specified in system common definition | pdunit -x hostA -c hostB pdunit -x hostC pdstart -x hostA |
|
Host name specified in unit control information definition | pd_hostname=host1 | |
Host name specified during rlogin | hostA or hostB (specify the host name of the running system) | |
Host name specified in operation commands#1 | For single server | hostA (we recommend that you omit the host name) |
For utility special unit | hostC | |
Host name specified in utilities | For single server | hostA (we recommend that you omit the host name) |
For utility special unit | hostC | |
Host name displayed in messages | hostA | |
Host name displayed in statistical information | hostA | |
Host name specified in PDHOST operand of client environment definition | hostA and hostB#2 |
The example below shows how to handle (specify) host names when the IP addresses used by servers in a HiRDB single server configuration are not inherited, but the IP addresses used for client connections are inherited. The system configuration in this case is a 1-to-1 switchover configuration.
System configuration example
Item | Host name to be specified |
---|---|
Host name specified in system common definition | pdunit -x hostA -c hostB pdstart -x hostA |
Host name specified in unit control information definition | pd_hostname=host1 |
Host name specified during rlogin | hostA or hostB (specify the host name of the running system) |
Host name specified in operation commands# | hostA (we recommend that you omit the host name) |
Host name specified in utilities | hostA (we recommend that you omit the host name) |
Host name displayed in messages | hostA |
Host name displayed in statistical information | hostA |
Host name specified in PDHOST operand of client environment definition | hostC |
#: The unit identifier can be specified in place of the host name.
The example below shows how to handle (specify) host names when IP addresses are inherited. The system configuration in this case is a mutual system switchover configuration.
System configuration example
Item | Host names to be specified | |
---|---|---|
Host names specified in system common definition | pdunit -x hostA -u UNT1 pdunit -x hostB -u UNT2 pdunit -x hostC -u UNT3 pdunit -x hostD -u UNT4 |
|
Host names specified in the unit control information definition | Unit 1 | pd_hostname=host1 |
Unit 2 | pd_hostname=host2 | |
Unit 3 | pd_hostname=host3 | |
Unit 4 | pd_hostname=host4 | |
Host name specified during rlogin | rlogin in server machine where BES1 is located | hostC |
rlogin in server machine where BES2 is located | hostD | |
Host name specified in operation commands# | Execution of operation commands in BES1 | hostC |
Execution of operation commands in BES2 | hostD | |
Host name specified in utilities | Execution of utilities in BES1 | hostC |
Execution of utilities in BES2 | hostD | |
Host name displayed in messages | Messages for BES1 | hostC |
Messages for BES2 | hostD | |
Host name displayed in statistical information | Statistical information about BES1 | hostC |
Statistical information about BES2 | hostD | |
Host name specified in the following client environment definitions:
|
hostA |
#: The unit identifier can be specified in place of the host name.
The example below shows how to handle (specify) host names when IP addresses are not inherited. The system configuration in this case is a mutual system switchover configuration.
System configuration example
Item | Host names to be specified | |
---|---|---|
Host names specified in system common definition | pdunit -x hostA -u UNT1 -c hostAA pdunit -x hostB -u UNT2 -c hostBB pdunit -x hostC -u UNT3 -c hostCC pdunit -x hostD -u UNT4 -c hostDD |
|
Host names specified in the unit control information definition | Unit 1 | pd_hostname=host1 |
Unit 2 | pd_hostname=host2 | |
Unit 3 | pd_hostname=host3 | |
Unit 4 | pd_hostname=host4 | |
Host name specified during rlogin | rlogin in server machine where BES1 is located | hostC or hostD (specify the host name of the running system) |
rlogin in server machine where BES2 is located | hostC or hostD (specify the host name of the running system) | |
Host name specified in operation commands#1 | Execution of operation commands in BES1 | hostC |
Execution of operation commands in BES2 | hostD | |
Host name specified in utilities | Execution of utilities in BES1 | hostC |
Execution of utilities in BES2 | hostD | |
Host name displayed in messages | Messages for BES1 | hostC |
Messages for BES2 | hostD | |
Host name displayed in statistical information | Statistical information about BES1 | hostC |
Statistical information about BES2 | hostD | |
Host name specified in the following client environment definitions:
|
hostA and hostB#2 |
The example below shows how to handle (specify) host names when the IP addresses used by servers in a HiRDB parallel server configuration are not inherited, but the IP addresses used for client connections are inherited. The system configuration in this case is a mutual system switchover configuration.
System configuration example
Item | Host names to be specified | |
---|---|---|
Host names specified in system common definition | pdunit -x hostA -u UNT1 -c hostAA pdunit -x hostB -u UNT2 -c hostBB pdunit -x hostC -u UNT3 -c hostCC pdunit -x hostD -u UNT4 -c hostDD |
|
Host names specified in the unit control information definition | Unit 1 | pd_hostname=host1 |
Unit 2 | pd_hostname=host2 | |
Unit 3 | pd_hostname=host3 | |
Unit 4 | pd_hostname=host4 | |
Host name specified during rlogin | rlogin in server machine where BES1 is located | hostC or hostD (specify the host name of the running system) |
rlogin in server machine where BES2 is located | hostC or hostD (specify the host name of the running system) | |
Host name specified in operation commands# | Execution of operation commands in BES1 | hostC |
Execution of operation commands in BES2 | hostD | |
Host name specified in utilities | Execution of utilities in BES1 | hostC |
Execution of utilities in BES2 | hostD | |
Host name displayed in messages | Messages for BES1 | hostC |
Messages for BES2 | hostD | |
Host name displayed in statistical information | Statistical information about BES1 | hostC |
Statistical information about BES2 | hostD | |
Host name specified in the client environment definition | PDHOST | hostZ |
PDFESHOST | hostX or hostY (specify the host name of the connected front-end server) |
#: The unit identifier can be specified in place of the host name.
Pay attention to the following notes about specifying a client environment definition when the standby system switchover facility is used.
When IP addresses are inherited after a system switchover, specify the host name of the primary system only in the PDHOST operand of the client environment definition. When IP addresses are not inherited, specify the host names of the primary system and the secondary system.
When a unit in the system manager inherits IP addresses after a system switchover, specify the host name of the primary system only (the host name of the system manager) in the PDHOST operand of the client environment definition. When IP addresses are not inherited after a system switchover, specify the host names of the primary system and the secondary system.
When a unit in the front-end server inherits IP addresses after a system switchover, specify the host name of the primary system only (the host name on the front-end server) in the PDFESHOST operand. When the unit does not inherit IP addresses after a system switchover, specify the host names of the primary system and the secondary system. For details about the PDHOST and PDFESHOST operands, see the HiRDB Version 9 UAP Development Guide.
The following subsections provide examples of how to specify host names when the standby system switchover facility is used.
The following shows examples of specifying the HiRDB system definition and client environment definition (host names).
System common definition
pdunit -x pkghost -u UNT1 -d /hirdb_x 1 |
Unit control information definition
set pd_hostname = mainhost 2 |
Client environment definition
export PDHOST = pkghost 3 |
The following shows examples of specifying the HiRDB system definition and client environment definition (host names).
System common definition
pdunit -x mainhost -u UNT1 -d /hirdb/pddir_s -c reservedhost 1 |
Unit control information definition
set pd_hostname = mainhost 2 |
Client environment definition
export PDHOST = mainhost,reservedhost 3 |
All Rights Reserved. Copyright (C) 2011, 2015, Hitachi, Ltd.