AutoSYNC Software User's Guide (Update 14)

Synchronization Over TCP/IP
HP AutoSYNC User’s Guide—522580-015
7-3
On the Destination System
The ASYNCLOG-ZASY port
The AutoSYNC logging port is used on the source system to accept a connection from
the destination system. However, the choice of an unpredictable port number is often
incompatible with a firewall configuration that only allows selected incoming ports to be
accessed.
If configured, the logging port number must be distinct from the ASYSYNC-ZASY port
number or any other assigned port number on the system.
If ASYNCLOG-ZASY is not configured, AutoSYNC asks TCP/IP to choose one from
the pool of unassigned port numbers.
The use of an assigned port number requires that only one pair of ASYSYNC
processes be attempting to establish the log record connection. To this end, AutoSYNC
creates a PORTLOCK file in the subvolume of the source ASYSYNC object file. This
file is opened by all source ASYSYNC processes that use TCP/IP. Each source
synchronization process locks the file when it is establishing the log record connection
and unlocks the file when the connection is completed.
On the Destination System
1. Specify the TCPIP, TCPSAM or TCP6SAM processes that will be used to
advertise the ASYSYNC-ZASY services.
On an HP NonStop server, there are multiple TCP/IP processes, each managing
connections on a separate IP address. There may be unique host names for each
IP address and there may also be host names for multiple IP addresses.
In HP NonStop S-series servers, TCP/IP connections can be configured using the
Parallel Library TCP/IP or TCP/IPv6 libraries. In such systems, TCPSAM and
TCP6SAM processes are configured in addition to the TCPIP processes.
In HP NS-series servers, TCP/IP connections are configured using the TCP/IPv6
libraries. In such systems only TCP6SAM processes are configured.
When performing (or configuring) synchronizations on the source system, you
specify either an IP address or a host name as the destination.
Thus, you must specify all TCPIP, TCPSAM or TCP6SAM processes that
correspond to those addresses, or the synchronization will fail to make the
connection.
Consult a networking specialist to determine the names of the TCPIP, TCPSAM,
and TCP6SAM processes.
Use the following SCF commands to understand your local networking
configuration: LISTDEV TCPIP and INFO PROCESS $<tcpip-process-name>,
DETAIL.