Original question:
We are preparing to perform a rolling upgrade of a cluster from DU
V4.0D with TCR 1.5 to T64 V4.0G with TCR 1.6.
The TCR 1.6 Installation manual states that when returning a member
to it's ASE during a rolling upgrade we should:
1. Run the asemgr utility on an existing ASE member system and add
the upgraded system to the ASE.
2. If the upgraded member's name was removed from the member list in
any ASE service's automatic service (ASP) policy when you deleted the
system from the ASE, use the asemgr utility to stop the ASE service
and add the member back to the ASP policy member list.
The TCR 1.6 Administration manual shows that it is possible to modify
the ASP without interrupting its availability.
My question is...do I really have to stop the ASE service as stated
in the Installation manual when adding the member system into the
service's ASP member list.
======================================================================
I received no responses to this question so I asked Compaq support.
The response was:
The reason the manual says to have the service offline is simply a
precaution to keep the service from failing over to the other (new)
member as soon as you set the ASP. This would be the case for
instance if you set the ASP to favor the other member and always fail
over when the member comes back up, or if you set it to be restricted
to that new member.
The manual instructs you to have the service offline simply to keep
from any nasty surprises.
[=================================
[ Randy Rodgers
[ randy.rodgers_at_ci.ft-wayne.in.us
[ Senior Systems Programmer
[ Allen County/City of Fort Wayne
[ Information Systems
[ (219)427-5727
[=================================
Received on Wed Mar 21 2001 - 13:46:44 NZST