ADSM-L

Re: Node attribute change

2005-09-07 05:18:26
Subject: Re: Node attribute change
From: "Large, M (Matthew)" <Matthew.Large AT RABOBANK DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 7 Sep 2005 10:18:11 +0100
 Ah, I think I'm looking for an 'official' answer - the node was
contacted using the Server Prompted option, TSM found a new TCP address,
at this point I would have expected TSM to record the new TCP address
against the node, and to use the new address in future contacts, not the
old one. 
The backup was not successful because TSM could not communicate with the
client wusing the IP it had, despite the node reporting an attribute
change.

Thanks for your suggestions,
Matthew

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
sandeep Jain
Sent: 07 September 2005 10:11
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Node attribute change

May be it tries to read/checks the client option file ( dsm.opt or what
ever u have specified)associated to schedular while defining tsm client
schedular , it may have kept those entries in database,  despite of this
message I feel that urs backup was successful..

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Large, M (Matthew)
Sent: Wednesday, September 07, 2005 1:53 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Node attribute change


Hi Sandeep,

We don't use accounting at the moment so we are not affected by that.
My question is why, if TSM updated the attributes after it noticed they
had changed, did it not attempt to communicate to the client over the
new TCP address? If it had it might not have failed to perform the
backup last night. Cheers

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
sandeep Jain
Sent: 07 September 2005 08:46
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Node attribute change

Hi matthew,
            ANR1639I indicates that the TSM server found that the client
node connected to the TSM server with a different IP address than it did
before. This does not affect operation, however it may affect accounting
depending on how accounting is performed for this node.
   Do u have  multiple network adapters on the same subnet....?

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Large, M (Matthew)
Sent: Wednesday, September 07, 2005 12:58 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Node attribute change


Hi SMers,

I picked up this message last night after a scheduled event failed, but
I was not expecting to read what I read: 06-09-2005 17:43:33 ANR1639I
Attributes changed for node CHEETAH: TCP Address from 172.17.40.228 to
172.17.44.56. (SESSION: 3310) 
06-09-2005 17:43:42 ANR0403I Session 3310 ended for node CHEETAH
(AIX).(SESSION: 3310)
07-09-2005 01:01:12 ANR2716E Schedule prompter was not able to contact
client CHEETAH using type 1 (172.17.40.228 1501). (SESSION: 623)

It would make sense if TSM had attempted to contact the client with the
new TCP address, but it tried on the old TCP address. My question is,
why?

Many Thanks,
Matthew

TSM Consultant
ADMIN ITI
Rabobank International
1 Queenhithe, London
EC4V 3RL


_____________________________________________________________

This email (including any attachments to it) is confidential, legally
privileged, subject to copyright and is sent for the personal attention
of the intended recipient only. If you have received this email in
error, please advise us immediately and delete it. You are notified that
disclosing, copying, distributing or taking any action in reliance on
the contents of this information is strictly prohibited. Although we
have taken reasonable precautions to ensure no viruses are present in
this email, we cannot accept responsibility for any loss or damage
arising from the viruses in this email or attachments. We exclude any
liability for the content of this email, or for the consequences of any
actions taken on the basis of the information provided in this email or
its attachments, unless that information is subsequently confirmed in
writing. If this email contains an offer, that should be considered as
an invitation to treat.
_____________________________________________________________
_____________________________________________________________

This email (including any attachments to it) is confidential, legally
privileged, subject to copyright and is sent for the personal attention
of the intended recipient only. If you have received this email in
error, please advise us immediately and delete it. You are notified that
disclosing, copying, distributing or taking any action in reliance on
the contents of this information is strictly prohibited. Although we
have taken reasonable precautions to ensure no viruses are present in
this email, we cannot accept responsibility for any loss or damage
arising from the viruses in this email or attachments. We exclude any
liability for the content of this email, or for the consequences of any
actions taken on the basis of the information provided in this email or
its attachments, unless that information is subsequently confirmed in
writing. If this email contains an offer, that should be considered as
an invitation to treat.
_____________________________________________________________
_____________________________________________________________

This email (including any attachments to it) is confidential, legally 
privileged, subject to copyright and is sent for the personal attention of the 
intended recipient only. If you have received this email in error, please 
advise us immediately and delete it. You are notified that disclosing, copying, 
distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. Although we have taken reasonable 
precautions to ensure no viruses are present in this email, we cannot accept 
responsibility for any loss or damage arising from the viruses in this email or 
attachments. We exclude any liability for the content of this email, or for the 
consequences of any actions taken on the basis of the information provided in 
this email or its attachments, unless that information is subsequently 
confirmed in writing. If this email contains an offer, that should be 
considered as an invitation to treat.
_____________________________________________________________

<Prev in Thread] Current Thread [Next in Thread>