Replication fails inbound with ANR3178E after upgrading to 8.1.6

blankgap

ADSM.ORG Member
Joined
Jun 5, 2018
Messages
64
Reaction score
2
Points
0
PREDATAR Control23

Hi Folks!

Server1 replicates to Server2 and vice versa

After upgrading Server2 to 8.1.6 (Server1 is 8.1.5) the node replication (Replicating a Nodegroup) fails (With Server2 as the Target)

ActLog reports a few different errors on both Servers for each Node in the Nodegroup:

ANR3178E A communication error occurred during session 2897 with replication server LNZBKP02. (SESSION: 1589, PROCESS: 68)
ANR0479W Session 2887 for server LNZBKP02 (Windows) terminated - connection with server severed. (SESSION: 1589, PROCESS: 68)
ANR8216W Error sending data on socket 78880. Reason 10054. (SESSION: 1589, PROCESS: 68)

The replication FROM Server2(8.1.6) to Server1(8.1.5) works fine, in the opposite direction it fails.

Any ideas from the experts here?
 
PREDATAR Control23

The errno = 10054 is a Windows return code which means....
An existing connection was forcibly closed by the remote host.

The TSM Server has rejected the TCP operation because it was unable to perform the TCP action on the physical network.

I would start at the network layer and to the transport layer or the data-link layer.
The layers that I am referring to are the 7 Layers of the OSI model.

I know that the replication FROM replication FROM Server2(8.1.6) to Server1(8.1.5) works fine.
If possible, change the replication time of from Server2(8.1.6) to Server1(8.1.5) to Server1(8.1.5) to Server2(8.1.6). See if the issue follows and if we get the same ANR message in the actlog.
Also , check the window event log around the time frame of when the TSM Server generate the ANR message.

Good Luck,
Sias
 
Top