Invalid destination

If the destination host or the next-hop host corresponding to the destination host are not defined properly, the transport phase of the synchronization process can fail.

The local host’s hosts file, hosts NIS map, or Domain Name Service must list one of the following hosts:
  • Destination host
  • Next-hop host corresponding to the destination host (on Linux® and the UNIX® system, defined in a ROUTE entry in the host’s shipping.conf file; on Windows®, defined in the Routing Information section in the host’s MultiSite Control Panel.)
Note: If hosts in your network are known only by their IP addresses, you can use the IP addresses instead of host names.

In the absence of such entries, the shipping server fails, because it cannot determine where to deliver the packet. In this case, it writes error messages to its log file (Linux and the UNIX system) or the Windows Event Viewer.

If the destination host name was misspelled, use the mkorder command to create a new shipping order with the correct host name. If a host name is misspelled in a mkreplica –export command, the incorrect host name is recorded. Verify the error with lsreplica –long, and correct the spelling with chreplica.

In other cases, you may have to revise the host’s database of remote hosts. The sending host must be able to communicate with the receiving hosts through TCP/IP channels. Use the rcp command on the sending host to copy a file to the receiving host. If it fails, you have a setup or networking problem with your host. If the command succeeds, contact IBM Software Support for Rational products.