Re: Full VM Instant Restore error ans2411e rc=6523

[Efim]

Hi,
did you configure iSCSI on ESXi and set VMISCSIServeraddress on datamover?
Efim
 

> 27 июля 2017 г., в 9:49, rou...@univ.haifa.ac.il  
> написал(а):
> 
> Hello All
> 
> Tried the new feature on TSM for VE 8.1.0.1  in the Restore section called 
> "Full VM Instant Restore" . Here what I got running this command.
> 
> Error Or Warning Messages:
> • ERROR ANS2421E Cannot detect the iSCSI initiator.
> • ERROR ANS2411E Instant Restore/Access of virtual machine 'Test1' failed 
> with rc = 6523
> • ERROR ANS2421E (RC6523) Cannot detect the iSCSI initiator.
> 
> I Check on my TSM server  , the iSCSI initiator is ON , I can see the iqn id 
> on the Configuration tab in the iSCSI properties
> 
> I know I miss something but what ?.
> 
> Any suggestion , tip what to look ?
> 
> Best Regards Robert

Re: Full VM Instant Restore error ans2411e rc=6523

[rou...@univ.haifa.ac.il]

Hello Efim

I run the process on another ESXi and no problem the machine was created 
successfully.

I will check with the VMware administrator the status of the iSCSI on this 
specific EXSi

By the way another question , after the process finished successfully I check 
in the Instant Access/Restore Status windows but got " No data to display"

The new machine is power on and working ?

I did the process with full vm Instant Access instead full vm instant restore , 
and when finished successfully I check in Instant Access/Restore Status and 
seethe machine
waiting to be dismount.

Best Regards Robert

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Efim
Sent: Thursday, July 27, 2017 10:32 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Full VM Instant Restore error ans2411e rc=6523

Hi,
did you configure iSCSI on ESXi and set VMISCSIServeraddress on datamover?
Efim
 

> 27 июля 2017 г., в 9:49, rou...@univ.haifa.ac.il  
> написал(а):
> 
> Hello All
> 
> Tried the new feature on TSM for VE 8.1.0.1  in the Restore section called 
> "Full VM Instant Restore" . Here what I got running this command.
> 
> Error Or Warning Messages:
> • ERROR ANS2421E Cannot detect the iSCSI initiator.
> • ERROR ANS2411E Instant Restore/Access of virtual machine 'Test1' 
> failed with rc = 6523 • ERROR ANS2421E (RC6523) Cannot detect the iSCSI 
> initiator.
> 
> I Check on my TSM server  , the iSCSI initiator is ON , I can see the 
> iqn id on the Configuration tab in the iSCSI properties
> 
> I know I miss something but what ?.
> 
> Any suggestion , tip what to look ?
> 
> Best Regards Robert

Re: Full VM Instant Restore error ans2411e rc=6523

[Efim]

I correct understood that you try to instant restore VM and can't see the 
current restore process status in the Restore -> Instant Access/Restore Status?
Efim

> 27 июля 2017 г., в 11:14, rou...@univ.haifa.ac.il  
> написал(а):
> 
> Hello Efim
> 
> I run the process on another ESXi and no problem the machine was created 
> successfully.
> 
> I will check with the VMware administrator the status of the iSCSI on this 
> specific EXSi
> 
> By the way another question , after the process finished successfully I check 
> in the Instant Access/Restore Status windows but got " No data to display"
> 
> The new machine is power on and working ?
> 
> I did the process with full vm Instant Access instead full vm instant restore 
> , and when finished successfully I check in Instant Access/Restore Status and 
> seethe machine
> waiting to be dismount.
> 
> Best Regards Robert
> 
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Efim
> Sent: Thursday, July 27, 2017 10:32 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Full VM Instant Restore error ans2411e rc=6523
> 
> Hi,
> did you configure iSCSI on ESXi and set VMISCSIServeraddress on datamover?
> Efim
> 
> 
>> 27 июля 2017 г., в 9:49, rou...@univ.haifa.ac.il  
>> написал(а):
>> 
>> Hello All
>> 
>> Tried the new feature on TSM for VE 8.1.0.1  in the Restore section called 
>> "Full VM Instant Restore" . Here what I got running this command.
>> 
>> Error Or Warning Messages:
>> • ERROR ANS2421E Cannot detect the iSCSI initiator.
>> • ERROR ANS2411E Instant Restore/Access of virtual machine 'Test1' 
>> failed with rc = 6523 • ERROR ANS2421E (RC6523) Cannot detect the iSCSI 
>> initiator.
>> 
>> I Check on my TSM server  , the iSCSI initiator is ON , I can see the 
>> iqn id on the Configuration tab in the iSCSI properties
>> 
>> I know I miss something but what ?.
>> 
>> Any suggestion , tip what to look ?
>> 
>> Best Regards Robert

Re: Full VM Instant Restore error ans2411e rc=6523

[rou...@univ.haifa.ac.il]

In  did . despite of the virtual machine was created successfully with the 
process Full VM instant restore

Regards Robert

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Efim
Sent: Thursday, July 27, 2017 11:33 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Full VM Instant Restore error ans2411e rc=6523

I correct understood that you try to instant restore VM and can't see the 
current restore process status in the Restore -> Instant Access/Restore Status?
Efim

> 27 июля 2017 г., в 11:14, rou...@univ.haifa.ac.il  
> написал(а):
> 
> Hello Efim
> 
> I run the process on another ESXi and no problem the machine was created 
> successfully.
> 
> I will check with the VMware administrator the status of the iSCSI on 
> this specific EXSi
> 
> By the way another question , after the process finished successfully I check 
> in the Instant Access/Restore Status windows but got " No data to display"
> 
> The new machine is power on and working ?
> 
> I did the process with full vm Instant Access instead full vm instant 
> restore , and when finished successfully I check in Instant Access/Restore 
> Status and seethe machine waiting to be dismount.
> 
> Best Regards Robert
> 
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
> Of Efim
> Sent: Thursday, July 27, 2017 10:32 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Full VM Instant Restore error ans2411e rc=6523
> 
> Hi,
> did you configure iSCSI on ESXi and set VMISCSIServeraddress on datamover?
> Efim
> 
> 
>> 27 июля 2017 г., в 9:49, rou...@univ.haifa.ac.il  
>> написал(а):
>> 
>> Hello All
>> 
>> Tried the new feature on TSM for VE 8.1.0.1  in the Restore section called 
>> "Full VM Instant Restore" . Here what I got running this command.
>> 
>> Error Or Warning Messages:
>> • ERROR ANS2421E Cannot detect the iSCSI initiator.
>> • ERROR ANS2411E Instant Restore/Access of virtual machine 'Test1' 
>> failed with rc = 6523 • ERROR ANS2421E (RC6523) Cannot detect the iSCSI 
>> initiator.
>> 
>> I Check on my TSM server  , the iSCSI initiator is ON , I can see the 
>> iqn id on the Configuration tab in the iSCSI properties
>> 
>> I know I miss something but what ?.
>> 
>> Any suggestion , tip what to look ?
>> 
>> Best Regards Robert

Re: Full VM Instant Restore error ans2411e rc=6523

[Efim]

I have no idea...
try to run query vm * -vmrestoretype=instantrestore -detail
Efim

> 27 июля 2017 г., в 11:39, rou...@univ.haifa.ac.il  
> написал(а):
> 
> In  did . despite of the virtual machine was created successfully with 
> the process Full VM instant restore
> 
> Regards Robert
> 
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Efim
> Sent: Thursday, July 27, 2017 11:33 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Full VM Instant Restore error ans2411e rc=6523
> 
> I correct understood that you try to instant restore VM and can't see the 
> current restore process status in the Restore -> Instant Access/Restore 
> Status?
> Efim
> 
>> 27 июля 2017 г., в 11:14, rou...@univ.haifa.ac.il  
>> написал(а):
>> 
>> Hello Efim
>> 
>> I run the process on another ESXi and no problem the machine was created 
>> successfully.
>> 
>> I will check with the VMware administrator the status of the iSCSI on 
>> this specific EXSi
>> 
>> By the way another question , after the process finished successfully I 
>> check in the Instant Access/Restore Status windows but got " No data to 
>> display"
>> 
>> The new machine is power on and working ?
>> 
>> I did the process with full vm Instant Access instead full vm instant 
>> restore , and when finished successfully I check in Instant Access/Restore 
>> Status and seethe machine waiting to be dismount.
>> 
>> Best Regards Robert
>> 
>> -Original Message-
>> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf 
>> Of Efim
>> Sent: Thursday, July 27, 2017 10:32 AM
>> To: ADSM-L@VM.MARIST.EDU
>> Subject: Re: [ADSM-L] Full VM Instant Restore error ans2411e rc=6523
>> 
>> Hi,
>> did you configure iSCSI on ESXi and set VMISCSIServeraddress on datamover?
>> Efim
>> 
>> 
>>> 27 июля 2017 г., в 9:49, rou...@univ.haifa.ac.il  
>>> написал(а):
>>> 
>>> Hello All
>>> 
>>> Tried the new feature on TSM for VE 8.1.0.1  in the Restore section called 
>>> "Full VM Instant Restore" . Here what I got running this command.
>>> 
>>> Error Or Warning Messages:
>>> • ERROR ANS2421E Cannot detect the iSCSI initiator.
>>> • ERROR ANS2411E Instant Restore/Access of virtual machine 'Test1' 
>>> failed with rc = 6523 • ERROR ANS2421E (RC6523) Cannot detect the iSCSI 
>>> initiator.
>>> 
>>> I Check on my TSM server  , the iSCSI initiator is ON , I can see the 
>>> iqn id on the Configuration tab in the iSCSI properties
>>> 
>>> I know I miss something but what ?.
>>> 
>>> Any suggestion , tip what to look ?
>>> 
>>> Best Regards Robert

2 nics on tsm server.

[Bo Nielsen]

Hi TSM's

I have recently added one more NIC to my TSM server.
The new NIC is connected directly to the server, for which archiving is 
required.
>From DSM.SYS on the archiving server, who is a RHEL:
   COMMmethod TCPip
   TCPPort1500
   TCPServeraddress  192.168.1.11
   tcpclientaddress  192.168.1.21

The TSM server is a W2K12 R2 and the TSM vers. 7.1.4.1.

When I try to start DSMC, I get this error:
27/07/17   10:15:04 ANS5216E Could not establish a TCP/IP connection with 
address '192.168.1.11:1500'. The TCP/IP error is 'Connection timed out' (errno 
= 110).
27/07/17   10:15:04 ANS9020E A session could not be established with a TSM 
server or client agent.  The return code is -50.
27/07/17   10:15:04 ANS1017E Session rejected: TCP/IP connection failure.

>From NETSTAT on TSM server server:
TCP0.0.0.0:1500   AIT-PTSM03:0   LISTENING
TCP192.168.1.11:139   AIT-PTSM03:0   LISTENING
TCP192.168.1.11:63177 192.168.1.21:ssh   ESTABLISHED

The firewall is disabled for now.

Pls, help!! I've search the internet.

Regards,

Bo Nielsen


IT Service



Technical University of Denmark

IT Service

Frederiksborgvej 399

Building 109

DK - 4000 Roskilde

Denmark

Mobil +45 2337 0271

boa...@dtu.dk

Re: 2 nics on tsm server.

[Karel Bos]

Hi,


Start with the basics, OS tools like ping. You probably have no static route
to this new/seperate network.

Kind regards,

Karel

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Bo Nielsen
Verzonden: donderdag 27 juli 2017 11:10
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] 2 nics on tsm server.

Hi TSM's

I have recently added one more NIC to my TSM server.
The new NIC is connected directly to the server, for which archiving is
required.
>From DSM.SYS on the archiving server, who is a RHEL:
   COMMmethod TCPip
   TCPPort1500
   TCPServeraddress  192.168.1.11
   tcpclientaddress  192.168.1.21

The TSM server is a W2K12 R2 and the TSM vers. 7.1.4.1.

When I try to start DSMC, I get this error:
27/07/17   10:15:04 ANS5216E Could not establish a TCP/IP connection with
address '192.168.1.11:1500'. The TCP/IP error is 'Connection timed out'
(errno = 110).
27/07/17   10:15:04 ANS9020E A session could not be established with a TSM
server or client agent.  The return code is -50.
27/07/17   10:15:04 ANS1017E Session rejected: TCP/IP connection failure.

>From NETSTAT on TSM server server:
TCP0.0.0.0:1500   AIT-PTSM03:0   LISTENING
TCP192.168.1.11:139   AIT-PTSM03:0   LISTENING
TCP192.168.1.11:63177 192.168.1.21:ssh   ESTABLISHED

The firewall is disabled for now.

Pls, help!! I've search the internet.

Regards,

Bo Nielsen


IT Service



Technical University of Denmark

IT Service

Frederiksborgvej 399

Building 109

DK - 4000 Roskilde

Denmark

Mobil +45 2337 0271

boa...@dtu.dk


---
Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
https://www.avast.com/antivirus

Re: 2 nics on tsm server.

[Bo Nielsen]

Hi,

I can ping from both servers. 
There isn't routing. It's a direct connection between the two servers.

Regards,

Bo

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Karel 
Bos
Sent: 27. juli 2017 11:27
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] 2 nics on tsm server.

Hi,


Start with the basics, OS tools like ping. You probably have no static route to 
this new/seperate network.

Kind regards,

Karel

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Bo Nielsen
Verzonden: donderdag 27 juli 2017 11:10
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] 2 nics on tsm server.

Hi TSM's

I have recently added one more NIC to my TSM server.
The new NIC is connected directly to the server, for which archiving is 
required.
>From DSM.SYS on the archiving server, who is a RHEL:
   COMMmethod TCPip
   TCPPort1500
   TCPServeraddress  192.168.1.11
   tcpclientaddress  192.168.1.21

The TSM server is a W2K12 R2 and the TSM vers. 7.1.4.1.

When I try to start DSMC, I get this error:
27/07/17   10:15:04 ANS5216E Could not establish a TCP/IP connection with
address '192.168.1.11:1500'. The TCP/IP error is 'Connection timed out'
(errno = 110).
27/07/17   10:15:04 ANS9020E A session could not be established with a TSM
server or client agent.  The return code is -50.
27/07/17   10:15:04 ANS1017E Session rejected: TCP/IP connection failure.

>From NETSTAT on TSM server server:
TCP0.0.0.0:1500   AIT-PTSM03:0   LISTENING
TCP192.168.1.11:139   AIT-PTSM03:0   LISTENING
TCP192.168.1.11:63177 192.168.1.21:ssh   ESTABLISHED

The firewall is disabled for now.

Pls, help!! I've search the internet.

Regards,

Bo Nielsen


IT Service



Technical University of Denmark

IT Service

Frederiksborgvej 399

Building 109

DK - 4000 Roskilde

Denmark

Mobil +45 2337 0271

boa...@dtu.dk


---
Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
https://www.avast.com/antivirus

AW: [ADSM-L] 2 nics on tsm server.

[Schneck, Dennis]

Hi,

can you connecttelnet  1500 for example

you should see:

Connected to .
Escape character is '^]'.



Von: ADSM: Dist Stor Manager [ADSM-L@vm.marist.edu]" im Auftrag von 
"Bo Nielsen [boa...@dtu.dk]
Gesendet: Donnerstag, 27. Juli 2017 11:50
An: ADSM-L@vm.marist.edu
Betreff: Re: [ADSM-L] 2 nics on tsm server.

Hi,

I can ping from both servers.
There isn't routing. It's a direct connection between the two servers.

Regards,

Bo

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Karel 
Bos
Sent: 27. juli 2017 11:27
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] 2 nics on tsm server.

Hi,


Start with the basics, OS tools like ping. You probably have no static route to 
this new/seperate network.

Kind regards,

Karel

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Bo Nielsen
Verzonden: donderdag 27 juli 2017 11:10
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] 2 nics on tsm server.

Hi TSM's

I have recently added one more NIC to my TSM server.
The new NIC is connected directly to the server, for which archiving is 
required.
>From DSM.SYS on the archiving server, who is a RHEL:
   COMMmethod TCPip
   TCPPort1500
   TCPServeraddress  192.168.1.11
   tcpclientaddress  192.168.1.21

The TSM server is a W2K12 R2 and the TSM vers. 7.1.4.1.

When I try to start DSMC, I get this error:
27/07/17   10:15:04 ANS5216E Could not establish a TCP/IP connection with
address '192.168.1.11:1500'. The TCP/IP error is 'Connection timed out'
(errno = 110).
27/07/17   10:15:04 ANS9020E A session could not be established with a TSM
server or client agent.  The return code is -50.
27/07/17   10:15:04 ANS1017E Session rejected: TCP/IP connection failure.

>From NETSTAT on TSM server server:
TCP0.0.0.0:1500   AIT-PTSM03:0   LISTENING
TCP192.168.1.11:139   AIT-PTSM03:0   LISTENING
TCP192.168.1.11:63177 192.168.1.21:ssh   ESTABLISHED

The firewall is disabled for now.

Pls, help!! I've search the internet.

Regards,

Bo Nielsen


IT Service



Technical University of Denmark

IT Service

Frederiksborgvej 399

Building 109

DK - 4000 Roskilde

Denmark

Mobil +45 2337 0271

boa...@dtu.dk


---
Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
https://www.avast.com/antivirus

Re: AW: [ADSM-L] 2 nics on tsm server.

[Sasa Drnjevic]

And what does arp say?


--
Sasa Drnjevic
www.srce.unizg.hr


On 27.7.2017. 11:54, Schneck, Dennis 
wrote:
> Hi,
>
> can you connecttelnet  1500 for example
>
> you should see:
>
> Connected to .
> Escape character is '^]'.
>
>
> 
> Von: ADSM: Dist Stor Manager [ADSM-L@vm.marist.edu]" im Auftrag von 
> "Bo Nielsen [boa...@dtu.dk]
> Gesendet: Donnerstag, 27. Juli 2017 11:50
> An: ADSM-L@vm.marist.edu
> Betreff: Re: [ADSM-L] 2 nics on tsm server.
>
> Hi,
>
> I can ping from both servers.
> There isn't routing. It's a direct connection between the two servers.
>
> Regards,
>
> Bo
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> Karel Bos
> Sent: 27. juli 2017 11:27
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] 2 nics on tsm server.
>
> Hi,
>
>
> Start with the basics, OS tools like ping. You probably have no static route 
> to this new/seperate network.
>
> Kind regards,
>
> Karel
>
> -Oorspronkelijk bericht-
> Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Bo Nielsen
> Verzonden: donderdag 27 juli 2017 11:10
> Aan: ADSM-L@VM.MARIST.EDU
> Onderwerp: [ADSM-L] 2 nics on tsm server.
>
> Hi TSM's
>
> I have recently added one more NIC to my TSM server.
> The new NIC is connected directly to the server, for which archiving is 
> required.
> From DSM.SYS on the archiving server, who is a RHEL:
>COMMmethod TCPip
>TCPPort1500
>TCPServeraddress  192.168.1.11
>tcpclientaddress  192.168.1.21
>
> The TSM server is a W2K12 R2 and the TSM vers. 7.1.4.1.
>
> When I try to start DSMC, I get this error:
> 27/07/17   10:15:04 ANS5216E Could not establish a TCP/IP connection with
> address '192.168.1.11:1500'. The TCP/IP error is 'Connection timed out'
> (errno = 110).
> 27/07/17   10:15:04 ANS9020E A session could not be established with a TSM
> server or client agent.  The return code is -50.
> 27/07/17   10:15:04 ANS1017E Session rejected: TCP/IP connection failure.
>
> From NETSTAT on TSM server server:
> TCP0.0.0.0:1500   AIT-PTSM03:0   LISTENING
> TCP192.168.1.11:139   AIT-PTSM03:0   LISTENING
> TCP192.168.1.11:63177 192.168.1.21:ssh   ESTABLISHED
>
> The firewall is disabled for now.
>
> Pls, help!! I've search the internet.
>
> Regards,
>
> Bo Nielsen
>
>
> IT Service
>
>
>
> Technical University of Denmark
>
> IT Service
>
> Frederiksborgvej 399
>
> Building 109
>
> DK - 4000 Roskilde
>
> Denmark
>
> Mobil +45 2337 0271
>
> boa...@dtu.dk
>
>
> ---
> Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
> https://www.avast.com/antivirus
>

Re: 2 nics on tsm server.

[Bo Nielsen]

Hi 

I can't telnet. telnet: command not found

Arp:

Interface: 192.168.1.11 --- 0x17
  Internet Address  Physical Address  Type
  192.168.1.21  00-e0-ed-24-97-af dynamic
  192.168.1.255 ff-ff-ff-ff-ff-ff static

Regards

Bo

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Schneck, Dennis 
Sent: 27. juli 2017 11:54
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] AW: [ADSM-L] 2 nics on tsm server.

Hi,

can you connecttelnet  1500 for example

you should see:

Connected to .
Escape character is '^]'.



Von: ADSM: Dist Stor Manager [ADSM-L@vm.marist.edu]" im Auftrag von 
"Bo Nielsen [boa...@dtu.dk]
Gesendet: Donnerstag, 27. Juli 2017 11:50
An: ADSM-L@vm.marist.edu
Betreff: Re: [ADSM-L] 2 nics on tsm server.

Hi,

I can ping from both servers.
There isn't routing. It's a direct connection between the two servers.

Regards,

Bo

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Karel 
Bos
Sent: 27. juli 2017 11:27
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] 2 nics on tsm server.

Hi,


Start with the basics, OS tools like ping. You probably have no static route to 
this new/seperate network.

Kind regards,

Karel

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Bo Nielsen
Verzonden: donderdag 27 juli 2017 11:10
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] 2 nics on tsm server.

Hi TSM's

I have recently added one more NIC to my TSM server.
The new NIC is connected directly to the server, for which archiving is 
required.
>From DSM.SYS on the archiving server, who is a RHEL:
   COMMmethod TCPip
   TCPPort1500
   TCPServeraddress  192.168.1.11
   tcpclientaddress  192.168.1.21

The TSM server is a W2K12 R2 and the TSM vers. 7.1.4.1.

When I try to start DSMC, I get this error:
27/07/17   10:15:04 ANS5216E Could not establish a TCP/IP connection with
address '192.168.1.11:1500'. The TCP/IP error is 'Connection timed out'
(errno = 110).
27/07/17   10:15:04 ANS9020E A session could not be established with a TSM
server or client agent.  The return code is -50.
27/07/17   10:15:04 ANS1017E Session rejected: TCP/IP connection failure.

>From NETSTAT on TSM server server:
TCP0.0.0.0:1500   AIT-PTSM03:0   LISTENING
TCP192.168.1.11:139   AIT-PTSM03:0   LISTENING
TCP192.168.1.11:63177 192.168.1.21:ssh   ESTABLISHED

The firewall is disabled for now.

Pls, help!! I've search the internet.

Regards,

Bo Nielsen


IT Service



Technical University of Denmark

IT Service

Frederiksborgvej 399

Building 109

DK - 4000 Roskilde

Denmark

Mobil +45 2337 0271

boa...@dtu.dk


---
Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
https://www.avast.com/antivirus

Re: 2 nics on tsm server.

[Sasa Drnjevic]

On 27.7.2017. 12:11, Bo Nielsen wrote:
> Hi
>
> I can't telnet. telnet: command not found


http://www.sysprobs.com/install-and-enable-telnet-in-windows-8-use-as-telnet-client

--








>
> Arp:
>
> Interface: 192.168.1.11 --- 0x17
>   Internet Address  Physical Address  Type
>   192.168.1.21  00-e0-ed-24-97-af dynamic
>   192.168.1.255 ff-ff-ff-ff-ff-ff static
>
> Regards
>
> Bo
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> Schneck, Dennis 
> Sent: 27. juli 2017 11:54
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] AW: [ADSM-L] 2 nics on tsm server.
>
> Hi,
>
> can you connecttelnet  1500 for example
>
> you should see:
>
> Connected to .
> Escape character is '^]'.
>
>
> 
> Von: ADSM: Dist Stor Manager [ADSM-L@vm.marist.edu]" im Auftrag von 
> "Bo Nielsen [boa...@dtu.dk]
> Gesendet: Donnerstag, 27. Juli 2017 11:50
> An: ADSM-L@vm.marist.edu
> Betreff: Re: [ADSM-L] 2 nics on tsm server.
>
> Hi,
>
> I can ping from both servers.
> There isn't routing. It's a direct connection between the two servers.
>
> Regards,
>
> Bo
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
> Karel Bos
> Sent: 27. juli 2017 11:27
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] 2 nics on tsm server.
>
> Hi,
>
>
> Start with the basics, OS tools like ping. You probably have no static route 
> to this new/seperate network.
>
> Kind regards,
>
> Karel
>
> -Oorspronkelijk bericht-
> Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Bo Nielsen
> Verzonden: donderdag 27 juli 2017 11:10
> Aan: ADSM-L@VM.MARIST.EDU
> Onderwerp: [ADSM-L] 2 nics on tsm server.
>
> Hi TSM's
>
> I have recently added one more NIC to my TSM server.
> The new NIC is connected directly to the server, for which archiving is 
> required.
> From DSM.SYS on the archiving server, who is a RHEL:
>COMMmethod TCPip
>TCPPort1500
>TCPServeraddress  192.168.1.11
>tcpclientaddress  192.168.1.21
>
> The TSM server is a W2K12 R2 and the TSM vers. 7.1.4.1.
>
> When I try to start DSMC, I get this error:
> 27/07/17   10:15:04 ANS5216E Could not establish a TCP/IP connection with
> address '192.168.1.11:1500'. The TCP/IP error is 'Connection timed out'
> (errno = 110).
> 27/07/17   10:15:04 ANS9020E A session could not be established with a TSM
> server or client agent.  The return code is -50.
> 27/07/17   10:15:04 ANS1017E Session rejected: TCP/IP connection failure.
>
> From NETSTAT on TSM server server:
> TCP0.0.0.0:1500   AIT-PTSM03:0   LISTENING
> TCP192.168.1.11:139   AIT-PTSM03:0   LISTENING
> TCP192.168.1.11:63177 192.168.1.21:ssh   ESTABLISHED
>
> The firewall is disabled for now.
>
> Pls, help!! I've search the internet.
>
> Regards,
>
> Bo Nielsen
>
>
> IT Service
>
>
>
> Technical University of Denmark
>
> IT Service
>
> Frederiksborgvej 399
>
> Building 109
>
> DK - 4000 Roskilde
>
> Denmark
>
> Mobil +45 2337 0271
>
> boa...@dtu.dk
>
>
> ---
> Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware.
> https://www.avast.com/antivirus
>

Re: Sloooow deletion of objects on Replication target server

[Zoltan Forray]

On Thu, Jul 27, 2017 at 2:24 AM, Chavdar Cholev 
wrote:

> did you try server instrumentation... if there is an issue with storage or
> network you should be able to identify from server instrumentation output..
>

Not yet. My first objective right now is to upgrade from 7.1.6.3 to
7.1.7.300 to address replication issues I have seen and are fixed in
7.1.7.x.  I am hoping there might be some performance improvements along
the way.


--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

Re: Sloooow deletion of objects on Replication target server

[Zoltan Forray]

On Thu, Jul 27, 2017 at 12:56 AM, Stefan Folkerts  wrote:

> The read intensive ssd's can be the enterprise value type from lenovo,


I will pitch the idea but am pretty sure I will be wasting my time.  There
are 2-other TSM servers that must be replaced/budgeted next year (we are
state budget July->June) due to warranty expiring.  Plus, we are a Dell/EMC
shop so we must buy from them.  I am focusing on the number of
cores/threads since even idle the box seems to be running 12+ processes.
Right now I am doing 2-movedata on NFS volumes that are 256GB in size (I
later realized this big a volume is a mistake and am rebuilding to 128GB
volumes) and 2-of my production servers are sending DB Snapshots (we use
this as a warm-site and store DBBackups, copies of volhist, devconfig, etc)
and the load average is >25.


--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

Re: tsm node replication fails no reason why

[Stefan Folkerts]

The reason is usually given just before the first line in your log on the
source server, so the line above the one with the ANR0986I code.


On Wed, Jul 26, 2017 at 8:07 PM, Tim Brown  wrote:

> TSM node replication fails , no indication why on source or target server?
>
> Source server
>
> 07/26/2017 13:25:49  ANR0986I Process 385 for Replicate Node running
> in the
>   BACKGROUND processed 3,782,768 items for a total
> of
>   777,525,123,113 bytes with a completion state of
> FAILURE
>   at 13:25:49. (SESSION: 21075, PROCESS: 385)
> 07/26/2017 13:25:49  ANR1893E Process 385 for Replicate Node completed
> with a
>   completion state of FAILURE. (SESSION: 21075,
> PROCESS:
>   385)
>
> Target server
>
> 07/26/2017 13:25:51  ANR0514I Session 486 closed volume
>   N:\ECM_PRIM2\01BC04E0.BFS. (SESSION: 486)
> 07/26/2017 13:26:22  ANR0408I Session 605 started for server
> TSMPOK_SERVER1
>   (Windows) (Tcp/Ip) for replication.  (SESSION:
> 605)
> 07/26/2017 13:26:22  ANR0409I Session 486 ended for server
> TSMPOK_SERVER1
>   (Windows). (SESSION: 486)
> 07/26/2017 13:26:22  ANR0409I Session 605 ended for server
> TSMPOK_SERVER1
>   (Windows). (SESSION: 605)
> 07/26/2017 13:26:41  ANR0985I Process 51 for Replicate Node ( As
> Secondary )
>   running in the BACKGROUND completed with
> completion state
>   FAILURE at 13:26:41. (SESSION: 410, PROCESS: 51)
> 07/26/2017 13:26:41  ANR1893E Process 51 for Replicate Node ( As
> Secondary )
>   completed with a completion state of FAILURE.
> (SESSION:
>   410, PROCESS: 51)
>
> Tim
>

Re: Full VM Instant Restore error ans2411e rc=6523

[Schneider, Jim]

My VM backup proxy server has a backup network connection but the client does 
not.  I have to disable the backup network NIC before starting the TSM Recovery 
Agent so that the client can see the iSCSI connection.

Jim Schneider
Essendant

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
rou...@univ.haifa.ac.il
Sent: Thursday, July 27, 2017 1:49 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Full VM Instant Restore error ans2411e rc=6523

Hello All

Tried the new feature on TSM for VE 8.1.0.1  in the Restore section called 
"Full VM Instant Restore" . Here what I got running this command.

Error Or Warning Messages:
* ERROR ANS2421E Cannot detect the iSCSI initiator.
* ERROR ANS2411E Instant Restore/Access of virtual machine 'Test1' failed with 
rc = 6523 * ERROR ANS2421E (RC6523) Cannot detect the iSCSI initiator.

I Check on my TSM server  , the iSCSI initiator is ON , I can see the iqn id on 
the Configuration tab in the iSCSI properties

I know I miss something but what ?.

Any suggestion , tip what to look ?

Best Regards Robert

**
Information contained in this e-mail message and in any attachments thereto is 
confidential. If you are not the intended recipient, please destroy this 
message, delete any copies held on your systems, notify the sender immediately, 
and refrain from using or disclosing all or any part of its content to any 
other person.