Hi Varun,
Sorry - I don't have any experience with the IBM solution. So I have comments, but not a solution.
The HADR Solution will work well in HA / cluster systems where the IP address is dynamically re-assigned to the active node. This allows the server configurations to point to just 'one' IP address and the cluster software (examples: MS Cluster, Veritas, HP Service Guard) assigns that IP to which ever node is active.
Using the IBM solution, (based on a quick Google search) it appears we rely on Open Server HA capability to include both addresses in the interfaces file under a single Server name, so that both address can be attempted when making a connection.
Unfortunately, the configurations created by the DR Agent do not support this type of configuration using Interfaces files. Most server address are assigned a single IP address, and most address are assigned directly (not pointing to an Interfaces file entry).
As an example, when the HADR nodes are configured in ASE, you define the other nodes in the HADR group with a command like the following:
sp_hadr_admin addserver, <node_name>,<server_name>
To use a interfaces file name for the server name, the command might look like:
sp_hadr_admin addserver, 'D01_Site1', 'D01'
But the configurations created by the DR Agent use a host:port syntax instead of an interfaces file server name, like:
sp_hadr_admin addserver, 'D01_Site1', 'host1.my.domain.corp:5001'
The point I am trying to make is that even if we edit the interfaces files to use the additional HA addresses, other configurations like the one above would need to be discovered and changed as well.
Unfortunately, even if all this reconfiguration work is accomplished successfully, the DR Agent itself does not use interfaces files and has no support for specifying an alternate HA address. And I am not aware of any workaround for that limitation.
In summary, I think that short answer is that we don't have HADR support using DR Agent for HA environments without a dynamic IP address. It might be possible to manually reconfigure some of it, but without support in the DR Agent itself, you would be missing failover and monitoring support the DR Agent provides.
Sorry that I do not have a more encouraging answer.
Regards,
Stephen