Re: Connecting with acsls
Hi, Jacque. I experimented with dropping gresham distributape on a test box to see how that would work out. I vaguely recall using the lbtest application to make sure I had configured the TSM SSI stuff correctly. Have you tried using lbtest to verify functionality? That can at least help narrow down the domain of the problem. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Jacque Mergens [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 7:51 AM To: [EMAIL PROTECTED] Subject: Re: Connecting with acsls Yeah, I have. This is evidenced by the RPC call and reply by the TSM server. It actually looks like the comms are working. I can only conclude that the TSM isn't sending the correct information since it looks like the RPC protocol is working properly but communication just stops after the firzt session. Do you know anything about the initial transaction during definition? This problem smells badly of a configuration problem but I can't for the life of think of what I did wrong and I can't troubleshoot it unless I know what the good information would be. Jacque -Original Message- From: Firmes, Stephen [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Connecting with acsls Jacque, Are you starting the ACSLS daemon that facilitates communications between TSM and ACSLS? This is the code I put in my DSMSERV.RC script and I am having no issues. This logic is executed before you start the TSM server. acsdir="/opt/tivoli/tsm/devices/bin" echo "Starting ACSLS daemon." cd $acsdir ./rc.acs_ssi quiet $* || "ACSLS Server (\"$acsdir\") error.. Aborting." Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com -Original Message- From: Jacque Mergens [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 7:36 AM To: [EMAIL PROTECTED] Subject: Connecting with acsls I am setting up a tsm server and cannot define an acsls library. When I attempt the following command: define library acslib libtype=acsls acsid=0 The server times out and says that the library is not currently available. I am currently running samfs on an E450 that can connect and access the ACSLS server without any problem so I don't think that ACSLS is the problem. I have generated traces that seem to indicate that the communication between the servers is fine but it stops after the first TCP session. In short the TSM interrogates properly for the RPC port, attaches to the port, runs the TCP session and then just shuts up. The configuration is as follows: P640: AIX 4.3.3 TSM 5.1.1 SCSI attached LTO within an L180 UltraSparq 5 Solaris 8 ACSLS 6.0 Connected to an L180
Re: Connecting with acsls
Yeah, I have. This is evidenced by the RPC call and reply by the TSM server. It actually looks like the comms are working. I can only conclude that the TSM isn't sending the correct information since it looks like the RPC protocol is working properly but communication just stops after the firzt session. Do you know anything about the initial transaction during definition? This problem smells badly of a configuration problem but I can't for the life of think of what I did wrong and I can't troubleshoot it unless I know what the good information would be. Jacque -Original Message- From: Firmes, Stephen [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Connecting with acsls Jacque, Are you starting the ACSLS daemon that facilitates communications between TSM and ACSLS? This is the code I put in my DSMSERV.RC script and I am having no issues. This logic is executed before you start the TSM server. acsdir="/opt/tivoli/tsm/devices/bin" echo "Starting ACSLS daemon." cd $acsdir ./rc.acs_ssi quiet $* || "ACSLS Server (\"$acsdir\") error.. Aborting." Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com -Original Message- From: Jacque Mergens [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 7:36 AM To: [EMAIL PROTECTED] Subject: Connecting with acsls I am setting up a tsm server and cannot define an acsls library. When I attempt the following command: define library acslib libtype=acsls acsid=0 The server times out and says that the library is not currently available. I am currently running samfs on an E450 that can connect and access the ACSLS server without any problem so I don't think that ACSLS is the problem. I have generated traces that seem to indicate that the communication between the servers is fine but it stops after the first TCP session. In short the TSM interrogates properly for the RPC port, attaches to the port, runs the TCP session and then just shuts up. The configuration is as follows: P640: AIX 4.3.3 TSM 5.1.1 SCSI attached LTO within an L180 UltraSparq 5 Solaris 8 ACSLS 6.0 Connected to an L180
Re: Connecting with acsls
Jacque, Are you starting the ACSLS daemon that facilitates communications between TSM and ACSLS? This is the code I put in my DSMSERV.RC script and I am having no issues. This logic is executed before you start the TSM server. acsdir="/opt/tivoli/tsm/devices/bin" echo "Starting ACSLS daemon." cd $acsdir ./rc.acs_ssi quiet $* || "ACSLS Server (\"$acsdir\") error.. Aborting." Stephen Firmes TSM Engineer Tivoli Certified TSM Consultant StorageNetworks, Inc Work: 781-622-6287 http://www.storagenetworks.com -Original Message- From: Jacque Mergens [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 7:36 AM To: [EMAIL PROTECTED] Subject: Connecting with acsls I am setting up a tsm server and cannot define an acsls library. When I attempt the following command: define library acslib libtype=acsls acsid=0 The server times out and says that the library is not currently available. I am currently running samfs on an E450 that can connect and access the ACSLS server without any problem so I don't think that ACSLS is the problem. I have generated traces that seem to indicate that the communication between the servers is fine but it stops after the first TCP session. In short the TSM interrogates properly for the RPC port, attaches to the port, runs the TCP session and then just shuts up. The configuration is as follows: P640: AIX 4.3.3 TSM 5.1.1 SCSI attached LTO within an L180 UltraSparq 5 Solaris 8 ACSLS 6.0 Connected to an L180
Re: Connecting with acsls
On 02-Jul-02 Firmes, Stephen wrote: > Jacque, > > Are you starting the ACSLS daemon that facilitates communications between TSM > and ACSLS? > This is the code I put in my DSMSERV.RC script and I am having no issues. > This logic is executed before you start the TSM server. > > acsdir="/opt/tivoli/tsm/devices/bin" > echo "Starting ACSLS daemon." > cd $acsdir > ./rc.acs_ssi quiet $* || "ACSLS Server (\"$acsdir\") error.. Aborting." Or put it into the /etc/inittab: autoacs:2:once:/usr/tivoli/tsm/devices/bin/rc.acs_ssi quiet >/dev/console 2>&1 #Start the ssi agent Cheers, Henk ten Have.
Connecting with acsls
I am setting up a tsm server and cannot define an acsls library. When I attempt the following command: define library acslib libtype=acsls acsid=0 The server times out and says that the library is not currently available. I am currently running samfs on an E450 that can connect and access the ACSLS server without any problem so I don't think that ACSLS is the problem. I have generated traces that seem to indicate that the communication between the servers is fine but it stops after the first TCP session. In short the TSM interrogates properly for the RPC port, attaches to the port, runs the TCP session and then just shuts up. The configuration is as follows: P640: AIX 4.3.3 TSM 5.1.1 SCSI attached LTO within an L180 UltraSparq 5 Solaris 8 ACSLS 6.0 Connected to an L180
