Node Replication stuck or even not running

almadi

Newcomer
Joined
Mar 31, 2014
Messages
4
Reaction score
0
Points
0
PREDATAR Control23

Hello,

We have 10 TSM Severs with this configuration:

TSM Version 7.1.7

TSM SERVER A/B/C --->> node replication to TSM SERVER D
TSM SERVER E/F/G
--->> node replication to TSM SERVER H
TSM SERVER I
---------->> node replication to TSM SERVER J

All of this replication jobs are getting failed since many weeks. During the night we are replicating around 2MB to 40GB. Between the servers we have up to 100Mbit and we calculated that with our bandwidth it should be easy possible to replicate the nodes.

We still opened a TSM PMR and IBM told us, that the error is in our network. We checked the whole company network with our network architects and there is no error during the replication.

Our question is:
Does anybody know something else what we could do, to get the replication running. Would be very great to hear from you.

Thanks
 
PREDATAR Control23

We checked the whole company network with our network architects and there is no error during the replication.
Keep in mind that the network actually starts with the TCP/IP stack of the OS of the source and ends with the TCP/IP stack of the target OS. Most network admins only start with the physical network where the network cable connects to the NIC. Essentially only focusing on 4 lower-levels of the 7 OSI layers, leaving the 3 upper-level to system administrators. Which is why many network admins report there are no network problems, when in reality it's that there is no errors on the portion they support.

So what is often overlook is:
- NIC settings
- NIC driver and firmware
- NIC errors
 
PREDATAR Control23

Hy marclant,

Thanks for your answer. Yes we know that the network admins only check the "physical network". So we also checked the NIC´s (Hardware and Windows settings), tried different drivers, also flashed to the newest firmware, checked Windows Eventlogs. But there is nothing to find.

Therefore we think we have a "TSM" problem and not a network problem.
 
PREDATAR Control23

Networking problems don't always manifest themselves in the form of errors. A sniffer trace with Wireshark or similar between the source and target may be needed.

You also have not posted the errors you get when it fails, so only general recommendations can be made.
 
PREDATAR Control23

Also, if you suspect a TSM problem, I'd recommend upgrading to the latest fixpack if you are not there already. No point trying to troubleshoot known fixed problems.
 
PREDATAR Control23

Hello,

We are already on the latest "7" Version --> 7.1.7

We will also check the Wireshark sniffing logs once more. But is there any other idea what we could do? Thank you very much.
 
Top