Network requirements

A private dedicated network for replication between the two Integrated Analytics System (IAS) appliances with a minimum 10 Gbps or fiber is preferred. To set up replication you will need the IP addresses and host names for the private network.

The following ports must be opened for replication on both source and target:

IBM® MQ: 1414 and 1415
BluDR REST server: 9444
Db2® SSL: 50001
Web console: For IAS, 11089; for Db2 Warehouse, 8443
SSL: 50022

Port opening (or blocking) is generally managed by a client networking team. If any firewalls exist in the client network between the replication servers, work with the networking team to ensure that these ports are opened in bidirectional mode in that network path, so that replication can communicate over those ports.

The following example shows a telnet command that is run from the IAS primary appliance for various cases (port open and running, port open but daemon not running, port closed).

[root@node0101 ~]# telnet bludr02-t03.ibm.com 11089
Trying 9.30.12.177...
Connected to bludr02-t03.ibm.com.
Escape character is '^]'.

[root@node0101 ~]# telnet bludr02-t03.ibm.com  9444
Trying 9.30.12.177...
Connected to bludr02-t03.ibm.com.
Escape character is '^]'.

[root@node0101 ~]# telnet bludr02-t03.ibm.com  1415
Trying 9.30.12.177...
Connected to bludr02-t03.ibm.com.
Escape character is '^]'.

In the example below, the IBM MQ queue manager is not running on the target bludr02-t03 appliance, resulting in the message below:

[root@node0101 ~]# telnet bludr02-t03.svl.ibm.com 1414
Trying 9.30.12.177...
telnet: connect to address 9.30.12.177: Connection refused

In the following example, port 21 is a non-secure FTP port and is blocked, resulting in the message that shows no route to host. Ensure that you do not see a No route to host message when you conduct tests on these required ports in your environment.

[root@node0101 ~]# telnet bludr02-t03.ibm.com 21
Trying 9.30.12.177...
telnet: connect to address 9.30.12.177: No route to host