Hi,
I only got one answer from Claude Scarpelli (claude_at_genoscope.cns.fr).
Thanks. Seems it is not as easy as I expect. I will repost the summary
if I could try it later.
Regards,
Raymond
> In a mail dated May 13, Raymond Pang <wmpang_at_se.cuhk.edu.hk> wrote:
> > Hi Managers,
> >
> > We have a 3 members cluster running DU4.0B and TCR1.4A. During the setup
> > phase, one of our subnet had been chosen for the memory channel subnet.
> > This leads to systems within that subnet cannot talk to those members.
> > As we are going to do the rolling upgrade of our system to DU4.0D and
> > TCR1.5 later, is it easy to change it back to use private addressing, like
> > 172.16.xxx.xxx, without affecting the services too much.
> >
> > Thanks in advance.
> >
> > Regards,
> > Raymond
>
>
> We switched addresses on the MC from a *real* address to a RFC1918
> one. We have been unable to do this without clearing all the ASE
> database.
>
> Here are the steps with run (no garranty, though) :
>
> 1) save the ASE config (asemgr -d -v SRV_NAME > /tmp/xxxx)
> 2) save the scripts (if any)
> 3) put all the service online, and group them on one member host
> 4) delete the other(s) member(s)
> 5) delete the member which hold the service
> 6) change your network configuration
> 7) initialize the database (asesetup -f) on each members
> 8) reboot
> 9) run asemgr on the member which held the services
> 10) add members
> 11) add services
>
Received on Thu May 20 1999 - 09:37:30 NZST