Re: Export server error - RESOLVED
Hi David, I´d like to thank you for your help. The problem was not a TSM problem after alleverything was configured correctly thanks to you guys.it was a network issue and once the network guys solved their problem, everything worked fine. Best regards, Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Sun, July 18, 2010 4:00:44 PM Subject: Re: Export server error Very puzzling - there's something either really obvious or pretty discrete afoot here preventing this from working. Just out of curiosity, can your TSM BA Client connect from the source to the target server (and vice versa)? And the admin client as well? Cheers, //DMc -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 18 July 2010 17:52 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, Everything u guys told me is in place - both source and target servers ping each other from the OS (the HLAddress configured with the DEFINE SERVER) - the admin user exists on both machines and have the same password - the admin I´ve registered and use also exists on both TSM Servers and have the same password - the LLAddress, TCP Port, is 1500 on both TSM Servers, which are installed on separate physical machines - the TCP Port 1500 is in LISTENING state on both machines (netstat -an)...both servers are Windows 2003 Servers - both hostnames are declared on each others HOSTS file - there is NO FIREWALL or anything between these TSM Servers - telnet on localhost on TCP Port 1500 accepts the connection on both machines Butthe PING SERVER command fail on both TSM Servers tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. tsm: TSM_TARGETping server tsm_source ANR1705W Ping for server 'TSM_SOURCE' was not able to establish a connection. ANS8001I Return code 4. Everything seems to be properly configuredwhat could be wrong or missing? Any help is aprreciated. Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 9:27:00 PM Subject: Re: Export server error Hi Mario, Looks like some detailed double-checking of the config is required - here goes! O - As Marcel points out, first you'll need to have an administrative user registered with the same password upon the source and target TSM Server instances. O - Next, the High Level Address (HLA) of the target server needs (visible in Q SERVER) to be resolvable/pingable from your shell/OS prompt on the source server. O - Finally, the Low Level Address (LLA) of the target server (visible in Q SERVER) needs to be set to the TCPPort upon which the target server is listening (e.g. visible from Q OPT output on target server). What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? Your source and target TSM Server instances can run on the same TCPPORT if they're running on different physical servers. If all of these are in place and there aren't any other factors getting in the way, PING SERVER commands should work and you'll have a platform for TSM Server to Server operations. HTH - let us know how you get on. //DMc London, UK - going to bed. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 17 July 2010 00:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, No...it is not successful...check the output below...I am calling the servers TSM_SOURCE and TSM_TARGET to make this easier: tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. The same happens the other way around. What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? tsm: TSM_SOURCEq server Server Comm. High-level Low-level Days Server Name Method Address AddressSince Password -- - - -- TSM_TARGET TCPIP xx.xx.xx.xx 1919 1Yes tsm: TSM_TARGETq server ServerComm. High-levelLow-level Days Server Name Method Address AddressSince Password -- - - -- TSM_SOURCE TCPIP xx.xx.xx.xx 15001 Yes Regards, Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 7:56:06 PM Subject: Re: Export server error Hi Mario, What does a `PING SERVER
AW: [ADSM-L] Export server error
Inbetween, had that Problem also after desaster Restore of Library Sharing Servers, just try an update server with force=yes´ Kind Regards hj Von: ADSM: Dist Stor Manager [ads...@vm.marist.edu] im Auftrag von Mario Behring [mariobehr...@yahoo.com] Gesendet: Sonntag, 18. Juli 2010 18:51 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] Export server error Hi David, Everything u guys told me is in place - both source and target servers ping each other from the OS (the HLAddress configured with the DEFINE SERVER) - the admin user exists on both machines and have the same password - the admin I´ve registered and use also exists on both TSM Servers and have the same password - the LLAddress, TCP Port, is 1500 on both TSM Servers, which are installed on separate physical machines - the TCP Port 1500 is in LISTENING state on both machines (netstat -an)...both servers are Windows 2003 Servers - both hostnames are declared on each others HOSTS file - there is NO FIREWALL or anything between these TSM Servers - telnet on localhost on TCP Port 1500 accepts the connection on both machines Butthe PING SERVER command fail on both TSM Servers tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. tsm: TSM_TARGETping server tsm_source ANR1705W Ping for server 'TSM_SOURCE' was not able to establish a connection. ANS8001I Return code 4. Everything seems to be properly configuredwhat could be wrong or missing? Any help is aprreciated. Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 9:27:00 PM Subject: Re: Export server error Hi Mario, Looks like some detailed double-checking of the config is required - here goes! O - As Marcel points out, first you'll need to have an administrative user registered with the same password upon the source and target TSM Server instances. O - Next, the High Level Address (HLA) of the target server needs (visible in Q SERVER) to be resolvable/pingable from your shell/OS prompt on the source server. O - Finally, the Low Level Address (LLA) of the target server (visible in Q SERVER) needs to be set to the TCPPort upon which the target server is listening (e.g. visible from Q OPT output on target server). What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? Your source and target TSM Server instances can run on the same TCPPORT if they're running on different physical servers. If all of these are in place and there aren't any other factors getting in the way, PING SERVER commands should work and you'll have a platform for TSM Server to Server operations. HTH - let us know how you get on. //DMc London, UK - going to bed. -- Es schrieb Ihnen: Heinz-Josef Kentgens Senior-Berater Xerabit GmbH Max-Planck-Strasse 5 85716 Unterschleißheim call to 089-20 20 99 10 mobil 0160-96 39 38 80 fax to089-20 20 99 119 mail to heinz-josef.kentg...@xerabit.de web http://www.xerabit.de Registergericht Amtsgericht München, HRB Nr. 175530 Geschäftsführer Bernhard Hopp, Günter Simmnacher __ Der Inhalt dieser e-mail ist vertraulich und ausschliesslich für den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser e-mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser e-mail unzulässig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der e-mail in Verbindung zu setzen. Wir möchten Sie ausserdem darauf hinweisen, dass die Kommunikation per e-mail über das Internet unsicher ist, da für unberechtigte Dritte grundsätzlich die Möglichkeit der Kenntnisnahme und Manipulation besteht. The information contained in this e-mail is confidential. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, any form of disclosure, reproduction, distribution or any action taken or refrained from in reliance on it, is prohibited and may be unlawful. Please notify the sender immediately. We also like to inform you that communication via e-mail over the internet is insecure because third parties may have the possibility to access and manipulate e-mails. __ -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 17 July 2010 00:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, No...it is not successful...check the output below...I am calling the servers TSM_SOURCE and TSM_TARGET to make this easier: tsm: TSM_SOURCEping server
Re: Export server error
Hi David, Everything u guys told me is in place - both source and target servers ping each other from the OS (the HLAddress configured with the DEFINE SERVER) - the admin user exists on both machines and have the same password - the admin I´ve registered and use also exists on both TSM Servers and have the same password - the LLAddress, TCP Port, is 1500 on both TSM Servers, which are installed on separate physical machines - the TCP Port 1500 is in LISTENING state on both machines (netstat -an)...both servers are Windows 2003 Servers - both hostnames are declared on each others HOSTS file - there is NO FIREWALL or anything between these TSM Servers - telnet on localhost on TCP Port 1500 accepts the connection on both machines Butthe PING SERVER command fail on both TSM Servers tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. tsm: TSM_TARGETping server tsm_source ANR1705W Ping for server 'TSM_SOURCE' was not able to establish a connection. ANS8001I Return code 4. Everything seems to be properly configuredwhat could be wrong or missing? Any help is aprreciated. Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 9:27:00 PM Subject: Re: Export server error Hi Mario, Looks like some detailed double-checking of the config is required - here goes! O - As Marcel points out, first you'll need to have an administrative user registered with the same password upon the source and target TSM Server instances. O - Next, the High Level Address (HLA) of the target server needs (visible in Q SERVER) to be resolvable/pingable from your shell/OS prompt on the source server. O - Finally, the Low Level Address (LLA) of the target server (visible in Q SERVER) needs to be set to the TCPPort upon which the target server is listening (e.g. visible from Q OPT output on target server). What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? Your source and target TSM Server instances can run on the same TCPPORT if they're running on different physical servers. If all of these are in place and there aren't any other factors getting in the way, PING SERVER commands should work and you'll have a platform for TSM Server to Server operations. HTH - let us know how you get on. //DMc London, UK - going to bed. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 17 July 2010 00:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, No...it is not successful...check the output below...I am calling the servers TSM_SOURCE and TSM_TARGET to make this easier: tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. The same happens the other way around. What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? tsm: TSM_SOURCEq server Server Comm. High-level Low-level Days Server Name Method Address AddressSince Password -- - - -- TSM_TARGET TCPIP xx.xx.xx.xx 1919 1Yes tsm: TSM_TARGETq server ServerComm. High-levelLow-level Days Server Name Method Address AddressSince Password -- - - -- TSM_SOURCE TCPIP xx.xx.xx.xx 15001 Yes Regards, Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 7:56:06 PM Subject: Re: Export server error Hi Mario, What does a `PING SERVER TSM_DEDALUS` from the source TSM Server admin CLI give you - is this successful? Cheers, //David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 16 July 2010 22:44 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export server error Hi list, I am trying to export all data from a TSM Server to a new one. Both servers are TSM 5.5.0.0 servers. I have defined the TARGET server on the SOURCE and vice versa, specifying a password and TCP Port (lladdress) for both servers. When I issue the EXPORT SERVER command with the PREVIEWIMPORT set to YES I get the following error on the SOURCE server: 07/17/2010 18:29:44 ANR2017I Administrator ADMIN issued command: EXPORT SERVER filed=all previewi=y tos=tsm_dedalus (SESSION: 18790) 07/17/2010 18:29:44 ANR0984I Process 254 for EXPORT
Re: Export server error
Very puzzling - there's something either really obvious or pretty discrete afoot here preventing this from working. Just out of curiosity, can your TSM BA Client connect from the source to the target server (and vice versa)? And the admin client as well? Cheers, //DMc -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 18 July 2010 17:52 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, Everything u guys told me is in place - both source and target servers ping each other from the OS (the HLAddress configured with the DEFINE SERVER) - the admin user exists on both machines and have the same password - the admin I´ve registered and use also exists on both TSM Servers and have the same password - the LLAddress, TCP Port, is 1500 on both TSM Servers, which are installed on separate physical machines - the TCP Port 1500 is in LISTENING state on both machines (netstat -an)...both servers are Windows 2003 Servers - both hostnames are declared on each others HOSTS file - there is NO FIREWALL or anything between these TSM Servers - telnet on localhost on TCP Port 1500 accepts the connection on both machines Butthe PING SERVER command fail on both TSM Servers tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. tsm: TSM_TARGETping server tsm_source ANR1705W Ping for server 'TSM_SOURCE' was not able to establish a connection. ANS8001I Return code 4. Everything seems to be properly configuredwhat could be wrong or missing? Any help is aprreciated. Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 9:27:00 PM Subject: Re: Export server error Hi Mario, Looks like some detailed double-checking of the config is required - here goes! O - As Marcel points out, first you'll need to have an administrative user registered with the same password upon the source and target TSM Server instances. O - Next, the High Level Address (HLA) of the target server needs (visible in Q SERVER) to be resolvable/pingable from your shell/OS prompt on the source server. O - Finally, the Low Level Address (LLA) of the target server (visible in Q SERVER) needs to be set to the TCPPort upon which the target server is listening (e.g. visible from Q OPT output on target server). What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? Your source and target TSM Server instances can run on the same TCPPORT if they're running on different physical servers. If all of these are in place and there aren't any other factors getting in the way, PING SERVER commands should work and you'll have a platform for TSM Server to Server operations. HTH - let us know how you get on. //DMc London, UK - going to bed. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 17 July 2010 00:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, No...it is not successful...check the output below...I am calling the servers TSM_SOURCE and TSM_TARGET to make this easier: tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. The same happens the other way around. What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? tsm: TSM_SOURCEq server Server Comm. High-level Low-level Days Server Name Method Address AddressSince Password -- - - -- TSM_TARGET TCPIP xx.xx.xx.xx 1919 1Yes tsm: TSM_TARGETq server ServerComm. High-levelLow-level Days Server Name Method Address AddressSince Password -- - - -- TSM_SOURCE TCPIP xx.xx.xx.xx 15001 Yes Regards, Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 7:56:06 PM Subject: Re: Export server error Hi Mario, What does a `PING SERVER TSM_DEDALUS` from the source TSM Server admin CLI give you - is this successful? Cheers, //David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 16 July 2010 22:44 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export server error Hi list, I am trying to export all data from a TSM Server to a new one. Both servers are TSM 5.5.0.0 servers. I have defined
Re: Export server error
On Jul 18, 2010, at 3:00 PM, David McClelland wrote: - telnet on localhost on TCP Port 1500 accepts the connection on both machines That should be tried across the servers, as well, to further narrow down the problem. Richard Sims
Re: Export server error
Just a question: Why you are using tsm_target in ping server tsm_target? This is real server name or you just do not want to give it in forum? Grigori G. Solonovitch Senior Technical Architect Information Technology Ahli United Bank Kuwait http://www.ahliunited.com.kw Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: grigori.solonovi...@ahliunited.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: Sunday, July 18, 2010 7:52 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, Everything u guys told me is in place - both source and target servers ping each other from the OS (the HLAddress configured with the DEFINE SERVER) - the admin user exists on both machines and have the same password - the admin I´ve registered and use also exists on both TSM Servers and have the same password - the LLAddress, TCP Port, is 1500 on both TSM Servers, which are installed on separate physical machines - the TCP Port 1500 is in LISTENING state on both machines (netstat -an)...both servers are Windows 2003 Servers - both hostnames are declared on each others HOSTS file - there is NO FIREWALL or anything between these TSM Servers - telnet on localhost on TCP Port 1500 accepts the connection on both machines Butthe PING SERVER command fail on both TSM Servers tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. tsm: TSM_TARGETping server tsm_source ANR1705W Ping for server 'TSM_SOURCE' was not able to establish a connection. ANS8001I Return code 4. Everything seems to be properly configuredwhat could be wrong or missing? Any help is aprreciated. Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 9:27:00 PM Subject: Re: Export server error Hi Mario, Looks like some detailed double-checking of the config is required - here goes! O - As Marcel points out, first you'll need to have an administrative user registered with the same password upon the source and target TSM Server instances. O - Next, the High Level Address (HLA) of the target server needs (visible in Q SERVER) to be resolvable/pingable from your shell/OS prompt on the source server. O - Finally, the Low Level Address (LLA) of the target server (visible in Q SERVER) needs to be set to the TCPPort upon which the target server is listening (e.g. visible from Q OPT output on target server). What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? Your source and target TSM Server instances can run on the same TCPPORT if they're running on different physical servers. If all of these are in place and there aren't any other factors getting in the way, PING SERVER commands should work and you'll have a platform for TSM Server to Server operations. HTH - let us know how you get on. //DMc London, UK - going to bed. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 17 July 2010 00:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, No...it is not successful...check the output below...I am calling the servers TSM_SOURCE and TSM_TARGET to make this easier: tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. The same happens the other way around. What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? tsm: TSM_SOURCEq server Server Comm. High-level Low-level Days Server Name Method Address AddressSince Password -- - - -- TSM_TARGET TCPIP xx.xx.xx.xx 1919 1Yes tsm: TSM_TARGETq server ServerComm. High-levelLow-level Days Server Name Method Address AddressSince Password -- - - -- TSM_SOURCE TCPIP xx.xx.xx.xx 15001 Yes Regards, Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 7:56:06 PM Subject: Re: Export server error Hi Mario, What does a `PING SERVER TSM_DEDALUS` from the source TSM Server admin CLI give you - is this successful? Cheers, //David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 16 July 2010 22:44 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L
Export server error
Hi list, I am trying to export all data from a TSM Server to a new one. Both servers are TSM 5.5.0.0 servers. I have defined the TARGET server on the SOURCE and vice versa, specifying a password and TCP Port (lladdress) for both servers. When I issue the EXPORT SERVER command with the PREVIEWIMPORT set to YES I get the following error on the SOURCE server: 07/17/2010 18:29:44 ANR2017I Administrator ADMIN issued command: EXPORT SERVER filed=all previewi=y tos=tsm_dedalus (SESSION: 18790) 07/17/2010 18:29:44 ANR0984I Process 254 for EXPORT SERVER started in the BACKGROUND at 18:29:44. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0609I EXPORT SERVER started as process 254. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0402I Session 18873 started for administrator ADMIN (Server) (Memory IPC). (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR8214E Session open with 200.143.2.89 failed due to connection refusal. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR0561E EXPORT SERVER: Process aborted - sign on to server, TSM_SERVER, failed. (SESSION: 18790, PROCESS: 254) The problem is that the TARGET server is refusing the connectionbut why?? NO messages appear in the ACTLOG at the TARGET server. What could be wrong? What am I missing? Regards, Mario
Re: Export server error
Hi Mario, What does a `PING SERVER TSM_DEDALUS` from the source TSM Server admin CLI give you - is this successful? Cheers, //David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 16 July 2010 22:44 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export server error Hi list, I am trying to export all data from a TSM Server to a new one. Both servers are TSM 5.5.0.0 servers. I have defined the TARGET server on the SOURCE and vice versa, specifying a password and TCP Port (lladdress) for both servers. When I issue the EXPORT SERVER command with the PREVIEWIMPORT set to YES I get the following error on the SOURCE server: 07/17/2010 18:29:44 ANR2017I Administrator ADMIN issued command: EXPORT SERVER filed=all previewi=y tos=tsm_dedalus (SESSION: 18790) 07/17/2010 18:29:44 ANR0984I Process 254 for EXPORT SERVER started in the BACKGROUND at 18:29:44. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0609I EXPORT SERVER started as process 254. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0402I Session 18873 started for administrator ADMIN (Server) (Memory IPC). (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR8214E Session open with 200.143.2.89 failed due to connection refusal. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR0561E EXPORT SERVER: Process aborted - sign on to server, TSM_SERVER, failed. (SESSION: 18790, PROCESS: 254) The problem is that the TARGET server is refusing the connectionbut why?? NO messages appear in the ACTLOG at the TARGET server. What could be wrong? What am I missing? Regards, Mario
Re: Export server error
- the admin account must exist on both servers - the passwords for those accounts must be in sync. Met vriendelijke groet, Marcel Anthonijsz Op 16 jul 2010 om 23:43 heeft Mario Behring mariobehr...@yahoo.com het volgende geschreven:\ Hi list, I am trying to export all data from a TSM Server to a new one. Both servers are TSM 5.5.0.0 servers. I have defined the TARGET server on the SOURCE and vice versa, specifying a password and TCP Port (lladdress) for both servers. When I issue the EXPORT SERVER command with the PREVIEWIMPORT set to YES I get the following error on the SOURCE server: 07/17/2010 18:29:44 ANR2017I Administrator ADMIN issued command: EXPORT SERVER filed=all previewi=y tos=tsm_dedalus (SESSION: 18790) 07/17/2010 18:29:44 ANR0984I Process 254 for EXPORT SERVER started in the BACKGROUND at 18:29:44. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0609I EXPORT SERVER started as process 254. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0402I Session 18873 started for administrator ADMIN (Server) (Memory IPC). (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR8214E Session open with 200.143.2.89 failed due to connection refusal. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR0561E EXPORT SERVER: Process aborted - sign on to server, TSM_SERVER, failed. (SESSION: 18790, PROCESS: 254) The problem is that the TARGET server is refusing the connectionbut why?? NO messages appear in the ACTLOG at the TARGET server. What could be wrong? What am I missing? Regards, Mario
Re: Export server error
Hi David, No...it is not successful...check the output below...I am calling the servers TSM_SOURCE and TSM_TARGET to make this easier: tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. The same happens the other way around. What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? tsm: TSM_SOURCEq server Server Comm. High-level Low-level Days Server Name Method Address AddressSince Password -- - - -- TSM_TARGET TCPIP xx.xx.xx.xx 1919 1Yes tsm: TSM_TARGETq server ServerComm. High-levelLow-level Days Server Name Method Address AddressSince Password -- - - -- TSM_SOURCE TCPIP xx.xx.xx.xx 15001 Yes Regards, Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 7:56:06 PM Subject: Re: Export server error Hi Mario, What does a `PING SERVER TSM_DEDALUS` from the source TSM Server admin CLI give you - is this successful? Cheers, //David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 16 July 2010 22:44 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export server error Hi list, I am trying to export all data from a TSM Server to a new one. Both servers are TSM 5.5.0.0 servers. I have defined the TARGET server on the SOURCE and vice versa, specifying a password and TCP Port (lladdress) for both servers. When I issue the EXPORT SERVER command with the PREVIEWIMPORT set to YES I get the following error on the SOURCE server: 07/17/2010 18:29:44 ANR2017I Administrator ADMIN issued command: EXPORT SERVER filed=all previewi=y tos=tsm_dedalus (SESSION: 18790) 07/17/2010 18:29:44 ANR0984I Process 254 for EXPORT SERVER started in the BACKGROUND at 18:29:44. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0609I EXPORT SERVER started as process 254. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0402I Session 18873 started for administrator ADMIN (Server) (Memory IPC). (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR8214E Session open with 200.143.2.89 failed due to connection refusal. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR0561E EXPORT SERVER: Process aborted - sign on to server, TSM_SERVER, failed. (SESSION: 18790, PROCESS: 254) The problem is that the TARGET server is refusing the connectionbut why?? NO messages appear in the ACTLOG at the TARGET server. What could be wrong? What am I missing? Regards, Mario
Re: Export server error
When posting, please include a summary of diagnostic measures you've already taken, so that we can productively suggest others. (Too often, assistance attempts are met with, Yeah, I already tried that.) I'd start by going to the target server system and doing 'lsof - i :LLaddressValue' to see if the port you think is being served, actually is - and by what. If it looks okay, try 'telnet localhost LLaddressValue' and see if that works. Then try the same telnet command from other systems in your area. If they can't connect, it is likely a firewall issue. An unlikely, but possible cause would be the server COMMMethod not allowing TCP/IP. Lastly, note that you are running two TSM servers with no maintenance, which represents some jeopardy as well as increasing the likelihood of problems. Richard Sims
Re: Export server error
Hi Mario, Looks like some detailed double-checking of the config is required - here goes! O - As Marcel points out, first you'll need to have an administrative user registered with the same password upon the source and target TSM Server instances. O - Next, the High Level Address (HLA) of the target server needs (visible in Q SERVER) to be resolvable/pingable from your shell/OS prompt on the source server. O - Finally, the Low Level Address (LLA) of the target server (visible in Q SERVER) needs to be set to the TCPPort upon which the target server is listening (e.g. visible from Q OPT output on target server). What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? Your source and target TSM Server instances can run on the same TCPPORT if they're running on different physical servers. If all of these are in place and there aren't any other factors getting in the way, PING SERVER commands should work and you'll have a platform for TSM Server to Server operations. HTH - let us know how you get on. //DMc London, UK - going to bed. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 17 July 2010 00:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, No...it is not successful...check the output below...I am calling the servers TSM_SOURCE and TSM_TARGET to make this easier: tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. The same happens the other way around. What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? tsm: TSM_SOURCEq server Server Comm. High-level Low-level Days Server Name Method Address AddressSince Password -- - - -- TSM_TARGET TCPIP xx.xx.xx.xx 1919 1Yes tsm: TSM_TARGETq server ServerComm. High-levelLow-level Days Server Name Method Address AddressSince Password -- - - -- TSM_SOURCE TCPIP xx.xx.xx.xx 15001 Yes Regards, Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 7:56:06 PM Subject: Re: Export server error Hi Mario, What does a `PING SERVER TSM_DEDALUS` from the source TSM Server admin CLI give you - is this successful? Cheers, //David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 16 July 2010 22:44 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export server error Hi list, I am trying to export all data from a TSM Server to a new one. Both servers are TSM 5.5.0.0 servers. I have defined the TARGET server on the SOURCE and vice versa, specifying a password and TCP Port (lladdress) for both servers. When I issue the EXPORT SERVER command with the PREVIEWIMPORT set to YES I get the following error on the SOURCE server: 07/17/2010 18:29:44 ANR2017I Administrator ADMIN issued command: EXPORT SERVER filed=all previewi=y tos=tsm_dedalus (SESSION: 18790) 07/17/2010 18:29:44 ANR0984I Process 254 for EXPORT SERVER started in the BACKGROUND at 18:29:44. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0609I EXPORT SERVER started as process 254. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0402I Session 18873 started for administrator ADMIN (Server) (Memory IPC). (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR8214E Session open with 200.143.2.89 failed due to connection refusal. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR0561E EXPORT SERVER: Process aborted - sign on to server, TSM_SERVER, failed. (SESSION: 18790, PROCESS: 254) The problem is that the TARGET server is refusing the connectionbut why?? NO messages appear in the ACTLOG at the TARGET server. What could be wrong? What am I missing? Regards, Mario
Re: Export server error
Hi Marcel, The ADMIN account exists on both servers, same password.the admin I use also exists on both servers and have the same password. About the passwods being in syncwhat do you mean? That they have to be equal, is that it, or is it something else? Regards, Mario From: Marcel Anthonijsz marcel.anthoni...@gmail.com To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 8:46:35 PM Subject: Re: Export server error - the admin account must exist on both servers - the passwords for those accounts must be in sync. Met vriendelijke groet, Marcel Anthonijsz Op 16 jul 2010 om 23:43 heeft Mario Behring mariobehr...@yahoo.com het volgende geschreven:\ Hi list, I am trying to export all data from a TSM Server to a new one. Both servers are TSM 5.5.0.0 servers. I have defined the TARGET server on the SOURCE and vice versa, specifying a password and TCP Port (lladdress) for both servers. When I issue the EXPORT SERVER command with the PREVIEWIMPORT set to YES I get the following error on the SOURCE server: 07/17/2010 18:29:44 ANR2017I Administrator ADMIN issued command: EXPORT SERVER filed=all previewi=y tos=tsm_dedalus (SESSION: 18790) 07/17/2010 18:29:44 ANR0984I Process 254 for EXPORT SERVER started in the BACKGROUND at 18:29:44. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0609I EXPORT SERVER started as process 254. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:44 ANR0402I Session 18873 started for administrator ADMIN (Server) (Memory IPC). (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR8214E Session open with 200.143.2.89 failed due to connection refusal. (SESSION: 18790, PROCESS: 254) 07/17/2010 18:29:45 ANR0561E EXPORT SERVER: Process aborted - sign on to server, TSM_SERVER, failed. (SESSION: 18790, PROCESS: 254) The problem is that the TARGET server is refusing the connectionbut why?? NO messages appear in the ACTLOG at the TARGET server. What could be wrong? What am I missing? Regards, Mario
