There are several prerequisites, guidelines, and configuration parameters for create route.
create route to dest_replication_server{ with primary at dataserver.database| set next site [to] thru_replication_server| [set username [to] user] [set password [to] passwd] [set route_param to 'value'] [set security_param to 'value']}
Supply the login name, password, and other parameters for direct routes only.
If you are enabling network-based security and unified login, user name and password are optional. The default user name is the principal user name, which is specified by the -S flag when you log in to Replication Server or start Replication Server.
If you create a route with a user and passwd that do not exist at the destination Replication Server, add or change the user and password at that destination.
If you are establishing a direct route from the current Replication Server to the destination Replication Server, do not use the next site clause.
Enter one create route command at a time, to ensure you have made no mistakes. Wait for a route to become valid before creating the next one.
If you do make a mistake, drop the route and re-create it only as a last resort. Include the with nowait option with the drop route command. Since the route has not been created, its current state requires that you use the with nowait option to drop it.
When you create a route, you can accept the default values for configuration parameters that manage memory size, the size of the amount of data that can be sent over the route at one time, time-outs, and synchronization intervals. You can also set your own values when you create or alter the route.
If network-based security is enabled at your site, you can also configure security parameters for routes. See Replication Server Administration Guide Volume 2 > Performance Tuning > Configuration Parameters that Affect Performance for a list and discussion of route parameters that affect performance.