25.4.1 HiRDB/Single Server

Organization of this subsection
(1) IP addresses inherited
(2) IP addresses not inherited
(3) IP addresses not inherited (only IP addresses for client connection inherited)

(1) IP addresses inherited

The following explains the procedure for handling (specifying) 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)
[Figure]
System configuration example (when switching LAN adapters)
[Figure]
ItemHost name to be specified
Host name specified in system common definitionpdunit -x hostA
pdunit -x hostC
pdstart -x hostA
Host name specified in unit control information definitionpd_hostname=host1
Host name specified during rloginhostA
Host name specified in operation commands*For single serverhostA (host name should be omitted)
For utility special unithostC
Host name specified in utilitiesFor single serverhostA (host name should be omitted)
For utility special unithostC
Host name displayed in messageshostA
Host name displayed in statistical informationhostA
Host name specified in PDHOST operand of client environment definitionhostA

* The unit identifier may be specified instead of the host name.

(2) IP addresses not inherited

The following explains the procedure for handling (specifying) host names when IP addresses are not inherited. The system configuration in this case is a 1-to-1 switchover configuration.

System configuration example
[Figure]
Hint
If the default host names are the same (host1 = host2), HiRDB cannot recognize a system switchover. Therefore, use different default host names.

ItemHost name to be specified
Host name specified in system common definitionpdunit -x hostA -c hostB
pdunit -x hostC
pdstart -x hostA
Host name specified in unit control information definitionpd_hostname=host1
Host name specified during rloginhostA or hostB (specify the host name of the running system)
Host name specified in operation commands1For single serverhostA (host name should be omitted)
For utility special unithostC
Host name specified in utilitiesFor single serverhostA (host name should be omitted)
For utility special unithostC
Host name displayed in messageshostA
Host name displayed in statistical informationhostA
Host name specified in PDHOST operand of client environment definitionhostA and hostB2

1 The unit identifier may be specified instead of the host name.

2 Specify the host names of the primary system and secondary system in the PDHOST operand of the client environment definition. If you specify the host names in this manner, changing the value specified in the PDHOST operand will not be necessary, even after a system switchover. However, when the running system switches from the primary system to the secondary system, a UAP attempts to connect to the primary system (standby system). Because the UAP connects to the secondary system (running system) after the connection could not be established, the UAP processing time increases by the amount of time it takes to establish this new connection. To resolve this problem, set the host name for the client connection to an alias IP address and make sure that IP addresses are inherited. For details about specifying host names in such cases, see (3) IP addresses not inherited (only IP addresses for client connection inherited).

(3) IP addresses not inherited (only IP addresses for client connection inherited)

The following explains the procedure for handling (specifying) host names when the IP addresses HiRDB/Single Servers use are not inherited, but IP addresses for client connections are inherited. The system configuration in this case is a 1-to-1 switchover configuration.

System configuration example
[Figure]
Explanation
  • hostA and hostB are the host names the HiRDB/Single Server uses. These hosts do not inherit IP addresses.
  • hostC is the host name (alias IP address) used for client connection. This host inherits IP addresses.
    Hint
    If the default host names are the same (host1 = host2), HiRDB cannot recognize a system switchover. Therefore, use different default host names.

ItemHost name to be specified
Host name specified in system common definitionpdunit -x hostA -c hostB
pdstart -x hostA
Host name specified in unit control information definitionpd_hostname=host1
Host name specified during rloginhostA or hostB (specify the host name of the running system)
Host name specified in operation commands*hostA (host name should be omitted)
Host name specified in utilitieshostA (host name should be omitted)
Host name displayed in messageshostA
Host name displayed in statistical informationhostA
Host name specified in PDHOST operand of client environment definitionhostC

* The unit identifier may be specified instead of the host name.