Resolution:
Among all EMS servers which are connected directory or indirectly, we recommend that each server is given a unique server name (in tibemsd.conf or tibemsd.json). If the name is not unique, there could be the following issues (E1-n: server name, A-Z machine name):

1). E1@A -> E2@B ------> E1@C

When a route is being created from E1@C to E2@B, E2@B rejects the connection with the error, "rejected connect from route: route already connected".

2). If there are the following routes:

E1@A -zone1-> E2@B -zone2-> E3@C --zone1------>E1@D

If a route is being created from E3@C to E1@D, E3@C rejects the connection with the error, "ERROR: Illegal, route to 'EMS-SERVER' creates a cycle.". In fact, there is no cycle. For reasons as to why E3 detects the cycle, refer to KB 36954.