ADSM-L

Re: Announce new node IP to Server

2001-04-10 08:42:30
Subject: Re: Announce new node IP to Server
From: "Chibois, Herve" <Chibois_H AT ADMIRAL DOT FR>
Date: Tue, 10 Apr 2001 14:41:07 +0200
Hi Clemens,

Stop/start you scheduler on the client. If it is a RS/6000 client
(and it it), a better solution is to reboot the node.

You can also force the client passwd on the server to force the
client to re-authentificate to its server.

you can also deassociates/reassociates your node from its schedule

rv

> -----Message d'origine-----
> De : Block, Clemens [mailto:block AT RZAG DOT NET]
> Envoyé : mardi 10 avril 2001 14:23
> À : ADSM-L AT VM.MARIST DOT EDU
> Objet : Announce new node IP to Server
> 
> 
> Hi all!
> 
> I have a problem with server prompted schedules.
> 
> We had to modify the IP Address of a client Node (IBM RS6000).
> It works really well for all standard appllikations running on the
> System.
> 
> To make a backup possible I edit the dsm.sys file on the Node and
> replace the old TCPCLIENTAddress with the new one. Depending
> on the new network structure the Hostname of the TCPServeraddress
> also changed and I replaced these option too.
> 
> Test to connect the Server from the client using dsmc work well. I can
> see sessions on the Server with the new IP Address. Backups are
> possible without any problem.
> Even if I execute "dsmc q schedule " I get the right 
> Informations about
> the Server prompted schedule for this node
> 
> Now the Problem:
> If the Server start to initiate a backup session caused by a 
> Server prompted
> schedule I get the connection error:
>   ANR2716E Schedule prompter was not able to contact client MORITZ
>   using type 1 (192.168.66.226 1502)
> The Message is correct, because 192.168.66.226 is the old IP Address.
> 
> So my question is:
> How can I notify the server, that the node has an new IP Address.
> 
> Thanks in advance,
>         Clemens
> 
<Prev in Thread] Current Thread [Next in Thread>