ADSM-L

Re: [ADSM-L] ANR8213W schedule fails client timeout

2012-06-06 14:29:25
Subject: Re: [ADSM-L] ANR8213W schedule fails client timeout
From: Tim Brown <tbrown AT CENHUD DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 6 Jun 2012 14:25:59 -0400
Netstat is listening on port 1501, tcpport is 1500 in dsm.opt
Telnet to server via 1501 works 1500 doesn't.

We have always coded tcpport 1500 in client dsm.opt ?
Other 2008 servers configured same work.

Thanks,

Tim

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Alex Paschal
Sent: Wednesday, 06 June, 2012 12:56 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: ANR8213W schedule fails client timeout

 From the TSM server:
    telnet hla lla
Example:
    telnet servera 1501
If it hangs and eventually times out, you have a firewall problem, as
David mentions.  If it says "Connection Refused" or similar, the CAD is
not listening on that port.  If it connects, your plumbing is fine.

Some other things to check:
      Have you set tcpclientport?
      Does netstat show your port in LISTENING state?  netstat -an |
find /I "listen"

Alex

On 6/6/2012 7:19 AM, Ehresman,David E. wrote:
> This is a classic symptom of a firewall blocking the cad port.  It works the 
> first time because the cad initiated the session and then the tsm server 
> times out the next time it reaches out to the client because the firewall is 
> blocking.  So you have to use webports to designate what port cad is going to 
> use and then open that port in the fire wall which can be a enterprise 
> firewall or a firewall running on the client.
>
> David Ehresman
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Tim Brown
> Sent: Wednesday, June 06, 2012 9:23 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] ANR8213W schedule fails client timeout
>
>   A few clients are failing with ANR8213W Session open with
> 10.1.4.130 timed out
>
>   If we restart the tsm service on the client the next
> scheduled backup runs ok but the
> next one times out. I even coded the hla and lla and set
> the client option
> file with tcpclientaddress, still issues. Any suggestions.
> Issue with 3-4 clients.
>
> Tim Brown
>
>
>
>