DB2 HADR setup with TSA using db2haicu and Virtual IP.
How can you setup HADR with TSA that would use Virtual IP in IBM DB2 for Linux- UNIX and Windows?
The private and the public networks need to be setup correctly beforehand.
The private network will be used for the communication between primary and standby node for the log replay.
The public network will be used for the applications connecting to the primary and standby (which will become primary after failover) nodes.
A virtual IP address needs to be created which does not need to be attached/mapped to NIC, as this is a virtual IP(VIP). This IP just needs to be provided during the setup through db2haicu.
During the failover, the VIP will be automatically mapped to the public network (eth0 or en0) on the working node and the clients will be automatically re-routed through this IP to use the other node.
The public network IP and hosts need to be defined in /etc/hosts file on both primary and standby servers.
The HADR_LOCAL_HOST and HADR_REMOTE_HOST database configuration parameters need to be assigned with values assigned for the private network.
The port number assigned to SVCENAME dbm cfg parameter needs to be correctly defined in /etc/services file and it should not be used by any other application.
This port will be used for VIP routing.
The VIP is also used for ACR (Automatic Client Re-route).
Here is the link to the white paper which describes in detail how to setup HADR with VIP:
More support for:
DB2 for Linux, UNIX and Windows
HADR - Setup
Software version: 9.7, 10.1, 10.5, 11.1
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 1439218
Modified date: 22 September 2010
Translate this page: