Did you use something like iperf with a long and heavy load? a bad nic or driver might cause this, so it might still be the network.
On Mon, May 13, 2019 at 4:15 PM Bjørn Nachtwey <bjoern.nacht...@gwdg.de> wrote: > Hi all, > > we planned to switch from COPYPOOL to Replication for having a second > copy of the data, therefore we bought a new server that should become > the primary TSM/ISP server and then make the old one holding the > replicates. > > what we did: > > we started by exporting the nodes, which worked well. But as the > "incremental" exports even took some time, we set up a replication from > old server "A" to the new one "B". For all nodes already exported we set > up the replication vice versa: TSM "B" replicates them to TSM "A". > > well, the replication jobs did not finish, some data and files were > missing as long as we replicated using a node group. Now we use > replication for each single node and it works -- for most of them :-( > > Replication the "bad" nodes from "TSM A" to "TSM B" first the sessions > hang for many minutes, sometimes even hours, then they got "terminated - > forced by administrator" (ANR0483W), e.g.: > > 05/13/2019 15:23:16 ANR2017I Administrator GK issued command: > REPLICATE NODE vsbck (SESSION: 26128) > 05/13/2019 15:23:16 ANR1626I The previous message (message number > 2017) was repeated 1 times. > 05/13/2019 15:23:16 ANR0984I Process 494 for Replicate Node started > in the BACKGROUND at 15:23:16. (SESSION: 26128, PROCESS: 494) > 05/13/2019 15:23:16 ANR2110I REPLICATE NODE started as process 494. > (SESSION: 26128, PROCESS: 494) > 05/13/2019 15:23:16 ANR0408I Session 26184 started for server SM283 > (Linux/x86_64) (Tcp/Ip) for replication. (SESSION: 26128, PROCESS: 494) > 05/13/2019 15:23:16 ANR0408I Session 26185 started for server SM283 > (Linux/x86_64) (Tcp/Ip) for replication. (SESSION: 26128, PROCESS: 494) > 05/13/2019 15:23:16 ANR0408I Session 26186 started for server SM283 > (Linux/x86_64) (Tcp/Ip) for replication. (SESSION: 26128, PROCESS: 494) > 05/13/2019 15:23:17 ANR0408I Session 26187 started for server SM283 > (Linux/x86_64) (Tcp/Ip) for replication. (SESSION: 26128, PROCESS: 494) > 05/13/2019 15:23:17 ANR0408I Session 26188 started for server SM283 > (Linux/x86_64) (Tcp/Ip) for replication. (SESSION: 26128, PROCESS: 494) > 05/13/2019 15:23:17 ANR0408I Session 26189 started for server SM283 > (Linux/x86_64) (Tcp/Ip) for replication. (SESSION: 26128, PROCESS: 494) > 05/13/2019 15:23:17 ANR0408I Session 26190 started for server SM283 > (Linux/x86_64) (Tcp/Ip) for replication. (SESSION: 26128, PROCESS: 494) > 05/13/2019 15:23:17 ANR0408I Session 26191 started for server SM283 > (Linux/x86_64) (Tcp/Ip) for replication. (SESSION: 26128, PROCESS: 494) > > 05/13/2019 15:24:57 ANR0483W Session 26187 for node SM283 > (Linux/x86_64) terminated - forced by administrator. (SESSION: 26128, > PROCESS: 494) > > on the target server we observe at that time: > > 13.05.2019 15:25:51 ANR8213E Socket 34 aborted due to send error; error > 104. > 13.05.2019 15:25:51 ANR3178E A communication error occurred during > session 65294 with replication server TSM. > 13.05.2019 15:25:51 ANR0479W Session 65294 for server TSM (Windows) > terminated - connection with server severed. > 13.05.2019 15:25:51 ANR8213E Socket 34 aborted due to send error; error 32. > > => Any idea why this replication aborts? > > => why is there a "socket abortion error"? > > > well, we already opened a SR case, send lots of logs and traces. as IBM > suspects a network problem, now both serves use a cross link connection > without nothing but NIC/GBICs, plugs and wires. > > thanks & best > > Bjørn > > -- > > -------------------------------------------------------------------------------------------------- > Bjørn Nachtwey > > Arbeitsgruppe "IT-Infrastruktur“ > Tel.: +49 551 201-2181, E-Mail:bjoern.nacht...@gwdg.de > > -------------------------------------------------------------------------------------------------- > Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen (GWDG) > Am Faßberg 11, 37077 Göttingen, URL:http://www.gwdg.de > Tel.: +49 551 201-1510, Fax: +49 551 201-2150, E-Mail:g...@gwdg.de > Service-Hotline: Tel.: +49 551 201-1523, E-Mail:supp...@gwdg.de > Geschäftsführer: Prof. Dr. Ramin Yahyapour > Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger > Sitz der Gesellschaft: Göttingen > Registergericht: Göttingen, Handelsregister-Nr. B 598 > > -------------------------------------------------------------------------------------------------- > Zertifiziert nach ISO 9001 > > -------------------------------------------------------------------------------------------------- >
