Replication with multiple network interfaces

Hello, I have an Enterprise Replication environment and I want to set up a secondary network interface to handle all of the replicated data between my two servers. Informix version is 11.70.FC5GE on SunOS 5.10. The sqlhosts file looks like this: metro_server group - - i=50 metrotcp onsoctcp astro 9005 g=metro_server metrotcp2 onsoctcp astro-rep 9006 g=metro_server metrobk_server group - - i=22 metrotcpbk onsoctcp sculptor 9005 g=metrobk_server metrotcp2bk onsoctcp sculptor-rep 9006 g=metrobk_server The onconfig file contains: DBSERVERNAME metrotcp DBSERVERALIASES metrotcp2 The network interfaces astro and astro-rep are on the same machine, but are on different subnets, likewise sculptor and sculptor-rep. I want all of the replication traffic to use the "-rep" interfaces. I have modified all of my cdr commands to connect to metrotcp2 using "--connect=metrotcp2". All of the commands are successful, but when I snoop the actual network interfaces, I see all of the replication traffic on astro port 9005 and nothing on astro-rep port 9006. I verified that I can connect to the database instance using the OpenAdmin Tool and specifying metrotcp2@astro-rep, port 9006. Can anyone point me to documentation that shows how to set this up? Thanks, Jeff

Original post: Hello, I have an Enterprise Replication environment and I want to set up a secondary network interface to handle all of the replicated data between my two servers. Informix version is 11.70.FC5GE on SunOS 5.10. The sqlhosts file looks like this: metro_server group - - i=50 metrotcp onsoctcp astro 9005 g=metro_server metrotcp2 onsoctcp astro-rep 9006 g=metro_server metrobk_server group - - i=22 metrotcpbk onsoctcp sculptor 9005 g=metrobk_server metrotcp2bk onsoctcp sculptor-rep 9006 g=metrobk_server The onconfig file contains: DBSERVERNAME metrotcp DBSERVERALIASES metrotcp2 The network interfaces astro and astro-rep are on the same machine, but are on different subnets, likewise sculptor and sculptor-rep. I want all of the replication traffic to use the "-rep" interfaces. I have modified all of my cdr commands to connect to metrotcp2 using "--connect=metrotcp2". All of the commands are successful, but when I snoop the actual network interfaces, I see all of the replication traffic on astro port 9005 and nothing on astro-rep port 9006. I verified that I can connect to the database instance using the OpenAdmin Tool and specifying metrotcp2@astro-rep, port 9006. Can anyone point me to documentation that shows how to set this up? Thanks, Jeff Response: I'm not sure this is the best way, but it appears to be a way based on a quick test. Basically, I think what you could do is just flip the lines of your entries in your sqlhosts file...so make them look like this: metro_server group - - i=50 metrotcp2 onsoctcp astro-rep 9006 g=metro_server metrotcp onsoctcp astro 9005 g=metro_server metrobk_server group - - i=22 metrotcp2bk onsoctcp sculptor-rep 9006 g=metrobk_server metrotcpbk onsoctcp sculptor 9005 g=metrobk_server It looks like the server does the connection for the group using the 1st entry it sees in the sqlhosts file. So flip the lines in your sqlhosts file, then either bounce your servers or pick 1 server and do a cdr disconnect server followed by a cdr connect server and I believe it should start using the -rep network instead. Jacques Renaut IBM Informix Advanced Support APD Team

Thanks for the suggestion, Jacques. Unfortunately, I got the same result. However, I did get it to work by removing the server group parameter from the interface that I did not want to use for replication. I.E., this sqlhosts configuration results in replication only using the "-rep" network interface: metro_server group - - i=50 metrotcp2 onsoctcp astro-rep 9006 g=metro_server metrotcp onsoctcp astro 9005 metrobk_server group - - i=22 metrotcp2bk onsoctcp sculptor-rep 9006 g=metrobk_server metrotcpbk onsoctcp sculptor 9005 Thanks, Jeff

For the sake of completeness, it was necessary to both flip the lines in the sqlhosts file so that the line containing the entry for the replication interface occurred first, and to remove the server group specification from the entry that is not to be used for replication.

The ER connection should be the only thing in the ER group - if you wa= nt to restrict the connections that ER is to use. Generally the only time that it makes sense to have multiple entries in= the ER group is for failover. The ER port on the secondary servers should = be in the same group as the primary so that when failover occurs, ER automatically can find the new primary. From: "JEFFREY GENEGA" <jeffrey.genega@spirent.com> To: ids@iiug.org, Date: 06/26/2013 10:44 AM Subject: Re: Replication with multiple network interfaces [30674] Sent by: ids-bounces@iiug.org Thanks for the suggestion, Jacques. Unfortunately, I got the same resul= t. However, I did get it to work by removing the server group parameter fr= om the interface that I did not want to use for replication. I.E., this sqlhos= ts configuration results in replication only using the "-rep" network interface: metro_server group - - i=3D50 metrotcp2 onsoctcp astro-rep 9006 g=3Dmetro_server metrotcp onsoctcp astro 9005 metrobk_server group - - i=3D22 metrotcp2bk onsoctcp sculptor-rep 9006 g=3Dmetrobk_server metrotcpbk onsoctcp sculptor 9005 Thanks, Jeff ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =