How to take over IP addresses from one another in a server cluster configuration

Customers use IASP to implement mutual backup between two different iseries, the client is connected to the main production machine or standby through Telnet, if the customer can not modify the client session parameter (the host's IP address) if the connected system fails. Seamlessly connect to another system with the same Telnet session?

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, this 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.

Configuration steps:

1-in Sysa and SYSB, configure the virtual IP address (example 19.19.19.19):

ADDTCPIFC Intnetadr (19.19.19.19)
LIND (*virtualip)
SubnetMask (255.255.255.255)
AUTOSTART (*no)

2-This IP address corresponds to the IP address used by the cluster: (the cluster IP must be stopped when modified)

In Sysa:

CHGTCPIFC Intnetadr (10.1.1.123)

LCLIFC (19.19.19.19)

In SYSB:

CHGTCPIFC Intnetadr (10.1.1.171)

LCLIFC (19.19.19.19)