Installation of replication server with erssd and routes snag

[Former Member]

We installed RS16.0/EBF 26769 SP0 on two boxes and created two Replication server instances, both of them using Embedded RSSD:

LOC_RS16_DEV on a local machine (Linux version 3.10.0-862.3.3.el7.x86_64)

embedded rssd: rep_erssd

LOC_RS16_DEV on AWS (Linux version 3.10.0-862.2.3.el7.x86_64)

embedded rssd: aws_rep_erssd

Added one ASE database to each server.

Tried to create a route between the two rep servers.

Route creation reported success:

> admin show_connections

Server User Database State Owner Spid

------------------------------------------------------------ ------------------------------------------------------------ ------------------------------------------------------------ ---------------------------------- -------------------- --------

AWS_RS16_DEV sa NULL active RSI 19 rep_erssd LOC_RS16_DEV_RSSD_prim rep_erssd free rep_erssd LOC_RS16_DEV_RSSD_prim rep_erssd free

But essd shows route is in the process of being created:

rs_helproute

route route_status

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

LOC_RS16_DEV --------> AWS_RS16_DEV

Route is being created. Destination has not yet finished creating system table subscriptions.

Systable Subs to be created

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

rs_objects0_at_16777317 rs_columns1_at_16777317 rs_classes2_at_16777317 rs_functions3_at_16777317 rs_funcstrings4_at_16777317 rs_routes5_at_16777317 rs_databases6_at_16777317 rs_systext7_at_16777317 rs_systext8_at_16777317 rs_erroractions9_at_16777317 rs_dbreps10_at_16777317 rs_dbsubsets11_at_16777317 rs_clsfunctions12_at_16777317 rs_objfunctions13_at_16777317 rs_asyncfuncs14_at_16777317

Log files for both replication servers and for the essd's show no errors.

It looks as if the ASA log transfer manager - dbltm - hangs when trying to send the erssd info from local to AWS.

Anyone has any thoughts about what the problem / solution might be?

Any pointers will be greatly appreciated. I can send log files if needed.

[kenneth_brozovich]

Please open an incident with Product Support.