(a) When 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-to1 switchover configuration.

System configuration example (when switching the IP address)

System configuration example (when switching LAN adapters)

#: The unit identifier can be specified in place of the host name.

(b) When IP addresses are not inherited

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

Hint

If the standard host names are the same (if host1 = host2), HiRDB cannot recognize a system switchover. Therefore, use different standard host names.

#1

The unit identifier can be specified in place 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, you do not need to change the value specified in the PDHOST operand, even after a system switchover occurs. However, when the running system switches from the primary system to the secondary system, UAPs first attempt to connect to the primary system (which is now the standby system). After this attempt fails, the UAPs establish a connection to the secondary system (the current running system), which increases the UAP processing time by the amount of time it takes to establish this new connection. To resolve this problem, set the host name for the client connections to an alias IP address and make sure that IP addresses are inherited. For details about how to specify host names in such cases, see 26.2.3(1)(c) When IP addresses are not inherited (but IP addresses for client connections are inherited).

(c) When IP addresses are not inherited (but IP addresses for client connections are inherited)

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

Explanation

• hostA and hostB are the host names the server in a HiRDB single server configuration uses. These hosts do not inherit IP addresses.
• hostC is the host name (alias IP address) used for client connections. This host inherits IP addresses.
  

  Hint

  If the standard host names are the same (host1 = host2), HiRDB cannot recognize a system switchover. Therefore, use different standard host names.

#: The unit identifier can be specified in place of the host name.

(a) When 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 mutual system switchover configuration.

System configuration example

#: The unit identifier can be specified in place of the host name.

(b) When IP addresses are not inherited

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

Hint

If the standard host names are the same (host1 = host2, host3 = host4), HiRDB cannot recognize a system switchover. Therefore, use different standard host names.

#1

The unit identifier can be specified in place of the host name.

#2

When units in the system manager do not inherit IP addresses, specify the host names of the primary system and secondary system in the PDHOST operand of the client environment definition. When units in the front-end server do not inherit IP addresses, specify the host names of the primary system and secondary system in the PDFHESHOST operand of the client environment definition. If you specify the host names in this manner, you do not need to change the value specified in the PDHOST or PDFESHOST operand, even after a system switchover occurs. However, if the running system switches from the primary system to the secondary system, UAPs first attempt to connect to the primary system (which is now the standby system). After this attempt fails, the UAPs establish a connection to the secondary system (the current running system), which increases the UAP processing time by the amount of time it takes to establish this new connection. To resolve this problem, set the host name for the client connections to an alias IP address and make sure that IP addresses are inherited. For details about how to specify host names in such cases, see 26.2.3(2)(c)When IP addresses are not inherited (but IP addresses for client connections are inherited).

(c) When IP addresses are not inherited (but IP addresses for client connections are inherited)

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

Explanation

• hostA is the host name used by unit 1 (primary system). hostA does not inherit IP addresses. hostAA is the host name used by unit 1 (secondary system).
• hostB is the host name used by unit 2 (primary system). hostB does not inherit IP addresses. hostBB is the host name used by unit 2 (secondary system).
• hostC is the host name used by unit 3 (primary system). hostC does not inherit IP addresses. hostCC is the host name used by unit 3 (secondary system).
• hostD is the host name used by unit 4 (primary system). hostD does not inherit IP addresses. hostDD is the host name used by unit 4 (secondary system).
• hostX to hostZ are the host names (alias IP addresses) used for client connections. These hosts inherit IP addresses.
  

  Hint

  If the standard host names are the same (host1 = host2, host3 = host4), HiRDB cannot recognize a system switchover. Therefore, use different standard host names.

#: 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.

(a) HiRDB single server configuration

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.

(b) HiRDB parallel server configuration

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.

(a) When IP addresses are inherited

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
 

Explanation

1. Specify the host name^# of a re-allocatable IP address in the -x option of the pdunit operand.
2. Specify the host name of the primary system in the pd_hostname operand.
3. Specify the host name^# of a re-allocatable IP address (the host name of the system manager for a HiRDB parallel server configuration) in the PDHOST operand of the client environment definition.
   If you are using multiple front-end servers, specify the host names^# of re-allocatable IP addresses (host names of front-end servers) in the PDFESHOST operand.
   

#

For VERITAS Cluster Server or ClusterPerfect, specify the host name of a logical IP address (the host name of the IP address set in the IP type resource). For Sun Cluster, specify the logical host name registered in Sun Cluster.

(b) When IP addresses are not inherited

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
 

Explanation

1. Specify the host name of the primary system in the -x option of the pdunit operand. Specify the host name of the secondary system in the -c option.
2. Specify the host name of the primary system in the pd_hostname operand.
3. Specify the host name of the primary system and the secondary system in the PDHOST operand of the client environment definition (for a HiRDB parallel server configuration, specify the host name of the system manager).
   If you are using multiple front-end servers, specify the host name of the primary system and the secondary system in the PDFESHOST operand (host name of the front-end server).