Clearing TSM reverse DNS cache

[joshmo]

Here is the situation: (server name changed and IP obscured)

I registered a new node in TSM called alpha ran a test backup from the GUI no problem.
The scheduled backup for that night failed with the following error:

ANR2716E Schedule prompter was not able to contact client
alpha using type 1 (beta ****** 1685).
(SESSION: 123)

So it turns out that there was an incorrect reverse dns entry for an old server beta the used to be on the same ip address as the new server alpha

I've corrected the DNS issue now and forward and reverse DNS works correctly, both resolve to the new server alpha and i've run ipconfig /flushdns on the TSM server.

So somewhere in TSM it is caching the incorrect details and I don't see to be able to update or change it.

I've tried running another manual backup from the GUI to see if that fixes it but no.

Is this stored somewhere in the nodes table? Can I get access to change it? Any suggestions welcome.

Thanks

Richard.

 

[gyuzik]

Issue a 'query node alpha' on the TSM server.
Check to see if the TCP/IP Address is correct.

If you need to change it... update node alpha LHAddress=x.x.x.x

You could also add TCPCLIENTAddress x.x.x.x to dsm.opt file on the server, then update the client scheduler.

 

[joshmo]

Thanks.

I understand I can specify the TCP address within the HLA setting.
Infact the TCP/IP address is correct anyway.

My issues is how does TSM cache the reverse DNS lookup of a node and how can I force this to update?

I've corrected the DNS issue but TSM is still caching the incorrect reverse lookup.