IP addresses for mutual takeover configuration methods in server clusters

&http://www.aliyun.com/zixun/aggregation/37954.html ">nbsp; A server cluster is the pooling of many servers together for the same service, which, in the client's view, is just like a server cluster can use multiple computers for parallel computing to achieve high computing speed, or multiple computers to do the backup, So that any one machine breaks down, the whole system is still functioning. Once the Cluster service is installed and running on the server, the server can join the cluster. Clustering can reduce the number of single points of failure and enable high availability of clustered resources. The following sections briefly describe node behavior in cluster creation and cluster operations.

Customers use iasp to make mutual backups between two different iseries, and the client connects to the main production machine or standby through Telnet, and if the connected system fails, Can customers seamlessly connect to another system with the same Telnet session without modifying the client session parameters (the host's IP address)?

According to the topology of the diagram below, this paper introduces the configuration of the IP addresses in the iseries cluster environment, as shown in the following figure:

Working principle:

First, the SYSA and SYSB two systems are configured as clustered environments, where IASP1 can be switched in two systems. The virtual IP is 19.19.19.19, and the network address range that this address belongs to does not belong to the current network.

This virtual IP address is owned by the cluster resource group (cluster resource GROUP-CRG) that contains the IASP1. When IASP1 switches from one system to another, the virtual IP stops at the first system and starts on another system that is switched on. This is mainly due to the RIP protocol, which maintains all routing tables within the network. When a virtual IP address is stopped on one system and it is started on another, the routing information to the address (19.19.19.19) will be modified (depending on which system the virtual IP address is launched, the route connecting to 19.19.19.19 is either 10.1.1.123 or 10.1.1.171). As a result, the client telnet to the same IP address, and when the system fails, the system automatically switches to the system that takes over the IASP1.