"France, Don (Pace)" wrote:

> SUCCESS... using 3.1.0.7 f2 fixtest package; the added parameters
> (/clusternode:yes and /group:xxx) enable registry replication upon
> fail-over, and it works... haven't tried to force fail-over during
> in-progress schedule, yet.
>
> Notwithstanding reports of difficulty using TSM 3.7; ie, (1) failure to
> restart in-progress schedule if fail-over occurs, and (2) 6-minute delay in
> transferring services during failover, all is okay.  I found a keystroke
> error in "dsmcutil" set up of the group that was failing... the /node:
> incorrectly contained the other group, which (of course) was being handled
> by its own schedule, so even the error message was correct --- just didn't
> include the node name value.
>
> Thanx,

Same happened to us.
As far as I know TSM 3.7 not cluster ready.
Deinstalling TSM 3.7 and installing 3.1.7 f2 fixtest works.


--
Martin Brodt                           E-mail: martin.brodt AT de.bosch DOT com
Martin Brodt                           E-mail: martin.brodt AT de.bosch DOT com
Bosch Telecom                          Fax:    +49 7191133824
QI/LBS3-BK                             Phone:  +49 7191132240