PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Solaris(TM) Operating System) |
Contents
Index
![]() ![]() |
Chapter 3 Environment configuration | > 3.7 Configuring other functions | > 3.7.2 Setting Dynamic Reconfiguration (DR) |
When building LAN environment for redundancy system using Redundant Line Control function, in order to replace or add the hardware without stopping the communication using Dynamic Reconfiguration, it is recommended to build the environment shown in figure 3.7 "Recommended LAN configuration".
Addition and deletion of hardware resource by a DR function are executed in an SB (System Board) unit. To continue communication when a DR command cuts off a system board, necessary to bundle actual interfaces on several different system boards as shown in a recommended configuration.
Redundant Line Control function uses DR function to manage NIC device name, which allows dynamic replacement or expansion, on a single configuration file (/opt/FJSVhanet/etc/dr.d/hanet_dr_dev). Ensure the NIC device name is defined in the configuration file. If the NIC device name is not defined in the configuration file, DR function cannot be used for dynamic replacement or expansion. In such case, use the text editor to define the NIC device name in the configuration file to allow dynamic replacement or expansion.
The following shows the verification procedure of the configuration file (/opt/FJSVhanet/etc/dr.d/hanet_dr_dev).
# cat /opt/FJSVhanet/etc/dr.d/hanet_dr_dev |
Contents
Index
![]() ![]() |